Error in SOAP to IDoc scenario

Dear Experts,
I have one SOAP to IDoc scenario where I am sending the request through Altova XML spy.
But I am getting the error "Only asynchronous processing supported for IDoc adapter outbound processg". but I have configured the QoS of Sender Communication channel as "Exactly Once(EO)" and I have activated the same.
In SXMB_MONI the "Type" of this scenario is also "Sync".
The created SOAP request URL is :" http://server:host/sap/xi/engine?type=entry&version=3.0&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX.
Here I am getting the error as "Only asynchronous processing supported for IDoc adapter outbound processg".
If I send the service usinng the URl "http://server:port/XISOAPAdapter/MessageServlet?channel=:BS_XXX:CC_SOPtoIDoc&version=3.0&Sender.Service=BS_EAN_DELE&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX",then I am getting HTTP 500 error.
Can you please suggest me where I have to change the configuration so that the "Type" will be async and the IDoc will be posted properly.
Thanks in advance.
Regards,
Amit Mandal

hi,
you can also do it like this:
http://server:host/sap/xi/engine?type=entry&version=3.0&ProcessindMode=Asynchronous&QualityOfService=ExactlyOnce
&Sender.Service=BS_XXX&Interface=http%3A%2F%2Fsoapadapter_SOAPtoIDoc%5EMI_XXX.
and set use query string parameter in soap sender adapter
Regards,
Michal Krawczyk

Similar Messages

SOAP to IDOC scenario: java.lang.NullPointerException

Our trading partners currently post their xml files directly to our Integration Engine, where they are converted to idocs and posted to ECC. I am now trying to change this scenario to a SOAP to IDoc scenario so that we can process the files through the Adapter Engine using HTTPS. But I am running into an error when trying to post an xml file and I'm wondering what I am missing.
My SOAP communication channel is configured as follows:
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Integration Server
HTTP Security Level: HTTP
Do Not Use Soap Envelope: *Checked*
Default interface and namespace have been specified
QoS: Exactly Once
If I post an xml file to this channel using the RWB test tool, I receive message java.lang.NullPointerException. However, I can find the message via the Message Monitoring in the RWB, with versions for both the AE and IE, each with status Successful. The idoc is created and successfully posted to ECC.
If I post this same file to the same URL using a third-party tool, I get the same error message along with more details (listed below). Futhermore, a message does *not* show up in the RWB and thus does not get converted to an idoc and posted to ECC.
Any ideas??? Thank you.
<?xml version="1.0" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Body>
- <SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
- <text>
- <![CDATA[
java.lang.NullPointerException
     at com.sap.aii.messaging.net.MIMEInputSource.decodeContentType(MIMEInputSource.java:425)
     at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:323)
     at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
     at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:381)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Here's the message log found in End-to-End monitoring from RWB test post (different from third-party tool message):
java.lang.NullPointerException
     at com.sap.plaf.frog.FrogScrollPaneUI$1.propertyChange(FrogScrollPaneUI.java:113)
     at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
     at java.awt.Component.firePropertyChange(Unknown Source)
     at javax.swing.JScrollPane.setHorizontalScrollBar(Unknown Source)
     at javax.swing.plaf.basic.BasicComboPopup.createScroller(Unknown Source)
     at javax.swing.plaf.basic.BasicComboPopup.<init>(Unknown Source)
     at com.sap.plaf.frog.FrogComboPopup.<init>(FrogComboPopup.java:21)
     at com.sap.plaf.frog.FrogComboBoxUI.createPopup(FrogComboBoxUI.java:410)
     at com.sap.plaf.frog.FrogComboBoxUI.installUI(FrogComboBoxUI.java:178)
     at javax.swing.JComponent.setUI(Unknown Source)
     at javax.swing.JComboBox.setUI(Unknown Source)
     at javax.swing.JComboBox.updateUI(Unknown Source)
     at javax.swing.JComboBox.init(Unknown Source)
     at javax.swing.JComboBox.<init>(Unknown Source)
     at com.sap.jnet.clib.JNcToolBar$ComboBox.<init>(JNcToolBar.java:64)
     at com.sap.jnet.clib.JNcToolBar.addComboBox(JNcToolBar.java:192)
     at com.sap.jnet.clib.JNcAppWindow.newUI(JNcAppWindow.java:607)
     at com.sap.jnet.clib.JNcAppWindow.newData(JNcAppWindow.java:1097)
     at com.sap.jnet.JNetData.createGraphFromDOM(JNetData.java:512)
     at com.sap.jnet.JNetData.load(JNetData.java:709)
     at com.sap.jnet.JNetApplet.initJNetApplet(JNetApplet.java:524)
     at com.sap.jnet.JNetApplet.access$000(JNetApplet.java:40)
     at com.sap.jnet.JNetApplet$1.run(JNetApplet.java:265)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)

