Getting "(3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data" error while triggering idoc

[kjyothiraditya]

Hi experts,

We have created a new IDoc type along with message type in Basis version 701 with all segments being created in 46C version. I have mapped the message type to partner profile. The idoc is getting triggered but in status 03 and in sm58 giving the above error and not able to reach PI.

Also tried to load the metadata manually into PI, but got couldnt find Idoc type.

Could you please suggest how to correct this issue.

[dhivakar]

Hi,

If you couldn't find the IDoc type in metadata, it didn't showed up in PI. Check we82 in abap system whether your new idoc entry is there in the table with the correct version. If not ask the Abaper to maintain the entry.

Reimport the Idoc in ESR and reactivate it. Make dummy changes in Sender Idoc channel also.

Best Regards,

[kjyothiraditya]

Yes, the idoc version is 701 in we30 and maintained the same in we82. Initially i have maintained the version as 46C in we20, later changed it to 701. For both these changes, it was not able to pick the metadata. Further for your info the idoc remains in status 30.

[dhivakar]

Have you reimported the Idoc after you change the entries in WE82? Please reimport once you maintain the correct version and activate the ESR objects. Now you can also try to manually load the metadata.Is it the first Custom Idoc in your landscape?

[PRAGSMATIC]

Can you mention the full stack strace from the log viewer of NWA when IDOC is pushed from ERP ?

[kjyothiraditya]

Hi Anurag,

I am not a PI person, but ABAPer. I will not be able to provide the trace.

Thanks,

Aditya

[Lakshmipathi]

Maintain the correct entries as listed out in OSS note 2084869

[kjyothiraditya]

Hi

Thanks for you reply. But just for clarity, is the issue from ECC side or PI side. The same settings when in DA1 are reaching the same PI, but in test system they are not able to reach PI.

[former_member366655]

Hi Jyothir,

Hope you have imported the IDOC in IR , and also the Metadata. Please go for Cache Refresh and also do some dummy changes in your configuration , and re-activate it.

Regards,

Vivek Jain

[kjyothiraditya]

Hi Vivek,

We have copied the metadata from an existing message type, added the metadata of the new segment and even then we are getting this error. Also we tried to manually load the metadata, even then it gave "idoc type could not be found" error.

Regards,

aditya