|
Functionality
This method checks whether the activity input records can be plannedcorrectly. Example
In cost center 4210 you want to plan activity inputs from cost center4220, activity type 110, and business process 1004210. In each case,240 hours per year are to be recorded.
You can fill the tables as follows:
INDEXSTRUCTURE:
OBJECT_INDEX | VALUE_INDEX
1 | 1
1 | 2
COOBJECT:
OBJECT_INDEX|COSTCENTER|ACTTYPE|CO_BUSPROC|ORDERID|WBS_ELEMENT
1 | 4210 | | | |
TOTVALUE:
VALUE_INDEX|SEND_CCTR|SEND_ACTIVITY|SENBUSPROC|QUANTITY_FIX...
1 | 4220 | 110 | | 240
2 | | | 1004210 | 240
The records are then checked accordingly. Description
The DELTA indicator indicates whether the function module should addthe values transferred to values that already exist. Value range
X - The value is added.
- The value is not added, but instead overwrites the old value. 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
- VERSION - Version, in which plan data is saved
- DOC_HDR_TX - Document header text; only saved with integrated
planning
- PLAN_CURRTYPE - Is ignored. For internal purposes only.
Value range
- PERIOD_FROM, PERIOD_TO - must be valid :
1 <= PERIOD_FROM <= PERIOD_TO <= Number of true posting periodsDescription
- OBJECT_INDEX - Index, which uniquely identifies the row, and thereby the
object. The index must be greater than zero and may not appear more thanonce in the table. If the index does not appear in the INDEXSTRUCTURE,the system ignores the row.
- COSTCENTER - Cost center receiving the activity
- ACTTYPE - Activity type receiving the activity.
Must be filled together with the COSTCENTER. This is only required foractivity-dependent activity input.
- CO_BUSPROC - Business process receiving the activity.
- ORDERID - Order receiving the activity
- WBS_ELEMENT - WBS Element receiving the activity
Only one object may be filled, namely one COSTCENTER, CO_BUSPROC,ORDERID or WBS_ELEMENT.Description
The IDX_STRUCTURE table assigns the contents of individual tables toone another. One object must be used in each row that exists in theOBJECT_INDEX field. You can also choose to transfer a row withperiodic values from the PER_VALUE table or with fiscal year valuesfrom the TOT_VALUE table and a row with control data.
The VALUE_INDEX field display the values. Value range
The OBJECT_INDEX field may only contain values that are contained inthe OBJECT_INDEX field of the OBJECT transfer table.
The VALUE_INDEX field may only contain values that are contained in theVALUE_INDEX field of either the PER_VALUE or VALUE_INDEX transfertables. Description
Here you transfer the values that refer to the activity relationships onthe senders. These are:
- VALUE_INDEX : A unique key of the row referred to in the
INDEXSTRUCTURE table. If the index does not appear in theINDEXSTRUCTURE, the system ignores the row.
- SEND_CCTR : Sender cost center, must be filled
together with the SEND_ACTIVITY field.
- SEND_ACTIVITY: Sender activity type, must be filled
together with the SEND_CCTR.
- SENBUSPROC : Sender business process. You must
specify either this field or SEND_CCTR/SEND_ACTIVITY.
- ORDER_CELEM : Order settlement cost element. You
must only specify this if you want to execute order planning withsenders.
|