Receiving IDOC through SOAP

Hello everyone,
Being new to XI, i'm still trying to process this brave new world. I've read and developed some simple scenarios using webservices. The last one i did was in a company A that needed to send ORDERS05 Idocs to company B. The latest provided a wsdl file used to create an external definition of the order document being sent. mapping is direct between all fields.
Now, Company B needs me to setup things here, and receive the IDOC sent from company A (message monitoring states that all messages from there are sent with success, but still missing the part i just described).
What is the best way to achieve this? can anyone point me to a document i could read on the subject (IDOC->IDOC with SOAP).
Thank you in advance

I'll try and explain the best i can:
In company B, i have two SWC:
COMPANYA - Represents the company that sent the IDOC ORDERS05 via webservice.
PI_COMPANYB - Represents the company where i stand fisically, where the IDOC must arrive and be integrated into SAP R3.
Here in company B i have created:
- edORDERS05 - An external definition, on a namespace dependent of COMPANYA, importing a xsd file ORDERS05.
- miOrdersDocuments - A message interface, of type edORDERS05.
In Integration Directory i have:
- COMPA - Party representing Company A
- COMPAPI - Business Service of COMPA with channel SOAP_Receiver_OrderRequest.
- SOAP_Receiver_OrderRequest - channel of communication to receive the webservice arriving from Company A, with URL like this:
http://65.222.222.222:50000/XISOAPAdapter/MessageServlet?channel=COMPB:COMPBPI:SOAP_Sender_OrdersRequests&version=3.0&Sender.Party=http%3A%2F%2Fsap.com%2Fxi%2FXI%3AXIParty%3ACOMPB&Sender.Service=COMPBPI&Interface=http%3A%2F%2FcompanyA.com%2FOrdersRequests%5EmiSalesDocumentsReq
The URL was snipped from "Location" tag in wsdl webservice previously created in Company B, using the "Tools->Define Webservice" from Integration Repository.
Right now the idoc is being sent successfully from SAP R3 to XI Engine in Company A, and then sent to Company B where the message should be arriving (logs in proxy at the company say so), but when arriving at XI Engine of company B, nothing appears on sxmb_moni transaction.
Hope i explained everything as asked.

Similar Messages

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

SOAP Receiver/Sender in IDOC- XI- SOAP receivers?

hi,
i have idoc-> xi-> soap receiver.
1. How can i get a response back from soap receiver?
2. in the above scenario is SOAP the receiver or agian the sender?
3. not sure how i can get a response back from the soap receiver?
any tips would be helpful.
thanks,
tirumal

Hi,
It should be
<i>
Under Target URL, enter the complete address (URL) of the Web service provider that you want to send the message to.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
What are you specifying?
Can you give the entry in Target URL...
Regards
Suraj
Message was edited by: S.R.Suraj

IDoc to SOAP Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

Send/receive IDOCs to SOLMAN system using AS2 protocol!

Hi All,
I want to send/receive IDOC file to/from web based SOLMAN system. Currently I'm using FTP server to send/receive IDOC file.
As of now the current process is to send the IDOCs from ECC to FTP server and from FTP to third party and vice-versa. But due to some constraints, I'm bound to use web based SOLMAN system. Please, can you let me know how to send/receive IDOC files to SOLMAN. Is there standrad FM/method to connect to SOLMAN from ECC as in case of FTP we have FM 'FTP_CONNECT'. Heard that same functionality in case of SOLMAN can be achieved through AS2 protocol.
Kindly help.
Thanks.
Regards,
Mukesh

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

Creation of IDOC through abap program.

hello all,
I hav created idoc through abap program. I hav used FM 'Master_idoc _distrribute'.this program creates an idoc but giving status 30. can any one tell me how to get status 03. I hav already created port, Logical sys,partner no.,distribution model.
My Program is as follows:
ABLES : CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control Record
       ORDER_NO TYPE CRMT_OBJECT_ID VALUE '5000000032'," SEGMENT ORDER DATA
       PRODUCT TYPE CRMT_ORDERED_PROD VALUE 'SRV_01',
       QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZORDER_NUM OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.     "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZORDER_NUM'.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZORDER_IDOC2', "Message Type
              C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',          "Partner type of receiver
              C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'BSNL_OUT',
              C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000006',
              C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'SAPBCD0000',
              C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'BCDCLNT100',
              C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZORDER2',
              C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.          "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*&      Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM.                    " generate_control_record
