Asynchronous ABAP proxy
hello everybody!
i'm working with PI 7.1
i create a interface ABAP proxy -> PI -> file
so is a async interface.
every step was created succesfully.
When i try to call proxy from my abap program or from test tool in SPROXY transaction i don't see any message in monitor.
No file arrived, no errors in log , (SM58, ST22, SM21, integration monitor)...nothing.
i tryed to change the Service Interface and set Syncrounous mode.
so now the file is arrived!!!!!! but... i have error in message monitor because (correctly) it's expecting a return mapping.
where is the problem? can i use this scenario?
thanks!
PS: I prefere find a solution without use the sync async bridge.
yes of corse:
in IR
MessageType_IN
MessageType_OUT
MessageMapping between the 2 MT
a service interface SI_SP2FS_OUT Outbound and Async
a service interface SI_SP2FS_IN Inbound and Async
a Operation mapping between SI_SP2FS_OUT and SI_SP2FS_IN
In ID
Communication Channel to FTP folder
Receiver determination with follow parameter:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
receiver party : *
receiver communication Component : *
Configured receivers: FTP_DEV
Interface Determination:
sender communication Component : SAP_DEV
sender Interface : SI_SP2FS_OUT
sender namespace : http://mynamespace
Receiver Agreement:
sender communication Component : SAP_DEV
receiver communication Component : FTP_DEV
receiver Interface : SI_SP2FS_IN
receiver namespace : http://mynamespace
In R3 abap side i created proxy pointing to SI_SP2FS_OUT with SPROXY transaction.
Similar Messages
-
Timeout Error in Call Transaction on Asynchronous Abap Proxy
Hi Gurus!!
We have a problem with a Call Transaction on Asynchronous Abap Proxy. When the process of Call Transaction (transaction CO02) takes more than 10 minutes, the process is cancelled with sy-subrc 1001 and the Abap Proxy continues with the execution. Strangely, there is a short dump in ST22 on transaction CO02, although on the ABAP Proxy we don't get any dump.
When this process is called from a Background Job no dumps are get.
Somebody knows if there is a problem with the Asynchronous ABAP Proxy executing CALL TRANSACTION statementent?
Thanks and regards,
Manuel.and the message after recording is
Number 1
Transaction F-22
SY-SUBRC 0
Messages
FB01 SAPMF05A 0301WEZ001 066
FB01 SAPMF05A 0300WEZ001 066
FB01 SAPMF05A 0300EEZ001 073
I F5 573 Correct the error reported before on the next screen
FB01 SAPMF05A 0300WEZ001 066
FB01 SAPMF05A 0300EEZ001 073
I F5 573 Correct the error reported before on the next screen
FB01 SAPMF05A 0330WEZ001 066
FB01 SAPMF05A 0301WEZ001 066
FB01 SAPMF05A 0301WEZ001 066
FB01 SAPMF05A 0301WEZ001 066
S F5 312 Document 100001677 was posted in company code 3100 -
Fault message in asynchronous ABAP Proxy
Hi,
I have a question about fault messages in asynchronous ABAP proxy server.
The configured scenario is SOAP XI ABAP Proxy. Between XI and the ABAP Proxy I have configured an inbound asynchronous interface with a fault message, and then I have generated all the classes and implemented some code for exception handling in the ABAP Proxy side successfully.
When I tested negative cases, the exception raises and it is visible in the SXMB_MONI transaction in the R/3 side, but this exception is not displayed in the SXMB_MONI of XI it just displays a successful delivery to the ABAP Proxy message.
According the XI documentation it says <i>In the asynchronous case, you can see a fault message in the monitoring of the Exchange Infrastructure.</i> But this is not working.
Am I missing something?Hi,
This parameters are form group RUNTIME.
Please check it:
http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/content.htm
Regards,
Wojciech -
Is Asynchronous ABAP proxy client possible without XI ?
Hi there,
Does anyone of you know if it is possible to create an asynchronous ABAP proxy client, without XI, thus directly in a SAP ERP 60 ABAP ?
KarimHi Anton,
thanks for your answer, it confirmed what I was thinking (asynchronous not possible in that case).
Now this leads me to a second question:
I would like to implement the scenario "acknowledge only and receive full answer later".
As you indicate: "...additionally to your webservice client you have to provide a webservice, which the receiver calls once it completes your request..."
In order to do this, I must practice as follows:
The service I call is using the WS-Addressing specifications.
Therefore, the information regarding the webservice that will be called when the request is completed should be sent as a special SOAP WS-addressing parameter, that should be indicated in the header of the SOAP Message, here is an example:
(001) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
(002) <S:Header>
(003) <wsa:MessageID>
(004) uuid:6B29FC40-CA47-1067-B31D-00DD010662DA
(005) </wsa:MessageID>
(006) <wsa:ReplyTo>
(007) <wsa:Address>http://business456.example/client1</wsa:Address>
(008) </wsa:ReplyTo>
(009) <wsa:To>http://fabrikam123.example/Purchasing</wsa:To>
(010) <wsa:Action>http://fabrikam123.example/SubmitPO</wsa:Action>
(011) </S:Header>
(012) <S:Body>
(013) ...
(014) </S:Body>
(015) </S:Envelope>
You can see that the WS-A specific part is in the header of the SOAP Message, not in the body, so not covered by the WSDL.
Question: Is it possible to include this in the header of the SOAP Message generated by the ABAP proxy client ??? -
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.
<b>1. Is my previous assumption correct???</b>
<b>2. How can I invoke from SAP XI3.0 an asynchronous Abap Proxy just with EO quality of service???</b>
<b>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)???</b>
Take Care
PCHi 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 -
JDBC to ABAP PROXY ASYNCHRONOUS SENARIO
Hi Experts
JDBC to ABAP PROXY ASYNCHRONOUS SENARIO IN PI 7.4 ?
Can you tell me any one step by step procedure
BR,
SagarHi Sagar
Check the documents below and you will be able to create the whole scenario.
JDBC sender part:
SAP PI Adapter Series: JDBC Adapter Configuration
ABAP proxy receiver part:
Step-by-step FTP to ABAP Proxy - Process Integration - SCN Wiki -
ABAP proxy transmit data to XI asynchronous,how to capture the status
We are facing a problem when using ABAP proxy to transmit record asynchronous to XI system. Situation is we canu2019t capture the status in XI system , as if XI failed to receive the record, in R3 we need to update the record as not successful received.
Kindly let me know if you have this similar experience in your project.
Thanks in advance.-Create object and suboject in SLG0 transaction
- In program
*Call function to create log
CALL FUNCTION 'BAL_LOG_CREATE'
*Call function to add messages
CALL FUNCTION 'BAL_LOG_MSG_ADD'
*Call function to save all the messages to database
CALL FUNCTION 'BAL_DB_SAVE'
-View the log in SLG1 transaction -
How to make an ABAP Proxy public as an asynchronous WebService
Hello together,
i have made an ABAP-Proxy public as an WebService by generating the WSDL from the directory for my asynchronous <b>outbound interface</b>. This outbound interface is mapped to the ABAP-inbound interface and so on. This works fine.
But actually i don't need any mapping. So i'm thinking about to how to send the WebService <i>directly</i> and to the ABAP-Inbound-Interface <u>asynchron</u>.
1. Is this possible at all (and how), and if so
2. does it makes sense in order to improve the performace (there is a mass-processing in behind)?
GunnarGunnar,
I guess its simple...go for SOAP to Proxy scenario.
If ur source and target structure is same ..u need not require mapping.u can execute the scenario without mapping also.
I have done same scenario 2 months ago.....
following things u need to do.
1)create outbound message interface
2)create inbound message interface
3)No need of message mapping and interface mapping(if u dont require any transformation of source structure)
4)create WSDL for outbound message interfce
5)create proxy for inbound MI
6)write the necessare code in ur proxy
7)using any SOAP editor like XML spy send data to proxy...
u have done the work!!!!
All the best
regards
biplab -
ABAP Proxy Receiver Asynchronous EOIO
Hi,
Is it possible to Guaranteeing the Sequence of Asynchronous Messages for ABAP Proxy Receiver(EOIO)?
If yes, how can I configure?
Thanks,
Kiara.Hi Stefan,
Thank you.
One quick question.
In case if I use JMS>PI>RFC(Async) then also no need of maintaining EOIO for RFC Receiver Async?
On JMS sender we are maintaining EOIO.
Reason for this request is currently we are using JMS>PI>RFC Async. We are using EOIO on JMS sender, but some times sequence of messages is missing.
Can you please let us know the cause of this issue.
Thanks,
Kiara. -
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" ?>
- <!-- Call Integration Server -->
- <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 -
ABAP proxy code using internal table
Hi XI guru's,
Good Afternoon,
My Scenario is ABAP Proxy to file using ztable.
i am getting data from Sap R/3 data base as Ztable. using this Ztable i have to write ABAP Proxy code. I generated ABAP Proxy and mentioned all below.Please send me ABAP Proxy code using this details. This is very urgent. Please help me.
ABAP proxy class: zco_mioa_tata
structure : zmt_tata
structure : zdt_tata
structure : zdt_tata_employee
Table : zdt_tata_employee_tab
Ztable : zcnu_proxy_table
outbound structure:
mt_tata
employee
thanks and regards
saiSai,
I guess this will help you.
1. Proxies can be a server proxy or client proxy. In our scenarios we require proxies to send or upload the data from/into SAP system.
2. One more thing proxies can be used if your WAS ≥ 6.2.
3. Use Tcode SPROXY into R/3 system for proxy use.
4. To send the data from R/3 system we use OUTBOUND PROXY. In Outbound proxy you will simply write an abap code to fetch the data from R/3 tables and then send it to XI. Below is the sample code to send the data from R/3 to XI.
REPORT zblog_abap_proxy.
DATA prxy TYPE REF TO zblogco_proxy_interface_ob.
CREATE OBJECT prxy.
DATA it TYPE zblogemp_profile_msg.
TRY.
it-emp_profile_msg-emp_name = 'Sarvesh'.
it-emp_profile_msg-empno = '01212'.
it-emp_profile_msg-DEPARTMENT_NAME = 'NetWeaver'.
CALL METHOD prxy->execute_asynchronous
EXPORTING
output = it.
commit work.
CATCH cx_ai_system_fault .
DATA fault TYPE REF TO cx_ai_system_fault .
CREATE OBJECT fault.
WRITE :/ fault->errortext.
ENDTRY.
Receiver adapter configurations should be done in the integration directory and the necessary sender/receiver binding should be appropriately configured. We need not do any sender adapter configurations as we are using proxies.
5. To receive data into R/3 system we use INBOUND PROXY. In this case data is picked up by XI and send it to R/3 system via XI adapter into proxy class. Inside the inbound proxy we careate an internal table to take the data from XI and then simply by using the ABAP code we update the data inot R/3 table. BAPI can also be used inside the proxy to update the data into r/3.
I hope this will clear few doubts in proxy.
Just go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
ABAP Server Proxies By Siva Maranani
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Generating java proxies..
/people/prasad.ulagappan2/blog/2005/06/27/asynchronous-inbound-java-proxy
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
Regards,
Sarvesh -
Problem receiving acknowledgement: abap proxy == file adapter
Hi experts,
I am developing an asynchrone interface using PI 7.0. The scenario is: SAP ==> FILE.
In SAP I have created an abap proxy in wich I requested an acknowledgement when calling from the abap code. In PI I have created an Integration Process with a receive step, and a send step. In de send step I am asking for a transport acknowledgement.
When I test the interface and I look in the SXMB_MONI in PI, I see the acknowledgement given back to the IP, but in the SAP backend system I don't receive anything in the abap proxy which had send the original message. In de SXMB_MONI from SAP I see a "?" Still awaiting acknowledgement.
Can anyone help me with this scenario? I really need an acknowledgement from the file adapter in the calling abap proxy.
Regards, JeroenYou need to crate a REceiver Agreement for this sender...
The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
-SM -
Hi,
In my scenario, I have written code in the execute_synchronous method of the abap proxy in ECC. I want to capture all possible errors that might occur here and for all of them i want to capture the message id and the text and send it out. what kind of possible errors/exceptions can occur and how to handle them. My proxy class simply selects data from multiple tables in ECC and returns the same.
thksHi,
for outbound proxies the error handling should be done within R3 itself and there is no need to send errors to XI or receiving system for that matter. You would want someone from R3 side to take a note of it.
For Inbound proxies, you will have to implement the Fault messages
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
· In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
· The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
For more information on the same.
http://help.sap.com/saphelp_nw04s/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In your case, since you said that you are selecting data from some tables, the possibility is that an entry is not found in the DB tables you will have to simply populate the fault message data and raise an expection CX_FM. It also depends on what error handling requirements from the Business .
regards,
Advait. -
Hi,
this scenario is abap proxy 2 soap ,, , source system send some data to target webservice and target webservice return approval number.
I checked target url and soap action in receiver soap adapter, and those value is correct.
on sxmb_moni
i got NO_MAPPINGPROGRAM_FOUND
http://test.test.com/pt/ses001/approvalprocess SES001_IM does not exist in runtime cache</SAP:Stack>
and Applicatoin Error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
here is Sent message log on MDT.
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
2006-08-29 13:25:37 Success SOAP: response message leaving the adapter
2006-08-29 13:25:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-08-29 13:25:37 Success Trying to put the message into the send queue.
2006-08-29 13:25:37 Success The response message for message 44f23177-e6ed-0270-0000-000046028211(INBOUND) was successfully transmitted to the calling application.
2006-08-29 13:25:37 Success The message status set to DLVD.
2006-08-29 13:25:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
here is Receive message log on MDT.
2006-08-29 13:25:37 Success The message was successfully received by the messaging system. Profile: XI URL: http://xi0034:50000/MessagingSystem/receive/AFW/XI
2006-08-29 13:25:37 Success Using connection AFW. Trying to put the message into the request queue.
2006-08-29 13:25:37 Success Message successfully put into the queue.
2006-08-29 13:25:37 Success The message was successfully retrieved from the request queue.
2006-08-29 13:25:37 Success The message status set to DLNG.
2006-08-29 13:25:37 Success Delivering to channel: R_TEST_SOAP_SSS001
2006-08-29 13:25:37 Success SOAP: request message entering the adapter
2006-08-29 13:25:37 Success SOAP: completed the processing
2006-08-29 13:25:37 Success SOAP: response message received 6bc3e4d0-3716-11db-a265-00145e483080
2006-08-29 13:25:37 Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i can see source data on sxmb_moni.
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:APPROVALREQ_SES_MT xmlns:nr1="http://test.test.com/pt/ses001/approvalprocess">
<TITLE>46</TITLE>
<GUBUN />
<REQUESTOR>46</REQUESTOR>
<TEXTLINE>SAFSAFSAFDSAF</TEXTLINE>
</nr1:APPROVALREQ_SES_MT>
request message mapping of request
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws">
<args1>46</args1>
<args2>46</args2>
</ns1:ApprovalRequest>
I can not see any return value comming from target webservice on sxmb_moni.
request message mapping error on response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
payload of request message mapping of response
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">ibmr52</ns2:hostname>
please check what was my fault.
thanks
venjaminHi Bhavesh.
thanks for the note.,,
please look at the bottom of this content.
i can not see "Method=Approval" between jws and args1 even though i set SOAP Action = Approval on Receiver SOAP Adapter.
is this happening something wrong? or is it normal log?
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
here is detail message log on MDT.
--SAP_512dbe91-372d-11db-b291-00145e483080_END
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header>
<sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-main-92ABE13F5C59AB7FE10000000A1551F7'>
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>synchronous</sap:ProcessingMode>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId>
<sap:TimeSent>2006-08-29T07:10:08Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party>
<sap:Service>BS_SAPR3_SSS0017</sap:Service></sap:Sender><sap:Receiver>
<sap:Party agency='' scheme=''></sap:Party><sap:Service>BS_MMM_D</sap:Service></sap:Receiver>
<sap:Interface namespace='http://sds.samsung.co.kr/pt/sessingle001/approvalprocess'>APPROVALREQ_MMM_IB</sap:Interface>
</sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging>
<sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'>
<sap:Hop timeStamp='2006-08-29T07:10:08Z' wasRead='false'><sap:Engine type='BS'>BS_SAPR3_SSS0017</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop>
<sap:Hop timeStamp='2006-08-29T07:09:06Z' wasRead='false'>
<sap:Engine type='IS'>is.00.xi0034</sap:Engine>
<sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-29T07:09:08Z' wasRead='false'>
<sap:Engine type='AE'>af.sxd.xi0034</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter>
<sap:MessageId>44f23fa9-e6ed-0270-0000-000046028211</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body>
<sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink' xmlns:wsu='http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7'/></SOAP:Body></SOAP:Envelope>
--SAP_512dbe91-372d-11db-b291-00145e483080_END
content-id: [email protected]
content-type: application/xml
<?xml version="1.0" encoding="UTF-8"?>
<ns1:ApprovalRequest xmlns:ns1="http://70.2.207.241:8080/axis/ApprovalService.jws"><args1>333</args1><args2>333</args2></ns1:ApprovalRequest>
SAP_512dbe91-372d-11db-b291-00145e483080_END
thanks
venjamin
Message was edited by: venjamin -
Hello everybody i have this error in my sxmb_moni of xi for a abap proxy server receiver:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Inbound Message
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1</SAP:P2>
<SAP:P3>EXECUTE_SYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText>Unable to execute the dynamic application call (kernel error ID UNCAUGHT_EXCEPTION, class ZFUS_CL_MI_FMGOB_CAT_FONDOS_C1, method EXECUTE_SYNCHRONOUS)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any suggestions?
Regards,
Julio CesarHi
Below is the full details of above links
For link 4196517?
Q) Hi All,
I have got a requirement to raise an exception from existing ABAP Proxy depending on condition. XI consultant created a fault messge type and attached to the inbound interface message type. I have regenerated the ABAP proxy but I cant find any thing in excpetion tab to raise exception.
Please let me know the solution for this.
Answers : 1) Go to Sproxy .
Select the message interface for which you generated the proxy.
Click on the Structure tab. Do you see any Exception Class generated for fault message ?
2) Just follow all the steps defined in the below Blog and you will find the solution.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
3) I can't find any exception class there in 'Structure' tab. what might be the problem.
4) In SProxy ..under the Message Interface you will see Fault Message Type.
Click on Fault Message Type and check if you can see the fault message type created by xi consultant.
Also ask your xi team to login to IR and re-activate the interface.
5) I can't find any fault message type under Fault Message Type. I will ask my XI consultant to reactivate the interface.
Is this the only problem for this or is htere any other reason for not finding this fault message type in SPROXY.
6) Ideally the fault message type should be visible unless he has defined Software Dependencies and using MT from some other SC.
Even if the fault message type is not visible everything could be all right.
Ask him to check if he selected the fault message type while activating the interface.
Do update us when you get a reply from ur xi team.
7) I have checked with XI admin, he said that he created fault message types in Development Xi but R/3 Development refers to Production XI system in exchange profiles. He asked me to change it to XI development in exhange profile settings. So I am searching info on how to set exchange profiles.
8) The following link will guide you ..
http://help.sap.com/saphelp_nw04s/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm
I dont think we need to do any changes in Exchange Profile for proxy communication.
Changing the RFC Destinations (in your R/3 system)- LCRSAPRFC & SAPSLDAPI should solve your problem.
II) For Link :4147406?
Q) Hi All,
We have an ABAP Proxy implemented for posting goods movement and it is calling BAPI function module to post good movement. We have got a requirement that if BAPI returns any error, this error message send back to SAP XI.
data call proxy
Legacy -
> XI -
> SAP R/3(call bapi)
<----
error message
Please let me know how to send the message back to XI.
Answers: 1) Refer the following
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Proxy to File
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - File to ABAP Proxy
2) you can utilize the fault messages for such an usage -
Ref:
Fault messages -
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -
/people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
3) You have to do Fault message implementation in this case...
A no. of exception will be there.For any error proxy will catch the exception and will write it in the fault message...so....from r/3 response will go to Xi as Fault message response in case any error/exception occours......
have look here...
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
4) Please go through it is very useful.
/people/krishna.moorthyp/blog/2005/12/23/monitoring-for-processed-xml-messages-in-abap-proxy --Monitoring for Processed XML messages in ABAP Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy --ABAP Proxies in XI(Client Proxy)
/people/sap.user72/blog/2005/12/29/service-enable-your-sap-application-component --- Service Enable Your SAP Application Component
5) the file adapter can work only asynchronous, so you cant have a response. You should build two asynchronous messages. File -> proxy inbound and after the bapi call an outbound proxy is called which is sending a second messge to the file adapter.
6) you can define a synchronous scenario which will include request/response messages.
send the response back to XI.
the file adapter supports BE QoS.
http://help.sap.com/saphelp_nw04s/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
7)I have an interface Z_stock_move(message interface(inbound)) and class z_STOCK_MOVE in that. I have clicked exception tab but not able to add exception there as its not enabled for change.
Please let me know how to add the exception to an existing abap proxy.so that i can raise an exception when bapi call to goods movenment returns errors.
Might be useful to U.
Maybe you are looking for
-
Some of the services of ITS 640 are not working
Hi All, I have implemented SAP NW 04 SR 1 Portal and integrated SRM 4.0(EBP 5.0).I have also implemented Business Package for mySAP SRM 4.0 60.2. I am using internal ITS for HTML GUI. Some of the iviews of the business packages are working but some
-
How to add row in presentation by using add button in Oracle BPM 10G
Hi, I have one presentation, in that i used some attributes as group. After launching workspace when click on+ sign iam getting new row, but instead of using that I want to use addrow button to get new row and same for remove row. please help me in c
-
I have a general Jdeveloper setting question. I have a comm-library folder. But I have to manually add to each and every project. Is there a way I can have it set up, that when I create a new project, automatically it picks up the comm-librar folder.
-
Hide option for SharePoint 2013 UI upgrade
Hello, I just want to know if there is a way to hide the banner which pops up for UI upgrade on SharePOint 2013? We are trying to leave few sites on 2010 UI only. Thanks,
-
my power cord was working,then all of a sudden it said it wasnt compatible or something,******* me off it was working just fine