difference b/w Master & Communication IDocs (2024)

The master Idoc is the Temporary Idoc & kept in memory buffers until communication IDocs are generated. These recipient-specific IDocs are called Communication IDocs and are Stored in the Database.

But the master Idoc is not.

The Communication IDocs are transferable IDocs not the Master Idoc. For every Receiver, each separate communication Idocs will be created from master Idoc.

*****************************************************************

more info on idocs....

Data Creation in Idoc

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.

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.

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

*IDocs are structured ASCII files (or a virtual equivalent).

*Electronic Interchange Document

*They are the file format used by SAP R/3 to exchange data with foreign systems.

*Data Is transmitted in ASCII format, i.e. human readable form

*IDocs exchange messages

*IDocs are used like classical interface files

IDOC types are templates for specific message types depending on what is the business document, you want to exchange.

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

FOr testing you can use WE19.

How to create idoc?

*WE30 - you can create a IDOC type

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

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

AND There are basically two types of IDOCs.

Basic IDOCs

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

Extended IDOCs

Extending the functionality by adding more segments to existing Basic IDOCs.

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)

imp links

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

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

www.sappoint.com

--here u can find the ppts and basic seetings for ALE

http://sappoint.com/presentation.html

www.sapgenie.com

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

WE30 - you can create a IDOC type.

An IDOC with data, will have to be triggered by the application that is trying to send out the data.

Try this..Hope this will help.

SAP ALE & IDOC<<<<

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.

Check these links.

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

Please check this PDF documents for ALE and IDoc.

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

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

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

Check below link. It will give the step by step procedure for IDOC creation.

http://www.supinfo-projects.com/cn/2005/idocs_en/2/

Regards

vasu

difference b/w Master & Communication IDocs (2024)

FAQs

What is the difference between master IDoc and communication IDoc? ›

Answers (3)

These recipient-specific IDocs are called Communication IDocs and are Stored in the Database. But the master Idoc is not. The Communication IDocs are transferable IDocs not the Master Idoc.

Tell Me More ›

What are the different types of IDoc? ›

An IDoc coming into an SAP system is called an Inbound IDoc, while an IDoc going out of a system is called an Outbound IDoc. An Outbound IDoc is triggered through document message control to the EDI subsystem.

What is the difference between IDoc type and message type? ›

A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type. An IDoc type specifies the structure of the data.

Tell Me More ›

What is the difference between EDI and IDoc? ›

EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS). EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.

Explore More ›

What is the difference between BD87 and WE19 in IDoc? ›

BD87 is used to monitor the inbound and outbound IDoc and also can be used to process a single IDoc. For mass processing, you can use program RBDAPP01 (inbound processing) and RSEOUT00 (outbound processing). WE19 (testing tool) is used to test an IDoc and also to simulate an IDoc error if occurs.

Know More ›

What are the different IDoc status in SAP? ›

Alert Types

iDOC Status	Description
01	iDoc created
02	Error passing data to port
03	Data passed to port OK
04	Error within control information of EDI subsystem

64 more rows

Find Out More ›

How many types of records we have in IDocs? ›

IDoc instance

Contains one Control Record per IDoc with one unique IDoc number. Contains one or more Data Records. The reference to the Control Record is done via the unique IDoc number.

Learn More Now ›

What is the difference between IDoc basic type and extension? ›

The term "IDoc type" was used to denote both the extended basic type and the umbrella term. Extensions are "appended" to basic types via reference segments. Since basic types cannot lose segments in subsequent SAP releases, compatibility is ensured.

Is IDoc different from CSS Profile? ›

Similarly to the CSS Profile, the IDOC is also administered by the College Board. As opposed to the CSS Profile and the FAFSA which send a report of your information to colleges, IDOC allows you to submit those documents directly via a secure portal.

Read The Full Story ›

What is the difference between IDoc and ALE IDoc? ›

An IDoc interface has a defined data structure and IDoc processing logic. The SAP term for data exchange with other in-house systems is ALE (or Application Link Enabling). The term EAI stands for Enterprise Application Integration and is also commonly used in non-SAP environments.

Show Me More ›

What is WE30 used for in SAP? ›

With tcode WE30, we can see the structure (segment,field names under segment) of the IDOC basic type.

Get More Info ›

What is the difference between IDoc and proxy? ›

IDOC :It has Standard Structure,Sender Communication Channel is not required,Used only for asyncronous Communication. Proxy: Depending upon the requirement have to create the structure,It supports huge volume of data processing,Can be used for both sync & async .

Discover More Details ›

What is the difference between SAP XML and IDoc? ›

While XML allows having some metadata about the document itself, an IDoc is obliged to have information at its header like its creator, creation time etc. While XML has a tag-like tree structure containing data and meta-data, IDocs use a table with the data and meta-data.

Why is IDoc used? ›

IDocs (Intermediate Documents) are standard containers for exchanging data between applications. Between SAP applications they are transferred using the ALE (Application Link Enabling) layer which again uses either tRFC or File technology as the underlying technique.

Find Out More ›

How do I send and receive an IDoc in the same system? ›

Sending a IDOC to the same client in a SAP system

Step 1-Create logical system for sender and receiver. Login to client ID1/270 and execute transaction code SALE and the following screen is displayed. ...
Step 2- Create port. ...
Step 3- Create partner profile. ...
Step 4-Create distribution model.

Sep 20, 2015

What is the difference between ALE and EDI IDoc in SAP? ›

ALE is technology for SAP mainly use to transfer data between SAP systems. EDI is the independent technology use to transfer data between two systems, they can be SAP systems or non SAP systems. The basic difference with ALE and EDI is ALE used for internal communications and EDI is meant for external communications.

View Details ›

What is the difference between IDoc status 03 and 12? ›

Status 12 helps to confirm the data dispatch to the receiving port. If in case the receiving port is down and the idoc fails to dispatch it to the receving port and the status remains '03'.

What is the difference between SAP DME and IDoc? ›

IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. DME is data media exchange, used for transfer data between entities. You must be a registered user to add a comment. If you've already registered, sign in.