cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC error 7.31

Former Member
0 Kudos

Hi All,

PI 7.31 single stack JAVA

File to IDOC scenario.

The error is coming at last step in receiver IDOC_AAE communication channel:

IDOC_ERROR_PARSE_FAILURE: The metadata for the parsed IDoc was not available. See cause exception for details. :

state=READING_ENDTAG, charPosition=0, lineNumber=0, columnNumber=0

i already saw this thread: http://scn.sap.com/message/9916254#9916254

Just for information - this scenario is working ok in dev environment, but after transporting it to Quality, it is giving the above error in Quality system.

any more suggestions, please, to resolve the above error.

Also if the metadata is to be manually uploaded - then i went to idoc monitor - metadata monitor tab, then in preload, i gave idoctype, business system and comm channel, but it gave error - preload failed, check parameters entered.

So does the metadata needs to be manually uploaded - this was not needed in dev environment, so why it is needed in quality environment. please suggest about this thing also.

Accepted Solutions (0)

Answers (4)

Answers (4)

suman_saha
Contributor
0 Kudos

Hi,

Are you using standard IDOC or any custom development is done?

You may try one thing.Delete the metadata from metadata monitor and run the scenario. During first run,the metadata should be auto generated. If its not getting generated, check in the receiving ECC system.There may be structure mismatch between the receiver ECC idoc and that is used in PI.

Suman

Former Member
0 Kudos

Hi Suman,

I am using custom IDoc for the development.

suman_saha
Contributor
0 Kudos

Hi,

Then the structure must be different. Check the versions of the IDOC Dev and Quality ECC .

Suman

Former Member
0 Kudos

Hello,

" So does the metadata needs to be manually uploaded - this was not needed in dev environment, so why it is needed in quality environment. please suggest about this thing also. "

The solution is that the IDoc metadata is not available in the receiving ECC system.

Former Member
0 Kudos

Hello Misec,

We have the same problem, that is "The metadata for the parsed IDoc was not available". And solved it by creating IDOC metadata(we30, we31) in the receiver system.

Hasan.

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

>>>So does the metadata needs to be manually uploaded - this was not needed in dev environment, so why it is needed in quality environment.

it does not need to be manually uploaded in case there are no issues with metadata upload

but it has to be done either manually or automatically on every landscape so investigate why the manual metadata upload does not work on test first,

Regards,

Michal Krawczyk

Former Member
0 Kudos

Thanks Michal for your reply.

actually i tried to do metadata upload, but there also an error is occuring. to do metadata upload, i went to idoc adapter monitor - idoc metadata cache monitor. there on clicking preload button, a pop-up window came asking for idoc type, party, service, comm channel - so i gave the idoc type, connection type - default, business system name and sender IDOC_AAE comm channel, then clicking ok it gave error - Preload failed. Check parameters entered.

I also tried using the receiver IDOC_AAE comm channel, but it also gave the same above error - Preload failed. Check parameters entered.

Even the log in NWA shows a strange error stating : java.lang.NullPointerException: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable key

So it seems to me that we need to raise an OSS message to SAP to get it solved, as our basis team is new in PI currently.

Well, if anyone knows the solution for the above problem, please suggest.