*&      Form send_idoc
FORM SEND_IDOC.
ZORDER-ORDER_NO = ORDER_NO.
ZORDER-PRODUCT = PRODUCT.
ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = S_CTRL_REC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = T_COMM_IDOC
      MASTER_IDOC_DATA               = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    COMMIT WORK.
    LOOP AT T_COMM_IDOC.
      WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
    ENDLOOP.
ENDIF.
ENDFORM.                    " send_idoc
I hav created segment , basic type,message typealso and release also .I also linked them.
Plz help me.
Hemlata

Hi Hemalatha,
Just call this Progream RSEOUT00 from your Zprogram and pass the basic parameters like IDOC number, Basic type,Partner number etc.
You can check the parameters by executing the Program RSEOUT00.
This Program will change the status of your IDOC 30 to 03.
Thanks.
Note:Reward Points if you find useful.

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <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="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
<i>CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only</i>
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

Idoc to soap sync without bpm. is it possible? Helping me..

Hi Experts,
i have a small clarification Idoc to soap sync interface in sap pi 7.0. i created IDoc to Soap sync using BPM but some times the signals are stuck due to load issue in swpr, while reprocess those signals all going successfully to the receiver. So We are trying to eliminate BPM.
I just wanted to know Idoc to Soap sync scenario without BPM is possible or not in SAP PI 7.0?
if it is possible kindly send me the links
Regards,
Kiran polani

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

IDOC to SOAP

Dear All,
My scenario is IDOC to SOAP(Asynchronous) .
In MONI ,I am able to see the succesful message but in receiver communication channel, I am getting the following below error,
SOAP:call failed:java.net.ConnectException:Connectiontimedout:
Please suggest me on this.
Regards,
Lavanya B.

Hi Lavanya,
Its very hard to tell exactly where it is going wrong. Some issues are already mentioned by prateek. Apart from it you can take the receiver payload and see whether it is the same as expected by the webservice or not. If possible try to load this payload manually so that if any issues are there you may come to know.
Regards,
---Satish

IDoc - XI - SOAP - XI - Mail

Hi all,
I want to do the following scenario:
IDoc is sent to XI, Xi is doing a Soap call with information from the Idoc, from the soap call I receive a response code. This response code will be sent by mail TOGETHER with info from the Idoc.
I've made the scenario from Idoc to Soap call. I also know how to sent information out with the mail adapter.
Where the problem is for me, is the combination of this all together.
I guess I have to use BPM for this?
Can anyone point me into the right directions for this problem?
Thinks like wich message types, interface mappings etc?
Thnx in advance!

I guess I have to use BPM for this?
Not necessary.
U may perform a Idoc - Xi - Mail scenario with Soap lookup in mapping
Webservice Calls From a User Defined Function.
Regards,
Prateek

Unknown receiver adapter (name = SOAP)

Hi,
I have an IDOC-XI-SOAP(Web service) scenario which is resulting in the following error
<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="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
<SAP:P1>SOAP</SAP:P1>
<SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unknown receiver adapter (name = SOAP)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any pointers..?

hi Siru TK
Check with thread
receiver soap error
Error in SOAP synchronus request.
Thanks!!

IDOC -XI-SOAP one sender different receivers based on condition

Hi All,
I have an IDOC to SOAP scenario.
For each record based on the input flag XI has to send the any one of the request ...like either create or update or delete request. All these message types are a part of single WSDL.
How can i do it?
Thanks in Advance
Jyothsna

