|Home • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Exchange Infrastructure (XI)
Time Bound File Processing - File to IDoc Scenario
By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies
document describes Time bound file processing scenario where in, a file
containing the employee work details is picked from a FTP server system
(Sender/Source) and sent to SAP System (Receiver/Target) via Exchange
Time bound file processing scenario requires a set of configurations in XI
system and the Receiver—SAP system.
guide gives step-by-step procedure to pick a file from Sender—FTP system to
Receiver—SAP system. A business system representing Sender-Third Party System
hosts a file, picked by XI at regular intervals using Sender File Adapter. Then
XI sends the IDoc to the receiving business system (Receiver SAP System) by
using the Receiver IDoc Adapter.
Maintain the System Landscape Directory
Maintain Technical Landscape: As the receiving system is SAP System it
should be configured as WAS as ABAP technical systems. In the Technical system Browser, create a New Technical
Maintain Business Landscape: Create a Business system to associate to the
technical system which was created in the previous step. During creation of this
business system, select role of the system as Application system.
Configuration in the integration server
Create RFC destination: Using transaction SM59 create an RFC Destination
of Type 3 in order to establish communication with the Receiver SAP System
Note: Created RFC Destination should point to the
Create Port: Create a port using Tcode: IDX1, which will be employed in
later stages to import the IDoc metadata. In this example, the port is SAPXXX
(Port for receiver system) where XXX is the system ID of the SAP backend system.
The created port has to be binded with the RFC Destination of the Sender SAP
System configured in the Step 3.a above.
Transaction IDX2: This configuration step is used to import the metadata
of the IDoc using the corresponding Business system port (created in the above
step) as below
Design the scenario in the integration repository
Import IDocs: Import the IDoc from Receiver SAP system. Enter the details
of the receiver system as below. In this scenario ZMREPT.ZMREPT02 is the inbound
message type. The inbound IDoc should be imported from the Receiver—SAP
IDoc structure is as follows:
Creation of Data type: The outbound data type is be created resembling
the structure of Inbound IDoc
File to be uploaded is as follows:
Employee Monthly details.
Create Message type: The outbound message type is to be created for
source data and can be viewed in the screen shot explained near Mapping.
Create Outbound Message Interface as shown in the screen shot below:
Define ‘Message Mapping’ from Outbound message interface to inbound
message interface(use custom idoc) as follows:
Define Interface mapping to include Outbound interface as ‘Source
Interface’ and Inbound interface as ‘Target interface’.
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards