Data Transfer of Network Component 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 .
Component requirements in special stock are transferred only if the special stock type is sales order stock or project stock.
If a component requirement belongs to a sales order, the requirement appears in SAP APO in the sales order stock.
If a component requirement belongs to project stock that is assigned to a WBS element, the requirement appears in SAP APO in the project stock for this WBS element.
For requirements grouping, if a component requirement belongs to project stock that is assigned to a WBS element and is grouped under a grouping WBS element, the requirement appears in SAP APO in the project stock of the grouping WBS element. Any additional grouping features of projects in SAP ERP are not supported. In SAP APO, the MRP run especially does not use any grouping information, such as assignment of materials to different grouping WBS elements by MRP group.
The confirmed quantity in SAP APO is equal to the confirmed quantity in SAP ERP minus the withdrawal quantity in SAP ERP, because in SAP APO the confirmed quantity always refers to the requirement quantity that is still open, whereas in SAP ERP the confirmed quantity always refers to the requirement quantity.
Recommendation
Manually entered requirement dates in SAP ERP are converted to an offset range between the activity start and the requirement date, and then transferred. This can lead to a different requirement date in SAP APO. Therefore, we recommend that you align requirement dates to the start or the end of an activity and use the offset 0, because ranges between the requirements date and the activity start and end are not scheduled in a calendar.
In SAP APO, component requirement quantities are displayed as negative quantities. The displayed requirements quantity is copied from the open quantity in SAP ERP.
The missing parts indicator from SAP ERP is transferred to the status of the ATP components in SAP APO.
In SAP APO, Characteristics-Dependent Planning (CDP) and iBase configuration information is processed.
Fixed pegging is supported by the integration, therefore existing fixed pegging relationships are retained where possible.
The following data is not transferred:
Component requirements for materials that are not contained in an active integration model
Component requirements with non-stock items (direct procurement)
Bulk materials and text items
Component requirements for which a preliminary purchase requisition has been generated for a WBS element
Component requirements that generate a planned independent requirement
Component requirements that are not planning-relevant
Component requirements that have a substitution component as a result of discontinuation in SAP ERP