Data Transfer of Network Capacity Requirements
Caution
The following is also mainly valid for change transfer, transfer for comparison purposes, and refresh transfer. Where differences arise, these are documented in Change Transfer and Deletion for Project Orders/Networks , Transfer to Compare Project Orders/Networks , and Refresh Transfer to Update Project Order/Network Data .
Capacity requirement in the work center in SAP R/3 is mapped to the resource in SAP APO.
The capacity requirement for SAP APO is calculated as the ratio of remaining work divided by remaining duration of the activity. The capacity requirement is distributed over the whole duration of the activity, which means there is no float for the work.
Capacity requirements determined in SAP R/3 are transferred to a multi-resource or a single resource. Capacity requirements for a single resource are set to one, meaning that the duration of the activity corresponds to the remaining work (there is no float for the work). For example, if work takes 4 hours for an activity with an 8 hour duration, the single resource is occupied for the full 8 hours. However, you can implement a Business Add-In using your own logic. For more information, see Enhancements for the Integration of Project Orders/Networks .
When calculating the remaining capacity requirement, the remaining work is reduced by the factor of the daily working time of the resource divided by the duration of a day, if the remaining work is maintained with a unit equal to or larger than a ‘day’.
Example
One week duration on a resource with a daily working time of 12 hours is transferred as 12 / 24 x 7 x 24 = 84 hours duration, even if in SAP R/3 one week = five working days.
Note
Capacity requirements are deleted if the corresponding activity is technically completed. The capacity requirements are then no longer transferred to SAP APO , and the reference to the activity and the resource is lost.
For an activity, the capacity requirements that belong to the activity on the database in SAP R/3 are transferred. These might be different to the capacity requirements that are shown on the interface. For example, work center A is entered, scheduled, and saved. Later, work center B is entered and saved, but not scheduled. However, work center A is the work center that is contained in the database.
To ensure that the change to the work center is noted in the database, you have to set the capacity requirement indicator on the network header and you have to schedule the network before saving it. To automatically schedule the network whenever it is saved, you can set the automatic scheduling indicator on the network header.
The following data is not transferred:
Capacity requirements for resources that are not contained in an active integration model
Capacity requirements for which the corresponding network should be scheduled in SAP R/3 as defined by an implementation in the method
CHANGE_NETWORK_DATA
in Business Add-In (BAdI)BADI_CIF_PS_NETWORK
, and in methodCHANGE_NETWORK_INBOUND
in BAdICIF_PS_NETW_IN
. For more information, see Enhancements for the Integration of Project Orders/Networks .Capacity splits
Capacity requirements with a requirement of zero, unless the corresponding activity has been finally confirmed, in which case the capacity requirement is transferred as 1. However, because the remaining activity duration is zero, this does not load the capacity requirement. This ensures that the resource is not lost in the activity in SAP APO.