hi There are two ways you can do this:
1. Without BPM - Since you have to create all the target messages adn you want either the 1st and second, or the first and third: create two multi-mapping with one and two, and one and three. In the receiver determination check the condtion based on which you decide the second or the third message has to be created and route it to the correct mapping accordingly.
2. with BPM, create all the target mapping. In the BPM check the condtion in the switch and do a send accordingly.
You can do this either on Receievr Determination or on Interface Determination.
Add multiple Receievrs/ Interfaces and then add the conditons on which the target should be choosen
to use Xpath for your receiver det. ref these blogs;
a combination of logics should help you in this case ...
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
pls reward points if solution found helpfull
regards
chandra.k

IDOC---XI----SOAP(Webservice) Sync

Experts,
Need to Develop IDOC-XI--SOAP(Webservice) Sync Communication Interface
I have importing the Standard Idoc & External Def for WSDL ,which has the Request & Response Structure.
I need to handle the SYNC message in the XI and ignore it/ do not pass to the source system.
Any Weblog will help ,
Thnaks
Edward

Hi Edward,
Follow the steps given below
In IR create following objects:
1: Import Web Service definition file in External Definition.
2: Import IDoc ZDLVRY. (I have used custom IDoc)
3: Create Message Interface
     a. Abstract Synchronous for sender
     b. Abstract Synchronous for Receiver
     c. Abstract Asynchronous for request
     d. Abstract Asynchronous for response
4. Create Message Mapping for Source Request to Target Request
5. Create Message Mapping for Target Response to Source Response.
6. Create Interface mapping and specify proper input in request and response tab.
7. Create Integration Process
Configuration in ID:
1. Create Integration Process for BPM created in IR.
2. Create receiver determination
    a. From SAP R/3 to Integration Process
    b. From Integration Process to Third Party (Web Service)
    c. From Integration Process to SAP R/3
3. Create Interface Determination
    a. From SAP R/3 to Integration Process
    b. From Integration Process to Third Party (Web Service)
    c. From Integration Process to SAP R/3
4. Create Receiver Agreement
5. Create Communication channel for Soap Receiver and IDoc Receiver.
6. Create Receiver Agreement for Soap Receiver
7. Create Receiver Agreement for IDoc Receiver
if u have any doubt in any step please let me know
Regards,
Manisha

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 and transport process

Scenario:-IDOC to SOAP:
We got the WSDl file from Target system and our current scenario is working perfectly fine in Dev.
Requirement:
I have to send the same IDOC to two different SOAP target system with different SOAP URL WSDL structure is same only the URl differ.
Solutions which I thought of:
1) Separate Design for both the scenarios in IR and one CS with two SOAP channel, interface and receiver determination and agreement.
2) Use the same WSDL file structure for both the case. this will avoid the separate IR configuration. in this case there will be common MM,IM. In ID the configuration will remain the same as the case one.
In 2 case I would like to know whether I can use the WSDL file which has the details of first SOAP target for the second SOAP target. Will this WSDL file act simply as structure? Does the URL mentioned in the WSDL file will create any problem?
Transport process:
SOAP WSDL file has different URL for DEV,QA and PROD. when I transport the IR from Dev to QA the Dev WSDl file will be reflected in QA as external definition, I wanted to know what is the best method to do the transport in the above situation.
Solution which I thought of
1) Go to QA IR and import the QA WSDL file.
2) Go to Dev and import the WSDl file of QA and import it in QA which avoids manual import in QA, if I go by this way will this affect the testing of my interfaces in Dev system.
What is the best method we do the transport for the above scenario.
Need ur suggestions?
chirag
Edited by: Chirag Gohil on Oct 1, 2008 1:29 PM

Hi Chirag,
As far as i know there wil not be any target URL in the WSDL File which we bought from the webservice application.
Can u please paste the WSDL File which u have .....
If we come to Dynamic URL Config means, as per my concern
You have only 2 Target locations to receive the Idoc. so its better to go a head with ur existing approch itself.
Why becase for Dynamic URL Config.....
we have to maintain the target URL's in One Table and need to use RFC lookup to pick this URL Dynamically based on some value from the Input file.
And also we need to use Standard UDF code for Dynamic config in Mapping .
And need to check the option Use ASMA in the Receiver SOAP CC.
Regards
Seshagiri

Receiving IDOC through SOAP

Similar Messages

Maybe you are looking for