SOAP to IDoc scenario without BPM

Hi,
I have 2 scenario's
1) IDoc-SOAP - -response -- IDoc scenario -- (have found some links to do it without BPM)
2) SOAP -- RFC request -- RFC response -- e-mail (no links found)
how can i achive both these scenario's without BPM. Currently i have these 2 scenarios in our 7.1 version with BPM. but our requirement is to migrate this scenario into 7.4 without BPM(No PO).
please help us to achive this scenario without BPM.
Your help is highly appreciated.
thanks,
Praveen

Hi Kiran,
Could you please let us know the exact requirement. How do you want to send the response back to IDOC?
ASync - Sync Bridge with IDOC sender is not possible in PI 7.0.
If It is something like IDOC --> SOAP --> IDOC , And If the SOAP request is small then you can use SOAP Lookup in IDOC to IDOC Scenario.
In The mapping You can do a lookup and get the response from SOAP(Webservice) and map that to your Target IDOC.
This is one possible way for you without BPM in PI7.0.
Please let me know if you need more details about this.
Thanks
Jyothi A

SOAP to IDOC scenario

Hello All,
I have a scenario where the sender system is outside our landscape and I need to post the PO data to SAP system using XI. I know its a SOAP to IDOC scenario but I am not given a wsdl but am given only a xsd and one XML as input. Can I use this XSD to create a sender message interface or is there any way I can convert the XSD to WSDL? Also, where should I give the path of the XML file in sender SOAP adapter?
And also I have to create a value mapping table where I have almost 4000 entries. Can any one let me know on how to create this?
I have browsed thru the SDN but havent found any information that I am looking for. Can anyone please help me on this.
I will be greatful if anyone can help me with Step by Step to SOAP to IDOC scenario.
Thanks and regards,
Neelima

I think what is this person asked to do is build an integration scenario using two business system
1. A business system understand web service technologies and also have a data definition they would like to use to communicate data with their business partner.
2. A business system which like to accept DATA in the format of IDOC.
So As long as we use XI as an integration framework, this is called SOAP to IDOC scenario.
I recomend to use the following steps to implement the integration need.
1. Understand the XSD data structure from the external service provider.
2. Using the external data definition create and outbound interface either SYNC or ASYNC format ( You have to discuss this with service provider for confirmation) in XI.
3. External service provider can use this outbound interface definition and associated data structure to send their data in their provided XML format to XI integration server.
4. Create an inbound service definition by using the XSD structure created for the IDOC you like to use.
5. XI integration server can use the inbound interface definition to pass the outbound interface message received once the outbound and inbound interface are connected using a configured scenario.
6. Using the outbound message type and inbound message type create a message mapping.
7. Using the message mapping create an interface mapping between outbound and inbound interface.
8. Create a WSDL from the outbound interface so that the service provider can use the service contract defined by the outbound interface in a web service enabled business system (Note: you have provided the data requirement in XSD format indicate that your business system is web service enabled). Make sure you are not getting fooled by the concept propose URL for the WSDL. You must provide the URL end point in created WSDL according to the following format.
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=<party>:<service>:<channel>
If the SOAP adapter channel belongs to a service without party, the address is as
follows:
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=:<service>:<channel>
9. Provide the WSDL to the service provider, ask them to use that WSDL to send data to your integration framework.
10. Configure the SOAP adaptor in sender mode, so that it can act as a end point to receive the XML data based on the XSD defined in the WSDL and convert the same to an XI document.
11. When u define the sender soap adaptor make sure you have selected the namespace and interface name same as the one you created for outbound interface.
Also recomend to read two How to guide related to web service and soap adaptor to complete your scenario.
Thanks

