Hi Gurus,
I have read several threads on this topic but still need to confirm the below :
Transfer of master data changes can have two scenarios :
CASE 1 : Change in data of a material that already exists in an active integration model
CASE 2 : Change in data of a material that makes it now eligible/ineligible to be transferred to APO as per the existing filtering criteria
Following are maintained :
- Activate ALE Change Pointers Generally maintained in transaction BD61
- Activate ALE Change Pointers for Message Types maintained for 'CIFMAT' in transaction BD50
- ALE Change Transfer, Periodic maintained in transaction CFC9
- Master data field (Material-MARC-PLIFZ) with message type CIFMAT is already mainatained in transaction BD52
For CASE 1 :
I noted the below when I change 'Planned delivery time' in MM02 :
- Creation of new integration model by CFM1 and activation by CFM2 DOES NOT TRANSFER the change
- Background job with RIMODGEN as step 1 and RIMODAC2 as step 2 DOES NOT TRANSFER the change (Essentially same as above but in background.Does this take care of only CASE 2 ? )
- Mere deactivation and reactivation of the model in CFM2 TRANSFERS the change
- RIMODINI TRANSFERS the change (But this is initial data transfer)
- Background job with RIMODAC2 (With deactivate all models) as step 1,RIMODGEN as step 2 and RIMODAC2 (With activate newest model) as step 3 TRANSFERS the change
Thus to transfer data change (to take care of both case 1 and case 2) and transfer dependent transaction data,is the below sequence in background job recommended ?
For master data change transfer :
STEP 1 : RIMODAC2 (With deactivate all models)
STEP 2 : RIMODGEN
STEP 3 : RIMODAC2 (With activate newest model)
STEP 4 : RIMODDEL
For transaction data transfer arising out of CASE 2 :
STEP 5 : RIMODGEN (For transaction data models)
STEP 6 : RIMODAC2 (For transaction data models)
(Above steps scheduled daily night)
RIMODINI scheduled weekly.
Kindly share if my above approach is ok or is there any other ?