Idoc

A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.

Need for Distributed Process:

• Business in Different Geographical Locations.

• Non availability of dedicated network.

• Cultural and language differences in Geographical locations.

• Running of Mission-critical Applications (Like Maintenance downtime etc.).

• Separate up gradation of Modules.

Distributed SAP SYSTEM – CHALLENGES

• A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.

• Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.

• Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.

• Receiving systems that can handle their own problems and not tie up the sending system.

• Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.

• A sound technology and methodology that can be used in all distribution scenarios.

SAP Distributed environment:

ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.

ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.

Benefits of ALE:

• Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.

• Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.

• Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.

ALE Architecture:

It consists of an Outbound process, an Inbound process, and an Exception – Handling process.

Outbound Process:

ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.

1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.

2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.

3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.

4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.

Inbound Process:

The inbound process receives an IDoc and creates a document in the system.

1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.

2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.

3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.

Over view of IDocs:

IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.

IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.

IDoc Types:

IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.

An IDoc is an instance of an IDoc Type and consists of three types of records.

i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.

ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.

iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.

Message in IDoc Type:

A Message represents a specific type of document transmitted between two partners.

Outbound Process in IDocs:

Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.

The Customer Model:

A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.

Message control:

Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.

Change Pointers:

The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.

Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.

IDoc Structure:

A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.

Selection Program:

Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.

Filter Objects;

Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.

Port Definition:

A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.

RFC Destination:

The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.

Partner Profile:

A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.

Service Programs and Configuration Tables:

The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.

Process flow for Distributing Transactional Data:

Transactional data is distributed using two techniques: with Message control and without message control.

Process flow for Distributing Master Data:

Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.

Triggering the Outbound Process via Stand-Alone Programs:

Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.

The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.

Triggering the Outbound Process via Change Pointers:

The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.

A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.

Processing in the Application Layer:

The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.

Processing in the ALE Interface Layer:

Processing in the ALE Layer consists of the following steps:

• Receiver Determination: The determination of the receiver is done through Customer Distribution Model.

• IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.

• Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.

• Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.

• Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.

• Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.

• Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).

• Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).

• IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).

Processing in the Communication Layer:

To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.

Inbound Process in IDocs:

An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.

Posting Program:

Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.

Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.

Workflow:

A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.

Partner Profile;

A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.

Process flow for the Inbound process via a Function Module:

In this process, IDocs are received from another system and passed to the posting function module directly.

1. Processing in the communication Layer:

The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.

2. Processing in the ALE/EDI Interface Layer:

• Basic integrity check: A basic integrity check is performed on the control record.

• Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.

• Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).

• IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).

• IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.

3. Processing in the Posting Module:

The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.

The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Creating an IDoc:

Basic Type:

Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.

Segments:

Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.

Steps in creating Segments:

T.Code WE31

Enter the name for your segment type and click on the create icon.

Type the Short text.

Enter the variable names and data elements.

Save and Go back.

Go to Edit -> Set Release.

Repeat the steps to create more segments.

IDOC TYPE:

Business data is exchanged with an external system using the IDoc Interface.

IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.

Steps in creating IDoc Type:

T.Code WE30 to create IDoc Type.

Enter the Object Name, Select Basic Type and click Create Icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDoc name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press enter

The system transfers the name of the segment type to the IDoc editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation.

Save it and go back.

Go to Edit -> Set Release.

Message Type:

Steps in Creating Message Type:

T.Code WE81.

change the details from Display mode to Change mode

After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back.

Assign Message Type to IDoc Type:

T.Code WE82

Change the details from Display mode to change mode.

After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back.

Reward Points if useful.

Read only

912

SAP Managed Tags
ABAP Development

hi

i hope that ur prob will be solved.

http://idocs.de/www3/cookbooks/idoc/cb10_idoc_03_firstlook/idoc_20_getafeeling/frameset.htm

regard

mukesh goyal

Read only

912

SAP Managed Tags
ABAP Development

Dear Bujji,

IDocs

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

IDoc is a intermediate document to exchange data between two SAP Systems.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

For more information in details on the same along with the examples can be viewed on:

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm

http://www.sappoint.com/presentation.html

http://www.allsaplinks.com/idoc_search.html

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://www.erpgenie.com/sapedi/idoc_abap.htm

ALE/ IDOC

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.sappoint.com/abap/ale.pdf

http://www.sappoint.com/abap/ale2.pdf

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm

http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm

http://www.allsaplinks.com/idoc_sample.html

http://www.sappoint.com/abap.html

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

http://www.allsaplinks.com/idoc_sample.html

http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

Best Regards,

