ARIBA Integration mapping in S4 HANA Cloud

[meisenberger]

Hello Community,

we would like to set up the order-to-invoice process with ARIBA network (4A1). However we do not find any option to map the fields of the cXML file we get from ARIBA into the S4 HANA Cloud.

We get following error messages in SAP:

Does anyone know how to fix this?

Thank you and BR
Mona

[JulianoRomanato]

Hello meisenberger.

How are you? I have included the Tag "SAP S/4HANA Cloud Extensibility" for this question, as it refers to SAP Ariba Integration with SAP S/4HANA Cloud.

Regards.

Juliano Romanato.

[meisenberger · Accepted solution]

We got now the information that there is no mapping opportunity on supplier CIG side for now, therefore the customer has to adapt the mapping. Our customer simply removed the region field in the mapping and it worked.

BR
Mona

[wagener-mark]

Hello @meisenberger ,

we have a S/4HANA private Cloud system and had the same issue. In the meanwhile the CIG team provided an improvement. They cut (trim) the value so that it does not exceed the maximum length anymore. In combination with implementing cloud BAdI EDI_SD_ORDER_MODIFY_HEAD_PARTY, it provides a workaround. In the BAdI implementation, you can e.g. empty the region...

I hope that helps.

Best regards,

Mark

[junaidalam]

Hi mona.eisenberger - My assumption is that in the field region you might have more characters. The region should be 2 characters as I see in the system. Can you please check and suggest that the your region is 2 character.

Junaid

[meisenberger]

Hi junaid.alam1976 ,

yes that is the case, however I do not unterstand how the values are converted/mapped between CIG and SAP S4HANA Cloud.

The field in the source payload from CIG is <State> and it is filled with the written out-value. CIG convertes this field into <Region> but the content is still Arges instead of AG.

For example:

Source payload from our customer:

<State>Bucuresti</State>

Target payload:

<Region>Bucure</Region>

The correct value would be:

<Region>B</Region>

This is the root cause for the error message in S4 HANA Cloud, but I did not find any documentation how to fix this.

BR
Mona