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 4220,activity type 110, and business process 1004210.
In each case, you plan using cost element 400000, - cost centers with$2400 fixed (controlling area currency) and $100 variable, the businessprocess with only $3000 fixed.
You 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 are transferred. The system takes theplanned values or the default values from the master data instead.
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 toset the PLAN_CURRTYPE field in the header info to "C", (Controllingarea currency).
The system then checks the records accordingly.

Description
The Header_Info structure contains the following fields:

• CO_AREA - Controlling area


• FISC_YEAR - Fiscal year


• PERIOD_FROM - First period for which the values are transferred


• PERIOD_TO - Last period for which the values are transferred


• PLAN_CURRTYPE - Are the prices planned in controlling area

currency, object currency, 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 acceptable:

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

Description
Transfers the control data.
These are:


• ATTRIB_INDEX - A unique key of the rows referred to in the

INDEXSTRUCTURE table.

• RECORD_QUANTITY - Defines whether or not actual

quantities are to be recorded.

• CELEM_ATTRIBUTE - Cost element attributes.

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
Table IDX_STRUCTURE assigns the contents of the individual tables toone another. Each row must contain an object that is stored in fieldOBJECT_INDEX.
Besides this, either a a row with periodic values from table PER_VALUE,or with 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 inthe transfer table PER_VALUE or in field VALUE_INDEX of TOT_VALUE.
The field ATTRIB_INDEX can only contain values that are stored in fieldATTRIB_INDEX of the transfer table CONTRL.

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


• VALUE_INDEX - A unique key for the row that is

referenced in the INDEXSTRUCTURE table.
If the index does not crop up in
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 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

Quantity fields are only taken into account when a unit of measure isspecified.

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 for the row that is

referred to in the INDEXSTRUCTURE table.
If the index does not appear in
INDEXSTRUCTURE, the row is ignored.

• COST_ELEM - The cost element requiring planning


• RESOURCE - The resource requiring planning


• 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 value


• DIST_KEY_FIX_QUAN - Dist. key for fixed value. 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 entered.