cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Management tick in ECC getting changed after update through MDM

Former Member
0 Kudos

Hello Experts,

In our scenario Batch management Field in MDM system is not mapped with ECC.

Even then, it has been observed that when no stocks are present for a material

the batch management tick (if present) in ECC gets removed while updating any material data through MDM.

Whereas if stocks are present, the error u2018Batch management requirement cannot be changedu2019 is thrown and nothing is updated in ECC.

Please let me know if there's any solution to this issue. Also this a little urgent because many users are suffering because of the removal of the batch management tick in ECC.

Regards.

Accepted Solutions (1)

Accepted Solutions (1)

michael_theis
Active Contributor
0 Kudos

Hi trueblue,

usually ALE requires always all data of an IDoc segment in ALE inbound! If you do not mention a field within a segment explicitely, ALE handles this as a deletion of the value. This explains why you loose this information on your side. If you really do not want to add this field to your MDM repository, you might try if your IDoc supports the "no data sign" which is a slash "/". Instead of mapping the field in MDM syndicator, set it's value per default to "/" (without " of course). Sometimes ALE is able to interprete this sign correctly as "keep the existing data of the record in the system". This works e.g. for CREMAS, DEBMAS, but does not work for ADRMAS. This I cannot tell you if it'll work on your side - but this can be easily tested!

Best regards

Michael

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

What is the idoc you are using?

Thanks,

Ravi

Former Member
0 Kudos

Hi,

In all agreement with Michael.

To put it simply,fields for which you want no value to be sent "/" is the value to send.

You can set this from PI or syndicator or MDM assignments as the standard value to be sent for batch management.

Thanks,

Ravi

Former Member
0 Kudos

Thanks a lot!

Will try using '/' and let you guys know the result.

Regards.

Former Member
0 Kudos

Hi Experts!

Thanks a lot.

The problem got resolved after using '/' in the idoc for XCHPF (batch management)

I still have a doubt. In production system Even though the batch management field is unmapped in syndicator, it is still

present in the generated xml. Whereas in the development system also the batch management field is unmapped but the

XCHF tag is NOT present in the xml file. What may be the reason for this difference?

Thanks Again

Regards.