Let`s say you want to support a B2B transaction like procurement using an industry standard. For this exercise, we can use the OAG. It is very similar to RosettaNet, CIDX and STAR in that the business process and technical definition of the message are provided by the organization. The objective of this exercise is to demonstrate the process of importing external definitions of industry standard messages into the SAP XI system. The following process can be used for almost all XML industry standards such as RosettaNet, CIDX, STAR, ACORD, PIDX, ebXML, etc. SAP provides a number of standard interfaces that are centrally managed and delivered for SAP, external partners, and customers, and can be downloaded for use in XI. For more information, see the Service Marketplace section below. In the previous SOAP to RFC example, we used the RFC function in SAP ECC and exposed these function modules remotely through web services to expose the SAP APIs. This document explains exactly the reverse flow. that is, HTTP to SOAP means that PI/PO calls an external Web service (Calling Sample Currency Conversion Web Service) currencyconverter.kowabunga.net/converter.asmx hosted on a third-party server through the Receiver`s SOAP adapter. Unlike a monster blog, I divided this exercise into 3 smaller parts.

For this exercise, we use ORDERS. COMMANDS05 IDOC. More information on this IDOC is available in the IFR. Otherwise, switch from your ERP system to the WE60 transaction. Enter ORDERS05 and enjoy reading! If you have access to SAP Service Market Place, download the XI Content Package for your specific version of SAP ERP or R/3. In this exercise, we use an SAP R/3-4.6C system. The Support Pack (SP 48) contains the necessary SAP interfaces (for example, ORDERS. ORDERS05), which are used in the exercise. Here are some of the interfaces in SP48 SAP APPL.

If you have access to the MarketPlace service, please obtain the SAP XI CONTENT application for SP48. If not, simply download the ORDERS. ORDER05 IDOC to your own CFC. (Note: There are already a few blogs describing how to download IDOCS from ERP to XI…) The order (and approximate time) is as follows: This is the first part of my 3-part series on B2B support with a specific industry standard in SAP Exchange Infrastructure. SAP supports business-to-business (B2B) interoperability in the high-tech, chemical, and automotive industries with RosettaNet, CIDX, and STAR standards. I am one of the few developers who has worked on integrating these standards into SAP content packages for XI. SAP offers a complete end-to-end solution that includes industry standards, integration platform, and application. archive.sap.com/kmuuid2/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8/HTTP%20Client%20Sample%20Code%20for%20Communicating%20with%20Exchange%20Infrastructure%203.0.pdf In this example, HTTP makes the request to the PI/PO and PI/PO call Web service through the SOAP adapter. The SOAP adapter response is returned to the PI/PO response and displayed on the HTTP Response tab of the HTTP test client. To be successful with this blog, you need to have access to at least 3 things. We`ll use the following URL for our sample demo. wiki.scn.sap.com/wiki/display/XI/HTTP+To+RFC+Synchronous+Scenario+-+FAQs Step 1.

Test the WebService to get a conversion rate of 1. Start the integration generator (transaction code SXMB_IFR). 2. Log in to the System Landscape directory. 3. Click on the “Software Catalog” link. 4. Select Products as the software type. 5.

Click the New Product button. 6. On the Define Product screen, do the following: 7. Enter the “xyz.com” vendor 8. Enter the name “MY product” and version “1.0” 9. Choose Create. Your product has been created. If you meet the above requirements, we will start preparing the environment. 10. Keep product and supplier information.

11. Enter the name “OAG_EXAMPLE” and version “30.1” of your CFC. 12. Select Create. Your software component has been created. currencyconverter.kowabunga.net/converter.asmx A final step before entering the mapping will be to create an XI message interface based on the external definitions that we just downloaded in XI. In order for the structure of the ProcessPurchaseOrder interface to be set correctly, we had to upload additional supporting XSD files.