Error in File-PI-Idoc scenario

Dear All,
While working on File-PI-Idoc scenario, I am getting the error as
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have checked various other posts on the same error but still I am not able to resolve this.
Please help me in resolving this error.
reg,
nj

Nishu,
Please check whether you have assigned the following roles to the particular user you are using for data communication.
Roles:
SAP_XI_IS_SERV_USER,
SAP_XI_APPL_SERV_USER
Regards,
Sugata

Error in Webservice to IDoc Scenario

Dear All,
Iam dealing with Web Service to IDoc Scenario . I have used Exactly Once in the Quality Of Service (QOS) in sender communication channel .
I got the following error:
ResponseCode: 200 (OK)
content-type:text/xml;charset=utf-8
content-length:458
x-xmb_ws_encoded:version=1%2e0&Sender.Party=%3a%3a&Sender.Service=bs_kalyan_ws&Interface=urn%3asap-com%3adocument%3asap%3aidoc%3amessages%5eDEBMAS%2eDEBMAS05&Receiver.Party=%3a%3a&Receiver.Service=bs_kalyan_ws&To.Interface=htttp%3a%2f%2fkalyan%5emi_kalyan_ws&MessageClass=SE&ProcessingMode=S&ConversationId=&MessageId=30B49C89-9E75-DA40-B1D8-C5416903FE7A&RefToMessageId=A1A63B08-51B6-524A-8386-98235D7A7834&QualityOfService=BestEffort&TimeSent=2007-08-30T05%3a58%3a41Z
soapaction:'http://sap.com/xi/XI/Message/30'
content-id:<[email protected]>
server:SAP Web Application Server (1.0;640)
<?xml version="1.0" encoding="utf-16"?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
    <SOAP:Fault>
      <faultcode>SOAP:Server</faultcode>
      <faultstring>System Error</faultstring>
      <detail>
        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
          <context>
          </context>
          <code>IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP</code>
          <text>Only asynchronous processing supported for IDoc adapter outbound processing</text>
        </s:SystemError>
      </detail>
    </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
Please do the needful.
Thanks in Advance,
Sarat

Hi Jai Shankar,
Ya what you told is correct just see the message that i got in sxmb_moni :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
But in ID part in Sender side communication channel QOS is EO only. How can this happen ?
Regards,
Sarat

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in SOAP to file scenario

Hey guys
i m doing a SOAP to File scenario and getting the following error.
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
any idea where should i look ?
thanx
ahmad

Hey
i m still getting a red flag in MONI,the error is
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
i checked my mapping by copyin payload from MONI,its working fine.
thanx
ahmad

IDOC is posting with Errors in File to IDOC scenario

Hi,
I did the File to IDOC scenario for CREMAS . IDOC is posting with Errors .. i.e. in the status record it was showing 56- EDI: Partner profile inbound not available ..
If I manually process that IDOC in WE19 , then it was processing successfully.. and in the we19 it was showing Inbound Processing : Port Not Maintained but even though manually it was posting fine...
any ideas regarding this will be appriciated.....
Regards
Babu

