ALE/IDOC

[Former Member]

Hi Guys,

Can anybody provide me with the Step by Step procedure of Configuring ALE/IDOC, It should be based on real time scenario.

Rewards if the document is useful and gives the clear idea on ALE/IDOC.

Thanks In Advance.

Vikas

[Former Member]

Hi Guys,

Can anybody provide me with the Step by Step procedure of Configuring ALE/IDOC, It should be based on real time scenario.

Rewards if the document is useful and gives the clear idea on ALE/IDOC.

Thanks In Advance.

Vikas

[Former Member]

Hi

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

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

Check these out..

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

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

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

go trough 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://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

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...

1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.

2.IDOCs are independent of the sending and receiving systems.

3.IDOCs are independent of the direction of data exchange.

The two available process for IDOCs are

Outbound Process

Inbound Process

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.

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.

You can directly create an iDoc using some transaction like...

Use TCODE bd10 - to Send Data

and TCODE bd11 - to Get Data

and you can check the IDoc List using TCODE we02.

As you want step by step procedure.

1. Define Logical System and Assign Logical System

TCODE sale

2. Define RFC

TCODE sm59

3. Define Port

TCODE we21

4. Define Partner Profile

TCODE we20

5. Define Distribution Model

TCODE bd64

6. Send Data

TCODE bd10

7. Get Data

TCODE bd11

8. IDoc List

TCODE we02

There are basically two types of IDOCs.

Basic IDOCs

Extended IDOCs

Idoc Components

Basic Idoc

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

Extension Idoc

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

Creation of IDoc

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.

Create IDOC Type

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

u can also check all these links related to idocs

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

http://www.allsaplinks.com/

http://www.sap-img.com/

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

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

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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off...

http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358

http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm

Regards,

Vishwa.

[Former Member]

Hi Vikas,

Please read this document. It is very useful for you.

Introduction

Purpose

This document describes in detail the necessary ALE/EDI Configuration settings in SAP .

Definitions & Acronyms

Term/Acronym Explanation

Idoc Intermediary document used for data transition in SAP

RFC Remote Function Call

1. General Configuration

2. Configuration - Outbound Process

3. Configuration - Inbound Process

General Configuration

To transfer the SAP data, necessary ALE customization should be carried out in SAP. This section explains the minimum general settings that have to be carried out irrespective of the process (Outbound or Inbound). DEBMAS02 is the IDoc type used for both inbound and outbound process.

Note: The menu paths given in this document refer to the 4.6B version of SAP. Wherever possible, transaction codes are also given. Depending on the SAP

Version, it is possible that the menu paths may vary.

The following are the settings that have to be maintained in case of general configuration settings. Each step is dealt in detail with the help of Screen Shot.

1. Maintain Logical System

2. Assign client to Logical System

3. Port Definition

4. Maintain Distribution Model

5. Change Partner Profile of the Logical System

6. Activate Change Pointers

Maintain Logical System

To distribute messages across systems, each system is uniquely identified as a logical system in SAP ALE Customizing.

