Example: Transferring Planned Data

This example illustrates a typical scenario to explain how plan data is transferred to the backend ERP system and SAP Multiresource Scheduling (MRS).

Note Note

This example uses Customizing settings that are delivered through BC sets.

End of the note.

Suppose a financial plan and plan version that contains plan data and is based on the following settings in Customizing for Start of the navigation path SAP Commercial Project Management Next navigation step Project Cost and Revenue Planning End of the navigation path :

Settings in Define Plan Scenarios

Plan Scenario	Resource Type	Cost Element (Revenue)	Cost Element (Cost)	Version Type	MapCOVersion	Transfer Strategy
`0PSM`	`0ACT`	`841910`	Secondary cost element	`0CURRENT`	`1`	`0TRANS_STRTG_PSP` (Update WBS Cost and Revenue)
`0PSM`	`0MAT`	`841050`	`400010`	`0CURRENT`	`1`	`0TRANS_STRTG_PSP` (Update WBS Cost and Revenue)

Settings in Start of the navigation path Transfer to ERP Next navigation step Make Settings for Transfer Strategies End of the navigation path

Transfer Strategy	Transfer Methods	Input Field 1	Value of Input Field 1	Input Field 2	Value of Input Field 2
`0TRANS_STRTG_PSP` (Update WBS Cost and Revenue)	`0TRANS_METH_COST` `0TRANS_METH_REV` `0TRANS_METH_MRS`	`KEY_FIG_COST`	`/CPD/FPCA`	`QTY`	`/CPD/FQTY`

For a list of the mandatory input fields for MRS, see Transfer of Planned Data.

Note Note

You must ensure that the key figures from which you transfer data must also be the same ones that store the results of valuation data for planned resources or resource types.

End of the note.

Process

Assuming that the plan version contains plan data for a consultant (resource type 0ACT) and for a laptop computer (resource type 0MAT), the application updates the cost and revenue for the WBS, in the following manner:

For the resource type 0ACT, the application transfers planned revenue to cost element 841910 and planned cost to the secondary cost element associated with the activity type.
For the resource type 0MAT, the application transfers planned revenue to cost element 841050 and the planned revenue to cost element 400010.
Both costs and revenues are transferred to controlling version 1 (MapCOVersion).
The system creates a demand request in SAP Multiresource Scheduling (MRS), for a consultant with the planned quantity.

The above transfer strategy uses transfer methods that update the controlling version. If you wish to update Easy Cost Planning, for example, from a forecast version, then you must use appropriate transfer methods that support this transfer. To know about the available transfer methods, see Transfer of Planned Data.