Solved: MM-SUS issue in XI interface

Former Member · ‎03-01-2013

Hello,

The following error is showed in XML file after the PO created and transferred from ECC to SUS.

Error in XI interface: Error during product mapping Program: SAPLBBP_BD_VALUE_MAPPING; include: LBBP_BD_VALUE_MAPPINGU42; Line: 285

Do you have an idea about this problem?

Here is my XML contents:

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

- <!-- Call Inbound Proxy

-->

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

- <SOAP:Header>

- <SAP:Main versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7" 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">

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

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

<SAP:MessageId>001E0BFD-0210-1ED2-9F83-65DAC2A0CE0E</SAP:MessageId>

<SAP:TimeSent>2013-02-21T11:38:16Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>BS_ECC_DEV</SAP:Service>

<SAP:Interface namespace="" />

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>BS_SRMSUS_DEV</SAP:Service>

<SAP:Interface namespace="http://sap.com/xi/SRM/SupplierEnablement/Global">PurchaseOrderRequest_In</SAP:Interface>

</SAP:Receiver>

<SAP:Interface namespace="http://sap.com/xi/SRM/SupplierEnablement/Global">PurchaseOrderRequest_In</SAP:Interface>

</SAP:Main>

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

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

</SAP:ReliableMessaging>

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

<SAP:Category>XIProxy</SAP:Category>

<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>

<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>

<SAP:P2>CL_BBPX1_SUSPO_IN</SAP:P2>

<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>

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

</SAP:Error>

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

- <SAP:Hop timeStamp="2013-02-21T11:38:16Z" wasRead="false">

<SAP:Engine type="IS" />

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

<SAP:MessageId>001E0BFD-0210-1ED2-9F83-65DAC2A0CE0E</SAP:MessageId>

<SAP:Info>ORDERS.0000000000858328:20130221083809</SAP:Info>

</SAP:Hop>

- <SAP:Hop timeStamp="2013-02-21T11:38:17Z" wasRead="false">

<SAP:Engine type="IS">is.00.dc1hjxd0</SAP:Engine>

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

<SAP:MessageId>001E0BFD-0210-1ED2-9F83-65DAC2A0CE0E</SAP:MessageId>

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

</SAP:Hop>

- <SAP:Hop timeStamp="2013-02-21T11:38:18Z" wasRead="false">

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

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

<SAP:MessageId>001E0BFD-0210-1ED2-9F83-65DAC2A0CE0E</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>20130221</SAP:Date>

<SAP:Time>085632</SAP:Time>

<SAP:Host>dc1hjcd0</SAP:Host>

<SAP:SystemId>JRD</SAP:SystemId>

<SAP:SystemNr>02</SAP:SystemNr>

<SAP:OS>HP-UX</SAP:OS>

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

<SAP:Language />

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

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

<SAP:User>T.UEVAJESU</SAP:User>

<SAP:TraceLevel>3</SAP:TraceLevel>

<SAP:LogSeqNbr>005</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>002</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_RECEIVER</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>RECEIVER</SAP:PipelineIdExternal>

<SAP:PipelineElementId>1DC6B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>

<SAP:PipelineService>PLSRV_CALL_INBOUND_PROXY</SAP:PipelineService>

<SAP:QIdInternal>XBTR0001</SAP:QIdInternal>

<SAP:CommitActor>X</SAP:CommitActor>

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

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

<SAP:NumberOfManualRetries>2</SAP:NumberOfManualRetries>

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

<SAP:PlsrvExceptionCode />

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

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>3004</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>24255</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>3004</SAP:PayloadSizeRequest>

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

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

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

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

<SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>

<SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>

<SAP:InterfaceAction>DEL</SAP:InterfaceAction>

<SAP:RandomNumber>19</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="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="begin" host="dc1hjcd0">20130221113818.251508</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="end" host="dc1hjcd0">20130221113818.318762</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="dc1hjcd0">20130221113818.319445</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="dc1hjcd0">20130221113818.814515</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="dc1hjcd0">20130221113818.814528</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="end" host="dc1hjcd0">20130221115632.580256</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

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

<SAP:Timestamp type="begin" host="dc1hjcd0">20130221115632.581305</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

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

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000022</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPFC">LS</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">JRDCLNT850</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPJED</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/Message/30" name="CALLER_CODEPAGE">4102</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">JEDCLNT150</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">ORDERS02</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">ORDERS</SAP:Record>

<SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>

</SAP:DynamicConfiguration>

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

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

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

</SAP:Diagnostic>

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

<SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SAM</SAP:Record>

</SAP:System>

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

<Trace level="1" type="T">http content length 7859</Trace>

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=receiver</Trace>

<Trace level="1" type="T">Remote address = 10.182.10.58</Trace>

<Trace level="1" type="T">Process ID: 451</Trace>

<Trace level="1" type="T">Work Process ID: 3</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

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

-->

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

-->

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

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

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

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

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

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

-->

<Trace level="1" type="T">Message-GUID = 001E0BFD02101ED29F8365DAC2A0CE0E</Trace>

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

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

-->

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

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

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

<Trace level="1" type="T">Generated prefixed queue name = XBTR0001</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">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">--start of determination of sender interface action</Trace>

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

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

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

<Trace level="1" type="T">hence keep interface action INIT</Trace>

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

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

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

<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement/Global</Trace>

<Trace level="1" type="T">no interface action for sender or receiver found</Trace>

<Trace level="1" type="T">hence set interface action to DEL</Trace>

<Trace level="1" type="T">--end of determination of receiver interface action</Trace>

<Trace level="1" type="T">Process ID: 449</Trace>

<Trace level="1" type="T">Work Process ID: 1</Trace>

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

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

-->

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

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

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

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

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

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

-->

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

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

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

-->

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

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

-->

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

-->

- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

- <asx:values>

<CX_ERROR href="#o160" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_SY_NO_HANDLER id="o160">

- <CX_ROOT>

<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_NO_CHECK />

- <CX_SY_NO_HANDLER>

<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>

</CX_SY_NO_HANDLER>

</cls:CX_SY_NO_HANDLER>

- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o159">

- <CX_ROOT>

<KERNEL_ERRID />

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_DYNAMIC_CHECK />

- <CX_AI_APPLICATION_FAULT>

<IF_AI_APPLICATION_FAULT.MT_FAULT_REASON_TYPE />

<IF_AI_APPLICATION_FAULT.MT_SUBCODE />

</CX_AI_APPLICATION_FAULT>

- <CX_BBPX1_STD_MESSAGE_FAULT>

<AUTOMATIC_RETRY />

<NO_RETRY />

- <STANDARD>

<FAULT_TEXT>Error in XI interface: Error during product mapping Program: SAPLBBP_BD_VALUE_MAPPING; include: LBBP_BD_VALUE_MAPPINGU42; Line: 285</FAULT_TEXT>

<FAULT_URL />

<FAULT_DETAIL />

</STANDARD>

</CX_BBPX1_STD_MESSAGE_FAULT>

</cls:CX_BBPX1_STD_MESSAGE_FAULT>

</asx:heap>

</asx:abap>

</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

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

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

-->

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

-->

<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>

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

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

-->

<Trace level="1" type="T">Process ID: 449</Trace>

<Trace level="1" type="T">Work Process ID: 1</Trace>

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

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

-->

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

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

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

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

<Trace level="1" type="T">user = T.UEVAJESU</Trace>

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

-->

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

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

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

-->

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

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

-->

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

-->

- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

- <asx:values>

<CX_ERROR href="#o163" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_SY_NO_HANDLER id="o163">

- <CX_ROOT>

<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_NO_CHECK />

- <CX_SY_NO_HANDLER>

<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>

</CX_SY_NO_HANDLER>

</cls:CX_SY_NO_HANDLER>

- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o162">

- <CX_ROOT>

<KERNEL_ERRID />

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_DYNAMIC_CHECK />

- <CX_AI_APPLICATION_FAULT>

<IF_AI_APPLICATION_FAULT.MT_FAULT_REASON_TYPE />

<IF_AI_APPLICATION_FAULT.MT_SUBCODE />

</CX_AI_APPLICATION_FAULT>

- <CX_BBPX1_STD_MESSAGE_FAULT>

<AUTOMATIC_RETRY />

<NO_RETRY />

- <STANDARD>

<FAULT_TEXT>Error in XI interface: Error during product mapping Program: SAPLBBP_BD_VALUE_MAPPING; include: LBBP_BD_VALUE_MAPPINGU42; Line: 285</FAULT_TEXT>

<FAULT_URL />

<FAULT_DETAIL />

</STANDARD>

