ABAP Proxy - Queue XBTS*

Dear experts,
I'm fairly new to proxies. I have set up a interface in XI and generated a proxy from this on a sending APO system. This system sends out orders.
Now I checked, and every time I send out some order, it uses queue XBTS.... of the APO system.
The strange thing to me is that XBTS* is registered as an INBOUND queue in the APO system. It is displayed in the QIN Scheduler. How is this possible? Is it like a pull system from XI? What are the inner workings of the proxies?
Thanks in advance.
Kind regards.
* Will reward points for helpful answers

Hi Prakash,
Generally, the queue gets locked, if there is message in the queue, which still in processing, since long time. so by re-registering the queue the issue will be resolved. Check the definition of the queues and define 1 queue for handling message greater than certian size.
using t-code 'sxmb_admin' > 'configure filter for queue prioritization', define queue.
and more over in 'smqs' , increase the number of connections and max runtime for that particular target system (which has issues). You see this kind of issues in PROD system commonly, since, production system will have large number of message to be processed at the same time,
hope this will help you to fix the issue.
with regards,
rajesh.

Similar Messages

Response message error in queue when using ABAP proxy

I am using an abap proxy for the first time, and some of the response messages are getting stuck in the sender's (R/3) inbound queue. To resolve them, I have to either reset the status or execute the LUW. Sometimes, this doesn't even work.
Here is my "asynchronous" scenario:
R/3 -> <proxy> -> PI -> <file adapter> -> File
The R/3 system that I'm using has not used PI before, so I'm thinking something is missing from the set-up on the R/3 side. On the errors I finally do get to process, I get the following error in the SXMB_MONI on the sender (R/3) side (the PI SXMB_MONI shows successful). Can someone help me understand what a response message is and how it is different from an acknowledgement? Also, help me to understand what could be causing the response messages to get stuck in the R/3 queue.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
 - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <SAP:Context />
 <SAP:Code p1="MessageId"
 p2="4962B2EDB60A003BE1008000A2844D1A"
 p3="00000000000000000000000000000000"
 p4="">PROTOCOL.WRONG_HEADER_IN_RESPONSE</SAP:Code>
 <SAP:Text language="EN">Response message header contains the value 00000000000000000000000000000000 in element MessageId instead of the expected value 4962B2EDB60A003BE1008000A2844D1A</SAP:Text>
</SAP:ErrorHeader>

Ultimate testing tool for services is soapUI (Freeware)
http://www.soapui.org/
If you can invoke your service from soapUI and you receive a response, then PeopleSoft is working fine and the request handling in the calling system is incorrect.
Try downloading soapUI and try invoking your service (not that a fan of SendMaster).
Hakan

File to ABAP Proxy (problem with inbound queues in R3)

Hi,
In File-XI-ABAP proxy scenario, XI is successfully picking up file and sending it to R3.
But in R3, an inbound queue is created in SMQ2 transaction code and I solved the same to automatically process the Queue by registering that in SMQR transaction code. But even though the inbound queue doesn't appear in SMQ2 (which means that it is processed successfully) it doesn't call the method EXECUTE_ASYNCHRONOUS. Can anyone help me whether I need to do any settings to run that method?
Also can anyone help me, after the inbound queue is successfully processed in SMQ2 transaction, what would be the next step to watch what exactly that queue has done?

Hi,
Please check the program code for Server ABAP proxy.
This will show you the trigerring of Proxy on inbound side.
ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
For Queues, you can go to SMQR and check for the register queue. Select and double click on it. If anything is stuck up then you can see in it. Even same with SMQ2
Thanks
swarup

Http to Abap Proxy communication with multiple queues generation in Recevr

Dear SDNs,
I need some help in the following scenario, appreciate your suggestions and help .
I am receiving the messages from sender to PI on http posting, from PI I am sending the message to SAP system using receiver xi communication channel ( receiver is abap proxy).
Sender will send the messages in QOS=EOIO, QUEueID=XXXt_100 etc parameters, when large volumes cases, it is getting delayed to process it using a single queue.
We are thinking to dynamically generate multiple queues in PI and send the same queue ids to receiver SAP system to process all the messages quickly in SAP System also.
Help /Clarifications needed:
1. XI receiver communication channel in pi does not provide any options to generate dynamic queue id based on payload content (using dynamic configuration) and sent it to SAP.
2. Module Tab in receiver communication channel also got disabled to add custom adapter modules, can we add custome adapter module on xi receiver channel to generate dynamic queue id ?
Really appreciate your immediate help and suggestions.
Thanks.
Suraj.

