Writing trace to ABAP proxy

Hi Friends,
is there any way to write trace message in ABAP proxy (server proxy).
I have a case where during processing of the inbound proxy i want to populate some information messages as trace, which can then be seen from SXMB_MONI-trace of the message.
I saw that only fault messages can be raised. But how to write a normal trace .
Any help will be useful -& rewarded with points.
thanks
PSD

Hi Prabhu,
just as in message mapping we can write a trace in udf , i want to do the same for ABAP inbound proxy message.
So when user logs on to the SAP R/3 system & sees the message trace (in SXMB_MONI), he should be able to see the information messages triggered from within the inbound proxy method (EXECUTE_ASYNCHRONOUS) .
My business requirement is , i am creating a Handling unit using the data in the proxy msg .
So i want to log all the HUs created during the processing of the inbound proxy message in R/3.
So trace in SXMB_MONI should be as follows :
" HU <1> created"
"HU <2> created "
...& so on.
This way the user can see the message trace & figure out all the data that was processed & what was the end result.

Similar Messages

Error while usinjg the JDBC to ABAP Proxy Scenario

Hello Rocks,
This is my scenario like JDBC --- Pi --- ABAP Proxy
while i am given a sender side jdbc XSD structure is like this
VWENTITYAGGREMENT
Row             1-unbound occurence
      POOL_ID   0-1 occurence
      CUST_ID
      AGREEMENT
       PRODUCT_ID
        CONTRACT_TYPE
        CONTRACT_TYPE_DESCR
        AGRMNT_STATUS
        STATUS_DESCR
          EFFDT
         TERMINATION_DT
         ADD_DT
         ADD_TM
while i am writing a select query in Sender JDBC CC is like this
SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement.
Here i am getting this Error message like this :
Error Description: Database-level error reported by JDBC driver while executing statement 'SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
So please give me your valuable inputs !
Regards,
Ravi.

Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
Did you confirmed the name POOL_ID as suggested?
Why is the tablename different (check the case) in the query that you make and in the XSD structure that you mentioned......check if this is causing the problem.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 4, 2010 10:24 AM

Business partner replication using ABAP proxy

Hello,
I want to send vendor master data records from the MDM to SAP SRM. There is a standard ABAP proxy interface in the SRM for this purpose and this proxy is also being used by the standard PI content for MDM.
Do you have any experience with this interface? I have done some test cases and I missed the logging. In PI I don't get any feedback if the business partner has been created or not. And in case it was not, there is no detailed error description. Neither in SXMB_MONI in the PI nor in the SXMB_MONI in the SRM.
Is there any other monitoring tool for this interface?
Would you recommend to use this interface in production, or would you prefer to use the BAPI interface?
Any comment appreciated.
BR,
Jürgen

Hi Jürgen,
yes I worked on a similar scenario, we were distributing customers to CRM, which is the dual of vendors in SRM, and at the end is just a different role of the business partner.
The Proxy I used is the standard proxy ABABusinessPartner, which is part of the standard content, and we never had problem using this object (productive since more than a year).
What is strange to me is that you do not see any trace in SXMB_MONI, you should see the message in both XI and SRM and when a message is in error you should see the trace there with a description of the issue.
Regarding Acknowledgement I think you have to configure MDM to request an acknowledgement since the ack only comes back if the first sender of the message request it.
Hope this help.
Ciao,
Sergio

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

Abap Proxy = Web Service - Connection timeout