Rajesh

Please reward points if found helpful.

Read only

912

SAP Managed Tags
ABAP Development

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30 )

Create Message Type ( WE81 )

Assign Idoc Type to Message Type ( WE82 )

Creating a Segment

Go to transaction code WE31

Enter the name for your segment type and click on the Create icon

Type the short text

Enter the variable names and data elements

Save it and go back

Go to Edit -> Set Release

Follow steps to create more number of segments

Create IDOC Type

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

Create Message Type

Go to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc Type

Go to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Best Regards,

Rajesh

Please reward points if found helpful.

Read only

912

SAP Managed Tags
ABAP Development

Dear Bujji,

Steps to configuration(Basis) >>

1. Create Logical System (LS) for each applicable ALE-enabled client

2. Link client to Logical System on the respective servers

3. Create background user, to be used by ALE(with authorizaton for ALE postings)

4. Create RFC Destinations(SM59)

5. Ports in Idoc processing(WE21)

6. Generate partner profiles for sending system

The functional configuration(Tcode: SALE)

• Create a Customer Distribution Model (CDM);

• Add appropriate message types and filters to the CDM;

• Generate outbound partner profiles;

• Distribute the CDM to the receiving systems; and

• Generate inbound partner profiles on each of the clients.

Steps to customize a new IDoc >>>

1. Define IDoc Segment (WE31)

2. Convert Segments into an IDoc type (WE30)

3. Create a Message Type (WE81)

4. Create valid Combination of Message & IDoc type(WE82)

5. Define Processing Code(WE41 for OUT / WE42 for IN)

6. Define Partner Profile(WE20)

Important Transaction Codes:

SALE - IMG ALE Configuration root

WE20 - Manually maintain partner profiles

BD64 - Maintain customer distribution model

BD71 - Distribute customer distribution model

SM59 - Create RFC Destinations

BDM5 - Consistency check (Transaction scenarios)

BD82 - Generate Partner Profiles

BD61 - Activate Change Pointers - Globally

BD50 - Activate Change Pointer for Msg Type

BD52 - Activate change pointer per change.doc object

BD59 - Allocation object type -> IDOC type

BD56 - Maintain IDOC Segment Filters

BD53 - Reduction of Message Types

BD21 - Select Change Pointer

BD87 - Status Monitor for ALE Messages

BDM5 - Consistency check (Transaction scenarios)

BD62 - Define rules

BD79 - Maintain rules

BD55 - Defining settings for IDoc conversion

WEDI - ALE IDoc Administration

WE21 - Ports in Idoc processing

WE60 - IDoc documentation

SARA - IDoc archiving (Object type IDOC)

WE47 - IDoc status maintenance

WE07 - IDoc statistics

BALE - ALE Distribution Administration

WE05 - IDoc overview

BD87 - Inbound IDoc reprocessing

BD88 - Outbound IDoc reprocessing

BDM2 - IDoc Trace

BDM7 - IDoc Audit Analysis

BD21 - Create IDocs from change pointers

SM58 - Schedule RFC Failures

Basic config for Distributed data:

BD64: Maintain a Distributed Model

BD82: Generate Partner Profile

BD64: Distribute the distribution Model

Programs

RBDMIDOC – Creating IDoc Type from Change Pointers

RSEOUT00 – Process all selected IDocs (EDI)

RBDAPP01 - Inbound Processing of IDocs Ready for Transfer

RSARFCEX - Execute Calls Not Yet Executed

RBDMOIND - Status Conversion with Successful tRFC Execution

RBDMANIN - Start error handling for non-posted IDocs

RBDSTATE - Send Audit Confirmations

FOr testing you can use WE19.

Best Regards,

Rajesh

Please reward points if found helpful.

Read only

912

SAP Managed Tags
ABAP Development

Hi Ammu , check this material so that u can hav e an clear idea on IDOC.

Intermediate Document

An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data. IDoc is not a process.

- IDocs are stored in the database.

- In the SAP system, IDocs are stored in database tables.

- IDocs are independent of the sending and receiving systems.

- IDocs are independent of the direction of data exchange.

Creation of IDOCs

? Transaction code: WE 30

Defining Segment:

Creating Segment : Tcode - WE31

Creating Message Type : Tcode - we81

Assigning Message type to Idoc type: Tcode - we82

Process

The two processes for IDoc are Outbound Process and Inbound Process.

Outbound Process

When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.

Inbound Process

When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.

Outbound Process (Sending System) Steps :

1) Goto Tcode SALE:

