Additional Blogs by SAP
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

How to Support Industry Standards in XI (Part III of III) - Config & Test

Former Member
‎09-09-2006 10:22 PM
0 Kudos
!https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/... !https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/...

h3. Welcome back! !https://weblogs.sdn.sap.com/weblogs/images/297/THUMB.jpg|height=25|alt=image|width=30|src=https://we...!
Thanks for sticking with me so far!!! I apologize for the delays in providing the final installment of this series.
I'll be at TechEd 2006 in Las Vegas. Hope to see you there!

h5. To recap The first two blogs ( How to Support Industry Standards in XI (Part II of III) - Mapping" target="_blank"> Part I


How to Support Industry Standards in XI (Part I of III) - Interfaces

) spent time in the SAP XI Integration Repository. We will leave that area of XI to go to the XI Integration Directory. We at SAP typically distinguish between '[Design Time | http://help.sap.com/saphelp_nw04/helpdata/en/61/fec608bc27654daadb20c1e6da7dd1/content.htm]' activities and '[Configuration Time | http://help.sap.com/saphelp_nw04/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/content.htm]' activities. Design-time relates to the XI Integration Repository and configuration-time relates to the XI Integration Directory. You have created your design time objects and now you would like to test.




Let's get down to business. The basic scenario looks like:


!https://weblogs.sdn.sap.com/weblogs/images/297/BUS_Scenario.jpg|height=205|alt=image|width=600|src=h...!


Or for the dyslexic: (like me) OAG XML --> XI --> R/3 IDOC


Note:  picture reprinted and edited with out permission from Sam Raju .



Step I: Configuring XI


From ABAP, start the Integration Builder (Transaction Code: SXMB_IFR).
    1. Login to the Integration Directory.

Click the Create Object button.


It's also possible to import an Integration Scenario that you define in Design Time in the Integration Repository. 
For more info see Shailesh Mane's
B2B Configuration (Part I) - Creating an "Integration Scenario" on this topic.  Of course, you can always ask me to do a step-by-step
blog specifically for this series, but I'll wait for your feedback... =P




Objects to Create


In the SAP XI Integration Directory, we will need to create or assign the following objects in


===============================


Party


We will need one (1) party for this Configuration Scenario - a Sender.  We will also create a Business Service and a Communication Channel under this party. 

  2. Right click on the Party icon
  3. Select "New".
  4. Enter OAG_Sender in the Party* field.

    Please note that case will matter when you get to Section II: Testing!!!




    !https://weblogs.sdn.sap.com/weblogs/images/297/5OAGSender.jpg|height=95|alt=image|width=225|src=http...!



  5. Navigate to the Identifiers section
  6. Under "Agency" enter the identifier for the SAP R/3 system which should be in the System Landscape Directory (SLD) (ex: BC_WC1800)
  7. Under "Scheme", enter ALE#KU
  8. Under "Name", enter the actual SAP R/3 Customer Master identifier for this trading partner (ex: DLR2_GRP02)


    !https://weblogs.sdn.sap.com/weblogs/images/297/8IdentifiersFilled.jpg|height=110|alt=image|width=305...!


Save your Party.


Business Service


    1. Create a Business Service under the Party OAG_Sender.
    2. Right click on Business Service, click New.
    3. Name the Service*, OAG_ProcessPurchaseOrder_Sender. Click Create.
    4. Click the "Sender" tab
    5. Click the Insert Line button
Click the F4 button, the Select Interface window will appear.
    1. Scroll through the list. Select the check box for ProcessPurchaseOrder



!https://weblogs.sdn.sap.com/weblogs/images/297/12BS_SenderIntfc.jpg|height=135|alt=image|width=535|s...!



Save your Business Service.


Communication Channel


    1. Create a Communication Channel. Right click on Communication Channel, click New.
    2. Name the Communication Channel*, OAGSender_Send_ProcessPurchaseOrder. Click Create.
    3. On the Parameters tab, click the F4 button for Adapter Type*.
    4. The Choose Adapter Metadata window will appear, select the SOAP adapter. Click OK.



===============================


Service Without Party


Next let's assign the Receiver.  In this example, this is the SAP R/3 4.6C backend system.  We'll assume you have already made the necessary entries in the SLD. 


  2. Click on the "Objects" tab



    !https://weblogs.sdn.sap.com/weblogs/images/297/9ObjectsPartyReceiver.jpg|height=120|alt=image|width=...!



  3. Navigate to the "Service Without Party" objects.
  4. Click on "Business System"
  5. Right Click on the appropriate SAP R/3 backend system. In this example, select BS_WC1800.
  6. Expand the Communication Channel node
  7. Select the channel associated with IDOC communication. In this example, select IndustrySpeak_IdocReceiver
  8. Select "Add to Scenario"




    !https://weblogs.sdn.sap.com/weblogs/images/297/10AddToScenario.jpg|height=155|alt=image|width=310|sr...!



  9. Select the appropriate Configuration Scenario you created earlier (ie: Guanzon_SDN_Blog)
  10. Click Add. The Business System and Communication Channel will be added to your scenario, under Service Without Party.



    !https://weblogs.sdn.sap.com/weblogs/images/297/11IdocChannelAssign.jpg|height=128|alt=image|width=28...!



  11. Save and Activate your changes.


===============================


Receiver Determination