Hi Experts,
I request your help on some issue we encounter actually on our Web services interfaces.
We have sceanario in which from SAP, we are sending a message to PI via Abap proxy.
PI then, send the message to the external system via a Web Service (we have configured the URL and authentification values).
When we want to test the scenario we have an issue.
- We see in SXMB_MONI message has status sent succesfully
- When we check the external system, we see that no message is received (no trace of message from PI).
- Then we check on PI runtime workbench, we see in the receiver communication channel error saying "Connextion Timeout"
(in detail: SOAP: call failed: java.net.ConnectException: Connection timed out")
We would like to investigate the issue.
Have you already encountered this kind of issues ? And how we could investigate the root cause here ?
And thanks for ur help,
S.N

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

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

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<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 = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</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 = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</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 + call qRFC now...</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="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</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 pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</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>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

ABAP Proxy Generation

Hi All,
I trying to create the ABAP Proxy(OUTBOUND)
I have created the message interface in XI and created outbound proxy in R/3 by using SPROXY Tcode.
Created the ZProgram by calling class.
and completed the Configuration steps in integration builder like (Receiver determination, Interface determination, Receiver Agreement and Receiver communication channel).
When I trying to execute Zprogram in R/3 it is giving "Proxy creation do not transport" and I did not see any message in SXMB_MONI in XI and R/3 too.
Is there any thing needs to be created in XI or R/3.
any help how to trace this..
Thanks
M

HEY MURALI,
In short : these are development steps for ur proxy :
1. generate the proxy based on a package of 4 layer strucutre.
2. After generating the proxy , activate it.
3. i will always test my proxy , at this level so that i can see its working and no issues w.rt. calling from z-program
4. i will now go and check the working of z-program and activate and execute it. you can also check if the earlier steps were successful , w.r.t debugging ur program.
5. Also check the settings/ configurations if anything missing.
Hope this helps
Vara
[PLEASE REWARD FOR POSTING]

Abap proxy call failed

Hi,
I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.
Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,
an error occured on the R3 system:
PROTOCOL.LOOP_IN_MESSAGE_ROUTING
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <SAP:Context></SAP:Context>
 <SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>
 <SAP:Text language="EN"></SAP:Text>
 </SAP:ErrorHeader>
 <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">
 <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type></SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type></SAP:Type>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 <SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>2.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type>PROXY</SAP:Type>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 </SAP:HopList>
 <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">
 <SAP:From>
 <SAP:Name>WebServer</SAP:Name>
 <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>
 </SAP:From>
 <SAP:To>
 <SAP:Name>UPG</SAP:Name>
 <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>
 </SAP:To>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
 <SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>
 <SAP:Direction>Response</SAP:Direction>
 <SAP:Document></SAP:Document>
 </SAP:MessageHeader>
 <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
 <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
 </SAP:InternalAttributesHeader>
 </SOAP:Header>
 <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
 <SAP:Payload xlink:href="cid:[email protected]">
 <SAP:Document>TraceDocument</SAP:Document>
 </SAP:Payload>
 </SAP:Manifest>
 </SOAP:Body>
 </SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:[email protected]
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
 <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
 <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</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="1" type="T">system-ID = UPG</Trace>
 <Trace level="1" type="T">client = 100</Trace>
 <Trace level="1" type="T">language = E</Trace>
 <Trace level="1" type="T">user = YLEBLEVEC</Trace>
 <Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>
 <Trace level="1" type="T">* * </Trace>
 <Trace level="1" type="T">* * </Trace>
 <Trace level="1" type="T">**************************************************** </Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
 <Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>
 <Trace level="1" type="T">PLNAME = SENDER</Trace>
 <Trace level="1" type="T">QOS = BE</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
 <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
 <Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>
 <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
 <Trace level="1" type="T">URL for integration server read from global configuration </Trace>
 <Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
 <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
 <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
 <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
 <Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>
 <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>
 </SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END
I guess the error occurs before the call of my proxy. Can anyone help?
Thanks,
Yann

Hi,
>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?
I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right
further reference (XI configuration guide):
Connecting Business Systems with an Integration Engine to the Central Integration Server <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)
>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?
yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)
no need for a second client on R3 side:)
sorry if I confused you with my response
Regards,
michal
Message was edited by: Michal Krawczyk

How to create ABAP Proxy for SSL secured ABAP Service

