Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

ABAP Client Proxy Problem

Hi Experts,

I am going with SAP to File using XI ( ABAP Client proxy )

All the ABAP Proxy settings are done in SAP

I followed How do you activate ABAP Proxies? to setup the ABAP proxy settings

SLDCHECK is successful.

While executing the ABAP Client proxy Program data is not reaching XI.

I checked SXMB_MONI ( Message Monitoring ) in SAP ( ECC 6.0) , there i can see al the messages with errors.

The Error Message is

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

- <!--

Call Integration Server

-->

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

- <SOAP:Header>

- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

<SAP:MessageId>48B76253-D5E2-0077-E100-80000A8C6728</SAP:MessageId>

<SAP:TimeSent>2008-09-01T05:10:17Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>Sys_RD2_520</SAP:Service>

<SAP:Interface namespace="http://SAP2File">Proxy_SAP_OB</SAP:Interface>

</SAP:Sender>

<SAP:Interface namespace="http://SAP2File">Proxy_SAP_OB</SAP:Interface>

</SAP:Main>

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

<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>

</SAP:ReliableMessaging>

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

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CO_ID_TRANSP_PROTOCOL_INVALID</SAP:Code>

<SAP:P1>INBDQ-S-XD1</SAP:P1>

<SAP:P2>XI</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Transport protocol INBDQ-S-XD1 not supported in adapter XI</SAP:Stack>

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

</SAP:Error>

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

- <SAP:Hop timeStamp="2008-09-01T05:10:22Z" wasRead="false">

<SAP:Engine type="BS">Sys_RD2_520</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>48B76253-D5E2-0077-E100-80000A8C6728</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

</SAP:HopList>

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

<SAP:Date>20080925</SAP:Date>

<SAP:Time>145544</SAP:Time>

<SAP:Host>INBDQ-S-RD2</SAP:Host>

<SAP:SystemId>RD2</SAP:SystemId>

<SAP:SystemNr>01</SAP:SystemNr>

<SAP:OS>AIX</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>014</SAP:ProcStatus>

<SAP:AdapterStatus>000</SAP:AdapterStatus>

<SAP:User>INABBMMNBS</SAP:User>

<SAP:TraceLevel>1</SAP:TraceLevel>

<SAP:LogSeqNbr>001</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal>

<SAP:PipelineElementId>FEC5B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>

<SAP:PipelineService>PLSRV_CALL_INTEGRATION_SERVER</SAP:PipelineService>

<SAP:QIdInternal>XBTS0004</SAP:QIdInternal>

<SAP:CommitActor>A</SAP:CommitActor>

<SAP:SplitNumber>0</SAP:SplitNumber>

<SAP:NumberOfRetries>0</SAP:NumberOfRetries>

<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>

<SAP:TypeOfEngine client="520">SND_CENTR</SAP:TypeOfEngine>

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID">0A8C6728007748BB794043CE</SAP:EOReferenceRuntime>

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>159</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>8264</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>159</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>

<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>

<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>

<SAP:Reorganization>INI</SAP:Reorganization>

<SAP:AdapterInbound>PROXY</SAP:AdapterInbound>

<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>

<SAP:InterfaceAction>INIT</SAP:InterfaceAction>

<SAP:RandomNumber>84</SAP:RandomNumber>

<SAP:AckStatus>000</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

</SAP:RunTime>

- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="begin" host="INBDQ-S-RD2">20080901051022.285034</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="INBDQ-S-RD2">20080901051024.618542</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="INBDQ-S-RD2">20080901051024.618561</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="INBDQ-S-RD2">20080925092544.179607</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>

<SAP:Timestamp type="begin" host="INBDQ-S-RD2">20080925092544.436125</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

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

<SAP:TraceLevel>Information</SAP:TraceLevel>

<SAP:Logging>Off</SAP:Logging>

</SAP:Diagnostic>

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

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

- <!--

-->

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

- <!--

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = RD2</Trace>

<Trace level="1" type="T">client = 520</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = INABBMMNBS</Trace>

<Trace level="1" type="Timestamp">2008-09-01T05:10:23Z INDIA</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

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

- <!--

-->

<Trace level="1" type="T">Message-GUID = 48B76253D5E20077E10080000A8C6728</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">QOS = EO</Trace>

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

- <!--

-->

<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>

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

<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>

<Trace level="1" type="T">Queue name : XBTS0004</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

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

- <!--

-->

<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface Proxy_SAP_OB*</Trace>

<Trace level="1" type="T">select interface namespace http://SAP2File</Trace>

<Trace level="1" type="T">no interface found</Trace>

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

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

- <!--

-->

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>

<Trace level="1" type="T">system-ID = RD2</Trace>

<Trace level="1" type="T">client = 520</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = INABBMMNBS</Trace>

<Trace level="1" type="Timestamp">2008-09-25T09:25:44Z INDIA</Trace>

<Trace level="1" type="T">----


</Trace>

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

- <!--

-->

<Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>

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

<Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>

<Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER" />

- <!--

-->

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

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

- <!--

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="1" type="T">URL for integration server read from global configuration</Trace>

<Trace level="1" type="T">URL= inbdq-s-xd1://SAPISU_XID</Trace>

<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />

- <!--

-->

<Trace level="1" type="System_Error">Error during split of URL = inbdq-s-xd1://SAPISU_XID</Trace>

</Trace>

</Trace>

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

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

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

- <!--

-->

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">

- <SAP:Payload xlink:href="cid:payload-48B76256D5E20077E10080000A8C6728@sap.com">

<SAP:Name>MainDocument</SAP:Name>

<SAP:Description />

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

All the messages are struk in SAP showing errors its not moving in XI

How to resoove such type of problems

Edited by: XI super on Oct 1, 2008 5:53 AM

Not what you were looking for? View more on this topic or Ask a question