Please check whether you had done the following assuming your doing File to Idoc
Settings in your Business service for the receiving system
Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
Settings in R/3
WE20 - Add the partner profile for the particular message type cremas and process code.
Your statement
" and that same logical system name had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
Please do mention R/3 Details in the receiver business service or system.
Thnz

How to catch Posting error in File to IDoc Scenario?

I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
Can anybody suggest the solution.
Regards,
Suraj Kumar

Hi Suraj,
this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
regards
jithesh

Getting Error 26 in ALE IDOC scenario .- EDI Syntax Check Error...

Hi..
i am working in ALE Idoc scenario...I am getting Status 3 as well as status 26 in we02 transaction in my custom IDOC scenario for outbound process..
The error is 'EDI- SYntax Check'..
How to remove this error..
Pls help.

ya, there is only one segment available in IDOC..named i.e zseg_a .
So , error in postion is avoided..
How to find syntax error then?

SET_PAYLOAD_FAILED error in SOAP to Proxy scenario

Hi PI Experts,
We have an inbound syncronus interface (Non sap system to SAP) using the SOAP to Proxy scenario.
When we test the interface using any soap tool like soapui it is working fine but when the interface is triggered end to end from source system then the below error is getting dispalyed on source system.
500 Internal Server Error
In XI below is the error message -
<?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="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">SET_PAYLOAD_FAILED</SAP:Code>
<SAP:P1>IN</SAP:P1>
<SAP:P2>REQUEST</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Internal error when completing the message object (setting the payload, direction: IN message: REQUEST)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any please let me know what is the issue here?
Appreciate your help.
Regards,
Jitender

We had a similar issue with a Synchronous Interface
The interface worked perfectly when sending the request directly to the integration server, but when sending it using SOAP the issue appeared.
It was very tricky to solve it because we had similar interfaces that worked without any issues.
SOLUTION: Create a new Service interface with a new name different from the one failing. And make sure The Message Types are in the same namespace as the service interface.
Why?:
The issue turned out to be in the sender agreement, and name-spacing issues.
Our Outbound Service Interface belonged to one SWCV and ns, We will call it "ns1:SI_A_OUT".
In PI 7.3, and I believe 7.11 also, the you no longer assign a default interface in the to the SOAP communication channel sender agreement pair.
Therefore the SOAP adapter determines the soap method from the payload. If The internal message type in the soap message belong to different namespace, the the java method getMessage() does not find the correct XML node, therefore does not find the payload.
<"ns1:SI_A_OUT">
...<ns2:MT_element>
getMessage( ns1:MT_element)
We are not sure if the issue is the implementation of the SOAP protocol or in the WSDL generation. But this issues seem to create orphan object during runtime, and even if you re-implement the complete interface, the sender agreement seems to be corrupt.
Therefore the only was we could solve this, was to move our MT to the same namespace as the service interface and rename the interface "ns1:SI_A2_OUT"
Hope this helps someone.
Juan Francisco Zurita Duque
NNIT A/S

Mapping Error with Sender JDBC- Idoc scenario

Hi Guru's,
I've got a simple asyncronous sender JDBC to Idoc scenario, and I encounter a strange problem with the mapping.
When I test the mapping it works fine, but when I run the scenario, only the first element (a constant) of the Idoc gets mapped, and mapping stops with no errors.
Does someone know where to find the error?
Thanks,
Karst

Hi Karst,
There might be several reasons that you do not see the IDOC structures are not created/mapped:
1. Most of the IDOC structures are optional (minOccrs = 0), so you have to make sure the structure itself (not just the fields within that structure) is mapped to something that does exist in the source data.
2. Make sure your JDBC generated source data does have the right namespace as you used in your mapping. I once had a similar problem, but finally found the source data generated in run time is slightly different from the one used in mapping in terms of namespace.
3. Test your mapping with the source data generated in runtime (you can copy it from SXMB_MONI). Then you may be able to find the problem.
Hope this helps.
Hart

