Functionality
This method checks whether primary costs can be planned correctly.

Example
You want to plan primary costs on cost center 4210, cost center 4220activity type 110, and business process 1004210.
In each case, planning involves cost element 400000 - the cost centerswith $2400 fixed (controlling area currency) and $100 variable, thebusiness process with just $3000 fixed.
The table can be filled 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 values or default values are transferred from the masterrecord.
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 as appropriate.

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

currrency, object currency, or transaction currency?

• PLANTYPE - What type of source provides 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
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
must 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. An object from the field OBJECT_INDEX has to be used ineach row.
In addition to this, a row with periodic values from table PER_VALUE orannual values from table TOT_VALUE and a row with control data istransferred. The field VALUE_INDEX references the values and the fieldATTRIB_INDEX references the control data.
Set the field to zero if one of them is not transferred.

Value range
The field OBJECT_INDEX can only contain values stored in the fieldOBJECT_INDEX of transfer table OBJECT.
The field VALUE_INDEX can only contain values that are stored in thetransfer table PER_VALUE or TOT_VALUE in field VALUE_INDEX.
The field ATTRIB_INDEX can only contain values that are stored in thetransfer table CONTRL in field ATTRIB_INDEX.

Description
This module contains the values that are checked as to whether they canbe updated, namely:


• VALUE_INDEX - A unique key for the rows that are

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

Quantity fields are only taken into account when units of measure areentered.

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 that is

referenced in the table INDEXSTRUCTURE.
If the index does not appear in
INDEXSTRUCTURE the rows are 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 the fixed value. Required field


• VAR_VALUE - Variable value


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


• FIX_QUAN - Fixed quantity


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


• VAR_QUAN - Variable Menge


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

The quantity fields are only taken into consideration when units ofmeasure are specified.