In clearing entries with orders without partner update, you cannot determine the origin of a posting in the cost center report. As of Release 3.0, you can identify the origin of a posting at the object type level. For this reason, a new report (1SHK-002 - Cost Centers: Actual/Plan Partner Object) is included in report group 1SHK which represents these cost allocations.
The main difference to report 1SHK-001 - Cost Centers: Actual/Planned With Partner - is that the report selects via field PAROB - Partner object and not via field PAFNR - Partner order, as was the case. As a result, you can select all partner objects of a cost center. Therefore, the report shows the primary costs in the first row block and the cost allocations with other cost element itemizations per cost element in the second row block.
Please note that the new report in report group 1SHK was set to the first position, that is, it is displayed first during the report call-up.
Field PAROB is supplied separately due to a central function module change in Release 3.0. As a result, new totals records are created in table COSS. The old posting records remain unchanged and are still processed in reporting.
To reduce the number of posting records, use program RKACUM26, which converts all old postings to the new logic and groups together all old COSS totals records with the new data records. The "Test run" parameter does not start an update. The changed object numbers are logged upon request.
As an example for a report which represents the business partner relations via field PAROB, you can import report group 1SKL into the customer client.
For more information on program RKACUM26, please refer to the program documentation.
We recommend starting program RKACUM26 for the following reasons: