IDOC_ERROR_METADATA_UNAVAILABLE in sm58 of Source system

[former_member192554]

Hi All,

We are on PI Single stack , AEX installation and have an issue with IDoc to IDoc scenario.

Issue: Source R/3 is sending custom IDoc , its getting released with green status but getting stuck in sm58.

Error at Sender system (sm58) : IDOC_ERROR_METADATA_UNAVAILABLE

Checking on PI logs , we could just find below details:

[JRA] ResourceAdapterImpl.sendDirectToMdb, exception: com.sap.conn.idoc.IDocRuntimeException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ZXXXX" is unavailable.

[JRA] handleRequest(), exception sent to client: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ZXXX" is unavailable., CONVID=12345

[JRA] serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_26, connectionId= abc-.|31111|XI_IDOC_DEFAULT_SID , Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ZXXX" is unavailable. (raised by system xxxx)

One clue that we have till now , that above error is coming only for CUSTOM IDoc's.

Any help is much appreciated

Many Thanks,

Abhi

[azharshaikh · Accepted solution]

Hi Abhi,

In addition to abv post, also check following if it helps:

(PI) IDoc remains stuck in SM58 of sender system with exception "IDocException occurred&amp...

Note # 1529038 - Idoc send to MII, METADATA_UNAVAILABLE

Regards,

Azhar

[former_member192554 · Accepted solution]

Hi Azhar,

Thanks for your inputs .We have been through this

I forgot to mention Sender system is R/3 and not ECC which is non-unicode system , and they are using TCP/IP connection  with program ID to connect to our AEX( single stack).

In R/3 ,TCP/IP , unicode settings are not present.

Regarding Note # 1529038 - Idoc send to MII, METADATA_UNAVAILABLE :

1)No user is getting used in Sender TCP/IP connection , only program ID is getting used , and

2)Sender has confirmed that they are pasing entire extension information while releasing it.

Thanks & Regards,

Abhi

[azharshaikh · Accepted solution]

Hi Abhi,

Please recheck on the following:

1. As suggest abv by Hareesh, where you able to preload the Metadata successfully into PI and is the Custom IDOC released & activated in R/3.

2. Partner Profile / ALE config is setup with correct values in R/3

3. Check whether InboundRA in NWA is functioning without any errors

Configuration of inboundRA in the Java IDoc_AAE Adapter - Process Integration - SCN Wiki

4. Check the Destination in NWA for this R/3 sys - are you able to Ping / Test this Destination Successfully?

5. Is the Sender IDOC_AAE CC Ping test successful

6. Get the complete error log from Basis team for the SM58 error that you see in R/3 for analysis.

Regards,

Azhar

[former_member192554 · Accepted solution]

Hi Azhar,

Thanks for you inputs.

Please find response to each below:-

Azhar Shaikh wrote:

Hi Abhi,

Please recheck on the following:

1. As suggest abv by Hareesh, where you able to preload the Metadata successfully into PI and is the Custom IDOC released & activated in R/3.

2. Partner Profile / ALE config is setup with correct values in R/3

3. Check whether InboundRA in NWA is functioning without any errors
Configuration of inboundRA in the Java IDoc_AAE Adapter - Process Integration - SCN Wiki

4. Check the Destination in NWA for this R/3 sys - are you able to Ping / Test this Destination Successfully?

5. Is the Sender IDOC_AAE CC Ping test successful

6. Get the complete error log from Basis team for the SM58 error that you see in R/3 for analysis.

Regards,
Azhar

1) Able to reload metadata successfully

2) Partner profiles are correct  as IDoc successfully generated with status Green in Sender side but got stuck in sm58 with IDOC_METADATA_ERROR

3) InboundRA working fine

4) Destination test is green

5) Ping channel is successful , without any error.

Please note that , issue is coming only with custom IDoc's which might be clue for finding the root cause.

Standard IDoc's are reaching successfully to PI , using same channel and destination.

Thanks & Regards,

Abhi

[azharshaikh · Accepted solution]

Hi Abhi,

Thanks for updates. Suggest you to try / check on the following as well:

1. Delete the Custom IDOC MetaData from - IDOC Adapter Monitoring: Metadata Monitor & then try to trigger the Custom IDOC again from Sender system...

2. If issue / error still persists then check on the following:

i) Try PI system restart and check if it helps

ii) Issue may be caused by a missing COMMIT WORK statement at the end of the program (MASTER_IDOC_DISTRIBUTE) that creates the cust IDoc.

Refer SAP Note: 1638631 - Custom idocs are in status 03 but are not sent

1575852 - Outbound IDocs remain in status 30

Regards,

Azhar

[Former Member · Accepted solution]

Partner profiles are correct  as IDoc successfully generated with status Green in Sender side but got stuck in sm58 with IDOC_METADATA_ERROR >>

I guess you have missed to add the extension in the partner profile. make sure to include the correct extension under idoc type!

[former_member184720]

try preloading the metadata manually and see if that helps?

follow below help document to do the same..

Managing IDoc Metadata Using IDoc Metadata Monitor - Advanced Adapter Engine - SAP Library

[former_member192554]

Hi Hareesh,

We have tried doing that but no help. Still facing the same issue.

Thanks,

Abhi

[former_member184720]

>>>We have tried doing that but no help. Still facing the same issue.

When you say you tried doing that, were you able to import the metadata into PI?

I hope all the segments have been released and activated for your custom IDOC.

[former_member192554]

Hi Hareesh,

Yes we were able to import metadata successfully in PI with no error.

Thanks & Regards,

Abhi