Click on Sending & Receiving Systems à Select Logical Systems

Here Define the Logical Systems à Click on Execute Button

Go for New Entries

1) System Name : LOG1

Description: Sending System

2) System Name : LOG2

Description: Receiving System

Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.

Assigning Client to the Logical System:

Select Assign Client to Logical Systems -à Execute

Ø 100 à Double click on this and give the following information

Client : Sending System

City : Chennai

Logical System : LOG1

Currency :

Client role :

Ø 250 à Double click on this and give the following information

Client : Receiving System

City :

Logical System : LOG2

Save this Data.

Step 2) For RFC Creation:

- Goto Tcode SM59 à Select R/3 Connects

Click on create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

Give the information for required fields:

RFC Destination : LOG2

Connection type : 3

Target Host : sappdc.wipro.com

System No : 00

Client : 210

User : Login user name

Password :

Save this & Test it and Remote Login

Step 3) Goto Tcode BD64: - Click on the change button

Click on the create model view

Short Text: model view

Technical Name: LMOD

Save this & press ok

Select just created model view

Name: "LMOD"

Goto add message type

Model Name : LMOD

Sender : LOG1

Receiver : LOG2

Message type: ZAZHARMESS

Save and press Enter.

4) Goto Tcode BD82:

Give Model View : LMOD

Partner system : LOG2

Execute this by pressing F8

It will gives you sending system port No: A00000000089 (Like)

5) Goto Tcode BD64:

Select the model view

Goto à Edit à model view à Distribute

Press ok & Press Enter.

Run your Zprogram

REPORT ZIDOC1 .

DATA: Begin of imara occurs 0,

matnr like mara-matnr,

mtart like mara-mtart,

end of imara.

DATA: wamas_con LIKE edidc,

imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,

icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.

PARAMETERS: e_matnr LIKE mara-matnr,

e_msgtyp LIKE edidc-mestyp,

e_rcvprn LIKE edidc-rcvprn.

retrive app. data from DB

SELECT matnr mtart FROM mara INTO TABLE imara WHERE

matnr = e_matnr.

*Master idoc control record

wamas_con-rcvprt = 'LS'.

wamas_con-rcvprn = e_rcvprn.

wamas_con-idoctp = 'ZAZHARIDOC'.

wamas_con-mestyp = e_msgtyp.

master idoc data records

LOOP AT imara.

imas_data-segnam = 'ZAZHARSEG'.

move imara to imas_data-sdata .

APPEND imas_data.

ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

master_idoc_control = wamas_con

TABLES

communication_idoc_control = icom_con

master_idoc_data = imas_data

COMMIT WORK.

6) Verifying Transfer of IDOCs Tcode - we05

ALE/IDOC Status Codes (outbound):

01 à IDoc Added

30 à IDoc ready for dispatch

29 à Error in ALE service Layer

12 à Dispatch ok

03 à Data passed to port ok.

Inbound Process (Receiving System) Steps:

Do the same step as you did in sending system

ü Creating IDoc

ü Defining the Segment

ü Creating Message Type

ü Assigning the Message Type

ü Defining the Logical System

ü Assigning the Logical System

ü Creating the Distribution Model

Goto Tcode - we57:

Assign function module to IDoc type

Module: Function module

Basic type:

Message type:

Direction: 2 (inbound)

Creating Inbound process code - we42

Verifying Idoc List Tcode - we05

ALE/IDOC Status Codes (Inbound):

50 à IDoc Added

51 à Application Document not posted

64 à IDoc ready to be transferred to application

62 à IDoc passed to application

53 à Application Document posted

1. What is the difference Between IDOC type and Message type? How to link the IDOC type with Message type?

Message type gives the meaning of the IDOC and IDOC type gives the structure of an IDOC.

The linkage will happen in WE82.

In the OO(Object Oriented) approach, Message Type can be refferred to a Class and IDOC Type as an instance of the class Message Type

2. Where the IDOC information gets stored?

Table Description

EDIDC Stores the Control information an IDOC

EDID4 Stores the Data Records from 4.0 onwards

EDIDS Stores the Status of an IDOC

3. What is process code? What are type of process codes

Process code refers to an workflow or a function module which helps in reading or writing data from/to Idoc. Following are types of process code

Process Code Description

Outbound Process Code This will read application data and place data in Idoc

Inbound Process Code This will Idoc and create corresponding application data

System Process Code This will create work item in case some error occurs in idoc / application document processing

Status Proces Code This will handle error that occurs when a idoc is sent to some other system

4. How to reprocess an IDOC?

