Time Bound File Processing - File to IDoc Scenario

By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies

1.

Introduction:

This 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 Infrastructure.
A Time bound file processing scenario requires a set of configurations in XI system and the ReceiverSAP
system.
This guide gives step-by-step procedure to pick a file from SenderFTP system to ReceiverSAP 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.
2.

3.

Maintain the System Landscape Directory

a.

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 system.

b.

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

a.

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 ReceiverSAP system.

4.

b.

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.

c.

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

a.

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 ReceiverSAP system.

b.

IDoc structure is as follows:

c.

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
1,1256,suraj
2,1,40,25
3,yash,consultant
4,40,25

Monthly

details.
kumar,Pabbathi,9-7-1974

d.

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.

e.

Create Outbound Message Interface as shown in the screen shot below:

f.

Define Message Mapping from Outbound message interface to inbound message

interface(use custom idoc) as follows:

g. Define Interface mapping to include Outbound interface as Source Interface and Inbound interface
as Target interface.
contd..

Time Bound File Processing - File to IDoc Scenario

Previous..
5.

Configuration in Integration Directory

a.

Import Business system from SLD for receiver systems

b.

Create a Business server to point a file system

c.

Receiver system pointing to SAP system

Create Sender Communication channel with following parameters
Type of adapter

File

Transport protocol

Filesystem (NFS)

Message protocol

File Content Conversion

Adapter Engine

Integration Server

And the content conversion parameters as follows:

d.

Create Receiver Communication channel with following parameters

Type of Adapter: IDoc

For eg.,

e.

Create Sender agreement with required Service and Outbound interface

f.

Create Receiver agreement with the above sender service, receiver service and inbound
interface

g.

Create Interface determination includes Sender, Outbound interface, Receiver, Inbound

interface

h.

Create Receiver determination with the above values including the required mapping

i.

Prepare the necessary ALE setting for receiving the IDocs in the receiving system like
Logical systems, partner profiles, port, RFC destination, Process code etc..

j.

Place the file in the source directory and activate the created objects both in integration
repository and integration directory.