Error ATTRIBUTE_IDOC_METADATA

[Former Member]

Hi everybody,

I'm trying to fill an IDOC with data from a JDBC adapter and always get following error:

- <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>XML IDoc conversion: No known segments identified</SAP:P1> 
  <SAP:P2 /> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

I searched the forum and already checked the metadata, imported the idoc again but still get the error. Does anybody has an idea what's the fault?

Regards

Dominic

[MichalKrawczyk · Accepted solution]

Hi,

try to reimport the IDOC metadata

in transaction IDX2 to see if there

are no problems with the RFC connection to the R3

you can also find this method in my book

<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member · Accepted solution]

Hey Michal,

if I try< to import the metadata i get the error (translated in English): The segment versions could not be read. (??)

Any idea?

Regards Dominic

[MichalKrawczyk · Accepted solution]

hi,

at first you need to fix this then

as it will not work without the metadata

try checking if the segments you're looking for are

released in r3 (WE30)

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

[Former Member · Accepted solution]

Hey Michal,

I found all the segments in WE30 (CRM).

Any other idea?

Regards

Dominic

[Former Member · Accepted solution]

Hey all,

I'm still getting the same error.

Does anyone has another idea to solve the problem?

Regards

Dominic

[Former Member · Accepted solution]

Hi,

Can you please paste the payload from the step where you are getting this error.

Perhaps, your IDoc-XML format is not being formed properly.

By the way, is the Idoc a Zee Idoc or a standarad Idoc???

[Former Member · Accepted solution]

Hey Seema,

here is the payload:

  <?xml version="1.0" encoding="UTF-8" ?> 
- <ZCMW_INT_ZCINTINBNLOG01>
  <IDOC BEGIN="1" /> 
  </ZCMW_INT_ZCINTINBNLOG01>

But it should have two more subsegments.

FYI: I request via a select query data from a database and get the right data. but somehow it isn't mappt into the idoc structure. Even if I use constants I just get the payload seen above...

Regards

Dominic

[Former Member · Accepted solution]

Dominic,

As you r saying that payload should have subsegments, this means that your mapping is not giving the desired results.

If you r using Message Mapping, then please test the mapping with the same data as in runtime.

i.e u can copy Source Payload (from sxmb_moni) and paste it in 'Test Mapping' in IR and see what results it gives.

[Former Member · Accepted solution]

Hey Seema,

I'm using message mapping and in the test it works properly. So the error must be somewhere after the mapping.

Regards

Dominic

[Former Member · Accepted solution]

Hi

Are you doing graphical mapping or via java?

In the last one, check if segments are treated like attributes.

regards

[bhavesh_kantilal]

Hi,

Make sure that the payload of the reponse is actually a valid IDOC strucutre.

Just click on Response --> Payload and see if the output IDOC after mapping is valid.

Regards,

Bhavesh

[Former Member]

Hey Bhavesh,

I don't get the IDoc to be filled right. Payload:

- <ZCMW_INT_ZCINTINBNLOG01>
  <IDOC BEGIN="1" /> 
  </ZCMW_INT_ZCINTINBNLOG01>

There are 3 subsegments to be filled. It doesn't work with mapped constants either.

Regards

Dominic

[Former Member]

Hi,

Check out for the RFC destination corresponding to the port in your recevier IDoc Adapter. To fetch the metadata, this RFC should be working

Sometimes, Adapter Engine uses this RFC destination to fetch metadata for the Idoc instead of picking metdata from IDX2.

Please visit this link to get a clearer idea

http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/content.htm

Hope this solves your problem

Regards,

Seema

[Former Member]

Hey Seema,

the RFC destination works fine.

Regards

Dominic