SAP AG.co in Will Give information of SAP related meterials Like SAP Platform and Operation,,SAP Security , SAP Enterprise Portal (EP), ,SAP Knowledge Management (KW), SAP Business Intelligence (BI), Exchange Infrastructure (XI),Application Server, Mobile (MI), Master Data Management MDM, Composit Appications Frame work,Web Dynpros,OOPABAP,Blog,Intergration Bulder, Integration Repository (IB),Integration Directory (ID).System Landscape Directory (SLD), And Adopter Configuration like File to File,File to JDBC, File to IDoc, File Content Convertion, RFC, HTTP,SOAP,XI Interview Questions,Xi Sertification Questions, and many more about SAP Netweaver Platform XI Training And Tutorial and XI interview Questions ..

SAP Exchange Infrastructure Tutorials

SAP XI Exercises File to IDoc

Exercise 1: File sender to IDoc

•  Processing mode: delete (the file will be deleted after being processed).

•  The sender file adapter is now configured. Save your communication channel.

•  The next step is to create a “Sender Agreement” object. This defines a binding between the communication channel you just created, and the outbound interface.

•  In the left frame, right-click on “Sender Agreement” à New.

•  Select your service (no party).

•  Select your interface (Vendor_out). Make sure that the correct namespace is utilized.

•  In the screen “Edit Sender Agreement”, use F4 help for the Sender Communication Channel field. Select your communication channel (File_sender). Save and close.

•  From the left frame, create a new “Receiver Determination” object. This is the main part of the routing process, where you assign a receiver for your message.

•  Select your sender service and interface

•  In the “Configured Receivers” area, choose the existing service for the target R/3 system (M13_800). Save your receiver determination.

•  In the following steps, you will create an “Interface Determination” object. Now that we have defined a receiver for the message, we need to assign an inbound interface, and an interface mapping (if necessary).

•  In the area “Configuration Overview for Receiver Determination” at the bottom of your screen, hit refresh.

•  In the column “Receiver (Partner/Service)” right-click and select “New Specific”, in order to create a new interface determination object.

•  You are now in the screen “Edit Interface Determination”. In the section “Configured inbound interfaces” select the following using F4 help. When you are done, please save the Interface Determination object.

•  Inbound interface: CREMAS.CREMAS03

•  Interface mapping: Vendor_out_CREMAS03

•  Finally you will create a “Receiver Agreement” object. This will allow you to assign a receiver communication channel to the receiver service/interface you have chosen.

•  Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of the screen, hit “Refresh”.

•  In the column “Receiver Determination (Communication Channel)” right click and select “New Specific”.

•  In the screen “Edit Receiver Agreement”, for the field “Receiver Communication Channel” use the input help (F4), and select the communication channel “XIWS_IDoc_receiver”. This is a predefined channel which is used for all inbound IDocs into the R/3 system. Save the Receiver Agreement.

•  Go back to the main receiver determination screen and refresh. Now your configuration is complete. Before activating the objects we need to set up the input file in the next step (indeed, as soon as your sender communication channel is activated, the polling sequence of the file adapter will start immediately).

Step 4 – Testing

•  Find the file Vendor[XX].xml which you had previously saved, and copy it to your shared folder under \\<hostname>\workshop\group[XX]. Please note, the name of the file should match exactly what you have specified in your sender communication channel.

•  Now you can go back to the Integration Directory, open your change list and activate your objects.

•  It will take a few seconds for the cache refresh to take place, and for your changes to be propagated to the Adapter Engine. Please ignore any message box that you may receive subsequently. This has to do with the propagation of configuration changes to some decentral adapter engines which are not in use.

•  Monitor your directory. After a few seconds your file VendorXX.xml should disappear. This means that the file adapter has successfully processed it and the file was deleted.

•  In SAPGui, choose monitoring à Integration Engine monitoring (transaction SXMB_MONI).

•  Choose “monitor for processed XML messages”. You can filter using different criteria, for example by date and also by sender service (find your own business service name in the drop-down list). In the monitor, your message should appear with a checkered flag (message processed successfully). From there you can also navigate to the IDoc adapter.

•  In the backend R/3 system, go to transaction WE05 and search for IDocs according to the logical system name used by your sender. Verify that your IDoc was posted. If everything goes well, the IDoc should have status 53 (application document posted). If you expand the status record you will see the vendor number that was created. Write down the vendor number for future reference.

•  Check in transaction MK03 that your vendor was created.

Appendix: naming conventions and terminology

Exercise 1

Transformation rules for Vendor à CREMAS03 mapping (constants are highlighted).

Previous

 Back to SAP XI Tutorials