IDOC to XML SOAP Scenario

Hi All,
I want to implement IDOC to XML SOAP scenario for 3 different IDOC types.
Should i implement it under same namespace or use different namespace for each IDOC to XML scenario.
Thanks,
Vishal

Hi,
depends on your requirement and your XML SOAP receiver
there are no general rules
Regards,
Michal Krawczyk

Similar Messages

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

IDOC to XML file scenario with party

Hi All,
I am developing a IDOC to XML file scenario with party in which I have extended the MATMAS idoc and configured the receiver FILE communication channel.
But its giving me the error *"No receiver could be determined"* with party. If I run the same scenario without the sender party its working fine.
And sender is my R/3 system under party P_Party and receiver is my third party system under P_Party.
Thanks in advance.
Gaurang

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

IDOC to websevice (SOAP) scenario

Hi Experts
I have a IDOC to SOAP scenario, i have searched for the step to step guide in SDN, but could not find it
Please let me know the step to step process for a IDOC to (webservice) SOAP scenario, like DT, MT etc.. and further steps
Regards
Lara

Hi Vijay
Thanks for the info shared.
below are the points observed from the links
My Scenario:
Source : IDOC
Target : SOAP
mode : Asynchronous
1. Import the IDOC which will be used in the message mapping at the source side
2. Create SOAP Datatype, Message Type, Service Interface.
3. Imoport the IDOC in message mapping and the SOAP message type that we have created in the above step
4. Operations Mapping and activate the scenario (same as normal idoc to file scenario)
5. Create Integration Scenario, SOAP Receiver Communication channel, Receiver Agreement, Receiver Determination, Interface Determination
Please let me know if anything else am I missing in this scenario
Regards
Lara

Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

Dear all,
I have to send the MATMAS05 IDOC via XML-SOAP-HTTP Interface to a subsystem. Sending works (the sub-system receives the SOAP-Request with the MATMAS05 as Body). So far so good. Now the SAP System is waiting for an answer (synchronous communication). How should this answer look like?
We receive the Error EA390 "Problem with SOAP Class" - execute_processing: entry result table
Can anybody give me a hint how the response should look like.
Many thanks and best regards
Roman

Hello Sven,
we find a solution. As far as I remember, there is a flag to send without waiting for answer (or technical better to not rely on SOAP standard).
Look in WE21 and the XML_HTTP Port you use. Uncheck the "SOAP Protocol" flag. Then it should work.
HTH and Best regards
Roman

Problem in IDOC to SOAP Scenario

Hi All,
we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target xml.
Thanks

Hi ,
This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also
What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.
What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this
Thanks
Edited by: vishal gadkari on Aug 22, 2009 4:15 PM

IDOC - SOAP scenario

Hi Guys,
I have configured the IDOC-SOAP scenario and i am sending to the target business partner with the soap receiver adapter.
I did not get any wsdl from the business partner instead i got the xml structure, target url and soap action. I have created a xsd for the given xml and send the data to the business partner.
The data is reacing the target system but the xml document has error saying "invalid at the top level of the document" and no xml is seen. I also get an acknowldegment error in sxmb_moni as
OUTBINDING CO_TXT_Routing_Back_Error
Error occured during back routing, error in communication channel
any help would be appreciated
Thanks,
Raj

I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:
You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc
adapter. You want to be able to request acknowledgments separately in the
XI for each sending system and interface. In the IDXNOALE exception table,
you can deactivate acknowledgments for certain systems or interfaces.
Previously, you could only maintain the table with transaction SE16.
Report IDX_NOALE is delivered with Support Package 10. With the report, you
can add, delete and display table entries.
Report IDX_NOALE is extended with additional functionality as of Support
Package 11. This allows a sender system to request or deny acknowledgements
for all message types centrally. You can set exceptions to this central
setting by message type. Generic exceptions (for example, message type
'ORD*') are not supported. Entries that are already present in the table
are unchanged.
To perform these activities, you need the authorization to maintain IDoc
metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').
Hope this helps.

IDOC-XI-XML Scenario Questions

Hi everyone,
I am actually trying to configure a scenario starting from SAP and finishing creating a XML file.
R/3 IDOC -> XI -> XML file
The XI is receiving IDOCs from SAP correctly, but when it try to send to third party system, the monitor engine (SXMB_MONI) are showing the following error: HTTP_RESP_STATUS_CODE_NOT_OK.
I am currently using the File Adapter, please take a look at the config for the communication channel:
Adapter Type: File
http://sap.com/xi/XI/System
SAP BASIS 6.4
Transport Protocol: File Protocol(FTP)
Message Protocol: File
Adapter Engine: Integration Server
Target Directory: / (root)
File Name Scheme: mptest_xi_output.dat
File Construction: Create
Overwrite File: X
File type: Binary
Adapter Status: Active
Regards,
Gabriel Santana

If you have enough authorization, then click on the last button which is change button.
Otherwise, open two windows of SAP and try to do the above step and when you get the authorization error, go to the second window and enter transaction /nSU53. Send that info to your security team.
Once you have authorization you should be fine.
One other thing, in which client you are doing this ?
Do not use DDIC user to change it.
regards
Shravan

IDoc to SOAP scenario is showing error

