Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error: ATTRIBUTE_IDOC_METADATA

Hello Guru's,

I have got the following scenario: XML to IDOC, but when the message is in XI, it gives me an error and I do not understand why. Hope someone can help me.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>

<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with CAO300 I::000 FM NLS_GET_LANGU_CP_TAB</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with CAO300 I::000 FM NLS_GET_LANGU_CP_TAB</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Best regards,

replied

logon user of the RFC destination does not have the necessary authorizations for determining the metadata.

In transaction PFCG, extend the role of the logon user by adding the following authorizations:

  • Authorization object S_RFC

Field name RFC_TYPE value FUGR

Field name RFC_NAME value EDIMEXT, SDTX

Field name ACTVT value 16

  • Authorization object S_IDOCDEFT

Field name ACTVT value 03

Field name EDI_CIM value ' '

Field name EDI_DOC value TXTRAW01

Field name EDI_TCD value WE30

  • Authorization object S_CTS_ADMI

Field name CTS_ADMFCT value TABL

  • Authorization object S_TABU_DIS

Field name ACTVT value 03

Field name DICBERCLS value

Note: You can activate the display of the technical names of objects and fields in authorizations maintenance by choosing the 'Technical Names' function from the 'Utilities' menu.

Then save and execute the 'Generate' function. Then choose 'Back' to return to role maintenance and switch to the 'Users' tab. Press the 'User comparison' button to execute this function

The problem is with the user id in sm59 of XI which is used to call the R3 system. Check the authorization with the following SAP Note - 837595. Also make sure that this user is not locked.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question