Hi Om
check as below with ur technical consultant it will be helpful. Check as below given by SAP.
Schedule Generation and Activation as a Job
Use
Master data is constantly being changed in the ERP system. For this reason you should regularly update your integration model to the newest status and transfer the changes to SAP EWM. You should also delete the old versions of the integration model on a regular basis because these can hinder performance. To do this, we recommend you create the following programs as periodic jobs:
- a) Generate new versions of the integration model (RIMODGEN)
- b) Activate the newest versions (RIMODAC2)
- c) Optional: Delete the old versions (RIMODEL)
This procedure offers the following advantages:
- Master data that has been newly created and that corresponds to the filter objects in existing integration models is included in those integration models and transferred to SAP EWM
.
- Master data that was changed in such a way that it no longer corresponds to the filter objects of the integration model is excluded from the transfer.
- Master data (materials, customers, vendors, sources of supply, and planning product assignment) that has been changed since the last transfer is updated to the most recent status and transferred to SAP EWM.
Recommendation
Recommend the following sequence of activities to prevent data inconsistencies that may arise if EWM-relevant master data is created during the generation and activation of a related integration model:
Generation
1. Integration model for master data with dependent objects
2. Integration model for master data (for example, material, plant)
Activation
1. Integration model for master data
2. Integration model for master data with dependent objects
Activities
1. Create a variant for the relevant program:
- Use transaction SE38 to call the ABAP/4 Editor.
- Enter the name of the report for which you want to create a variant.
- Under Subobjects choose the option Variants and then Create.
- Enter a name for the variant and choose Create.
- Fill the entry fields as required.
- Enter the attributes for the variant.
2. Schedule the program as a job:
- Define a job using the program name and the variant you have maintained.
- Schedule the job as a periodic job.
- Create a job for each variant that you have previously defined.
Further notes
We recommend that you schedule this sequence of jobs for each integration model for which ALE change pointers are written for the objects. These objects include:
- Material masters
- Vendors
- Customers
- Planning product assignment
- Sources of supply
Schedule Periodic Transfer Using ALE Change Pointers
Use
The change transfer for master data with the APO Core Interface (CIF) usually takes place using ALE change pointers. ALE technology is used to write and evaluate change pointers for the objects that are changed.
- Transaction CFP1
- Activate the relevant integration model
The objects that have been changed are completely re transferred to SAP APO.
We recommend that you schedule a change transfer using ALE change pointers as a periodic job. For more information, see Schedule Generation and Activation as a Job. This replaces transaction CFP1.
Requirements
To be able to work with change pointers, the following settings must have been made:
1. The relevant indicator must be set in the
Activate Change Pointers Generally
IMG activity.
2. The transfer of ALE change pointers must be set in the
Configure Change Transfer for Master Data
IMG activity.
3. The transfer must be set up for the relevant message type in the
Activate ALE Change Pointers for Message Types
- IMG activity.
Regards
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.