Hi guys,
I try to set up transport security for my ABAP web service. The service should be called via a ABAP Proxy.
These are my steps to create the ABAP web service:
1. Create function module (se80)
2. Create web service (web service definition) (service wizard)
2.1 Authentication = STRONG
2.2 Transport Guarantee = BOTH
3. Activate service (wsconfig)
4. Control service (wsadmin)
Afterwards I tried to create the proxy but when I add the WSDL URI I always get an
HTTP error (return code 407, message "ICM_HTTP_SSL_ERROR")
I tried to find a "How to" but I was not successfull. Also the saphelp http://help.sap.com/saphelp_nw04/helpdata/en/65/6a563cef658a06e10000000a11405a/frameset.htm was not helpful for me.
Hopfully you can help me! Every comment is appreciated!
Regards

I advise to have a look into the ICM trace file (dev_icm) - either by using ABAP transaction ST11 or SMICM.
There you should find error details. Most likely it's about the "chain verifier" complaining that he's unable to verify the certificate of the communication peer.
In that case [SAP Note 1094342|https://service.sap.com/sap/support/notes/1094342] might be helpful.

Steps in BW for intigration with PI system through ABAP proxy communication.

Hello Experts,
Need your help.
We need to extract data from PI system through ABAP proxy communication. Kindly suggest the steps need to be perform on BW side.(from data source creation to setting up the delta queue )
Thanks,
Arpan

Hi Raja Sekhar,
Thanx for the quick reply.
If i have got you point right, you are telling me to right a program that will fetch the PO's and push the data into our Interface.
Let me explain you the complete scenario, we already have a ECC to SUS thrgh PI implemeted for the same PO's generated. Our requirement is that depending on the vendor details in PO's we have got to route the PO details to either SUS or BPM.
I had thought of writing a prgm but the abapers feel that a standard BADI for the same would lessen their efforts.
Meanwhile can you explain with a little more detail the standard approach you are referring to... probably some material relating to this would help us...
thanx a lot..
waiting for your reply,
Nandan

ABAP proxy to FILE - filename partly build from PAYLOAD

Hi
I have an ABAP proxy sent from SAPBACKEND ->PI->FILE
I need to build the filename dynamically based on a template "FILENAME"+variable1.XML
Variable 1 is from the payload - so a field in my XML - "FIELDVAL".
How to extract the value from the payload and build the filename dynamically?
Can I use substitution values in the filename in the CC? or must I build up the entire filename in UDF?
We are using PI 7.11
Cheeers

Hi,
You can do this either by Dunamic configuration (Writing a UDF) OR by variable substitution..
Check below links
http://wiki.sdn.sap.com/wiki/display/Snippets/SAPXIDynamic+Configuration
http://wiki.sdn.sap.com/wiki/display/XI/CombiningthreedifferentaspectsofPIinoneshot
/people/shabarish.vijayakumar/blog/2009/03/26/dynamic-configuration-vs-variable-substitution--the-ultimate-battle-for-the-file-name
Amol

DYNAMIC_CALL_FAILURE - ABAP Proxy Inbound

I have the following error when I try to test a proxy interface with the data coming into ECC 5.0 System.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZSMDCL_MI_FUSION_PRODUCT_MAINT</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a function module which sends a message out depeding on the return status of a BAPI. The proxy is giving the above error when it calls this function module.
reg
reg

Hi Naveen
Try to catch exception in proxy itself
Use follwing link

http://help.sap.com/saphelp_nw04/helpdata/en/a1/082589fc4246f09793039d5fb01a17/content.htm
For Catching Exception in Proxy
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
Thanks
Abhishek
***Please Reward points if helpful********

Consume WSDL in ABAP proxy : Issue with name space

Hi,
I was trying to consume a WSDL in ABAP and I have created ABAP proxy using wizard in SE80 and also did the LPCONFIG.
While calling the proxy methods it is throughing the "authrization failed" error because of the following issue.I have successfully executed same WSDL from some third party tools with out error.only difference I have observed in SOAP request is, Third party tools passing all name spaces at envelope level but in ABAP proxy it is not passing all name spaces at envelope level.
1. SOAP genarated from WSDL in third party tool.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://schemas.xxxxx.com ">
<soap:Body>
 <tns:GetKMContent>
 <tns:request>
 <tns:clientID>1</tns:clientID>
 <tns:employeeID>307478</tns:employeeID>
 <tns:languageCountryCode>en-US</tns:languageCountryCode>
 <tns:wscVariables>
 <tns:empcountry>US</tns:empcountry>
 </tns:wscVariables>
 </tns:request>
 </tns:GetKMContent>
</soap:Body>
</soap:Envelope>
SOAP genarated from WSDL in ABAP proxy.
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
<n0:Trace xmlns:n0="http://www.sap.com/webas/630/soap/features/runtime/tracing/">
<TraceLevel xmlns="http://www.sap.com/webas/630/soap/features/runtime/tracing/">Full</TraceLevel>
</n0:Trace></soap-env:Header>
<soap-env:Body>
 <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com ">
 <nr1:request>
 <nr1:clientID>1</nr1:clientID>
 <nr1:employeeID>307478</nr1:employeeID>
 <nr1:languageCountryCode>en-US</nr1:languageCountryCode>
 <nr1:wscVariables>
 <nr1:empcountry>US</nr1:empcountry>
 </nr1:wscVariables>
 </nr1:request>
 </nr1:GetKMContent>
</soap-env:Body>
</soap-env:Envelope>
I was trying to use the SOAP genarated in ABAP proxy in thrid party tool and end up with same "authrization failed " error. If I move the name space nr1 from <nr1:GetKMContent xmlns:nr1="http://schemas.xxxxx.com "> GetKMContent node to soap-env:Envelope <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nr1="http://schemas.xxxxx.com "> then it is working fine.
Question :Is there any way in ABAP proxy to pass name space at soap-env:Envelope level or is there any way to change the SOAP request once it is genarated from ABAP Proxy?. Is there any API to change SOAP information?
Thanks,

Hi Kavitha,
I am also facing the same issue.
Could you please share the solution if you have solved this.
Thanks,
Arun

Abap Proxy: ICM_HTTP_FAILED_ERROR

Hi
We are trying to connect the Ecc6 to XI using the ABAP Proxy:
we have done the following settins in Ecc6
Created the following RFC
1. LCRSAPRFC---->Pointing to SAP XI
2. SAPSLDAPI---->Pointing to SAP XI
maintained the SLDAPICUST TC Pointing to SLD of XI server
SLDCHECK is working from Ecc6
I have also created the connection type 'H' pointing to XI pleae see the error.bmp file for details, the problem is when i execute this RFC Dest created it is giving me ICM_HTTP_CONNECTION_FAILED.
All the servicess in the SICF is activated, in SMICM i have the HTTP servcie and is active.
I have also configured the ECC6 SXMB_ADM accordingly:
Role of busniess system -
> Application System
Corresponding Integ.server-->dest://(RFCcreated type H)
i am also getting the following error when i try to check the Sproxy
Run->Sproxy error:No connection to Integ Builder found.
when the run the following reports to debug this i am getting following outputs
SPROX_CHECK_IFR_ADDRESS: http://nwserv04s:50000/rep
SPROX_CHECK_HTTP_COMMUNICATION: HTTP communication contains errors
SPROX_CHECK_IFR_RESPONSE: HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")
SPROX_CHECK_IFR_CONNECTION: Integration Builder data not understood
And also in the SMICM trace level the error details it is showing me the entry for the default port 8080, when i check after executing the RFC type H.
kindly let us know where i have to look into
regards
suresh

Moorthy
1) SMICM--> Services->Find for Http in XI system: check the port in XI box with port used in SM59 of ECC system : Checked my HTTP Service port in XI is 8000 and same port i am using in SM59 on ECC
2) Same in ECC : ECC Http service is also active and port is 8001 ( i am using XI port in SM59 of Ecc)
3) User ID and Passwords used in the SM59: PIAPPLUSER and PWD
4) url used in the SM59 ? type this url with port in the browser and check what is the status ? : the pth string is /sap/xi/engine?type=entry Host:Nwserv04s Service: 8000
this is the link: http://nwserv04s:8000/sap/xi/engine/?type=entry
regards
Nisar

Writing trace to ABAP proxy

Similar Messages

Maybe you are looking for