Three more items to go...  We still have to create a Receiver Determination (RD), Interface Determination (ID), and Receiver Agreement (RA).  Let's create a Receiver Determination:


  2. Right click on Receiver Determination, click New.
  3. Under the Sender section in the Party field, please click F4.
  4. Select the party OAG_Sender. Click OK.
  5. Under Service*, Click F4.
The Search Result should return the Service OAG_ProcessPurchaseOrder_Sender with the +Party + OAG_Sender.


===============================


Interface Determination



  2. Right click on Interface Determination, click New.
  3. Under the Sender section in the Party field, please click F4.
  4. Select the party OAG_Sender. Click OK.
  5. Under Service*, Click F4.
The Search Result should return the Service OAG_ProcessPurchaseOrder_Sender with the +Party + OAG_Sender.
    1. Under Interface*, Click F4.
      The Search Result should return the ProcessPurchaseOrder interface.



    2. Please ensure that the Software Component Version is SAP APPL 4.6C. Click OK.


===============================


Receiver Agreement



  2. Right click on Receiver Agreement, click New.
  3. Under the Sender section in the Party field, please click F4.
  4. Select the party OAG_Sender. Click OK.
  5. Under Service*, Click F4.
The Search Result should return the Service OAG_ProcessPurchaseOrder_Sender with the +Party + OAG_Sender.
    1. Under the Receiver section, leave the Party field blank.
    2. In the Service* field, Click F4. In the Search Result, select the Service without PartyBS_WC1800. Click OK.
    3. In the Interface* field, Click F4.
    4. The Select Interface window will appear, scroll down to the appropriate target interface, in this example select ORDERS.ORDERS05


    2. Please ensure that the Software Component Version is SAP APPL 4.6C. Click OK.

    1. Click Create.
    2. In the Receiver Communication Channel*, click F4.
    3. Select the appropriate inbound (backend) communication channel, in this example select IndustrySpeak_IdocReceiver

    2. Leave the Header Mapping fields blank


Congratulations!


You've now completed the basic configuration objects necessary in the Integration Builder.
Let's move on to how to test this scenario.




====================================================



Step II: Testing the Scenario


!https://weblogs.sdn.sap.com/weblogs/images/297/BUS_Scenario.jpg|height=205|alt=image|width=600|src=h...!



This scenario involves a trading partner (OAG_Sender) to send a message to a recipient who has SAP Netweaver and an SAP R/3 4.6C system.
  The SAP Exchange Infrastructure (XI) will receive an OAG  XML message sent by the HTTP Client.

Of course, you can use the Quick Test Tool (QTT) in the Runtime Workbench (RWB) in XI to simulate sending messages. More on the QTT in a separate blog...



!https://weblogs.sdn.sap.com/weblogs/images/297/24QuickTestTool.jpg|height=190|alt=image|width=445|sr...!



Prerequisites for testing

    2. HTTP Client
    3. Sample XML file
An SAP ERP backend (preferably one that has ALE and the inbound ORDERS.ORDERS05 IDOC configured)
Note: documentation for this topic (#3) is out of scope - please see elsewhere in SDN for this info







  2. First, prepare the XML file to be sent from the HTTP Client to XI from the party: OAG_Sender.

Have a look at this
XI - A Heavyweight Alternative to Notepad (for XML)   =P for the XML input file to be used in the HTTP Client.


Next, please have a look at this HTTP Client Code Sample. My distinguished XI RIG colleague, Joachim Orb has graciously allowed me to post +his +code found here.


Step III: Monitoring XI



  2. From ABAP, goto "Integration Engine - Monitoring" (Transaction Code: SXMB_MONI)

      2. Alternatively, through the menu path:

        Exchange Infrastructure --> Monitoring --> Integration Engine - Monitoring.

  3. Click "Monitor for Processed XML Messages"
  4. Enter the appropriate date/time range for when you sent the message from the HTTP Client to XI.
Click the Execute (F8) Button.


If you get the Checkered Flag in the Status column, you can move to Step IV.




Otherwise, if you received some other status than the checkered flag, please recheck and compare all of the values you entered in the HTTP Client against the XI Configuration objects. Make any necessary modifications and re-run the test by sending the message to XI.



Step IV:  Monitoring SAP ERP (R/3)



  2. Login to your SAP ERP system.
  3. Monitor the IDOC's received on the SAP ERP system (Transaction Code: WE02).


      2. Alternatively, from the meun navigate to Tools --> ALE --> ALE Administration --> IDoc Display --> Display

  4. Enter the appropriate time and date parameters, based on when you sent your OAG XML message from either the HTTP Client or XI Test Tool.
Click the Execute button or the F8 button.
Click on the Data records for info on the different segments of the IDOC, this is essentially the business payload.  For more info about IDOCs please see my IDOC Information on IFR....  Additionally, you can check out SAPGenie (Thanks Sam Raju for this link!).



Voila!

You're done.  We've now had a chance to have a look at how to support industry standards, such as OAG, within SAP XI.  We've uploaded interfaces, created mappings, configured, tested and monitored XI.  In addition, we have had an opportunity to peak into the lovely functionality of SAP R/3.  I hope you've learned something, as I've had a fun time producing this series of Blogs!  Cheers! 





Note:  My XI system was upgraded from NW04 SP14 to NW04s SP08 between the publishing of How to Support Industry Standards in XI (Part II of III) - Mapping
and this final installment.  Please allow for any unintentional image inconsistencies in this blog.


4 Comments
Popular Blog Posts