</CX_BBPX1_STD_MESSAGE_FAULT>

</cls:CX_BBPX1_STD_MESSAGE_FAULT>

</asx:heap>

</asx:abap>

</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

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

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

-->

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

-->

<Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>

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

<Trace level="3" type="T">Manual Restart: increase Tracelevel to 3</Trace>

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

-->

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

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

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

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

<Trace level="3" type="T">Trace object available again now. OK.</Trace>

<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>

<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>

<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>

<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>

</Trace>

<Trace level="1" type="T">Process ID: 449</Trace>

<Trace level="1" type="T">Work Process ID: 1</Trace>

<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>

<Trace level="2" type="T">Increment log sequence to 005</Trace>

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

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

-->

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

<Trace level="3" type="T">system-ID = JRD</Trace>

<Trace level="3" type="T">client = 850</Trace>

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

<Trace level="3" type="T">user = T.UEVAJESU</Trace>

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

-->

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

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

<Trace level="3" type="T">External PLID = RECEIVER</Trace>

<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>

</Trace>

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

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

<Trace level="3" type="T">PID = SAP_RECEIVER</Trace>

<Trace level="3" type="T">ENABLE = 1</Trace>

<Trace level="3" type="T">TRACELEVEL = 0</Trace>

<Trace level="3" type="T">EXEMODE = A</Trace>

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

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="1" type="Timestamp">2013-02-21T11:56:32Z UTC-3 Begin of pipeline processing PLSRVID = RECEIVER</Trace>

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

-->

<Trace level="1" type="Timestamp">2013-02-21T11:56:32Z UTC-3 Start of pipeline service processing PLSRVID= PLSRV_CALL_INBOUND_PROXY</Trace>

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

<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>

<Trace level="3" type="T">P_CLASS = CL_PROXY_FRAMEWORK_WS_XI</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</Trace>

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

-->

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

-->

- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

- <asx:values>

<CX_ERROR href="#o163" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_SY_NO_HANDLER id="o163">

- <CX_ROOT>

<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_NO_CHECK />

- <CX_SY_NO_HANDLER>

<CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>

</CX_SY_NO_HANDLER>

</cls:CX_SY_NO_HANDLER>

- <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o162">

- <CX_ROOT>

<KERNEL_ERRID />

<IS_RESUMABLE />

- <INTERNAL_SOURCE_POS>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_DYNAMIC_CHECK />

- <CX_AI_APPLICATION_FAULT>

<IF_AI_APPLICATION_FAULT.MT_FAULT_REASON_TYPE />

<IF_AI_APPLICATION_FAULT.MT_SUBCODE />

</CX_AI_APPLICATION_FAULT>

- <CX_BBPX1_STD_MESSAGE_FAULT>

<AUTOMATIC_RETRY />

<NO_RETRY />

- <STANDARD>

<FAULT_TEXT>Error in XI interface: Error during product mapping Program: SAPLBBP_BD_VALUE_MAPPING; include: LBBP_BD_VALUE_MAPPINGU42; Line: 285</FAULT_TEXT>

<FAULT_URL />

<FAULT_DETAIL />

</STANDARD>

</CX_BBPX1_STD_MESSAGE_FAULT>

</cls:CX_BBPX1_STD_MESSAGE_FAULT>

</asx:heap>

</asx:abap>

</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

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

<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>

</Trace>

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

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

-->

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

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

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

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

- <SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" 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">

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

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

<SAP:Description />

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

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

former_member208244 · ‎03-01-2013

Hello Alberto,

Is your ESR connection active?

Problem seems to be in Contructor Method in the PROXY for the interface service PurchaseOrderRequest_In. Check SPROXY transaction, and verifiy if it is active (an ESR PROXY connection is needed to PI repository).

If it is active, try with next steps:

1. Export MainDocument from Payload in the receiver XML.

2. Run SPROXY transaction and find Interface Service in the related namespace.

3. Test proxy (F8)

4. Upload XML and test with "debug constructor".

5. Place a breakpoint and check where exception is raised.

Hope it helps.

Kind Regards,

SG

MM-SUS issue in XI interface

Accepted Solutions (1)

Accepted Solutions (1)

Answers (0)

Why doesn't SLP recognize suppliers with special c...

Re: Workflow Email notification in CP

Workflow Email notification in CP

Question about Ariba contracts events

Re: Ariba catalogs to migrate to SRM