[-9046]: System error: BD No converter entry

Hi,
when i try to execute
delete person where oid = 'AAAAAZAT'
i get the message
: System error: BD No converter entry
this table, have many references back, all foreign keys are DELETE CASCADE, i executed many deletes for other tables, and all works, i disabled the redo log, too, any idea?
thanks
Clóvis

Hi Melanie,
I checked the database, and dont have any problem, but i think that i discover the problem, think something like having a table:
CREATE TABLE Person (
    oid VARCHAR(8) NOT NULL,
    my_Parent VARCHAR(8),
    primary key (oid)
ALTER TABLE Person ADD FOREIGN KEY my_Parent REFERENCES Person(oid) ON DELETE CASCADE
Then if i delete a person that can cascade delete many rows from other tables and the same table, and that maybe overflow the system, then the error occurs, if i just set my_Parent to null where my_Parent is equals the Person to be deleted, the commands works well.
best regards
Clóvis

Similar Messages

  • System error -no entry in table T093 for the chart of depreciation or ccode

    When checking “Depreciation Areas of Company Codes” in overview for experts (transaction SPRO) I first get a warning message “inconsistent rounding entries were corrected”.
    After saving once in the maintenance transaction (as recommended in the help text) I get the following system error: “there is no entry in table T093 for the chart of depreciation or company code”. I checked table T093 and all entries are in there!
    What else I have to correct?
    Regards
    Cordula Speh

    hi ,
    yours is customizing problem only, check all steps once again in customizing. T093 is initial customizing for asset accounting. just go through below things and check based on this order all customizing.
    1.     Copy Reference Chart of Accounts Depreciation / Depreciation Areas.
    2.     Specify Description of Chart of Depreciation (COD).
    3.     Copy / Delete Depreciation Areas.
    4.     Creation of  ‘0’ Tax Codes for Non-Taxable Transaction.
    5.     Assign Tax Codes for Non-Taxable Transactions.
    6.     Assign COD to Company Code.
    7.     Specify Account Determination.
    8.     Create Screen Layout Rules.
    9.     Define Number Intervals.
    check one by one and if you find anything missedout do it, i think max you prblm solve, if not give some more details about your problem.
    thanks and regards
    vk.

  • Convert application error to system error

    Iam facing an issue in BPM, Iam triyng to access to a webservice using synchronous send step, and I ahve an exception branch to catch the syetm error and fault message. Eventhough I specified fault messages, application error was not properly recognized. For this Iam trying to write an adapter module.
    In that adapter module I want to access the error in runtime environment, massage the application error look like system error.
    Iam lookign for info like, how do I access the error in runtime environment and covert it to look like system error so that BPM could see that as a system error.

    Hi Vamsi,
    As per my understandiong Application errors different with System errors. so i dont think we can convert application error to system error.
    you need to find other way to handle applications error.
    Regards,
    Raj

  • ERROR"Unable to convert sender service to an ALE logical system,(Urgent)

    Hi All when i am not giving the sender service address in the Receiver Aggrement i am getting this perticular error .
    <?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>Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Transaction IDX1: Port SAPRP1, client , RFC destination contain errors</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    ==========================================
    And if i am giving this one then i am not getting any such error rather i am getting another error "Unable to convert sender service to an ALE logical system" for this also i have checked the LS system name in the Adapter specific Identifier and the logical name are exactly same. But still i am getting this error
      <?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 sender service to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    =============================================
    Still i am getting this error can anyone please let me know what to do now..??
    Please treat this as urgent

    Hi,
    This error is caused when Sender System name does not match the logical system name of partner. As you mentioned you have done all the steps to ensure that, here's a checklist that could be helpful:
    1. Check adapter specific parameters for sender system.
    2. Maintain header mapping in receiver agreement and ensure that sender service name provided is same as business partner name required in R3 and business partner type is LS.
    3. This may sound very basic, but ensure that checkbox for 'Apply control record from payload' is not checked and if it is then the values passed through payload are appropriate.
    Hope this would be helpful.
    Thanks,
    Bhavish

  • Error :  Entry 4 not in table EMSEG (system error) in MIGO

    Hi All,
    I am getting the below error while cancelling the material document in MIGO.
    Error :  Entry 4 not in table EMSEG (system error)
    Please provide any information on the same issue.
    Thanks & Regards,
    Ashish Dholi

    you can only know it after you have read, justified and  implemented the notes.
    That is your work, it cannot be made by anyone here.
    In general, if OSS notes are supposed to fix program errors, then it will usually not harm to implement them, you will get it anyway with the next hotpackage.
    if your issue is caused by a program error, then there is no workaround to applying a OSS note to get your issue fixed.

  • Error "Unable to convert the sender service  to an ALE logical system"

    Hi,
    I send I message from XI to R3 and I get the error "Unable to convert the sender service  to an ALE logical system" in transaction "sxmb_moni". I've configured the idoc-adapter, as following:
    -I have created a business system "r3sys_bs" with a logical system "r3system". This business system is the idoc-adapter. This logical system is also created in transaction "bd54". In the ID I have assigned the business system the logical system (adapterspecific identification).
    So, this error still appears.
    Can anybody help me please?
    Regards
    Stefan

    Hi,
    our scenario is JMS --> XI --> IDoc
    so, I have created a business system "jms_bs" without a logical system in sld, that I use for the jms-connection to another software. so, the business system is a "third party".
    Then I have created a business system with assigned logical system for the IDoc-Receiver as I in my first posting mentioned.
    Which of both business systems need a logical system?
    Thanks
    Regards
    Stefan

  • Unable to convert the sender service XID_900 an ALE logical system Error~

    Dear Expert:
    I received a IDOC Ack but there is an error ocour~
    Unable to convert the sender service XID_900 an ALE logical system
    XID_900 is our business system that config in SLD.
    it's very weird ....sender server should be like point to our BPM isn't?
    Regards
    Jack Lee

    hi,
    >>>it's very weird ....sender server should be like point to our BPM isn't?
    this means that your XID_900 business system in Integration directory
    does not have adapdater specific identifiers filled in
    it has nothing to do with a BPM
    also check out my blog:
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    Regards,
    Michal Krawczyk

  • ERROR" unable to convert the service as an ALE logical system"

    Hello All,
    In SOAP to IDOC scenario I tested the webservice with the client tool. Its hitting the integration engine but its throwing up an error" unable to convert the service as an ALE logical system". How can I maintain a logical system for a service as its outside our landscape. Can any one let me know how to proceed with this.
    Looking forward to expert comments.
    Thanks and regards,
    Neelima

    Hi,
    Check this blog by Michal.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    Regards,
    Sudheer.

  • E71 system error with meeting entry

    Hello everyone, I just bought my E71 and I have the following problem: when I try to add a meeting, after i do "done" it gives me:system error.
    when I try to insert a "to do" or memo, it works fine but when I write a meeting I have this error.
    I tried to add a meeting on outlook and then I syncronized, after this I have a "to do" or task on my phone and not a meeting.
    The sync works fine.
    Thanks a lot for your support.

    pippobaudo:
    Thanks for the info. After many redundant backups and original setting realoadings I managed by trial and error to work out that the error is caused by the backup utility whenever you backup calender or todo notes.
    So I fixed it by making a full backup of my phone, but excluding calender and todo notes. Then I reset to original settings, and loaded the backup. Works fine now.
    Its a bit of a hack that the backup utility cannot restore calender entries correctly...

  • SYSTEM ERROR, IDOC_ADAPTER, Unable to convert ALE to logical system

    Hi,
    I just wanted to check when i am using SXMB_IFR for monitoring then in message monitoring ---> if i check for Integration server as a whole i Find error as SYSTEM ERROR but if i check only for Adapter engine I get all the idocs successful.
    So what we have to monitor the whole integration server or adapter engine only

    saras,
    When you see successful in the Adapter Engine, what it impliesis that the Adapter Engine has picked up the message ( file in your case ) and then passed it to the Integration Engine for processing ( this is where the actual pipeliining steps take place). As far the adapter Engine is concerned the message has been passed to the integration engine and so its job is done.
    The error you see in Integration Server is becuase it includes the status of the messge in both the adapter Engine and the Integration Engine. You messages has errored out in the Integration Engine and so the problem!
    Just rememebr this terminology --> Integration Server is the runtime of XI which in turn contains the Adapter Engine and the Integration Engine.!!
    Regards,
    Bhavesh

  • Abort System Error in Program SAPLRRV and for RRSV_CHAVL_TO_VALUE_CONVERT

    Hello SDN
    While refreshing a query in a Workbook, I have received this error message and getting disconnecting form the BW server.
    "Abort System Error in Program SAPLRRV and for RRSV_CHAVL_TO_VALUE_CONVERT"
    Does anyone has any idea? It is happening in Production and need to fix it as soon as possible.
    Appreciate any help and points will be assigned for useful information.
    Thanks
    kumar

    Hi Dinesh
    It is stopping at the BREAK-POINT in Function LRRMSU13(RRMS_X_MESSAGE)
    variable_screen=X&template_id=0QUERY_TEMPLATE
    In the messages , For generation, it display:
    &CAUSE&
    The query contains selection elements with "Constant Selection". Such a
    query cannot be run in the read mode 'Read Everything at Once'.
    &SYSTEM_RESPONSE&
    The read mode is automatically converted.
    &SYS_ADMIN&
    In the Variables, I see
    &CAUSE&
    Variable <(>&<)>V1& is used in the query in such a way, that an
    optional entry is not possible.
    For example, you might be using an "Exclude", or the variable might be
    connected using OR to additional selections for <(>&<)>V2& in the
    global filter, but is still displayed in the columns selections.
    It is also not possible to use an optional parameter variable to fill
    an interval selection in either the from-field or the to-field.
    &SYSTEM_RESPONSE&
    &WHAT_TO_DO&
    If you are able to accept the mandatory entry, you need not do
    anything. Otherwise you must work with several variables in the query.
    You can use an optional interval variable to do this.
    &SYS_ADMIN&
    For Key Figs :
    &CAUSE&
    Quantities are multiplied with values for the key figure &V2& (&V1&).
    This is not sensible.
    A basic key figure was probably defined that contain a price. Only
    addable amounts should be written on the database. Ratios and prices
    are calculated as key figures. Therefore, the system maintains the
    correct sequence, meaning summing takes place on every place and then
    the quotient is formed.
    If a 'price amount' is saved as a basic key figure after all then the
    'non-aggregated indicator' can be undone using 'Change key figure'.
    Therefore, the system carries out the multiplication (or division)
    before the summing. The key figure is then assigned to the group 'Other
    columns'.
    &WHAT_TO_DO&
    Please check the definition of the key figure &V2& (&V1&).
    <DS:TRAN.KDNN>Check or change key figure &V1&</>
    Can you please let me know how to fix this issue?
    Thanks
    Kuamr

  • When trying to use MobileMe I am getting an error message: AppleSyncPref.exe - Entry Point not found  Can you help?

    When trying to use MobileMe I am getting an error messgae: AppleSyncPref.exe - Entry Point not found  Can anyone assist?

    MobileMe no longer exists...that system was discontinued and merged into iCloud.
    Your old MobileMe email addresses shoule still be valid, or convert into some form of user@ me .com or icloud . com.

  • Logical System Error

    Hi AlL
    I am working on the JDBC TO IDOC Scenario and when testing I get error:
    Unable to convert the sender service ABC_Service to an ALE logical system  
    I check on the SLD under the Business System and what I find is that there is no LOGICAL SYSTEM NAME.
    How to make the PI System to keep up the LS, on the TCode BD54  I created it
    Role:  
    Pipeline URL:  
    Group:   
    Technical System: PI1 on saptrain1 Change...
    Client: 001 of PI1
    Logical System Name:  #######
    Thanks
    Yonela

    Hi Guys
    On my JDBC TO IDOC Scenario when testing on the MONI I get the below error:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message canceled
      -->
    - <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="XICACHE">BUSINESS_SYSTEM</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>NO INTEGRATION SERVER</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    but on the SLD my Business System looks like this:
    Role: Integration Server 
    Pipeline URL:   http://saptrain1:8000/sap/xi/engine?type=entry
    Group:    No group assigned
    Technical System: PI1 on saptrain1 Change...
    Client: 001 of PI1
    Logical System Name:  LSJDBC
    I have done 
    with this user : PIDIRUSER i have done the full cache
    http://saptrain1:8000/CPACache/refresh?mode=full
    CPA cache refresh (mode=full) successfully executed in 30937 milliseconds.
    but when running
    http://saptrain1:8000/sap/xi/engine?type=entry  on the browser i get :
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Header />
    - <SOAP:Body>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Client</faultcode>
      <faultstring>Empty HTTP request received</faultstring>
      <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
    - <detail>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
      </SAP:Error>
      </detail>
      </SOAP:Fault>
      </SOAP:Body>
      </SOAP:Envelope
    What I am I missing out
    Thanks,
    Yonela

  • URGENT: system error - Maual restart possible

    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

    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

  • Error: Unable to convert the sender service SC_PO_fileidoc to an ALE logica

    Hi,
    I'm currently creating an Idoc adapter receiver with BPM. However I've received an error at the second stage from BPM - IDOC. It gives the error "Unable to convert the sender service SC_PO_fileidoc to an ALE logical system". Appreciate if anybody can help me.
    Cheers
    Zubair

    Hi,
    This weblog will help you resolve this issue.
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    under the section "Intgeration Process as the receiver system"
    Check whether you have assigned the Logical system (LS) name to the integration process in the adapter specific identifiers (Integration Directory). Also check whether an entry for the LS is available in the SLD for the sender Business system.
    Regards,
    Sridhar

Maybe you are looking for