Problems to transfer customer master from MDM to ECC

[Former Member]

Hi experts,

We're using the standard iDoc to transfer customer master data from MDM 7.1 to ECC. The iDoc is divided in two parts (DEBMAS e ADRMAS).

Both are sent without problems to SAP, but with errors on DEBMAS. Checking the error message on the transaction WE02, it shows that the required fields are not been informed. However these addresses fields exists on the message ADRMAS and are posted successfully on SAP. (the mapped fields on syndicator do have data)

I'm wondering that the system is not linking the iDocs as suggested by SAP:

1. Send the iDoc ADRMAS before DEBMAS

2. Send the Customer # on the ADRMAS

3. Send the letters BP on the field ADDR_Group

When we first test, the problem was hidden, we were sending the address data on equivalents fields that exists on the main iDoc (DEBMAS). however the problem got critical when the field e-mail become obligatory on ECC. (the e-mail field does not exist on the iDoc DEBMAS).

Does anybody faced similar situation or knows how to help us?

Best regards,

Armando Martines Neto

[Former Member · Accepted solution]

Problem solved.

The solution was quite simple. Never send slashs ("/") on the empty and optional idoc fields.

If these fields do not have a valid information, simple don't send them on the idoc.

Thank you all for the help.

Regards,

Eduardo

[Former Member]

Hi Michael, how are you?

I work with Armando, facing the same problem. Follow the answers to yours questions:

1) Do you update existing customers in ECC or do you create new records?

Both situations happen. Therefore, there are no errors when updating, because address data is already linked to the customer. On this case, the new address information just doesn't get updated.

2) Is the ADRMAS iDoc really linked to the DEBMAS iDoc? Do you use the correct Customer Number? How are your number ranges defined in ECC (e.g. do you need leading zeros or not)?

Yes, the Customer Number is correct. The "linkage" information remains recorded on table ADOWNERREF, but when creating new customers, this table is not being checked for the address data. I think the number range is not the problem, because when debugging via WE19 transaction and manually inserting data, the customer is created without problems.

3) Which field is missing in DEBMAS posting? What is the detailed error message that you can see in iDoc inbound?

E-mail address field is missing, because there is no corresponding fields on DEDMAS idoc for e-mail. E-mail information is being sent on ADRMAS idoc that should be automatically linked to DEBMAS.

4) Which processing code do you use for iDoc inbound (see partner profiles in transaction WE20)?

We are using DEBM for DEBMAS and BAPI for ADRMAS.

Have you ever seen something like this?

Thanks in advance for any help.

Best regards

Eduardo and Armando

[michael_theis]

Hi Eduardo,

> 1) Both situations happen. Therefore, there are no errors when updating, because address data is already linked to the customer. On this case, the new address information just doesn't get updated.

Again this sounds like that the link between the ADRMAS and the DEBMAS does not really work. Or that your DEBMAS iDoc overwrites the changes of the ADRMAS. Do you use the "no data signs" in DEBMAS for those fields that are maintained with ADRMAS?

> 4) We are using DEBM for DEBMAS and BAPI for ADRMAS.

We're using different ones in our local test systems:

DEB2 for DEBMAS

BAPI_MDM for ADRMAS

Both process codes call different, more MDM specific iDoc inbound function modules. Maybe you can change your configuration and re-test?

Best regards

Michael

[michael_theis]

Hi Armando,

a few questions:

1) Do you update existing customers in ECC or do you create new records?

2) Is the ADRMAS iDoc really linked to the DEBMAS iDoc? Do you use the correct Customer Number? How are your number ranges defined in ECC (e.g. do you need leading zeros or not)?

3) Which field is missing in DEBMAS posting? What is the detailed error message that you can see in iDoc inbound?

4) Which processing code do you use for iDoc inbound (see partner profiles in transaction WE20)?

Best regards

Michael

[Former Member]

Hi Bis,

I was unable to find the field ZCUSTEMAIL on E1KNA1M segment, ae yiu sure that it's a standard field?

best regards

Armando

[Former Member]

yes this is part of thestandard idoc.

we are using this.

regards,

Bis

[michael_theis]

Hi Bis,

the field you're mentioning is not available in the SAP Standard.

Best regards

Michael

[Former Member]

Hi Armando Martines Neto,

There is a segment in DEBMAS as E1KNA1M>> ZCUSTEMAIL,which will map to email. please use that. There is a work around for this also. create the field in MDM as user stamp and maintain the e-mail id for the users using MDM. enable e-mail sending feature with idoc success and failure in the program.when the user updates and syndicates record from MDM,it'll send e-mail.

Regards,