In SAP R/3

BADI_CIF_PS_NETWORK

You can implement BAdI BADI_CIF_PS_NETWORK to control the data that is transferred from SAP R/3 to SAP APO. This BAdI enables you to:

Specify networks that should not be transferred to SAP APO, even through they belong to an active integration model (method CHANGE_NETWORK_HEADERS ). This accelerates performance by avoiding the reading of unnecessary network data from the database.

If you filter out networks in this method, you must also filter out the same networks in method CHANGE_NETWORK_DATA , because this method is not processed in the change transfer.

Change network data before it is converted into SAP APO format. For example, you can add user-specific data to the structures used by SAP, specify networks that should be transferred to SAP APO without capacity requirements, because the capacity requirements should be scheduled in SAP R/3 (method CHANGE_NETWORK_DATA ).

Change network data after it has been converted into SAP APO format. For example, you can add user-specific data to the structures used by SAP (method CHANGE_OUTBOUND_DATA ).

The methods in this BAdI are processed as follows:

Method CHANGE_NETWORK_HEADERS

In the initial data transfer, this method is processed after selection of the network headers and deletion of the network headers with statuses ‘deleted’, ‘deletion flag’, ‘technically completed’, and ‘completed’.

In the change transfer, this method is not processed.

In the transfer of network data for comparison purposes, this method is processed after selecting the network headers and deleting the network headers with status ‘deleted’, ‘deletion flag’, ‘technically completed’, and ‘completed’.

In the refresh transfer of network data that is triggered by the update logic, CIF error handling, or the delta report, this method is processed after selection of the network headers.

Method CHANGE_NETWORK_DATA

If capacity requirements planning should take place in SAP R/3 for networks, those networks have to be listed in table CT_AUFNR_SCHED_IN_R3 in this method

The same networks have to be listed in table CT_AUFNR_SCHED_IN_R3 in method CHANGE_NETWORK_INBOUND of BAdI BADI_CIF_PS_NETW_IN ).

In the initial data transfer, this method is processed after reading the SAP R/3 data for the networks to be transferred to SAP APO, but before the data is filtered and converted to SAP APO format.

In the change transfer, this method is processed before the SAP R/3 data is filtered and converted into the SAP APO format.

At this point, the network headers that are not in an active integration model have already been filtered out. However, data belonging to these network headers might still exist. This data is deleted during the filter and conversion into the SAP APO format. Data from other orders, such as maintenance orders or production orders, might also be contained in the parameters for the method. This data is also deleted during the filter and conversion in the SAP APO format. However, you can also ensure that the corresponding order headers are networks. You can check this in parameter CT_CAUVF of the method.

In the refresh transfer, this method is processed after reading the data in SAP R/3 for the networks that should be transferred to SAP APO, but before filtering the data and converting it into SAP APO format.

Network headers and activities are always read, however component requirements are read only if requested, and relationships and capacity requirements are never read.

Method CHANGE_OUTBOUND_DATA

This method is processed after filtering and converting the data to SAP APO format.

BADI_CIF_PS_NETW_IN

You can implement BAdI BADI_CIF_PS_NETW_IN to control the data that is transferred from SAP APO to SAP R/3. This BAdI enables you to change the data received from SAP APO immediately after receipt and before the corresponding SAP R/3 data is read and updated with the SAP APO data (method CHANGE_NETWORK_INBOUND ).

If capacity requirements planning should be carried out in SAP R/3 for networks, the networks have to be listed in table CT_AUFNR_SCHED_IN_R3 in method CHANGE_NETWORK_INBOUND .

The same networks have to be listed in table CT_AUFNR_SCHED_IN_R3 in method CHANGE_NETWORK_DATA of BAdI BADI_CIF_PS_NETW_IN .

If the data transferred from SAP APO is not sufficient to decide whether the capacity requirements planning for a network should take place in SAP R/3, BAdI BADI_CIF_PS_NETW_IN contains a sample implementation showing how further network data can be received.

In SAPAPO

You can implement BAdI /SAPAPO/PRJ_INBOUND to control the data that is transferred from SAP R/3 to SAP APO. This BAdI enables you to:

Change the order data after it has been imported into SAP APO and grouped into individual orders (method CHANGE_CIF_DATA ).

Change the order data after it has been imported into SAP APO, grouped into individual orders, and mapped to the live Cache structures (method CHANGE_DATA_BEFORE_LC_UPDATE ).

The methods in this BAdI are processed as follows:

Method CHANGE_CIF_DATA is processed at the beginning of the inbound process, after the data has been transferred from SAP R/3, but before the data is sent to the live Cache.

Method CHANGE_DATA_BEFORE_LC_UPDATE is processed after the data has been changed to the live Cache structure, but before the data is updated to the live Cache.

See also:

Initial Data Transfer for Project Orders/Networks

Change Transfer and Deletion for Project Orders/Networks

Transfer to Compare Project Orders/Networks

Refresh Transfer to Update Project Order/Network Data

Data Transfer

Processing of Networks Received from SAP APO in SAP R/3