Dear Praveen,
Thanks lot for the immediate reply, we need to use EOIO, as the messages need to be processed in the same order we send and receive, there is no flexibility in QOS=EOIO, Appreciate if there is any other thoughts?
Thanks In Advance.
Suraj.

Queue Stucked - Exactly Once Async Abap Proxy

Hi Guys
I have several JMS->Xi->Abap Proxy scenarios in my production environment, the Abap Proxies servers are in a SAP IS-OIL 4.72 with a SAP WEBAS 6.20 and the XI is the XI 3.0.
Some of the Abap Proxies calls are asynchronous, and when one of the abap proxies has an sysfail error (for example), it stuck the entire queue, and this is causing some problems, for the other calls (interfaces) that are not being processed until the "bad" abap proxy is "solved".
I know that we can schedule a job that reprocess the call but imagine that the problem is still not solved, I still have the other calls waiting, ie, I am putting in jeopardy some interfaces because of one error.
It seems that this queue management happens because SAP IS-OIL is treating all asynchronous AbapProxy calls as EOIO calls.
1. Is my previous assumption correct???
2. How can I invoke from SAP XI3.0 an asynchronous Abap Proxy just with EO quality of service???
3. How can I setup the CCMS to alert when a queue is stucked (please be aware that I have a ERP SAP has a SAP WEBAS 6.20)???
Take Care
PC

Hi Moorthy
> You are calling Proxy from XI right ?
Yes
> What is the source system ?
The source system is a 3rd party app that sends an XML message via JMS to XI, XI then calls the abap proxy that is in our SAP ISOIL.
> You can restrict the quality of service in the
> Outbound Interface..i.e message coming into XI.
>
Are you saying that has to be the 3rd party that has to say to Xi that the async call that XI will have to do to SAP ISOIL has to be EO??? How can this be done?? Is in the Message Interfaces configuration - Integration Repository???
Remember that I'm having queue problems in SAP ISOIL, where the abap proxies are processed !!!
> Here is the link for CCMS -
> http://help.sap.com/saphelp_nw04/helpdata/en/e5/5d1741
> b393f26fe10000000a1550b0/frameset.htm
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2894
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2895
> https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/
> 2777
>
Thanks a lot for the links, it seems that is good head start.
However I'm concerned that because my SAP ISOIL has the SAP WEBAS 6.2 (old Integration Engine), the CCMS features that are explained in the links will not work in the old version. Remember that I've probably have to configure the CCMS in XI3.0 (my integration platform) and SAP IS-OIL my main system, where all abap proxys are run and called, where IDOCS are sent and received, ie, is the point of origin and final point of all my integrations...
That's why I'm so concerned about the stopped queues in SAP ISOIL, I really need full availability in this system (queues), I am talking around 10.000 messages being sent and received... and in the near future will be around 100.000 messages for sure...
> Regards,
> Moorthy
Take Care
PC

PI to ECC via ABAP Proxy - Outbound Queue for HTTP

Dear Experts,
Is there any Outbound Queue for HTTP?
I've a interface scenario where the receiver is SAP ECC and the receiver adapter XI ABAP proxy. As I see in the communication channel the transport protocol used is HTTP. So I think could there be an outbound queue to manage HTTP connection when PI send the data to SAP ECC?
Just like when we are sending IDocs to ECC via tRFC, we could check if the IDoc has really been sent to ECC by checking in tcode SM58 (Outbound tRFC).
In case for ABAP Proxy via HTTP, is there any similar connection to SM58 (IDoc via tRFC)?
Thank you,
Suwandi C.

Hi Kandasami,
Thank you for the reply. I will check for it.
Hi Jens,
Yes, I mean somewhere after the SXMB_MONI in PI and before SXMB_MONI in ECC, is there any queue in between those two?
Thank you,
Suwandi C.

Queue specific ABAP Proxy in ECC

Hello Experts,
I've a service interface abap proxy-based and I wanna assign it to a specific queue of tcode smqr.
My main goal is ensure that every message of one specfic interface will get only one specific queue.
Does anyone knows if it's possible and how?
Best Regards,
Bruno

Hi Stefan,
How about Step no 1 :
1. Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
1.Execute transaction SM59 in the business system.
2.Choose Create.
3.Enter at least the following:
 1.RFC Destination: LCRSAPRFC
 2.Connection Type: T
 3.Description: <your description>
 4.Choose ENTER.
 5.Choose the Technical settings tab page and do the following:
 6.In the Program ID field under Registered Server Program, enter LCRSAPRFC
 7.This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.
Because i have done this configuration in my application but the failed to test connection ?
Regards
Fernand