SOAP to IDocs Scenario...IDocs getting locked at SAP

Dear Experts
We are sending measuring point details to SAP system from 3rd Party. Scenario is working fine for small amount of load. If more number of messages triggered (say 100) IDocs at SAP are getting stuck u201CMeasPoint 10000211 currently locked -> document processing not possibleu201D.
I tried configuring Sender SOAP adapter as EOIO and specified the Queue name as Test Queue. Still IDocs are getting stuck at SAP ECC. Now one more issues messages are getting stuck in queue SMQ2. We can control the flow by using BPM in PI. I donu2019t want to use BPM for this. Can we control this from SAP or using Trigger by background program in Partner profiles?
Please suggest. Thank You.
SAP Error Details:-MeasPoint 10000211 currently locked -> document processing not possible
Message no. IR007
Diagnosis
The object you want to access is locked, either
u2022     By yourself in another session, or
u2022     By another user
u2022     or by the system, which is still processing data for this object
System Response
The system cannot access the object.
Procedure
u2022     If you are locking the object yourself in another session, exit processing in the other session and continue processing in this session.
u2022     If the object is locked by another user, you can
o     contact the other user
o     wait until the other user has finished processing the object
u2022     If the object is locked because the system is still processing its data, wait a while, and then call up the object again.

1. Create a new process code "Z" and check the enque state of the objects before passing back to standard processing modules. Id also change to process immediate as part of this change
or
2. I think assuming RBDAPP01 is still used you may be able to make use of an exit there to do the same thing .. check and wait before processing.
or
3. In message mapping place a UDF that has some kind of wait timer in it (this is random and wont always work cause you wont know when the lock is dropped) but should work.
or
4. Dont use IDOC's create an abap proxy to do the work as a sync process. Processing will need to finish in the proxy and return to the PI stack before the next message is processed in the EOIO queue - this would be the prefered option as far as im concerned, it guarenteed to work and as long as your proxy sticks to the standard rouintes it should be upgrade friendly.
or
5. Use a proxy as above but dont do any processing, just use the proxy to build the IDOC and post it - then check the status of the locks until you are ready then rinse and repeat ..... but like scratching your right ear with your left hand .. but it will work.

SOAP with IDOC scenario

Hi Experts,
Could you help me with the following scenario using XI:
The sender is a webservice client which sends a SOAP request with the order number (over HTTPS). The order number needs to be pased to SAP ECC to return the order details as a SOAP response synchronously. The order details are actually stored in very complex custom idocs in SAP ECC.
Plz let me know how to configure this scenario.
Thanks,
Shobhit

Steps in BPM:
1) Receive Step: (Receive New Order from WebServer)
Message: sales_order1 (Give the appropriate message type)
Start Process: Click on the check box
Mode: Asynchronous
Activate correlation:
Order_number:
2) Send Step: (Send order to SAP R/3)
Mode: Asynchronous
Create New transaction: Do not Click on the check box
Message: sales_order1 (Give the appropriate message type)
Acknowledgement: none
received from : Send Contect
3) Receive Step: (receive purchase Order from R/3)
Message: Purchase_order1
use correlations: Order_number
4) Send Step: (Send order response to WebService)
Mode: Asynchronous
Create New transaction: Do not Click on the check box
Message: Purchase_order1 (Give the appropriate message type)
Acknowledgement: none
received from : Send Contect
These are basic steps, depends on your requirement(Error Handling or response time limitations) the design may change.
The ID Configuration is same...
Receiver determination:
1) Service_is_Sender_WS - Sender_Interface_Sales_Ord (Party is optional)
2) Service_is_IP - Interface_is_request_abs
3) Service_is_IP - Interface_is_response_abs
4) Service_is_SAP - Interface_is_IDoc_PURCH_Ord
Same as Interface determination....

Error in SOAP to IDoc scenario

Similar Messages

Maybe you are looking for