IDX2 Meta data import fails. I::000 error.

[Former Member]

Hi All,

I am trying to import metadata using the IDX2 and it gives me I::000 error. I have checked the authorizations for the user PIAPPLUSER on R/3 and it has

Role : SAP_XI_APPL_SERV_USER

Profiles : SAP_ALL and SAP_NEW and SAP_XI_APPL_SERV_USER.

I am not sure when can I check the log which can show me where could be the problem...

[Former Member]

Is the IDoc a custom or extended IDoc ?

All the segment has "released" status ?

Regards,

Sandro

[Former Member]

Checked the report, IDX_CHECK_METADATA and It was consistent.

Its not extended IDOC, its the standard IDOC that we have from SAP.

[Former Member]

How many port you have pointing to the same SAP system ?

I mean port with same <SID> but different client.

The port with with the client number smaller will be used when retriving IDocs with the transaction IDX1, and for this reason the RFC destination related to the client more close to 000 will be used (and must to work).

Regards,

Sandro

[Former Member]

Hi Sandor,

There are 3 Ports with different SIDs. And the other two are working fine and importing Metadata properly.

[Former Member]

If I still copy the IDOC meta data from the other SID system...i can copy it..

and when I run the XML -> XI -> IDOC, it gives me this error.

<SAP:Code area="IDOC_ADAPTER"><b>ATTRIBUTE_IDOC_RUNTIME</b></SAP:Code>

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

And here is the trace..

<Trace level="1" type="T">Parse XML-BODY</Trace>

<Trace level="1" type="T">Get the Metadata for port SAPPSR</Trace>

<Trace level="1" type="T">Convert one IDoc</Trace>

<Trace level="1" type="T">Warning: IDoc does not contain control-record</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

<Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

</SAP:Trace>

it just gives the warning for the metadata, which it also gives me in case of Succcessfully processed IDOC(for another SID).

[bhavesh_kantilal]

Vijaya,

We faced a similar issue and implementing the authorizxations given in this note did the trick.

Please make sure that the user id has the following authorizations given in this note : 837595.

Regards,

Bhavesh

[Former Member]

I have given full authorization to PIAPPLUSER on R/3

Roles : SAP_XI_APPL_SERV_USER

SAP_XI_IS_SERV_USER

Profiles: SAP_ALL and SAP_NEW.

and we have checked in PFGC, there is full authorisation for the Roles.

[Former Member]

Is the unicode flag in set correctly in the RFC destination pointing to the backend system ?

Regards,

Sandro

[Former Member]

The Problem got solved.

The User id that I was using in the RFC destination in XI was not having the right password. So very silly. I tried the test connection but the remote logon i realised as not happening just because of the password.

Whenever there is any problem with this kind of error first look into the RFC destinations and their login.

Thanks everyone for the replies...i learnt so much.

[Former Member]

Good!

"Check the RFC destination related to the port you use for the IDoc import: transaction IDX1, select RFC dest, Test Logon."

[STALANKI]

try debbuging the report idx*metadata and see what causes an error.

[Shabarish_Nair]

as per some earlier forum post, it was suggested that it could be a authorizations issue. Seems the rights are not sufficient. Ref and check if the hint helped.

[Former Member]

Check the RFC destination related to the port you use for the IDoc import: transaction IDX1, select RFC dest, Test Connection.

Regards,

Sandro

[Former Member]

Yes, I have checked the Test connections on both the RFC destinations (PI and R/3) and both are successful. I have done also the test connection for LCRSAPRFC and SAPSLDAPI, with Success.

Any other place that I should be looking?

[Former Member]

yes, i checked this thread already..Not sure where to check for the short dump?

[Former Member]

T-code ST22 for short dump and check the note also mention in thread.

Thanks,

Tuhin

[Former Member]

Hi,

Look at following thread.

Thanks,

Tuhin