Menu: SAP Standard Menu  Tools  Accelerated SAP  Customizing  SPRO  SAP Reference IMG  Basis Components  Distribution (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System

Transaction Code: SALE

Explanation:

1. A Dummy logical system with an appropriate name should be defined in ALE Customizing.

(Refer Screen Shot 1.1 and Screen Shot 1.2)

Screen shot 1.1

Screen shot 1.2

Assign client to Logical System

The defined logical system should be assigned to the client of SAP from which IDocs are to be triggered.

Menu: SAP Standard Menu  Tools  Accelerated SAP  Customizing  SPRO  SAP Reference IMG  Basis Components  Distribution (ALE)  Sending and Receiving Systems  Logical systems  Assign client to Logical system

Transaction Code: SALE

Explanation:

The following fields are to be maintained

1. Logical System

2. Standard Currency

3. Client role (Customizing)

4. Changes and transports for client-dependent objects

5. Client-Independent object changes

6. Protection level: Client copier and comparison tool

(Refer Screen Shot 2.1)

Screen shot 2.1

Port Definition

Port definition is the logical destination to be used by the SAP system during data interchange. Here, the technical characteristics of the connection between the SAP System and other system are defined. The file port type has to be maintained for the directory. The outbound IDoc files are stored in the mentioned outbound file whereas the Inbound files are stored in the mentioned Inbound File.

In outbound processing, SAP system creates the IDocs, processes them and then sends to the directory defined in the file port. Whereas in case of inbound processing, the ASCII files are taken from the Inbound Directory, converted to IDocs, processed and a new record is created in the SAP Database.

Menu: SAP standard menu  Tools  Business Communication  IDoc  IDoc

Basis  Port Definition

Transaction code: WE21

Explanation:

1. The function module EDI_PATH_CREATE_CLIENT_DOCNUM (or any other appropriate function module) is used for generating the IDoc file names.

2. Physical Directory has to be selected

(Screen Shot 3.1)

Screen Shot 3.1

Maintain Distribution Model

A distribution model shall be maintained in ALE customization to distribute data. Messages of type DEBMAS02 have to be distributed to Extransx logical system.

Menu: SAP Standard Menu  Tools  Accelerated SAP  Customizing  SPRO  SAP Reference IMG  Basis Components  Distribution (ALE)  Modelling and Implementing Business Processess  Maintain Distribution Model and Distribute Values

Transaction code: BD64

Explanation:

Distribution model contains the following assignments:

1. Create distribution model view (Screen Shots 4.1, 4.2)

2. Assign From and To Logical System. (Screen Shots 4.3, 4.4)

3. Add message types to be transferred u2013 DEBMAS

4. Save distribution model.

5. Generate partner profile for logical system. (Screen Shots 4.5, 4.6)

Screen shot 4.1

Screen shot 4.2

Screen shot 4.3

Screen shot 4.4

Screen Shot 4.6

Change Partner Profile of logical system

For logical system, a partner profile can be automatically generated from the distribution model. In this step relevant ports are assigned to the logical system.

Menu: SAP Standard Menu  Tools  Accelerated SAP  Customizing  SPRO  SAP Reference IMG  Basis Components  Distribution (ALE)  Modelling and Implementing Business Processess  Partner Profiles and Time of Processing  Maintain Partner Profile Manually

Transaction code: WE20

Explanation:

The following details are maintained in the partner profile

1. Outbound messages (DEBMAS) to be transferred from SAP. (Screen Shots 5.1 and 5.2)

2. IDoc type (DEBMAS02) to be triggered for each message type

3. File Port to be used for transfer of IDocs .

4. IDoc pack size. This should be set to 1 only.

5. Output mode (Transfer IDoc immediately).

6. Receiver of error notifications (user id) if any, occurs during the process.

Change the port that can be used for both the messages types to the appropriate port defined in the step 3.

Activate change pointers

Change pointers have to be activated generally and then specifically to a message type.

Menu: SAP Standard Menu  Tools  Accelerated SAP  Customizing  SPRO  SAP Reference IMG  Basis Components  Distribution (ALE)  Modelling and Implementing Business Processess  Master Data Distribution 

Replication of modified Data  Activate Change Pointers Generally (and) Activate Change Pointers for message types.

Transaction code: SALE or BD61/BD51

Explanation: The relevant message types (DEBMAS) are activated. (Screen shots 6.1, 6.2, 6.3 and 6.4)

B) Execute Manually:

To execute program RBDMIDOC manually, the following steps are to followed.

Menu: SAP Easy Access  Tools  ABAP Workbench  Development

 ABAP Editor

Transaction: SE38.

Refer Screen Shot O .34.

Explanation:

1. On the screen enter the name of the program as u2018RBDMIDOCu2019 and press the execute button on the menu bar.

2. On the second screen ie selection screen enter the name of the message type DEBMAS and execute the program

3. During the execution, two message windows will come. Press the continue button.

Regards,

Pullaiah

[Former Member]

Helpful.