OBJECTS_OBJREF_NOT_ASSIGNED error while executing ABAP proxy

Hi ,
I am getting the following error when i try to execute an abap proxy .
Unit ID in Background RFC     001EC9D184F702ECAA8DBC7401DC13E0
Name of First Function Module     SRT_SEQ_SCD_DLV_TRM_QRFC_NEW_C
Inbound Destination Name     WS_SERVICE_02DCA4961A0B_IN
Transaction Code                     SE38
Name of qRFC Queue                     SRTQC_001EC9D184F702ECAA8DBC6FE29753DB
Created On                     28.01.2009
No. of Predecessors                   1
Created At                                    12:44:10
Executed At                     12:44:13
Created At (Time Stamp)     20.090.128.114.410,9989340
User name                                     DEVELOPER
Tcode/program                      CL_SOAP_SCHEDULER_QRFC_NEW====CP
ID of Lock in Background RFC     001EC9D184F702DCAA8DBCA25EC41F5E
Lock Reason                     System error; not executed
Background RFC Scheduler ID              1
Message number                       341
Language Key                            EN
Status Text                               Unit has execution errors
Execution State                             Access using a 'ZERO' object reference is not possible.
Number of Called Function Modules     1
Number of Locks                                    1
Commit Check Disabled               X
Message Class                                  0
Message Variable                             OBJECTS_OBJREF_NOT_ASSIGNED
Executed On                             28.01.2009
and in ST22 transaction i am getting the following dump
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Exception         :CX_SY_RF_IS_INITIAL
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "WSRM_CLONE_FOR_SPECIFIC_OPS" "(METHOD)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    An attempt was made to access a component (variable: "ME->M_CTX") with a 'ZERO'
    object reference (points to 'nothing').
    An object reference must point to an object (an instance of a class)
    before it can be used to access a component.
    Either the reference has not yet been set or it was set to 'ZERO' using
    a CLEAR statement.
Please help in solving this issue.
Thanks&Regards,
Hamsa Shree

Hi
Runtime Errors : OBJECTS_OBJREF_NOT_ASSIGNED
Check with the SAP Notes Note
557770 - SAP BP: Short dump OBJECTS_OBJREF_NOT_ASSIGNED
may be you get the exact help
Regards
Abhishek

Message flow in SAP PI 7.31 JAVA only for ABAP Proxy synchronous scenario with Oracle DB

Dear Experts,
I am working on a synchronous scenario Sender ABAP Proxy <===> SAP PI 7.31 JAVA only <===> Oracle Database.I have successfully
configured all the proxy configurations as well both Sender SOAP and JDBC receiver channels are showing no error when pinged from
Cc monitoring in NWA.
1.During testing at Tx SPROXY , I am triggering a message and after 5 minutes I receive an PARSING error message with 2 messages in ECC
local IE i.e. Tx SXMB_MONI.
Note : In NWA , I can see only 1 message that too in cancelled status.
2.Seeing the trace of the messages I assume that the messages have not moved from sender ECC system. I am still confused with flow of message
from the Message Audit log. Audit log of error messages.Could any one share the full Audit log of a successful message generated in SAP PI 7.31 JAVA only.
3.I observed that the QIN Scheduler status in ECC is in INACTIVE status. There is no queue id for 2 messages generated in ECC. Does
it should in ACTIVE status in Tx SMQR..
Regards
Rebecca

Hi Thomas,
Valuable inputs..
1. Since I don't have any audit log for successful message, would you be able to share referring to the
below screenshot whether the message was put into receiver JDBC adapter and JDBC adapter tried to retrieve the Select response from Oracle Database.
2.I have done some setting in Advance mode of the receiver JDBC to increase the time out and other parameters as per SAP note but still the issue is same. If you perhaps have some experience in such scenarios, please share some input so that I can ask the Oracle Database administrator exactly what is required from our side.
3.Regarding the slow response from Oracle , there was some suggestion that the datatype of the request and response should match the column name of the Oracle database. I did that.. Do you have any more suggestion that may be hampering the generation of the response message from the Oracle like SAP note or document.
Regards
Rebecca

Missing asyn abap proxy client message in ECC

Hi,
I have a asyn scenario which an abap program will send data from ECC to PI using abap proxy client. My problem is i notice some of the message was no send to PI. Checked in PI SXMB_MONI no message was found. Any idea where the message was stuck? I check on smq1 in ECC also found nothing in the queue.
Thanks.

