cancel
Showing results for 
Search instead for 
Did you mean: 

URGENT: system error - Maual restart possible

Former Member
0 Kudos

Hi Experts,

I'm facing a problem in Xi prodoction. Both inbound and outbound are throwing system error - Maual restart possible. The user is restarting manually in order to post the invoice.

Basically this is retail project, from POS s/w to Xi to SAP R/3. The scenario is file to idoc(inbound) and idoc to file (outbound).

The error is :

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

- <!-- Interface Determination

-->

- <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="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>XML message not found</SAP:Stack>

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

</SAP:Error>

The acknowledgement error is :

<?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_INV_SND_SERV</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>

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

</SAP:Error>

I have gone throw the sdn post and blogs but i'm uable to trace the problem.

Kindly suggest me ASAP as this is business critical and posting have been stoped.

Regards,

Pawan

Accepted Solutions (0)

Answers (1)

Answers (1)

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi

se this blog

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

also see this

if you have a legacy as sender system, in receiver aggrement>header maping> sender service--> select PI Bussines System

Thanks

Rodrigo

ps:Reward points if useful

Former Member
0 Kudos

Hi,

I have legacy as receiver and sender is r/3.

r/3 sending idocs and the legacy receiving the file.

kindly let me know wat to check now.

Regards,

Pawan

Former Member
0 Kudos

Hi,

Check this

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Regards

Seshagiri

Former Member
0 Kudos

Hi Frds,

In sxmb_moni, the error "system error - Manual restart possible" is showing in Interface Determination.

This is asynchrounouns message. Kindly see the error below:

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

- <!-- Interface Determination

-->

- <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="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>XML message not found</SAP:Stack>

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

</SAP:Error>

Please suggest me how to rectify the error. the client business has been stopped.

I have gone through the michal blogs and some sdn post on this...but no clue.

Regards,

Pavan

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

plz check all your configuration in ID.

also

think there is problem in message mapping.

XML-message not found ,if you are dynamically determining the Interfaces i.e on condition wise

say INTERFACE A is executed if input data say X = 10.

similarly INTERFACE B is executed if input data x = 20.

if you have conditional interfaces where interface is determined with respect to source XML-payload,and in this case if payload from source is empty then engine ll through runtime error.

ensure that XML payload is not empty before reaching Interface determination.

XI pipelines ll have problems with respect to Data table sizes.

dont think its a pipeline problem.

Thanks

Rodrigo

Edited by: Rodrigo Pertierra on Mar 26, 2008 2:31 PM

Former Member
0 Kudos

Hi Rodrigo,

Thanks for your help. But i have checked the message mapping and interface mapping with the SAOP payload xml downloaded from MONI and it was executed successfully.

How to find if there are conditonal interfaces..but i dont think conditional interfaces are there because there are simple IDOC to file scenario.

R/3 IDOC sender and Third party file receiver.

Can you give me any other hint?

REgards,

Pavan

Edited by: pavan kumar on Mar 26, 2008 11:22 PM

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

in SXI_MONI can u see the inbound and result mapping?? if you can only see the inbound check your configuration in ID as suggested you before. check de receiver determination if it have any condicion and interface determination if you assig ppropertly the structures to corresponde BS

Former Member
0 Kudos

Hi Rodrigo,

I have checked the ID and interface determination as suggested by you. every thing looks fine.

As you suggested in previous mail it may be pipeline issue becoz of database. I think this might be the problem, because we have done the deletion of xml messages last week...but it switched the tables from SXMSPMAST to SXMSPMAST2, which switched 7lakh records from SXMSPMAST to SXMSPMAST2.

Again we have run the deletion procedure with switch procedure activated, it switched from SXMSPMAST2 to SXMSPMAST. But we killed the process in the middle because xi prd server became very slow. now SXMSPMAST2 contains 7 lakh records and SXMSPMAST contain 50k records and SXMSPMAST is active now.

Even the basis has applied some patches on the database level to increase the database size.

In Moni, its showing error at interface determination, so i think its not able to determine the interface. Do you think this is related to Pipeline "PLSRV_INTERFACE_DETERMINATION".

We have restarted the server and checked, but no improvement.

Please suggest me how to proceed with this? any clue on pipelines?

Thanks,

Pavan

Former Member
0 Kudos

Hi,

Please find the interface determination trace. Hope this will help you to provide some suggestion.

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

- <!-- Interface Determination

-->

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

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

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

-->

<Trace level="1" type="T">User: XIBGUSER</Trace>

<Trace level="1" type="T">Language: E</Trace>

<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>

<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>

<Trace level="2" type="T">Tunneling needed?</Trace>

<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>

<Trace level="3" type="T">Sender Interface</Trace>

<Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>

<Trace level="1" type="T">Syntax-Check-Flag X</Trace>

<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>

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

- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">

<Trace level="1" type="T">Get the Metadata for port SAPRT2</Trace>

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


</Trace>

<Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>

<Trace level="2" type="T">Port : SAPRT2</Trace>

<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>

<Trace level="2" type="T">Cimtyp :</Trace>

<Trace level="2" type="T">RFCDest :</Trace>

<Trace level="2" type="T">Release : 700</Trace>

<Trace level="2" type="T">Version : 3</Trace>