Dear Experts,
We were trying a scenario which is IDoc-XI 3.0->SOAP and where the WebService is situated outside our office network. Our network team have bypassed proxy for accessing that WebService URL and the same is accessible from our XI3.0 application server from browser. We have configured the scenario and when we have tested the scenario from RWB->Component M onitoring->Integration Engine->Test and this has worked fine. But when we have tested the scenario by triggering IDoc from the R/3 system, it is throwing the below mentioned error in both at the comm chanel and at the SXMB_MONI acknowledgement.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 403 Service Error
points to be noted here:
1. Business Service has been configured correctly for triggering ALEAUD messages and ALEAUD messages are reaching R/3 successfully.
2. We have chosen option Keep Headers and Do not use SOAP header options.
3. We are passing some values to the SOAP Header from SOAP channel.
Please could somebody help us on the root cause of the error message.
We have run report IDX_NOALE for that particular IDoc so that it doesn't return any acknowledgement back to the R/3 system.
Thanks and regards,
Sugata
Edited by: Sugata Basu on Nov 19, 2011 12:40 PM

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Idoc to soap scenario - soap response error

hi
i am using pi 731 single stack.
the scenario is idoc to soap. the message mapping is working fine and output is generated successfully.
the message is failing in mesage monitor and communication channel monitor. error is -
Exception caught by adapter framework: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: VEN-OMI-1007:
This scenario is async scenario. How to soap remove this response message error.
rgds

Dear,
IDoc to Soap scenario we have to import wsdl at receiver end and map the field from the mapping document but some times receiver end some changes may happen. if it is correct only your mapping we have to conclude from the below points.
1. Check the mapping in Message Mapping and Operation Mapping Test and conclude.
2. you should check url from receiver that is correct or wrong.
3. ask the wsdl from receiver end.
the given ED and receiver side application is same this type of error will not come.
Please check at receiver application or else what ever new fields are added in reciver may be miss mach of ED.
Regards,
Kiran Polani

Hi, In a IDOC --- XI(BPM)--- SOAP Sync Scenario failrure.

Hi, In an IDOC ->XI(BPM)->SOAP Sync Scenario I observed recently messages are failing in SXMB_MONI with an error as:
com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://172.16.209.162/esdryrun/ContractData_Push. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
friends, could u plz help on this.
Thanks,
satya.

Hello,
This indicates a configuration issue with this SOAP receiver adapter. Please check the on line help for the configuration of the SOAP adapter (the link is below). Please set the indicator in the "SOAP Action" field.
Configuring the Receiver SOAP Adapter
http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
(Below is the extract from the link)
SOAP Action
Specify the SOAP action. The action specifies the value for the
SOAPAction in Web service messages; set the indicator.
Regards,
Sarah

Explain about Idoc to soap scenario

Hi All,
I am beginner to sap pi can anybody help me out, How to perform Idoc to soap scenario...

Dear Gaffar,
Please use the search functionality to learn.
Redirecting...
http://www.google.com/cse?cx=013447253335410278659%3Ak8ob9ipscwg&ie=UTF-8&q=idoc+to+soap+scenario&siteurl=www.google.com…
try out the scenario,create the thread if you face any issues.

Using ABAP Web Service tor convert IDoc to XML and transfer to SOAP Server

Hi all,
I have a problem to use ABAP Web Service to convert IDoc's to XML and then send them to a SOAP Server.
Currently we have the following landscape:
SAP->XI->Archive
The sap-system (ECC6.0) sends an IDoc to the Exchange Infrastructe. The XI maps the IDoc and converts it to the required XML format, used by the archive. Afterwards, the XML documents are sended to the SOAP Server.
So I'm trying to replace the Exchange Infrastructure with ABAP Web Service.
I've read a lot of posts and documents reagarding ABAP Web Serivce, converting IDoc's to XML, RFC and so on, but I'm not able to do the replacement.
I don't know how to start and which steps are required.
The required roles and authorizations at the sap-system and the service for soamanager and the Web Service Viewer are available.
First I thought to create the RFC and partner profiles and then the report to convert IDoc to XML as a BAPI. With this BAPI I supposed to create and define a Web Service. The problem is, I don't know how to trigger the report if the Idoc should be send to the archive.
Hopefully, someone has an idea or a how-to for me.
Thanks in advance.
Regards,
Christoph
Edited by: BigTicket on May 12, 2010 9:36 AM

Hi BigTicket.
A suggestion to trigger the BAPI / WebService at the IDoc receiving is to use a user exit or enhanced inside the idoc function module. When the idoc arrived to the idoc port the system start the related function module and then your user exit/enhanced in which you invoke your BAPI.
I hope this help.
Ciao.
Nicola

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

Error in IDOC(ALEAUD) to file Scenario

Hi ..
we have a client requirment were they want the ALEAUD acknowledgement in the form of file.
So we are creating a IDOC to file scenario, where IDOC is ALEAUD which is mapped to create a file in the traget system. but when we post the IDoc we get thwe following error.
*Note: have a small doubt. Can we use ALEAUD Idoc as a normal IDoc to File Scenario. because with the documents i understand that ALEAUD is a acknowledgment IDoc which is generated based on the request IDOC. but in our scenario we are manually using the structure of ALEAUD in the source 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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Kindly help me out .
Thanks in advance
Deepika

Hello,
If you need to send the ALEADUIT back to the SAP system if the file returns a successful ack, then you will need to have a BPM with a separate SEND step to send back the ALEAUDIT.
And check this ......
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
*******Reward points if found useful

IDOC to XML SOAP Scenario

Similar Messages

Maybe you are looking for