Fonction SAP BAPI_PDTRANSCO_POSTKEYFIGURE - Transfer of Planning Data: Post Stat. Key Figures

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
HEADERINFO BAPIPLNHDRTRANS2 u 54 Header Data

Paramètre Reférence Long. Facultatif Description
COOBJECT BAPISKFOBJ 70 Object List (Cost Center/Activity Type or Business Process)
INDEXSTRUCTURE BAPIACISTRU 12 Assignment of Objects, Values and Control Data
PERVALUE BAPISKFVAL 330 X Plan Values Per Period
RETURN BAPIRET2 548 Error Messages
TOTVALUE BAPISKFTOT 98 X Plan Values Per Fiscal Year and Distribution Key

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 areacurrency), 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 fieldPLAN_CURRTYPE has to be set to "C" in HEADERINFO (controlling areacurrency).
The records are then checked accordingly.

Description
The Header_Info structure contains the following fields:

  • CO_AREA - Controlling area

  • FISC_YEAR - Fiscal year

  • PERIOD_FROM - First period for which values are transferred

  • PERIOD_TO - Last period for which values are transferred

  • PLAN_CURRTYPE - Are the prices planned in group, object,

    • or transaction currency?
    • PLANTYPE - What type of source supplies the data?

    • OBJ_SYS - Logical system of the data source

    • OBJ_KEY - Reference key of the data source

      • Value range

      • PERIOD_FROM, PERIOD_TO - The following must hold:

        • 1 <= PERIOD_FROM <= PERIOD_TO <= Number of actual posting periods
        • PLAN_CURRTYPE - The following values are allowed:

          • C - Planning in controlling area currency
          O - Planning in object currency
          T - Planning in transaction currency

          Description

          • OBJECT_INDEX - Index that uniquely identifies the row, and thereby

            • the object. The index must be greater than zero and
            may not appear in the table more than once.
            If the index does not occur in INDEXSTRUCTURE,
            the row is ignored.
            • COSTCENTER - Cost center to be planned.

            • ACTTYPE - Activity type; can only be filled

              • together with COSTCENTER.
              • CO_BUSPROC - Business process to be planned.

              • ORDERID - Order to be planned.

              • WBS_ELEMENT - WBS element to be planned.

                • Only one object may be filled! COSTCENTER, CO_BUSPROC, ORDERID orWBS_ELEMENT.

                Description
                The table IDX_STRUCTURE assigns the contents of the individual tablesto each other; each row must contain an object that is stored in fieldOBJECT_INDEX.
                In addition, either a row with periodic values from table PER_VALUE, orwith annual values from table TOT_VALUE can be transferred, togetherwith a row containing control data.
                The field VALUE_INDEX refers to the values and the field ATTRIB_INDEXrefers to the control data.
                If one of these two is not transferred, the field should be reset tozero.

                Value range
                The field OBJECT_INDEX must only contain values that are stored in thefield OBJECT_INDEX of the transfer table OBJECT.
                The field VALUE_INDEX may only contain values that are either stored intransfer table PER_VALUE or in field VALUE_INDEX of TOT_VALUE.
                The field ATTRIB_INDEX must only contain values that are stored in thefield ATTRIB_INDEX of the transfer table.

                Description
                This module contains the values that are to be updated, namely:

                • VALUE_INDEX - A unique key of the row referenced from the

                  • INDEXSTRUCTURE table.
                  The row is ignored if the index
                  does not appear in the INDEXSTRUCTURE.
                  • COST_ELEM - Cost element

                  • RESOURCE - Resource

                  • TRANS_CURRENCY_ISO - ISO code of the transaction currency

                  • TRANS_CURR - Transaction currency

                  • UNIT_ISO - ISO code of the unit of measure

                  • QUANTITY_UNIT - Unit of measure

                  • FIX_VAL_PER01-16 - Fixed values for periods 1-16

                  • VAR_VAL_PER01-16 - Variable values for periods 1-16

                  • FIX_QUAN_PER01-16 - Fixed quantities for periods 1-16

                  • VAR_QUAN_PER01-16 - Variable quantities for periods 1-16

                    • The quantity fields are only taken into consideration when a unit ofmeasure is entered.

                    Description
                    Return table, containing any error messages that may have occurred.

                    Description
                    This module contains the values that are to be updated, namely:

                    • VALUE_INDEX - A unique key of the row referenced

                      • in the INDEXSTRUCTURE table
                      If the index is not contained
                      in the INDEXSTRUCTURE, the row is ignored
                      • COST_ELEM - The cost element to be planned

                      • RESOURCE - The resource to be planned

                      • TRANS_CURRENCY_ISO - ISO code of the transaction currency

                      • TRANS_CURR - Transaction currency

                      • UNIT_ISO - ISO code of the unit of
                        • measure
                        • QUANTITY_UNIT - Unit of measure

                        • FIX_VALUE - Fixed value

                        • DIST_KEY_FIX_VAL - Dist. key for fixed value. Required field

                        • VAR_VALUE - Variable value

                        • DIST_KEY_VAR_VAL - Dist. key for variable value. Required field

                        • FIX_QUAN - Fixed quantity

                        • DIST_KEY_FIX_QUAN - Dist. key for fixed quantity. Required field

                        • VAR_QUAN - Variable quantity

                        • DIST_KEY_VAR_QUAN - Dist. key for variable quantity. Required field

                          • The quantity fields are only taken into consideration when a unit ofmeasure is specified.