PlanDataTransferCO

The business object PlanDataTransferCO is used to transfer planning
data that (regularly) arises outside Overhead Cost Controlling and which is to included in the planning process of Overhead Cost
Controlling.

Examples include personnel cost planning from an HR system, planned
depreciation from Assets Management, cost planning from production
planning, and other external systems that can for example transfer statistical key figures.

In the R/3 System, you should define each application in an external
system as a separate planning source. Even if Asset Accounting and
Production Planning run in the same external system, you should define two separate planning sources for them.

Structure

Planning data on statistical key figures, activity input, activity output, and primary costs can be transferred.

Integration

The business object CostActivityPlanning is also used to carry out
planning (consistent updating in Overhead Cost Controlling). You should
use the business object PlanDataTransferCO if the external system does
not know the CO planning versions, for example because it is an HR system. However, if the external system has all the information
required (perhaps because it uses user-programmed plan data entry via
Intranet for example) use the business object CostActivityPlanning.

Available Methods

• CheckActivityInput : Plan data transfer: Check activity input [ BAPI_PDTRANSCO_CHECKACTINPUT ]
  
• CheckActivityOutput : Plan data transfer: Check activity planning [ BAPI_PDTRANSCO_CHECKACTOUTPUT ]
  
• CheckKeyFigures : Plan data transfer: Check stat. key figures [ BAPI_PDTRANSCO_CHECKKEYFIGURE ]
  
• CheckPrimaryCosts : Plan data transfer: Check primary costs [ BAPI_PDTRANSCO_CHECKPRIMCOST ]
  
• GetSourceInfos : Information about settings for plan data source [ BAPI_PDTRANSCO_GETSOURCEINFOS ]
  
• PostActivityInput : Planning data transfer: Post activity inputs [ BAPI_PDTRANSCO_POSTACTINPUT ]
  
• PostActivityOutput : Planning data transfer: Post activity planning [ BAPI_PDTRANSCO_POSTACTOUTPUT ]
  
• PostKeyFigures : Transfer of planning data: Post stat. key figures [ BAPI_PDTRANSCO_POSTKEYFIGURE ]
  
• PostPrimaryCosts : Plan data transfer: Check primary costs [ BAPI_PDTRANSCO_POSTPRIMCOST ]
  

CheckActivityInput

This method checks whether activity inputs can be planned correctly.

Example

ou want to plan activity inputs on cost center 4210 from cost center4220, activity type 110, and from business process 1004210. In each case, 240 hours of activity is to be recorded annually.

To do so, the tables should be filled 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 by the system.

CheckActivityOutput

This method checks whether 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, planning involves cost element 400000 - the cost centers
with $2400 fixed (controlling area currency) and $100 variable, the business 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 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) in HEADERINFO.

The records are then checked as appropriate.

CheckKeyFigures

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 on business process 1004210.

The planning involves cost element 400000 - the cost centers with $2400
fixed (controlling area currency) and $100 variable, the business process 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) in HEADERINFO.

The records are then checked accordingly.

CheckPrimaryCosts

This method checks whether 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 - both cost centers
with $2400 fixed and $100 variable, (controlling area currency), the business process with just $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 were transferred. The system takesthe planned 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 DIST_KEY_XXXX (distribution key) in each case.

TRANS_CURR does not need to be specified here. You only need to set thePLAN_CURRTYPE field in the HEADERINFO to "C" (Controlling area currency).

The system then checks the records accordingly.

GetSourceInfos

This module returns the settings that were entered in the Maintain Planning Sources transaction. Thistransaction is used internally and should only be called up when the information is required.

PostActivityInput

This method checks whether 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.

On each occasion you plan using cost element 400000, - cost centers
with $2400 fixed and $100 variable, (controlling area currency), the business process with just $3000 fixed.

To do so, 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 were transferred. The system takesthe planned 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 in the HEADERINFO to "C" (controlling area currency).

The system then checks the master records accordingly.

PostActivityOutput

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 business process 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", (Controlling area currency).

The system then checks the records accordingly.

PostKeyFigures

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 area currency), 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 area currency).

The records are then checked accordingly.

PostPrimaryCosts

This method checks whether primary costs can be planned correctly. It then updates them.

Example

You want to plan primary costs on cost center 4210, on cost center 4220, activity type 110 and on business process 1004210.

You plan each time using cost element 400000 (the cost centers each
with $2400 fixed and $100 variable, the business process with $3000 fixed (controlling area currency)

The table is filled as follows:

INDEXSTRUCTURE:

OBJECT_INDEX | VALUE_INDEX | ATTRIB_INDEX

1 | 1 | 0

2 | 1 | 0

3 | 2 | 0

The zeros indicate that no values were transferred. Instead, the systemtakes the planned values values or the default value from the master data.

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 (distribution key)

TRANS_CURR does not need to be specified in this case. You only need toset the PLAN_CURRTYPE field in the HEADERINFO to "C" (Controlling area currency).

The records are then checked and updated by the system.