<Trace level="2" type="T">Direct : 1</Trace>

<Trace level="2" type="T">SAPREL : 700</Trace>

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


</Trace>

<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>

<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>

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


</Trace>

<Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>

<Trace level="2" type="T">Port : SAPRT2</Trace>

<Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>

<Trace level="2" type="T">Cimtyp :</Trace>

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


</Trace>

<Trace level="2" type="T">Create XML-Control Record</Trace>

<Trace level="2" type="T">Create XML-Data Records</Trace>

<Trace level="3" type="T">Create data Record E1WPA01</Trace>

<Trace level="3" type="T">Create data Record E1WPA02</Trace>

<Trace level="3" type="T">Create data Record E1WPA03</Trace>

<Trace level="3" type="T">Create data Record E1WPA04</Trace>

<Trace level="3" type="T">Create data Record E1WPA05</Trace>

<Trace level="3" type="T">Create data Record E1WPA01</Trace>

<Trace level="3" type="T">Create data Record E1WPA02</Trace>

<Trace level="3" type="T">Create data Record E1WPA03</Trace>

<Trace level="3" type="T">Create data Record E1WPA04</Trace>

<Trace level="3" type="T">Create data Record E1WPA05</Trace>

<Trace level="3" type="T">Create data Record E1WPA01</Trace>

<Trace level="3" type="T">Create data Record E1WPA02</Trace>

<Trace level="3" type="T">Create data Record E1WPA03</Trace>

<Trace level="3" type="T">Create data Record E1WPA04</Trace>

<Trace level="3" type="T">Create data Record E1WPA05</Trace>

<Trace level="3" type="T">Create data Record E1WPA01</Trace>

<Trace level="3" type="T">Create data Record E1WPA02</Trace>

<Trace level="3" type="T">Create data Record E1WPA03</Trace>

<Trace level="3" type="T">Create data Record E1WPA04</Trace>

<Trace level="3" type="T">Create data Record E1WPA05</Trace>

</Trace>

<Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>

<Trace level="2" type="T">Set Sender Routing-object</Trace>

<Trace level="1" type="T">Set Receiver Routing-object</Trace>

<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>

<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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>

<Trace level="3" type="T">Getting type of XMB...</Trace>

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

<Trace level="2" type="T">XMB kind = CENTRAL</Trace>

<Trace level="3" type="T">Start pipeline found</Trace>

<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>

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

<Trace level="3" type="T">No triggers found. OK.</Trace>

</Trace>

<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="3" type="T">system-ID = XIP</Trace>

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

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

<Trace level="3" type="T">user = XIBGUSER</Trace>

<Trace level="1" type="Timestamp">2008-03-27T06:35:02Z UTC-7</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 = DCFBC7EA238100F1B64A00145EDC94EF</Trace>

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

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

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

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

-->

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

<Trace level="3" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>

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

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

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

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

</Trace>

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

<Trace level="3" type="T">Generate prefixed queue name</Trace>

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

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

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

<Trace level="3" type="T">Setup qRFC Scheduler</Trace>

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

<Trace level="3" type="T">Call qRFC .... MsgGuid = DCFBC7EA238100F1B64A00145EDC94EF</Trace>

<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>

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

<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>

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

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

-->

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

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

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

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

<Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>

<Trace level="1" type="T">no interface found</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">Note: the following trace entry is written delayed (after read from persist)</Trace>

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

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

-->

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

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

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


</Trace>

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

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

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

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

<Trace level="3" type="T">user = XIBGUSER</Trace>

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7</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 CENTRAL</Trace>

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

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

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

</Trace>

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

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

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

<Trace level="3" type="T">PID = SAP_CENTRAL</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" />

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

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

<Trace level="3" type="T">ELEMPOS = 0001</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0002</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0003</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0004</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0007</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0008</Trace>

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

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

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

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

<Trace level="3" type="T">ELEMPOS = 0009</Trace>

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

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

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

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

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

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Begin of pipeline processing PLSRVID = CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>

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

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

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

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

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

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

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

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

<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</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_LOG =</Trace>

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

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

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

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

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="2" type="T">Start without given receiver</Trace>

<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>

<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>

<Trace level="2" type="T">...valid Receiver w/o Condition: - e_solutionsPOS</Trace>

<Trace level="2" type="T">No Receiver found behaviour: 2</Trace>

<Trace level="2" type="T">Number of Receivers:1</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>

</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 = 001</Trace>

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

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

</Trace>

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>

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

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

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

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

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

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

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

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

<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</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_LOG =</Trace>

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

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

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

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

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) e_solutionsPOS WP_PLU.WP_PLU03</Trace>

<Trace level="2" type="T">...valid InbIf without Condition: WP_PLU.WP_PLU03</Trace>

<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>

</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 = 002</Trace>

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

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

</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 = 002</Trace>

<Trace level="3" type="T">Message version 002</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 002</Trace>

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

</SAP:Trace>

Thanks,

Pavan

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi,

FIRST AT ALL, I RECOMMEND YOU DO NOT DELETE THE QUEUES IN PRD.

if the error relate to interface determination, that means that the structures you receive are differents that you are specting.

try this.

go to moni and get the inbound message and do a test mapping.

also, check wether the receiver structure did change

Rgds

Rod