cancel
Showing results for 
Search instead for 
Did you mean: 

Fields getting wiped out while posting DEBMAS04 IDoc

Former Member
0 Kudos

Hi All,

We are using DEBMAS04 IDoc to create/modify customer data in SAP ERP via XI interface.

However, we are finding that whenever a customer is modified by the interface, some company code data gets wiped out.

IDoc is posted using process code DEBM and standard routine IDOC_INPUT_DEBITOR.

In E1KNB1M (Company code data) segment, we are passing only KNB1-BUKRS (Constant value 1000),

KNB1-AKONT (A Constant value 0000112110) and KNB1-ZTERM ( Constant value ZOF3). Rest of the fields in this segment have not been mapped in the message mapping. The users modify the records manually (via XD02) if they need to update other company code data.

After such manual modification (XD02), if the interface is run for that customer, the newly modified fields get wiped out.

I am not able to understand why the fields get wiped out if they are initially not mapped in the message mapping.

I would highly appreciate your help on this.

Thanks.

Regards,

Riyaz

Accepted Solutions (0)

Answers (2)

Answers (2)

moorthy
Active Contributor
0 Kudos

Hi.

First try to simulate the error via WE19 test tool. If you are getting the same error, then you need to debug the Function Modules used in the IDOC processing

Also probably some of the BADIs etc may be active or deactive.

IF you are getting proper data in the WE02, then still data is not reflected, you can check the IMG configuration with the help of Functional Team.. Some Configuration Settings may cause this problem

If still the problem, then prefer to contact SAP.. Because many a times these types problem because of active/inactive version of the function modules. etc

Hope this helps,

regards,

Moorthy

Former Member
0 Kudos

The reply is too late,

If you are trying to achieve an Vendor scenario ,you won't be able to process Debmas it need to split it to Cremas and Adrmas using xslt and corresponding values from the debmas needs to be populated into the output cremas and adrmas using BPM.

In our case we used a no data indicator "/" on the Local fields of MDM and on the Global field (if exists then pass) logic is used.

For an Vendor create the all values passes whereas in case of change vendor the value do not get wiped out which is taken care by the no data indicator.

Thanks,

Sudhansu

Former Member
0 Kudos

The reply is too late,

If you are trying to achieve an Vendor scenario ,you won't be able to process Debmas it need to split it to Cremas and Adrmas using xslt and corresponding values from the debmas needs to be populated into the output cremas and adrmas using BPM.

In our case we used a no data indicator "/" on the Local fields of MDM and on the Global field (if exists then pass) logic is used.

For an Vendor create the all values passes whereas in case of change vendor the value do not get wiped out which is taken care by the no data indicator.

Thanks,

Sudhansu

Former Member
0 Kudos

Hi Riyaz,

check the field values of the IDoc in your R/3 system using transaction WE02.

well you can go to WE19 and modify any field value and repost the document.

you can debug that as well.

It will help you to find out reason behind this error.

regards

pushkar