STEP BY STEP MATERIAL UPLOAD THROUGH IDOC

Summary

 This Document explains step by step procedure to transfer the Material which was created in a SAP server to another SAP server using IDoc Methodology.

T-Codes used in this Procedure

When we are working with IDocs we need to know following Tcodes.

SALE - This is used to Customizing IDoc Interface/Application Link Enabling ( ALE )

SM59 - Used to configure RFC connections

WE21 - Create/Change Ports used in IDoc Processing

WE20 - Used to define the Partner Profiles

BD64 - Used to define Distribution Model for IDoc Processing

BD10 - Used to send Materials

BD87 - Used to check the status of IDoc

Step 1: Creation of Logical System in IDES System for Client 800

To create Logical System we need use SALE T-Code as showing in following figure.

When you are creating Logical System that is cross client so confirm the alert message shown while creation.

The Next screen shows list of Logical Systems if you have in your SAP servers.

To create your own logical System click on New Entries button in the same screen you will display the following screen where you can enter the details for new logical System

While saving the Logical System SAP will prompt for Work Bench Request as shown below to create click on new button as shown in below

Enter the Short description and save the screen, as a result it creates a new transport request and new number will be populated in Request text box. This transport number will be used for further process.

In the next screen you will display the list of logical System assigned to different clients. If you want to do new assignment click on “New Entries” button and enter the following details.

If you are changing any existing assignment then you need to use tool for conversion of Logical Systems names using BDLS as shown below. In my case I changed Old Logical System to new Logical System for this demo purpose for 800 client. So I am executing this as following screen

Step 2: Creation of Logical System in RD2 System for Client 120

We need to create a logical System in RD2 server by following the same points which are used to create logical System in IDES. The logical System name is “RD2”.

The following screen shot explains the same

Step 3: Creation of Another Logical System in IDES System

We need to create another Logical System in IDES with same name of logical System which was created in another server i.e. RD2 server. As we created logical System name as “RD2” in RD2 server, so I am going to create a logical System with a name of “RD2” in IDES System.

There is no need for us to assign client for this Logical System. We are creating this logical System in IDES because we are moving data (Materials) from IDES server to RD2 System. If you want move the data from RD2 to IDES then you need create logical System with a name of LSIDES in RD2 server.

The below screen shot explains the same

Step 4: Creation of RFC Destination in IDES System

We need to create RFC destination in IDES System. This destination is for RD2 System for client 120

This can be done by the following steps

In SM59 you need to create New ABAP connection using create Icon shown the following screen

Select ABAP Connections and click on new button, and you need to fill details in the following screen shown in the figures

After entering the required details and save RFC destination. After saving use “Connection Test” button to test the connection from IDES System to RD2. You need to get the success message to move further. Success message is shown as follows

Step 5: Creation of tRFC Port in IDES System

We need to a Transactional RFC using WE21 TCode.

When you click on New button after selecting Transactional RFC you will be prompted for option to create Port name option. You can create your own name port or SAP assigns new port number if you choose Generate Port Name. 

After entering the above details, Save the Port details.

Step 6: Creation of Partner Profile in IDES System

We need to create Partner Profile for the Logical System which we created. This can be done by using WE20 TCode.

Select the “Partner Type LS” and click on “New” icon to create New Partner profile. In the next screen you need to fill the require details as shown the above figure.

As the Materials are moving from IDES System to RD2 we need to enter the Message type related to Materials in Outbound Parameter list as shown the above figure.

To add Outbound parameter you need to click on the Create Outbound Parameter Icon as shown in the below figure.

In the next screen you need to enter the Message Type, Receiving Port and Base Type details as shown in the figure

Step 7: Creation of Distribution Model in IDES System

We need to create Distribution model in IDES System using BD64 TCode. You need click on “Create New Model” button after changing to Change Mode as shown in figure.

Once the Model is created we need to Add Message Type to the model to add this you need to select the newly created model and then click on “Add Message Type” button as shown in the figure.

To add Message Type you need to enter the following details

1. Sender - Logical System Name from the data is transferring

2. Received - Logical System Name to which server data is transferring in our case it is “RD2” which was created in IDES System.

3. Message Type – Message type for Materials is MATMAS

After entering the above details and confirm the alert box you can see the following Distribution model.

Step 8: Creation of Logical System in RD2 System

We need to create another logical System in RD server. This logical System name should equal to the logical System what we created in IDES System (Source System) “LSIDES”.

To create logical System we need to follow the same points which were explained in step1.

Once the Logical System is created in RD2 there is no need to assign the client for this Logical System.

Step 9: Creation of Partner Profile in RD2 System

We need to create Partner profile in RD2 System using WE20.

After creation of Partner profile we need add inbound parameter to the Partner Profile which was newly created as shown figure.

After saving the Inbound Parameters you can see Partner Profile Inbound Parameter list as shown below

Step 10: Demonstration of sending Material

Create a simple material in DEV System as shown in figure. I created simple material with Industry Sector as “Retail” and Material Type as “Finished Product” and I chosen Basic Data 1 and Basic Data 2 views while creating. 

After creating material you need to send this material using BD10 TCode as shown in the figure

After entering above details you can execute. You need to get the following messages.

Now you need to know the IDoc is processed or not. All the IDoc status will be know using BD87 TCode

Enter the appropriate details and execute the same. These results will be displayed in the next screen as shown in the figure

The above status tells us that IDoc was transmitted from DEV System. Now we need to check in RD2 System for Inbound IDoc status to confirm that IDoc was received successfully in RD2 System.

Now the check the Material “UMA01042010_1” is present in RD2 System or not using MM03

Some error are show in Inbound processing as material Industry sector is not available in target System ( RD2 )

AUTHOR           : SANGEETA YADAV

LOCATION       : DELHI

OCCUPATION : EMPLOYEE