Functionality This method checks whether the primary costs can be planned correctly. Example You want to plan primary costs on cost center 4210, cost center 4220activity type 110, and on business process 1004210. The planning involves cost element 400000 - the cost centers with $2400fixed (controlling area currency) and $100 variable, the businessprocess with only $3000 fixed. To do this, you can fill the tables as follows: INDEXSTRUCTURE:> OBJECT_INDEX | VALUE_INDEX | ATTRIB_INDEX> 1 | 1 | 0> 2 | 1 | 0> 3 | 2 | 0> A zero indicates that no value was transferred. In such cases theplanned 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 explicitly in this case. Youjust set the field PLAN_CURRTYPE to "C" (controlling area currency) inHEADERINFO. 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 controlling area,
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 applies:
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 currencyDescription
- 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 one another. An object must be used in each row that is stored inthe OBJECT_INDEX field. In addition, either a row with periodic values from table PER_VALUE, orwith annual values from table TOT_VALUE and a row with control data canbe transferred. The field VALUE_INDEX references the values and the field ATTRIB_INDEXreferences the control data. You should set the field to zero if one of the two happens not to betransferred. Value range The field OBJECT_INDEX can only contain values that are stored in theOBJECT transfer table in the OBJECT_INDEX field. The VALUE_INDEX field is only allowed to contain values that are storedin the transfer table PER_VALUE or in the field VALUE_INDEX ofTOT_VALUE. The ATTRIB_INDEX can only contain values that are stored in thetransfer table CONTRL in the field ATTRIB_INDEX. Description This function module contains the values to be updated, namely:
- VALUE_INDEX - A unique key of the row which is referenced
in the INDEXSTRUCTURE table. If the index does not occur in the INDEXSTRUCTURE the row is ignored.
- 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 if you specifieda unit of measure.Description Return table, containing any error messages that may have occurred. Description This module contains the values that are checked as to whether they canbe updated, namely:
- VALUE_INDEX - A unique key for the row to which reference is
made in the table INDEXSTRUCTURE. The row is ignored if the index is not contained in the INDEXSTRUCTURE.
- 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 values
- 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 account when a unit of measureis entered.
|