File to IDOC

Scenario: Simple Simple File to IDOC The requirement is for an Inbound Interface (Legacy to ECC) using IDOC. Find below the following steps: System: RPI – 100; Transaction  – SXMB_IFR 1. Login to Enterprise Services Builder

Note: It might take some time for the application to get downloaded.

Page 1

Once the application gets downloaded, we need to enter our credentials and finally the ESR (Enterprise Services Builder) will be open.

1. Need to import the SWCV from the SLD I to ESR before creating the design objects. Click on ‘Object’ & choose ‘New’ to create a SWCV for your design objects.

Click on the

icon to choose from the SWCV that are present in the

SLD. Select the appropriate SWCV that you have created . This step is done once only , for each new interface/exercise we only create the namespace under that SWCV.

Page 2

2. Look for the appropriate Software Component  – ‘-DELOITTE_USI_PI_LEARNING of  Deloitte’.

3. Expand the Software Component and find the Software Component Version  – DELOITTE_USI_PI_LEARNING of Deloitte ‘.

4. Right Click on the Version, Click on ‘NEW’ and opt for Namespace option.

Page 3

5. Lets enter the following Namespace - https://rcholleti/Ex4/File_to_IDoc

6. Click on Create, Save and Activate.

Page 4

7. Once we activate the Namespace (for any other object), the same would be visible on the Left Side.

8. Creation of Data Types: Right Click on the Namespace and click on New.

Page 5

9. Enter the Data Type Name – ‘Cust_DT’ with appropriate Description.

10. Click on Create. 11. Assign the corresponding fields to the Cust_DT Data Type.

We have 4 fields – 1) Customer 2) AccountGrp 3) Name1 and 4) Search Term

Page 6

12. Save and Activate. So the Source Data Type ‘Cust_DT’ is created. 13. Now we need to create the Message Types  – ‘MT_Cust’ 14. Just like creating the Data Type, select the same Namespace, Right Click and New.

Page 7

15. Once we drag and drop the source Data Type on the ‘Hand’ sign, we find a message as shown below – ‘Loading structure for Message Type ‘Cust_DT’.

16. After few seconds we find all the fields for the Source Data Type as shown below.

17. Save and Activate. So the Source Message Type is created now.

Page 8

18. Now we need to create the Service Interfaces  – ‘SI_Cust’ under the same Namespace.

19. Once we click on Create, we find the Source Operation with identical name as compared to the interface:-

20. In the Operation, we assign the Message Typ e; rather we drag and drop it to the Name column as shown below.

Page 9

21. Save and Activate. So the Source Service Interface is created. 22. So now we have created Namespace, Data Types, Message Types, and Service Interfaces. 23. For the Target Structure, in the Imported Objects, we need to Import the IDOC. In our scenario, it is ‘ DEBMAS.DEBMAS03‘ as shown below.

24. Now we need to create the Message Mapping. 25. Alike other object creation, select the Namespace, right click and say ‘New’. Look for Message Mapping under Mapping Objects as shown below.

Page 10

26. Click on Create and then find the below shown screen.

So here we need to assign the Source Message Type and Target Message Type and finally map all the fields.

Page 11

Look for your own Message Types for source and target within your own Namespace.

Once we double click on the source message type, we find all the fields of the source structure as shown below. Similarly we do the same steps for the Target Structure.

Page 12

27.Now one of the most important steps, Mapping. How to do it? Let us find it out in the below provided screen shot.

Page 13

28. Follow similar steps for the other fields. 29. Save and Activate it. So Now Message Mapping is done. 30. Now we create Operation Mapping under the same Namespace.

31. Click on create and find the below shown screen.

32. Here we need to provide the Source and Target Operation. Also we need to provide the Message Mapping. Provide  – meaning – drag and drop or via F4 help.

Page 14

33. We find that the Source and Target Messages are Blank. To fill them, click on Read Operations.

34. Save and Activate it. The Operation Mapping is done. 35. Now we move to Integration Builder (IB) for the rest of the Steps.

Page 15

Integration Directory (ID) System: RPI – 100; Transaction  – SXMB_IFR

Note: It might take some time for the application to get downloaded. Once the application gets downloaded, we need to enter our credentials and finally the ID (Integration Directory) will be open.

Page 16

Follow the below mentioned steps: 1. Creation of Configuration Scenario. Select ‘Configuration Scenario’, right click and say ‘New’ as shown below.

Click on create then Save and Activate. 2. Create the Receiver and Sender Communication Channels under the respective Communication Components. Communication Components are as follows: a. Business Component

b. Business System

In Business System, we will find ECC and in Business Component we will find File which is coming from any other system

Page 17

3. Create the Sender Communication Channel under the Business Component  – ‘BC_File’ as shown below: -

4. Click on create and specify the following details:a. Adapter Type: File b. Transport Protocol: NFS c. Message Protocol: File d. Adapter Engine: Central Adapter Engine e. Select the ‘Sender’ Radio Button f. Specify the source directory and file name.

In the Processing tab, we need to provide the following details:-

Page 18

a. Quality Service b. Poll Interval c. Processing Mode d. File Type 5. Similarly create the Receiver Communication Channel under the Business System  – “RE6CLNT950” with the details as shown below.

a. Adapter Type: IDOC b. Transport Protocol: IDOC c. Message Protocol: IDOC d. Adapter Engine: Integration Server

Page 19

e. Select the ‘Receiver’ Radio Button f. Specify the RFC Destination, Interface Version, Port and SAP Release. 6. Assign the Business System and Business Component to the above create scenario. Expand the Business Component Select BC_File right click and Assign Configuration Scenarios – ‘CS_sudiroy_File_To_IDoc’ as shown below: -

Page 20

7. Similarly Assign Business Component ‘RE6CLNT950’ t o the same Scenario.

Page 21

8. Sender Agreement Provide the following details as shown below:-

We pass the following field values:  

Communication Component . Service Interface Sender Communication Channel.

Save and Activate.

Page 22

9. Receiver Determination

We pass the following value: 

Sender Communication Component



Sender Service Interface

Page 23

10.

Interface Determination.

Here we pass: 

Sender Communication Component.



Sender Service Interface



Receiver Communication Component.



Operation Mapping.

Page 24

11.

Receiver Agreement.

Here we pass: 

Sender Communication Component.



Receiver Communication Component.



Receiver Communication channel.

Page 25

12. Once all the components are created and activated, assign each one of them to

the Configuration Scenario  –  “CS_sudiroy_File_To_IDOC”.

Finally Save and Activate the Configuration Scenario.

Testing :- For Testing we need to put the file in a folder from which the file adapter will pick up the file. 1. Log on to PI7 system and go to transaction sxda_tools. By using the transaction SXDA _TOOLS on the system one can transfer files from his client machine to the server.

2. Select the options as shown below from the available options.

Page 26

Click Copy button.

Select file in presentation server and target file in application server. Note that the file you selected would be copied to the server with this new name given at server. Note :- Keep this file name same as set in your file sender channel. Click on the tick mark.

Page 27

3. Now, go to AL11, to look all the /usr/sap folders on the server. Click on the folder you uploaded the file to.

4. Find the file here. By double clicking here, one can look at the file contents.

Done with the job..!!

Page 28

Sample File :-

Cremas_295472.xml

Page 29