Ansicht
Dokumentation
BAPI_PDTRANSCO_POSTACTOUTPUT - Planning Data Transfer: Post Activity Planning
BAL Application Log Documentation SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis 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 on cost center 4210, on cost center 4220, activity type 110, and on business process 1004210.
In each case, planning is to be carried out with cost element 400000: cost centers with USD 2400 fixed and USD 100 variable (controlling area currency), the business process with USD 3000 fixed.
You can fill the tables as follows:
INDEXSTRUCTURE:
OBJECT_INDEX | VALUE_INDEX | ATTRIB_INDEX |
---|---|---|
1 | 1 | 0 |
2 | 1 | 0 |
3 | 2 | 0 |
The zeroes 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 relevant DIST_KEY_XXXX
TRANS_CURR does not need to be specified in this case. You only need to set the PLAN_CURRTYPE field in the HEADERINFO to "C" (controlling area currency).
The system then checks the records accordingly.
Notes
Parameters
CONTRLCOOBJECT
HEADERINFO
INDEXSTRUCTURE
PERVALUE
PRICE_QUANT_PLAN
RETURN
TOTVALUE
Exceptions
Function Group
6031RFUMSV00 - Advance Return for Tax on Sales/Purchases ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4248 Date: 20240523 Time: 153312 sap01-206 ( 32 ms )