You can use the below Programs for IDocs Reprocessing:

· RBDMANI2 : Reprocess Idocs manually

· RBDMANIN : Posting of IDocs with Status 51

· RBDMOIND : Outbound Idocs status 03->12

· RSEOUT00 : For Processing 30 Status IDocs

· RBDAPP01 : For Processing 64 Status IDocs

· RBDAGAIN : Reprocess Incorrect Outbound IDocs

· RBDAGAI2 : Reprocessing of IDocs after ALE Input Error

5. How to trace the IDocs of the Receiving system from the Sending system?

Steps:

· Execute the transaction BD87

· Give the Outbound IDocs in the IDoc Number field and execute or Just Note the Start time and End time when u execute the Master Data Transaction say for eg.BD10 and specify the same in the Time Created input field of BD87,also give the Message Type and the Receiving System Names and execute.

· Select the Repective Message Type and Press the Trace IDoc Button.

6. How to trace IDocs based on the data .

Steps:

· Execute Transaction WE09

· Put in the message type name in the field labeled 'Logical Message' Ex - DEBMAS

· Now we will move to the section 'Criteria for Search in Data Records '

· In this section we will put the Segment name in which we want to search the existance of data in the field labeled 'Search in Segment' EX - E1KNA1M

· In the field labeled 'Search in Field' we will put the field name of the segment in which we want to search the existance of data. Ex - KUNNR for searching IDOCs for certain customer number.

· Now in the field labeled 'For Value' we will put the search value. Ex - Customer number as 100 .

· We will now execute the transaction.

· The result can be a single Idoc or a list of multiple IDOCS depending upon the Search Criteria entered.

Read only

912

SAP Managed Tags
ABAP Development

Hi Ammu , check this material so that u can hav e an clear idea on IDOC.

Intermediate Document

An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data. IDoc is not a process.

- IDocs are stored in the database.

- In the SAP system, IDocs are stored in database tables.

- IDocs are independent of the sending and receiving systems.

- IDocs are independent of the direction of data exchange.

Creation of IDOCs

? Transaction code: WE 30

Defining Segment:

Creating Segment : Tcode - WE31

Creating Message Type : Tcode - we81

Assigning Message type to Idoc type: Tcode - we82

Process

The two processes for IDoc are Outbound Process and Inbound Process.

Outbound Process

When the data is sent out from the system, the process is called Outbound Process and the IDoc is known as Outbound IDoc.

Inbound Process

When the data is coming in, the process is called Inbound Process and the IDoc is known as Inbound IDoc.

Outbound Process (Sending System) Steps :

1) Goto Tcode SALE:

Click on Sending & Receiving Systems à Select Logical Systems

Here Define the Logical Systems à Click on Execute Button

Go for New Entries

1) System Name : LOG1

Description: Sending System

2) System Name : LOG2

Description: Receiving System

Press Enter & Save it will ask for Request if you want new request create new request or press continue for transferring the objects.

Assigning Client to the Logical System:

Select Assign Client to Logical Systems -à Execute

Ø 100 à Double click on this and give the following information

Client : Sending System

City : Chennai

Logical System : LOG1

Currency :

Client role :

Ø 250 à Double click on this and give the following information

Client : Receiving System

City :

Logical System : LOG2

Save this Data.

Step 2) For RFC Creation:

- Goto Tcode SM59 à Select R/3 Connects

Click on create Button

RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

Give the information for required fields:

RFC Destination : LOG2

Connection type : 3

Target Host : sappdc.wipro.com

System No : 00

Client : 210

User : Login user name

Password :

Save this & Test it and Remote Login

Step 3) Goto Tcode BD64: - Click on the change button

Click on the create model view

Short Text: model view

Technical Name: LMOD

Save this & press ok

Select just created model view

Name: "LMOD"

Goto add message type

Model Name : LMOD

Sender : LOG1

Receiver : LOG2

Message type: ZAZHARMESS

Save and press Enter.

4) Goto Tcode BD82:

Give Model View : LMOD

Partner system : LOG2

Execute this by pressing F8

It will gives you sending system port No: A00000000089 (Like)

5) Goto Tcode BD64:

Select the model view

Goto à Edit à model view à Distribute

Press ok & Press Enter.

Run your Zprogram

REPORT ZIDOC1 .

DATA: Begin of imara occurs 0,

matnr like mara-matnr,

mtart like mara-mtart,

end of imara.

DATA: wamas_con LIKE edidc,

imas_data LIKE edidd OCCURS 0 WITH HEADER LINE,

