Idoc

Former Member — Sat, 06 Oct 2007 07:18:11 GMT

what are the main transaction used for idocs? what is the structure of idoc?

Re: Idoc

paruchuri_nagesh — Sat, 06 Oct 2007 07:36:00 GMT

sale(asiginig & defining logical systems)

SM58( creating RFC

BD64(creating MODEL view)

BD82( generate partner profile automatically)

BD72(distribute model view)

BD10(sending material)

BD11(recieving material)

BD12(sending customer details)

BD13)recieving cust details)

BD14(sending vendor details)

BD15(recieving vendor details)

WE05( see idoc status)

WE19( testing idoc)

WE20(partner profiles manually)

WE21( creating port)

SARA ( to archive idocs)

structure of idoc is it when executing ale settings memory idoc will be creates

this memory idoc checks with distribution modelview to find recipients

depend on the recepients

it generates communaction idoc

communication idoc contains

control record (stores in EDIDC table)

multiple data record(stores in EDID4 table)

multiple status records( stores in EDIDS table)

reward if u find use ful

regards

Nagesh.Paruchuri

Re: Idoc

Former Member — Thu, 03 Jan 2008 05:54:58 GMT

Hi George,

The most used transactions for Idocs are as below:

SALE Area Menu for ALE configurations.It includes transactions for Logical System definition and linking it to a client.

RFC Destination and Port Definition Etc.

SM59 RFC Destination

We specify the login settings for the destination including the IP address and the User name and password. We can create number of types of RFC Destinations but 3 types are important .R/3 to R/3, LS(logical system) and TCP/IP.

WE21 Port Definition.

There are 6 types of ports but only 2 types File and Transactional RFC types of ports are important.

WE57 This is used to assign the Inbound function module to the Message Type and to the IDOC Type.

WE42 This is used to define the process Code for Inbound Processing.

BD95 Define Filter object type .We can specify the field and the table it belongs to as a filter object .

BD59 Assignment of Filter object type to the Message Type .Here we create the link between Filter object and the segment and the message type and the segment Field.

BD50 Set message Type to reducible.

BD65 Define Mandatory Fields.

BD64 Distribution Model . Also known as Customer Distribution Model Used to define all the messages that will be exchanged between remote systems and the name of thes logical systems. Any filters can also be specified.

BD21 Creating IDOcs from change pointers.

This can be used to create IDOCs from change pointers for a particular message LIKE MATMAS.

BD22 This can be used to delete change pointers.

BD87 Status Monitor. Idocs can be selected base on number of criteria and there processing status can be seen in detail.

BD10 Material Master Data Distribution .

Based on Message MATMAS.

BD12 Customer Master Data Distribution .

Based on Message CREMAS.

BD14 Vendor Master Data Distribution

Based on Message DEBMAS .

BDFG Generate ALE Interface for BAPI.

Here we specify the Business Object and the BAPI Function module for which the interface has to be created.

WE31 Segment Editor.

This is used to create segments. We specify the

fields and the data elements these corresponds to create segments.

WE30 IDOC Editor

It is used to create a new IDOC Type or IDOC Extension .We specify the segments that will be added to the IDOC type.

WE02/05 IDOC List.

Various selct options and parameters are provided to select IDOCs depending on the date, direction , mesage type etc.

WE20 Partner Profile

Here we create partner profile for each and every partner from to which the messages will be exchanged.There are 6 types of PF generally only profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.

SE38 It is the program editor.

Regarding the structure of the Idoc

An IDoc consists of a header line, several connected data segments and status records.

Function of IDoc Elements

Header

Defines the content, structure, sender, receiver and status of the IDoc

Data segment

Consists of a "leader" (consecutive segment number and a description of the type of segment) and a field string 1000 characters long (containing segment data)

Status records

Describe processing steps of the IDoc up to the present.It contains the various status that the Idoc have undergine since its creation.

Sravani.

Reward if found useful.

topic Re: Idoc in Application Development and Automation Discussions

Idoc

Re: Idoc

Re: Idoc