Generation of an Integration Model for Project Orders/Networks

PS networks can be created in SAP R/3 only. To transfer the networks to SAP APO, you have to generate an integration model for the networks, and activate it. You generate an integration model for networks in the same way as described for material-independent objects . In the integration model, you select the filter objects ‘network type’ (that is, order type) and ‘plant’. Networks with the specified ‘network type’ and ‘plant’ belong to the integration model.

We recommend that you create your own network types for use only with networks that should be transferred to SAP APO.

If new network types or plants are created after the integration model has been generated, they are not contained in the integration model. This applies even if the selection conditions in the integration model contain the new network type or plant. To include new network types and plants, you have to generate the integration model again.

The transfer of the same order to different SAP APO target systems is not recommended and a combination of network type and plant should appear only in integration models that have the same target system. If the same network is transferred to several different SAP APO systems and is changed in those systems, the changes from one SAP APO system are updated in SAP R/3, however those changes are not transferred to the other SAP APO systems. This leads to data inconsistencies between the SAP APO systems.

Initial Data Transfer

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 .

If the network type and plant in a network match the combination of network type and plant defined in the integration model, the network is transferred from SAP R/3 to SAP APO. The following data is transferred:

Network header

For more information, see Data Transfer of Network Header .

Activities, activity dates, and activities without capacity requirements

For more information, see Data Transfer of Network Activities .

Relationships

For more information, see Data Transfer of Activity Relationships in Networks .

Component requirements

For more information, see Data Transfer of Network Component Requirements .

Capacity requirements

For more information, see Data Transfer of Network Capacity Requirements

Confirmation – Interruptibility

For more information, see Data Transfer of Confirmations - Interruptibility

Business Add-Ins (BAdIs)

BAdIs in SAP R/3 and SAP APO enable you to control the transfer of the data. For more information, see Enhancements for the Integration of Project Orders/Networks .

Monitoring of the Transferred Data

You can monitor the data that has been transferred to SAP APO. For more information, see Monitoring .

If problems occur during the transfer, you can use core interface (CIF) error handling, where you can trigger retransfer of the networks. For more information, see Transfer to Compare Project Orders/Networks , Refresh Transfer to Update Maintenance Order Data , and CIF Error Handling .