Dedicated queue from outbound ECC to CRM

[Former Member]

Hello!! All

We have proxy to proxy scenario our from ECC in to CRM thru PI 7.31 - we would like to have message in CRM in 1 queue (due to functional requirement).

Please, let us know the best approach - as no matter how many messages - everything is expected in one queue - so that can process sequentially - similar to EOIO.

Your help is greatly appreciated!!

Thank you,

Ritu

[former_member190293 · Accepted solution]

Hi, Ritu!

I didn't try it myself but you can try this code in your sender proxy:

   data lo_proxy type ref to zcl_outbound_proxy.

data lo_async_proxy type ref to if_wsprotocol_async_messaging.

lo_async_proxy  ?=  lo_proxy->get_protocol( if_wsprotocol=>async_messaging ).

        lo_async_proxy->set_serialization_context( '_CUSTOM_OUTBOUND' ).

        try.

            call method lo_proxy->call_outbound_method

              exporting

                output = ls_output.

          catch cx_ai_system_fault. .

Where _CUSTOM_OUTBOUND is your custom queue name.

[Former Member · Accepted solution]

HI Komakov, All

Implementing the above option in ECC ABAP program is giving the below serialization error in PI.

• We have made changes using the above logic to have a queue by the name ZCONTRACTQ in ECC program and its coming in to PI with name XBQFI_ZCONTRACTQ.
• The message is failing in PI will the below Error.
• Please, let us know if we need to have any addl. setting in PI to get past the below PARSER SERIALIZATION_ERROR

Thank you,

Ritu

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

<!-- Message canceled -->

-<SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="PARSER">SERIALIZATION_ERROR</SAP:Code>

<SAP:P1/>

<SAP:P2/>

<SAP:P3/>

<SAP:P4>ST_XMS_RUN_TIME_ENV</SAP:P4>

<SAP:AdditionalText>Error during access to the ref node &#39;SITE_ID&#39;. The ref node is not defined or does not have the necessary type</SAP:AdditionalText>

<SAP:Stack>System error in parser Error during access to the ref node &#39;SITE_ID&#39;. The ref node is not defined or does not have the necessary type </SAP:Stack>

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

</SAP:Error>

[nitindeshpande · Accepted solution]

Hi Ritu,

Please follow the below document to have a dedicated queue for your interfaces -

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a...

Regards,

Nitin

[Former Member · Accepted solution]

Hi Nithin

Thanks for your response - we still would need help in knowing wat is causing the error - as the link does not garantee a dedicated queue.

In our case the queue is being created in ECC sucessfully - however, its failing in PI.

Is there any information along with the Queue name which needs to come over from ECC ?!

Wat is the root cause for this error:

Error during access to the ref node &#39;SITE_ID&#39;. The ref node is not defined or does not have the necessary type

Please, kindly let us know your thoughts.

Thank you,

Ritu

[former_member190293]

Hi, Ritu!

You may also take a look at this blog:

[Former Member]

Hi Kolmakov

Please, let us know if you have thoughts on the root cause for the below error.

Thank you,

Ritu

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

-<SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="PARSER">SERIALIZATION_ERROR</SAP:Code>

<SAP:P1/>

<SAP:P2/>

<SAP:P3/>

<SAP:P4>ST_XMS_RUN_TIME_ENV</SAP:P4>

<SAP:AdditionalText>Error during access to the ref node &#39;SITE_ID&#39;. The ref node is not defined or does not have the necessary type</SAP:AdditionalText>

<SAP:Stack>System error in parser Error during access to the ref node &#39;SITE_ID&#39;. The ref node is not defined or does not have the necessary type </SAP:Stack>

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

</SAP:Error>

[former_member190293]

Hi, Ritu!

First, try to call proxy in usual way, without setting serialization context. If it comes without errors, this means that error is caused by setting context. If the error stays the same, it means that parser doesn't understand your message structure or you use data types that parser can't transform.

Regards, Evgeniy.

[nabendu_sen]

Execute transaction XSLT_TOOL and check CALL TRANSFORMATION.

Regards,

Nabendu.

[Former Member]

Hi Nabendu

Thank you for you response!!

Can you please help with as to ...

Where do we check call transformation in XLST_TOOL and wat can look in to with this this regard to the above error.

The regular proxy message is working fine - only when changed the ABAP outbound program to give the custom queue name -  it started giving this error. Please, help us on wat is the best way to resolve.

Thank you,

Ritu

[Former Member]

HI Kolmakov

This is happening only in the case of when we added the above logic to help with creating custom queue in ECC.

This message has no mapping - and all other outbound proxies are working perfectly fine - we see only when we are trying to create custom queue it is failing with this error.

Thank you,

Ritu

[nabendu_sen]

Sorry, I thought it failed at CRM side when reading XML from PI.

What value you are passing through <set_serialization_context>?

Regards,

Nabendu.