In most cases, you make changes to master data in the ERP system because this is the superordinate system for master data. There are two different scenarios for this:
Changes to master data fields that are already contained in an active integration model
The ERP system marks these changes using change pointers (see
Transfer of Data Changes Using ALE Change Pointers
below).
When the integration model is activated, the system automatically evaluates all change pointers and transfers the corresponding master data records to the target system. Only the master data records that have been changed are transferred, not all of the data records that are contained in the integration model.
Changes to master data fields relevant to filtering
These changes mean that certain master data entries now fulfill the selection criteria of an integration model that already exists. Fields relevant to filtering are those that are given in the
General Selection Options for Materials
section of the selection screen for the integration model (material type, plant-specific material status, MRP controller, MRP type, and ABC indicator).
When creating a new version of the integration model, CIF transfers the master data record that now meets the selection criteria, including all dependent objects.
Example
A material that previously had the MRP type PD and that was planned in the ERP system will, in the future, have the MRP type XO and will be planned in SAP APO. This change means that it now fulfils the selection criteria
MRP Type XO
of an integration model that already exists. The ERP system includes the material in this integration model and generates a new version of the integration model. When the integration model is activated, the material is transferred to SAP APO including all dependent objects such as stocks, orders, and so on.
This operation can influence performance. We therefore recommend that you use a periodic transfer using background processing at a time when the system load is low (for example, at night).
For more information about the periodic transfer using background processing and the online transfer using BTE, see Initial Creation of Master Data .
For the transfer of data changes, you must differentiate between changes to:
Material, customer, vendor, and source of supply
Production process model (only SAP APO)
Planning product and work center (only SAP APO)
Special cases to bear in mind for the transfer of changes to these object types are listed below.
If you change these master data objects in the ERP system, the system writes a note for ALE change pointers (ALE = Application Link Enabling). Here, message type CIFMAT stands for material, CIFCUS for customer, CIFVEN for vendor, and CIFSRC for source of supply.
As a prerequisite, change pointers must have been activated in CIF Customizing in the ERP System . In addition, you must specify for which message types changes pointers should be written. To do this, make the following settings:
In the CIF IMG, choose
Set the relevant indicator.
Then, in the IMG for CIF, choose
Choose the relevant message types.
Recommendation
Schedule background jobs in which the integration model is activated regularly (for example, at night). The change pointers will then be evaluated each time. This ensures that your master data in the target system is always up-to-date.
If you do not regularly activate the integration model and want to evaluate the change pointers, you can use report RCPTRAN4. Create a variant of this report containing the target system and the selection of master data objects.
You can access this report using transaction CFP1 or in the SAP Menu by choosing
.
For the material, customer, vendor, and setup group master data (message types CIFMAT, CIFCUS, CIFVEN, and CIFSTG), you can also set the periodic transfer of change transfers by using transaction CFC9. In this case, change pointers must also be activated.
In the IMG for CIF, choose
or call transaction CFC9. For the relevant object type, choose
ALE Change Transfer, Periodic
.
You can also use transaction BD52 to configure the master data fields with message type CIFMAT for which a change pointer should be set.
Recommendation
ALE change pointers are not deleted in SAP R/3 after the transfer of data changes. Instead, they are marked as
Processed
. To prevent a drop in system performance, we recommend that you delete ALE change pointers regularly using the relevant IMG activity in the CIF IMG (
) or by calling transaction BD61.
As of SAP R/3 Plug-In 2000.2, you can transfer changes to material, customer, and vendor masters that are already contained in an active integration model to the target system as soon as they have been posted in the ERP system.
In the IMG for CIF, choose
or call transaction CFC9. For the relevant message type, choose
BTE Transfer, Immediately
. In this case, the SAP R/3 system automatically sets the indicators for message types CIFCUS, CIFMAT, and CIFVEN to active.
For more information about the online transfer using BTE, see Initial Creation of Master Data .
You use transaction CFP3 (report RSPPMCHG) to transfer changes to production process models (PPMs). To find the report, on the
SAP Easy Access
screen, choose
.
During the transfer of data changes, the system overwrites the PPM that already exists in SAP APO. However, data that has been manually created in SAP APO and that is not contained in the Core Interface (CIF) is not overwritten.
The system writes a note when changes are made to bills of material (BOMs), routings, receipts, and production versions. Phantom assemblies (logical groupings of components) are an exception.
Changes that are relevant to scheduling (for example, changes to the duration of an operation) are taken into account in the transfer of data changes. The explosion date of the PPM must be set correspondingly. As of SAP R/3 Plug-In 2001.1, you are able not only to explode routings/BOMs according to the selection date entered (as before) but also according to the time of transfer and the start/end date of the production version. The selection date specified in the integration model is set as default. If the selection date lies in the past, any current changes will not be taken into account.
Locked production versions in the ERP system lead to a deactivation of the corresponding PPMs.
The system does not write change pointers if you change referenced objects at the work center (for example, formulas).
Only those operations and BOM components are transferred to SAP APO for which work centers or materials are contained in an active integration model.
For more information, see the SAP Library for SAP APO under
For more information, see the SAP Library for SAP APO under
To transfer changes to planning products or the relationships between a product and a planning product, or changes to ERP change numbers or work centers, we recommend that you create a background job with the following reports that is scheduled to run at night:
Optionally, you can delete the old version of the integration model (report RIMODDEL).
Start the initial data transfer (report RIMODINI, set the
Set to Active
indicator )
Generate the (new version of the) integration model (report RIMODGEN)
Activate integration model (report RIMODAC2, activate the
Activate Newest Version
radio button)