Start of Content Area

 Function documentation Posting Run Creation  Locate the document in its SAP Library structure

Use

The information in the travel expense results of Travel Management needs to be formatted for further processing in Accounting. You can specify how the system is to summarize the data for Accounting. The system records the formatted information in trip transfer documents  and collects these in posting runs. Travel Management transfers these posting runs to Accounting.

When a posting run is created, checks of the data in the target system are made to see whether the accounts to be posted existed. Do the transferred account assignment elements exist, and are they valid? Do vendors exist for the personnel numbers?

If errors occur when the posting run is created, the affected trips are sorted out and their status reset. Only the trips that do not have errors in this first check are included the posting run. They are locked against changes until the posting run is posted or rejected.

Integration

When a posting is created, this does not yet mean that accounting results are transferred to Accounting. You start the technical transfer of posting runs with the Post Posting Run  function.

Features

Simulation

In the selection screen Create Posting Run, you can set the indicator Posting Run as Simulation. A posting run generated in this way does not reset the statuses of the affected trips and can take on any of the above posting run statuses except Documents Posted and Zero Postings Posted. In the posting run management list, simulations are indicated with a black triangle in the column Si. These posting runs can be deleted directly (without having to first be rejected).

The following table explains the basic differences between the two options.

 

Posting Run Creation

Posting Run as Simulation

The system locks all trips for which accounting results are included in the posting run.

You can not change the trips until you have posted or rejected  the posting run.

The system does not lock the trips to prevent changes.

The system sets the trip status transferred FI for all trips for which accounting results are included in the posting run.

The system does not set a new trip status.

You can post the posting runs. The system transfers the data to Accounting.

You cannot post simulated posting runs.

 

Automatic Replacement of Incorrect Account Assignment Objects

During setup of trip transfer documents, the system already checks in SAP Controlling to see if postings can be made to the specified account assignment objects for the selected trips. During posting run creation, you can decide if the system should replace incorrect account assignment objects.

If you have not activated automatic replacement and the system identifies incorrect account assignment objects, it does not include the relevant trips in the posting run and indicates the trips in the log tree as not postable trips.

If you have activated automatic replacement, the system replaces the incorrect account assignment object with the employee’s master cost center or an alternative cost center that must be stored in the table TKA3G in SAP Controlling and that documents all replacements in the trip transfer document. If the system cannot find valid information in the master cost center or in table TKA3G, it omits the relevant trip from the posting run and indicates the trip in the log tree as a not postable trip.

See also:

Creating Posting Runs

Posting Run Management

 

 

 

End of Content Area