icom_con LIKE edidc OCCURS 0 WITH HEADER LINE.

PARAMETERS: e_matnr LIKE mara-matnr,

e_msgtyp LIKE edidc-mestyp,

e_rcvprn LIKE edidc-rcvprn.

retrive app. data from DB

SELECT matnr mtart FROM mara INTO TABLE imara WHERE

matnr = e_matnr.

*Master idoc control record

wamas_con-rcvprt = 'LS'.

wamas_con-rcvprn = e_rcvprn.

wamas_con-idoctp = 'ZAZHARIDOC'.

wamas_con-mestyp = e_msgtyp.

master idoc data records

LOOP AT imara.

imas_data-segnam = 'ZAZHARSEG'.

move imara to imas_data-sdata .

APPEND imas_data.

ENDLOOP.

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'

EXPORTING

master_idoc_control = wamas_con

TABLES

communication_idoc_control = icom_con

master_idoc_data = imas_data

COMMIT WORK.

6) Verifying Transfer of IDOCs Tcode - we05

ALE/IDOC Status Codes (outbound):

01 à IDoc Added

30 à IDoc ready for dispatch

29 à Error in ALE service Layer

12 à Dispatch ok

03 à Data passed to port ok.

Inbound Process (Receiving System) Steps:

Do the same step as you did in sending system

ü Creating IDoc

ü Defining the Segment

ü Creating Message Type

ü Assigning the Message Type

ü Defining the Logical System

ü Assigning the Logical System

ü Creating the Distribution Model

Goto Tcode - we57:

Assign function module to IDoc type

Module: Function module

Basic type:

Message type:

Direction: 2 (inbound)

Creating Inbound process code - we42

Verifying Idoc List Tcode - we05

ALE/IDOC Status Codes (Inbound):

50 à IDoc Added

51 à Application Document not posted

64 à IDoc ready to be transferred to application

62 à IDoc passed to application

53 à Application Document posted

1. What is the difference Between IDOC type and Message type? How to link the IDOC type with Message type?

Message type gives the meaning of the IDOC and IDOC type gives the structure of an IDOC.

The linkage will happen in WE82.

In the OO(Object Oriented) approach, Message Type can be refferred to a Class and IDOC Type as an instance of the class Message Type

2. Where the IDOC information gets stored?

Table Description

EDIDC Stores the Control information an IDOC

EDID4 Stores the Data Records from 4.0 onwards

EDIDS Stores the Status of an IDOC

3. What is process code? What are type of process codes

Process code refers to an workflow or a function module which helps in reading or writing data from/to Idoc. Following are types of process code

Process Code Description

Outbound Process Code This will read application data and place data in Idoc

Inbound Process Code This will Idoc and create corresponding application data

System Process Code This will create work item in case some error occurs in idoc / application document processing

Status Proces Code This will handle error that occurs when a idoc is sent to some other system

4. How to reprocess an IDOC?

You can use the below Programs for IDocs Reprocessing:

· RBDMANI2 : Reprocess Idocs manually

· RBDMANIN : Posting of IDocs with Status 51

· RBDMOIND : Outbound Idocs status 03->12

· RSEOUT00 : For Processing 30 Status IDocs

· RBDAPP01 : For Processing 64 Status IDocs

· RBDAGAIN : Reprocess Incorrect Outbound IDocs

· RBDAGAI2 : Reprocessing of IDocs after ALE Input Error

5. How to trace the IDocs of the Receiving system from the Sending system?

Steps:

· Execute the transaction BD87

· Give the Outbound IDocs in the IDoc Number field and execute or Just Note the Start time and End time when u execute the Master Data Transaction say for eg.BD10 and specify the same in the Time Created input field of BD87,also give the Message Type and the Receiving System Names and execute.

· Select the Repective Message Type and Press the Trace IDoc Button.

6. How to trace IDocs based on the data .

Steps:

· Execute Transaction WE09

· Put in the message type name in the field labeled 'Logical Message' Ex - DEBMAS

· Now we will move to the section 'Criteria for Search in Data Records '

· In this section we will put the Segment name in which we want to search the existance of data in the field labeled 'Search in Segment' EX - E1KNA1M

· In the field labeled 'Search in Field' we will put the field name of the segment in which we want to search the existance of data. Ex - KUNNR for searching IDOCs for certain customer number.

· Now in the field labeled 'For Value' we will put the search value. Ex - Customer number as 100 .

· We will now execute the transaction.

· The result can be a single Idoc or a list of multiple IDOCS depending upon the Search Criteria entered.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My Account

My Account