SAP Program RPTPDOC0 - Transfer Additional Data for Activity Allocation to Accounting

Description
Report RPTPDOC0 posts activity allocation documents inControlling.

Status information
The current status of new and incorrect time infotype records withadditional activity allocation data (additional time data) and theresulting activity allocation documents (posting documents) to beposted for a user in Controlling is displayed.
You can choose Additional time data and Posting documentsto display the relevant data as an interactive list. Error texts arealso displayed for incorrect additional time data. You can double clickto go to the infotype records or error long texts. This considerablysimplifies error handling.
If there are incorrect posting documents, the error should be correctedin Controlling and the posting of the document triggered again. To dothis, you can use the functions for checking (Check document)and reposting documents (Post documents) on the overview listfor the posting documents.
To check a document, you must select the relevant line. All selecteddocuments are posted.

Selection conditions
The report reads data from table COIFT, filters and summarizes thedata, and generates posting documents. You can specify conditions forthe personnel number, Valid from date, Infotype,and Status on the selection screen.
You can use the Last retrieved by, Last retrieved on, andLast retrieved at parameters to specify additional restrictionsfor data records assigned the status incorrect.
The documents are validated again before they are posted. If there areerrors, the relevant errors remain in table COIFT with the statusincorrect. Error-free records are assigned the statusretrieved successfully. The data is flagged with the date andtime of retrieval, and the name of the person who retrieved it.

Other data
In the Posting date field, you enter the posting date with whichyou want the data to be posted in Controlling.
If Transfer personnel number is selected, the personnel numberis also transferred for activity allocation.
If the personnel number is not transferred, the number of postings inCO can be reduced considerably. The activity consumption of identicalrecords is totalled for several personnel numbers, and only the totalis posted.
The Detailed log and Test run options are intended fortesting purposes. No table entries are changed or documents posted ifyou carry out a test run. The detailed log shows all data recordsprocessed.

Precondition
The interval 01 has been created for the number range object 'HRposting documents' using transaction PT12.
The data in table COIFT is entered in Time Management (Humanresources->Time management->Administration, Timedata->Maintain) together with employee working time data.

Output
The number of correct posting records is displayed at the end of thereport. The number of incomplete or incorrect posting records (if thereare any) is also displayed.

Technical-info
Additional time data is imported from table COIFT. The data is filteredand summarized to generate activity allocation documents which areposted in Controlling. These documents are stored as original documentsin tables HRAAHDR and HRAAITM and can be displayed when auditing.
The data is checked and posted using the function modulesK_ACT_ALLOC_DOC_CHECK and K_ACT_ALLOC_DOC_POST.

Further_hints
The Enterprise IMG contains a section that describes in detail how toSet Up Activity Allocation.

Error Handling
Although all entries are validated when activity allocation data isentered, errors sometimes still occur when the documents are posted dueto changes made to the Controlling objecst.
If there is incorrect additional time data, the relevant records remainin table COIFT with the status incorrect. You can display a listof the incorrect records by choosing additional time data. Bydouble clicking, you can go from the list straight to the relevantinfotype records.
If technical errors occur when the generated documents are posted, theposting documents remain in table HRAAHDR or HRAAITM. You can choosePosting documents to display a list of the documents still to beposted. You can repost and check the documents from the list.

860798Expensive SQL statements in transaction PT68 (DB2/390)