Posting Run Creation 
Posting Run Creation
Use
The information stored in the Travel Management settlement results has to be formatted for further processing in Accounting. You can specify how the system is to summarize the data for Accounting. The system collects the formatted information in
trip transfer documents and collects these in posting runs. Travel Management transfers these posting runs to Accounting.Creation of a posting run starts the formatting of the data and thus the business process of transferring the settlement results to Accounting.
Integration
Creation of a posting run does not yet mean actual technical transfer of settlement results to Accounting. You start the technical transfer of posting runs with the
Post posting run function.Features
Simulation
When you create a posting run, you can decide whether the system should consider the posting run a real posting run or a simulation. In both cases, the system creates a posting run, but it assigns a different status.
The following table shows you the basic differences between the two options.
Create Posting Run |
Create Posting Run as Simulation |
The system locks all trips for which settlement 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 settlement results are included in the posting run. |
The system does not set a new trip status. |
You can check the posting runs. |
You can check the posting runs. |
You can post the posting runs. The system transfers the data to Accounting. |
You can not post simulated posting runs. |
Automatic replacement of incorrect account assignment objects
During setup of trip transfer documents, the system already checks in R/3 Controlling to see if the specified account assignment objects for the selected trips can be posted to.
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 R/3 Controlling and that documents all replacements in the trip transfer document. If the system can not find valid information in the master cost center or 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:
Create Posting Run Posting Run Management