Transfer of Planned Data
By allowing transfer of planned data such as quantities, cost, or revenue to business objects in backend systems (for example, SAP ERP and SAP Multiresource Scheduling
(MRS
)), Project Cost and Revenue Planning
provides an end-to-end integration that allows users to view unified and consistent information in downstream processes.
Caution
If you use Project Cost and Revenue Planning
as the front-end application for financial planning, do not post manual entries directly to Easy Cost Planning
. During the transfer process from Project Cost and Revenue Planning
to ECP, the system deletes existing data for corresponding business objects and overwrites them with data from Project Cost and Revenue Planning
.
Business objects to which you want to transfer data must have valid start and end dates.
The following Customizing settings for SAP Commercial Project Management
under are required:
Make Settings for Transfer Methods
Make Settings for Transfer Strategies
Optionally, you can use your own implementation of BAdI: Transfer of Project Financials to ERP
to determine dependent business objects and use the appropriate transfer scenario. You can also use this BAdI to override values for input parameters in transfer methods.
The following scenarios are available for transfer of planned data:
Network Activities
Note
You can update only internal and external network activities.
Manually created material components in PS (transaction CJ20N), are not updated during transfer. When you transfer costs or quantities for a material resource type, the system automatically creates corresponding material components in the network activity.
Update only the quantity in a network activity.
In such a case, the system transfers quantities for a combination of multiple materials and only one other resource type.
For internal network activities, the system updates quantities in the Work field; whereas for external network activities, the system updates quantities in the Activity qty field.
Update Easy Cost Planning
with only the cost for a network activity.
In such a case, the system transfers costs for any combination of resource types. Note that if you choose to transfer costs per period, the posting date is always the first date of the respective period.
Update Easy Cost Planning
with quantities and costs for a network activity.
In such a case, the system transfers the costs for any combination of materials and resource types, and transfers the quantities for all materials. However, you can transfer the quantity only for one resource or resource type (other than the material resource type).
WBS Elements
Directly update cost and revenue in work breakdown structure elements (WBSe) using transaction CJR2.
For activity resource types, the costs are determined based on activity-specific rates maintained in transaction KP26. Note that for activity types, manually-entered plan rates or costs are not transferred to Controlling
.
Directly update Easy Cost Planning
with cost and revenue for work breakdown structure elements (WBSe).
Note that if you choose to transfer costs or revenue per period, the posting date is always the first date of the respective period.
In SAP ERP, revenue is planned at high-level WBSs that are billing relevant. However, in SAP Commercial Project Management
, you can plan revenue based on costs, that are in turn, based on a margin percentage. You can do this at the structure element and resource levels. You can then can transfer the data to SAP ERP. During transfer, SAP Commercial Project Management
aggregates the revenue planned from lower level elements or resources, and transfers it to billing-relevant higher-level WBSs in SAP ERP.
cProjects
Update cost and revenue in WBS elements assigned to phases or tasks in cProjects.
Note that you can plan for resources for a phase or task in a cProject and transfer the demand request to MRS. However, it is not possible to retrieve staffed information from MRS into cProject.
SAP Multiresource Scheduling (MRS)
Transfer staffed quantity to MRS, create demand requests in MRS, and update the request number in the planning sheet.
Note that the system creates one demand request for resources planned in a structure element.
In the Customizing activity Make Settings for Transfer Methods
, you do the following:
Use classes to define transfer methods to transfer quantity, cost, or revenue to a business object.
For each transfer method, you assign values for each of the parameters in the transfer method.
Specify the status (of plan versions) for which the system processes a transfer method.
The following transfer methods are available:
Name | Transfer Method | Description | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
WBS Cost Update |
| This transfer method updates the cost in the plan currency, to a cost element of a WBS element. | ||||||||||||||||||||||||||||||||||||||||||||||||
NWA Material Creation |
| This transfer method creates a material component in a network activity and updates the quantity planned for the material. This method defaults the procurement type based on the following conditions:
| ||||||||||||||||||||||||||||||||||||||||||||||||
Transfer Method for MRS |
| This transfer method updates the quantity for a resource in | ||||||||||||||||||||||||||||||||||||||||||||||||
NWA Cost Update |
| This transfer method updates the cost in plan currency, to a cost element of a network activity. This transfer method also updates | ||||||||||||||||||||||||||||||||||||||||||||||||
NWA Quantity Update |
| This transfer method updates the planned quantity for a resource to a network activity. | ||||||||||||||||||||||||||||||||||||||||||||||||
WBS Revenue Update |
| This transfer method updates the revenue in the plan currency, to a cost element of a WBS element. | ||||||||||||||||||||||||||||||||||||||||||||||||
NWA EAC Cost via ECP |
| This transfer method updates | ||||||||||||||||||||||||||||||||||||||||||||||||
WBS EAC Cost via ECP |
| This transfer method updates | ||||||||||||||||||||||||||||||||||||||||||||||||
Aggregated WBS Cost & Revenue via ECP |
| This transfer method updates | ||||||||||||||||||||||||||||||||||||||||||||||||
Periodic WBS Cost & Revenue via ECP |
| This transfer method updates | ||||||||||||||||||||||||||||||||||||||||||||||||
NWA Cost via ECP (Periodic) |
| This transfer method updates | ||||||||||||||||||||||||||||||||||||||||||||||||
SKF Transfer for Network |
| This transfer method updates the statistical key figure (SKF) in a network, with the planned output quantity. | ||||||||||||||||||||||||||||||||||||||||||||||||
SKF Transfer for WBS |
| This transfer method updates the SKF in a WBS, with the planned output quantity. | ||||||||||||||||||||||||||||||||||||||||||||||||
SKF ETC Transfer for Network |
| This transfer method updates the SKF for a network, with the ETC output quantity. | ||||||||||||||||||||||||||||||||||||||||||||||||
SKF ETC Transfer for WBS |
| This transfer method updates the SKF for a WBS, with the ETC output quantity. |
In the Customizing activity Make Settings for Transfer Strategies
, you create a transfer strategy and do the following:
Assign transfer methods that provide relevant information to transfer
Choose the characteristics whose values must be transferred
By assigning transfer strategies to different version types (in the Customizing activity ), you decide the plan versions that contain the most accurate plan and can be the best source to transfer plan information to objects in ERP.
When you transfer data to a back-end ERP system, you can choose the CO version to which the data is transferred. This is possible in the following ways:
Transfer of data from one plan version type to one CO
version
In the Customizing activity Define Version Types
, you can specify the CO
version to which data from a version type is transferred. With this setting, data from a version type is always transferred to the same CO
version.
Transfer of data from one version to multiple CO
versions
Alternatively, you can use the input parameter VER
in transfer methods, to transfer relevant data into different CO
versions.
When you transfer planned data to ERP, the system transfers cost and revenue to cost elements according to the settings in Customizing for , and in the following order or priority:
Define Resources
Define Default Cost Elements
By default, whenever you initiate transfer of data from Project Cost and Revenue Planning
to a back-end system, the system creates and stores a copy of the data that is transferred. This data is stored in the real-time planning InfoCube /CPD/PFP_R01
.
You can deactivate this default behavior by implementing the Business Add-In method Disable Transfer Versions in Customizing for SAP Commercial Project Management, under .
You can use the Financial Plan Consistency
report (/CPD/PFP_MAINTAIN_CONSISTENCY
) to ensure consistency between structure elements in financial plans and business objects in the backend system. For example, you have planned data for a WBS element in a PS project definition. However, the WBS element is subsequently deleted from the backend system.
Administrators can:
Run this report to ensure consistency of data in the financial plans and business objects
Schedule to run this report as a background job, at regular intervals
Example: Transferring Planned Data uses a sample scenario to explain how data is transferred.