Error: Requested parameter does not exist -Sending IDocs to R/3

[former_member185751]

Hi,

I'm running XI 3.0/WebAS6.4 with Stack05 on IBM AIX5.2

My scenario is Transformation of a custom XML message to a Custom IDOC structure.

The following error occurs when XI is trying to send the IDoc to R/3 :

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <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>Requested parameter does not exist</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: Requested parameter does not exist</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Trace shows the following:

...................

...................

</Trace>

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

<Trace level="3" type="T">Persisting message after plsrv call</Trace>

<Trace level="3" type="T">Message-Version = 007</Trace>

<Trace level="3" type="T">Message version 007</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</Trace>

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

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

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

-->

<Trace level="3" type="T">Persisting message Status = 014</Trace>

<Trace level="3" type="T">Message version 008</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</SAP:Trace>

Is the IDoc adapter trying to convert the IDOC XML to the actual IDOC and fails during that process?

Can anyone please help me out with this error....

Thanks

Regards,

Sri

[Former Member]

Hi All!,

I've encountered also the same error as indicated above.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <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>Requested parameter does not exist</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: Requested parameter does not exist</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

The scenario is that Idoc will be sent to SAP A5A.

But, SAP A5A is down at this time.

Im thinking, that, it affects the connection (sending Idocs to A5A[R/3]), thats why, it has an error like this.

On our scenario, we're on GDA box.

I think, that the metadata of the Idoc in GDA needs to be refreshed so that it will be matched with the message I am sending to the R/3 (A5A).

But, because, its down, the metadata refresh, cannot be done.

Is my concepts/logic correct?

Kindly advise us SAP experts..

Thanks!

[Former Member]

Hi,

Check the receiver communication channel (Created using IDOC adapter). In this communication channel check if the two mandatory parameters are passed correctly.

Following is further info on those two mandatory parameters.

(i)Check if the RFC destination which is created in XI to connect the target SAP R/3 system is working fine.

(ii)Check if the port that has been created in XI is in the form SAP<SID of R/3 system>. If not, create in the form of SAP<SID of R/3 system>. To this port, specify the above RFC Destination.

Refer this weblog as well for more detail:

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

Thnx

Chirag

[Former Member]

Hi Chirag!

Thanks for the information.

Our RFC Destination (SAPA5A) is down right now, so, i think, it is the reason of the error.

Maybe, ill check it again, once, the RFC Destination is up already.

Fred

[former_member859847]

Hi,

I hope, you load the meta data in IDX2.

and mapped the attribute fields in receiver also.

any how, please check it.

regards

mahesh.

[Former Member]

HI Mahesh!

Thank you for the reply.

I've checked using transaction IDX2, there is no SAPA5A on the list.

What should be next step?

Thanks!