APO CIF Core Interface

- in SAP Extended Warehouse Management

4/5/2016 9:37:26 PM

This blog about APO CIF Core Interface - Frequently asked questions on the subject of "APO CIF (CoreInterFace)".

1. We have 50 integration models for each object type, since we have 50 plants. Should we define fewer integration models?

Before PlugIn 2002.1, we recommend that you define fewer models for performance reasons. Generally, the size of the integration models depends on the data volume for each plant. To optimize the integration model number, we recommend that you purchase consulting expertise.

As of Plug-In 2002.1, the "Runtime version of the integration model" is available. Using the runtime version guarantees better performance in the online operation (also refer to the documentation for the report RCIFIMAX).

Even though the number of integration models does not affect the performance significantly, we recommend that you keep the number of integration models low, in order not to increase the runtime for generating the runtime model.

That is, do not regularly create new integration models, rather only create new versions of integration models.

You can find release notes for the PlugIn on SAP Service Marketplace at: "http://service.sap.com/R3-PLUG-IN" -> Media Center -> Release Notes PI 2002.1 Release Notes SAP APO.

2. Do we have to transfer the master data of the vendor together with the stock data, so that consignment stocks are transferred?

Yes - this ensures that the consignment stock is correctly linked to the vendor location in SAP APO.

3. Master record objects that were changed since the last transfer are transferred again to SAP APO by initial transfer.

Does this mean that the report RCPTRAN4 (evaluate and send change recordings) does not have to run?

And what about the report RBDCPCLR (delete change pointers) for reorganizing the change pointers?

You do not have to execute the report RCPTRAN4 in this case, since the dataset in SAP APO is up to date due to the initial data transfer.

You should use the report RBDCPCLR to delete "old" change pointers.

4. The master and movement data for a material 4711 is in two active integration models (A+B). Assuming that one of the two is deactivated - what happens then?

The master data and movement data remains active. See also Note 533755 "Description of the delta logic or the program RIMODINI".

5a. What happens if you deactivate an integration model that has master record objects?

Planning in SAP APO is still possible. However, you can no longer transfer the transaction data to SAP R/3.

5b. What happens with the master and movement data in SAP APO after the master data was deactivated?

The master data remains in SAP APO.

5c. What happens with the transaction data if there is another activation?

The transaction data is transferred again. Provided that you reschedule (for example plan automatically (not for plan/manufacturing orders)), the old transaction data is deleted. Note that the integration model for the master data must also be active if the transaction data is transferred again.

6. How do I change from small to large integration models?

You activate the large model (all data already selected in active models is not transferred again) and then deactivate the small models.

7. Why are my orders not transferred from SAP R/3 to SAP APO?

Refer to the information contained in Note 424927 "No order transfer from R/3 to APO" and check your settings accordingly.

8. My material removals are not transferred in the APO order, but the stocks change.

Refer to the information contained in Note 421940 "No reduction of order reservations in APO" and check your settings accordingly.

9. Can data be transferred from SAP R/3 to SAP APO using BTE change pointers (for example from the table MBEW table using user exits)?

Since the APO standard system does not require data from the table MBEW, this is not transferred to the CIF during the transfer of data changes using BTE. Via BTE, data for all SAP standard fields is transferred from SAP R/3 to SAP APO from the table MARA (plant-independent material data), the table MARC (plant-dependent material data), the table MARM (conversion of units of measure) and the table MAKT (material texts). In the customer exit in SAP R/3 also only this data is available. An alternative here is the transfer of the material master changes using ALE change pointers.

For example: Transferring the "floating average price/periodic unit price" (MBEV-VERPR) using the user exit CIFMAT01 does not work. For this, the BD52 Customizing must be changed and the data must be transferred using the ALE method.

Changes to customer-specific fields can also only be transferred to SAP APO using ALE in connection with customer exits.

10. How can I avoid overlaps and thereby inconsistencies during the integration model transfer?

If you use parallel processing for the initial data transfer, transaction data may be transferred to SAP APO before the corresponding master data is available in SAP APO. For example, you can then create in-house production orders in SAP APO without PPM even though this should not be the case. Unfortunately, this cannot be prevented technically. The integration models must be cut accordingly and scheduled in background jobs so that this does not happen. Background jobs also check whether queues have been processed correctly and without errors.

11. Where can I find information about parallel processing during the initial data transfer?

You can find release notes for the PlugIn on SAP Service Marketplace at: "http://service.sap.com/R3-PLUG-IN" -> Media Center -> Release Notes => PI 2002.1 Release Notes SAP APO.