Topic 56: Posting to Finance Accounting

[freesaphr]

Authorizations and profiles

Special authorizations are required for posting to Accounting. You have the option of assigning different authorizations for the different activities within posting to Accounting.
Authorization Objects

The system checks the following HR authorization objects during posting to Accounting:

• HR: Posting run (technical name: P_PYEVRUN)

• HR: Posting document (technical name: P_PYEVDOC)

Note
This is not a complete list of authorization objects that the system checks for posting to Accounting. In certain system constellations, for example, additional authorizations are needed for the Application Link Enabling (ALE) to be able to perform posting to Accounting. For more information about ALE authorizations refer to the Basis Customizing under Application Link Enabling (ALE) -> Sending and Receiving Systems -> Assign Required Authorizations.


Authorizations for Posting Runs
You maintain these authorizations based on the run type and simulation mode.

Activity	Authorization	Step
Insert or	01	Create Posting Run
Display
Display	03	Display Posting Runs
Delete run	06	Delete Posting Run
Post run	10	Post Posting Run
Reverse run	85	Reserve Posting Run and
		Reset Reversal after
		Termination

Authorizations for posting documents
These authorizations are dependent on the company code.

Activity	Authorization	Steps
Display	03	Display Payroll Documents
		and Display Accounting
		Documents
Post	10	Post Run and Reverse
		Posting Run
Line items	28	Analyse Formation of
		Posting Documents
Release	43	Release Posting Documents

This is done by BASIS Team

[freesaphr]

Now we need to create G/L Accounts which we do at Production system.

And before to create GL we we need to Move the Configuration to Quality and then to Production.

Because at the time of G/L creation we need to assign the G/L accounts to Company Code.

Company Code only presents once you move to Production.

[freesaphr]

T-Code : SE10

[freesaphr]

[freesaphr]

Select Customizing Requests

Use

Changes to Customizing settings are recorded in Customizing requests.
When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.


The client settings determine whether

• changes to the Customizing settings are possible

• the changes are recorded

When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.



Select Workbench Requests

Definition

Workbench requests record changes made to ABAP Workbench objects.
There are local and transportable Workbench requests. (Local Workbench requests have the target system .)


The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.


Select Transport of Copies
Definition

Transports of copies allow you to transport (sub-)objects in an object list into any other SAP System you want.
In contrast to Workbench or Customizing requests there is no automatic delivery into other systems for transport of copies.



Select Relocations

There are three types of relocations:

• Relocations without package change

• Relocations with package change

• Relocations of complete packages