Customer Updates are not captured on DEBMAS when replicating with DRF

[magnusjjessen]

Hi Experts,

I'm working on a MDG-C implementation project where we have configured MDG-C (S/4 system) to replicate customers via ALE to ECC (non S/4 system) and likewise we use CVI to convert Business Partners to Customers in MDG.

Here, I have an issue with capturing the active data records in the DEBMAS when updating General Data with a Change Request.

See following example:

If I edit the General Data (like Name 2 and House ID) on the Business Partner using a Change Request type designed for customer changes then the changed values are not captured in the DEBMAS IDOC and instead the previous active record is processed to ECC by DRF. Like, if changing fields in the segment where with highlighted fields the previous record will be captured in the DEBMAS

sap-question.png

However, if I make a change to Customer Sales Area Data (e.g. Payment Terms) the change is captured correct in the DEBMAS.

I think this issue relates to MDG generates the DEBMAS before the changes that was made to the General Data fields in the Change Request has been captured in KNA1. Do any of you have some insights to this issue and will be able to provide a solution?

BR

Magnus

[former_member1451]

Hi Magnus,

Name 2 and House ID will be transferred in ADRMS not in DEBMAS, please create serialization for ADRMAS and DEBMAS in both MDG and receiver system, Hope it solves your issue.

Regards,

Ravi Shankar. L

[magnusjjessen]

Hi Ravi,

Thanks for your swift response. We have implemented serialization in receiver system where DEBMAS trigger immediately and ADRMAS is processed by background job with delay. But I am not sure if how to do it in MDG when using Data Replication Framework for ALE. Setting serialization on ECC solved our issue on address related fields since ADRMAS now adds the active Address Record to the customer in ECC.

However, I encounter same type of issue with the active data record not getting captured in the DEBMAS when performing updates to Deletion and Block fields via Change Requests from the MDG UI.

For instance we have a CR for customer deletion and if I mark the Central Deletion Flag on a customer the LOEVM field is not populated on the generated DEBMAS which I would expect it to be. But if I am updating the field directly on the customer from the BP transaction the DEBMAS is generated with correct data. Makes me think segments in DEBMAS generate faster than the synch from the MDG UI to Customer record. Do you have any thoughts on this?

[former_member1451]

Sorry for the delay, long time not logged into it.

Configuration

Please follow the below document link for configuration in MDG and ECC.

Deletion Flag

Use FM MASTERIDOC_CREATE_REQ_DEBMAS and EXIT EXIT_SAPLVV01_001 , fill the deletion flag fields after CR activation it works automatically or push the BP manually via DRFOUT after CR activation also will work.