Outbound Setting

<< Click to Display Table of Contents >>

Navigation:  All About ABAP Technique > English > Costumized IDOC >

Outbound Setting

Define Logical Systems and Assign Client to Logical System – Transaction SALE

SALE-4

 

Go to Define Logical System (See the figure)

Define a new logical system to identify the local system and save it

SALE-1

 

Now, go to Assign Client to Logical System (See the figure)

Add a new entry

Specify the client, previously created logical system and other attributes

Save the entry

SALE-2

 

Define a new logical system to identify the partner system and save it

SALE-3

 

Maintain RFC Destinations – Transaction SM59

Create a new RFC destination for R/3 type connection

Specify the target host on Technical settings tab

SM59-1

Provide the Logon credentials on the Logon/Security tab

SM59-2

Save the settings

To verify the settings, Click on Test connection or Remote logon

 

Define Ports – Transaction WE21

We need to define a tRFC port for the partner system

Click on Transactional RFC node

Create a new port

WE21-1

Provide a description

Specify the name of the target RFC destination

WE21-2

Save the object

 

Maintain Distribution Model – Transaction BD64

Click on Change BD64-1

Create a new model view BD64-2

Provide a Short text and Technical name to the model view

BD64-3
Note : Technical Name sebaiknya namanya sesuai dengan RFC Destinations. Selain itu Technical Name adalah Case Sensitive.

Add message type BD64-5

Specify sender and receiver systems

Also, specify the message type that we created previously

BD64-4

Save the Distribution model

Note : Setelah Add message type sebaiknya disave dulu, jangan jalankan langkah di bawah ini (Generate/Create Partner Profile) karena akan muncul message "No messages have been defined for the selection conditions in the model".

Generate/Create Partner Profile – Transactions BD82/WE20

To generate Partner profiles automatically you may use BD82 or go to BD64 and use the menu path Environment -> Generate partner profiles

oOtherwise, you may use transaction WE20 to create a partner profile

BD64-6

On selection screen, specify the model view, target system and execute

The result log will be displayed on the next screen

BD82-1

To verify the partner profile go to WE20

Check the partner profile for the target system

WE20-1

 

Distribute Model View – Transaction BD64

Select the Model View

Go to menu path Edit -> Model View -> DistributeBD64-7

Result log will be displayed on the next screen

BD64-8

 

Outbound IDoc Generation Program

Create an executable program ZRZ_ORDER_IDOC in SE38. Below, I have described the program logic:

Fetch the data from the DDic tables ZCUSTOMERS, ZSOHEADERS and ZSOITEMS as per the selection criteria

Fill the control record structure of type EDIDC

oSpecify message type, Basic IDoc type, tRFC Port, Partner number and Partner type of the receiver

Fill the data records

oDefine structures like the IDoc segments

oFill the structures with fetched data

oPass the segment name and the above structure to the appropriate fields of EDIDD type structure

oAppend the EDIDD structure to the EDIDD type internal table

Now, call the function module MASTER_IDOC_DISTRIBUTE and pass the IDoc control record structure and data record table

Commit work if return code is zero

Function module returns a table of type EDIDC to provide the details about generated IDoc

Display appropriate log

Source Code