CIF from multiple R/3 systems

[Former Member]

If we CIF same material codes (phiscally diffrent products) from multiple R/3 systems via diffrent business system group, is APO able to seperate them in forecasting/planning?

Is only one material master created in APO? how about the description and other attributes, which one is used in planning and relased to R/3?

thanks,

Siir

[kenneth_snyder]

that is the purpose of the business system group; to distinguish which R/3 system sent the master data. APO will support this.

You can modify the APO product number to include the BSG, otherwise, how will you select product A from R/3 system X vs product A from R/.3 system Y.

Some people use a user exit to append the BSG to the product number.

As for DP; the actual product number is irrelevant. DP uses CVC's, so it depends upon how you want to represent the different products.

But to use the UOM of the product master, the DP characteristic value for product must match the product definition in SNP.

Ken Snyder

[Former Member]

Thank you all. But, I had mentioned same to my client. In same plant, same material number stiuation, they want system to identify the source and keep those records seperate such as making business system group as a key. But, looks like this is not possible through standard ways.

Thanks all.

Siir

[Former Member]

Hi Siir

The Masterdata that is CIFed is not really used in Forecasting. you need to create characteristic value combinations for Demand Planning as mentioned in Charlie's answer.

for Supply Network Planning or , Production Planning you would use the material masterdata but you can ensure that the different masterdata coming from your different R3 systems are differentiated. If the APO locations(usually plants or dc or vendor or customer in r3) in the different systems are unique then it would be fine because the planning masterdata is usually based on a location-product combination

if you have same locations in your different r3 systems then you need to think of a way to differentiate them

[Former Member]

there sould be one R/3 system only then only it' call ERP but you may have CRM, SRM etc but should have only one R/3 system

CIF Customizing in SAP APO is used to set up the system infrastructure and to configure the data transfer between SAP Advanced Planning and Optimization (SAP APO) and the ERP system via SAP APO Core Interface (CIF). CIF Customizing also covers application-specific settings and enhancements for CIF.

An Implementation Guide (IMG) is available for CIF Customizing. The IMG provides you with a clear overview and explanation of all steps that are necessary for integration via CIF. With the exception of organizational IMG activities that only contain a description, you can go directly to the relevant transaction and execute the action.

Integration

In addition to the Customizing settings in SAP APO, you must also make the necessary Customizing settings in the ERP system. For more information, see CIF Customizing in the ERP System.

Features

The Implementation Guide for CIF consists of three main areas:

· Basic Settings for Creating the System Landscape

Here you can find all the IMG activities that are necessary for the partner systems to be able to communicate with each other using CIF (for example, naming the logical systems, naming RFC destinations, and making qRFC settings).

· Basic Settings for the Data Transfer

Here you can find all the IMG activities that are necessary for the data transfer itself and for monitoring the transfer, for example, settings for publishing the planning results from SAP APO, CIF error handling, and the CIF comparison/reconciliation of transaction data.

· Application-Specific Settings and Enhancements

Here can you find customer exists, Business Add-Ins (BAdIs), and settings for individual applications such as for stocks, for sales scheduling agreements, or for in-house production.

Activities

1. You call the IMG in SAP SCM. In the SAP Reference IMG, choose Integration with SAP Components ® Integration via APO Core Interface (CIF).

2. You make the relevant settings.

Note that some of the basic settings are target-system-dependent or client-specific. These settings are not transported from the Customizing client to the productive client. This means you also have to make the settings in the productive client.

Only one mateiral master created in APO and the other attribute of the materal alnog with material master you can transfer via info object.( in the info object you can define all the attributes which you want to transfer from R/3 to APO.

For the planning you can create CVCs call as characterstic value combination like

mateial and plant etc