Hi ,
KIndly check with the abap program if its thrwing any dump . If every thing is fine with ABAP program then might be its issue of RFC destination . check with transaction SPROXY are u able to connect and your sender interface is reflecting there if yes then double click on your interface open the proxy andthen click on GOto and click on connection test if nay issue is in connection then it will display the error here .might be some rfc DESTINATION is missing or authnetication error .
Regards,
Saurabh

ABAP Proxy - No message in PI

Hi experts,
We are developing a scenario using ABAP Proxy to send an assynchronous message to PI 7.3.
The problem is that the message is sent by ABAP code, but is not shown at SXMB_MONI.
The routing objects were created at Integration Directory, but seems that PI is not processing the message sent by the proxy.
Any idea about what may be wrong?
Edited by: David Tiago Conceição on Jan 5, 2012 2:13 PM

Hi David,
you should catch exceptions and print them out like:
data: l_sys_exception type ref to cx_ai_system_fault,
      l_error_text type string.
CATCH cx_ai_system_fault INTO l_sys_exception.
        l_error_text = l_sys_exception->errortext.
        write l_error_text.
In addtion monitor the ERP / PI queues at SMQ1/SMQ2 - may be will find the message there.
Depending from the results we go further, may be the destination to PI does not work or proxy configuration is wrong or something else.
Regards,
Udo

How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Hi all,
In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
I think ur data is worng,if it is wrong then only u will get this type of errors.
Regards,
Phani

File to Abap Proxy Scenario : No message log in SXMB_MONI

I have a PI Scenario in which a FTP server is polled every 5 minutes, and when it receives any file, file is archieved and abap proxy is called. Few days back it was running perfectly fine. But For last couple of days I am facing strange error.
My File is archived but abap proxy isnot called, neither I get any message in SXMB_MONI.
any guesses what should I do?
Jawed Ali

Hi Jawed,
HOLD means you have given QoS as EOIO in sender channel and the first message got failed and hence all messages are waiting..
Check this thread
Re: PI 7.1 Messages stuck into the Queue of the Adapter Engine
Try resending the messages through runtime workbench->message monitoring->adapter engine
Regards
Suraj

File to ABAP proxy with EOIO

Hi Experts,
I am working on File to ABAP proxy scenario. The requirement is to have EOIO from end to end.
Which means the files have to be sent to target system (R/3) in the same order as they are placed in the file location. I have two questions regarding this.
1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
Please provide your valuable inputs.
Thanks and regards,
Prasad

Hi,
1. Do I have to create 2 queues, one in PI and one in R/3 to acheive this? In File Sender CC we have option of specifying queue name but in XI Receiver CC, I do not see such option. How to handle this?
1 queue is okay. Just specify it in the Sender File CC.
2.For picking the files from folder if I use NFS, then I have option of specifying 'Processing Sequence' as 'By Date' to pick the files based on timestamp. But if I am using FTP, how can I make sure that the files are sent to Integration engine based on timestamp?
Processing Sequence is not supported for FTP and is only for NFS.
If you have to use processing sequence, then do an FTP, bring the files to an NFS directory and then use the processing sequence accordingly.
Hope this helps.
Regards,
Neetesh

IDOC to abap proxy- Receiver Service Cannot be converted into ALE logical

Dear all,
I have idoc to abap proxy -
R3 to SRM scenario.
I am getting the error Receiver service cannot be converted to ale logical system.
I have check the receiver bs SRM_BS , adapter specific attributes ... im getting the logical system ( this is not the problem)
i am using receiver XI adapter
with XI 3.0 as protocol
and http destination with /sap/xi/engine?type = receiver
i can see the data in the moni of receiver SRM system but it shows a red flag
pls help

Hi kiran,
i have checked all the RFC destinations ... seems OK
problem is in SRM moni .. sender service and sender interface are not visible.
trace ::::
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</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 = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:03Z CET</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 = DD2FF717DAE395F186DF001560A1C7CB</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</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 *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</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 RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SR5</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCADMIN_SR5</Trace>
<Trace level="1" type="Timestamp">2008-06-01T16:27:04Z CET</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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <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="Inbound Framework" />
- 
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o3314" />
</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="o3314">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o3313" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1564</CONTID>
</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="o3313">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>496</PROGID>
<CONTID>1738</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_DYNAMIC_CHECK />
<CX_AI_APPLICATION_FAULT />
- <CX_BBPX1_STD_MESSAGE_FAULT>
<AUTOMATIC_RETRY />
<CONTROLLER />
<NO_RETRY />
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</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="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>
fault message says the sender is not having logical sys...but my sender sys is showing logical system in adapter specific attributes
pls help
points will be awarded

ABAP Proxy - Queue XBTS*

Similar Messages

Maybe you are looking for