Ansicht
Dokumentation
BAPI_PDTRANSCO_POSTKEYFIGURE - Transfer of Planning Data: Post Stat. Key Figures
Addresses (Business Address Services) CPI1466 during BackupThis documentation is copyright by SAP AG.
Functionality
This method checks whether the primary costs can be planned correctly.
Example
You want to plan primary costs in cost center 4210, cost center 4220, activity type 110, and business process 1004210.
In each case planning, is to be carried out with cost element 400000, cost centers with $2400 fixed and $100 variable (controlling area currency), the business process with $3000 fixed.
To do so, you can fill the tables as follows:
INDEXSTRUCTURE:
OBJECT_INDEX | VALUE_INDEX | ATTRIB_INDEX
1 | 1 | 0
2 | 1 | 0
3 | 2 | 0
The zeros indicate that no values have been transferred. In this case, the planned or default values are transferred from the master record.
COOBJECT:
OBJECT_INDEX|COSTCENTER|ACTTYPE|ORDERID|WBS_ELEMENT|CO_BUSPROC
1 | 4210 | | | |
2 | 4220 | 110 | | |
3 | | | | | 1004210
TOTVALUE:
VALUE_INDEX|COST_ELEM|...|TRANS_CURR|...|FIX_VALUE|...|VAR_VALUE|DK|...
1 | 400000 | | | | 2400 | | 100 | |
2 | 400000 | | | | 3000 | | | |
DK is the respective DIST_KEY_XXXX
TRANS_CURR does not have to be entered in this case, the field PLAN_CURRTYPE has to be set to "C" in HEADERINFO (controlling area currency).
The records are then checked accordingly.
Parameters
COOBJECTHEADERINFO
INDEXSTRUCTURE
PERVALUE
RETURN
TOTVALUE
Exceptions
Function Group
6031SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 2488 Date: 20240523 Time: 183114 sap01-206 ( 28 ms )
