Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

idocs

Former Member
0 Kudos

hi all,

i just wanna know the step by step procedure for creating an idoc with an example.

6 REPLIES 6

Former Member
0 Kudos

PROCESS DIAGRAM

Outbound Interface

1. Analyse Hierarchy Levels

2. Create New segment

3. Create New IDoc Type

4. Create New Message Type

5. Link Message with IDoc Type

6. Create an entry in EDP13 via transactions WE20 and BD64

7. Populate the Custom IDoc via ABAP Program

7b Error Handling

7c. Send Status Email

8. Test the Population of the Custom IDoc

Step 1 – Analyse Hierarchy Levels:

Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.

Navigate to transaction code WEDI

Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.

Step 2 – Create a new segment:

via wedi : Development - IDOC Segments or Transaction code WE31.

• Enter segment name and click on Create.

 The name of the segment type must start with Z1 , and have a maximum of eight characters.

• Enter description and enter the relevant field names and data elements.

 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.

• Save the segment and enter Person Responsible and Processing Person .

• Go to Edit and Set Release.

• Repeat this procedure for each new Segment in the IDOC.

Step 3 – Create a new IDOC Type

via wedi Development - IDOC Types or Transaction WE30.

• Enter segment name (starting with Z), click on Basic Type and then Create.

• Create as new, enter Person Responsible and Processing Person and enter description.

• On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.

• Complete relevant fields in the Maintain Attributes screen:

• From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.

• The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).

• The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.

• Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.

• When IDOC created return to initial screen. Go to Edit and Set Release.

• Go to Transaction WE60 to view the IDoc Type you have created.

Step 4 – Create new Message Type

via wedi Development - Message Types or Transaction WE81.

• Display/Change and click on New Entries

• Create a new Message Type and Save.

Step 5 – Link Message Type to IDOC Type

via wedi Development - IDOC Type/Message or Transaction WE82.

• Display/Change and then click on New Entries.

• Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.

Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.

The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.

• WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.

• BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.

Step 7 – Populate the custom IDOC via ABAP Program

See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.

• Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.

• The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.

PERFORM populate_Control_structure USING c_mestyp

c_SEGMENT_type1.

• The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.

PERFORM transfer_Parent_data_to_seg.

• The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.

PERFORM master_idoc_distribute.

• NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.

• The ALE Layer handles the sending of the IDOC to the receiving system.

• Error Handling (see Step 7b).

• Commit work.

Project SpecificStep 7b – Error Handling

• Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.

• Declare a structure of type ‘MCMAILOBJ’ for sending instructions.

• Enter values for the internal table based on structure ‘MCMAILOBJ’

• For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module ‘MC_SEND_MAIL’.

• Enter values in the following parameters: -

MS_MAIL_SENDMODE = ‘B’ (Batch Mode)

MS_MAIL_TITLE = 'Mail Title'

MS_MAIL_DESCRIPTION = ‘Error description’ (e.g. MATNR not given)

MS_MAIL_RECEIVER = ‘Name of Receiver’ (To be determined)

MS_MAIL_EXPRESS = ‘E’ (Express Delivery)

MS_MAIL_DLINAME = Leave Blank

MS_MAIL_LANGU = 'E' (Language)

MS_MAIL_FUNKOBJ_NAME = Leave Blank

TABLES

MS_MAIL_CONT = I_MCMAILOBJ

Note:

It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.

When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)

Step 7c – Send status mail

• Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.

• Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).

• Use function Module ‘MC_SEND_MAIL’ to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.

Step 8 – Test the population of the custom IDOC

via wedi IDoc - Display IDoc or Transaction WE02.

• Enter your message type and execute.

• Status should be green, double click on one of the Idocs you have created to view its contents.

• If a problem has occurred click on Status which will give you a description of the error.

• Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.

• Click on each individual segment and view the content to check that the correct data has been read.

• If you have UNIX access by using AL11 you can view the file that you have created.

Note:

For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.

hope you can start now seeing above steps

Useful Transaction Codes:

WEDI : IDoc Menu

WE02 : IDoc List (can enter IDoc number to select on)

WE05 : IDoc List

WE19 : Transaction WE19 can be used to test the IDoc

WE30 : IDoc Type Development: Initial Screen

WE31: Development Segments: Initial Screen

WE60 : Documentation for IDoc Types. This allows you to view the IDoc you have created.

WE81 : Display View ‘EDI: Logical Message Types’: Overview

WE82: Display View ‘Message Types and Assignment to IDoc Types’: Overview

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

rewards if useful,

regards,

Madhavi

0 Kudos

hi madhavi

can u elaborate step3 plz regarding adding attributes

Former Member
0 Kudos

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.

former_member156446
Active Contributor
0 Kudos

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

Former Member
0 Kudos

hi refer this.

Create Message Type (WE81)

Create Segment type (WE31)

Create IDOC Type (WE30)

Assign Segment type to Idoc Type (WE30)

Assign Idoc Type to Message Type (WE82)

Assign Function Module – Mtype – Idoc Type (WE57)

Create a Process Code – (WE41-outbound, WE42-Inbound)

Enable Customized FM to ALE (BD51)

Assign these to Partner Profile (WE20)

check the following thread:

/message/2222912#2222912 [original link is broken]

http://help.sap.com/saphelp_erp2005vp/helpdata/en/e6/04c03e7856b300e10000000a114084/frameset.htm

Also check this:

Creation of Custom IDOc type and message Type

First Create Partner Profile(WE20 Tcode) and Port Definition in WE19 Tcodes.

take the Basis help to create them.

1.First create segments in WE31 Tcode with the required dataelements

2.Create the Basic Idoc Type in WE30

release the Segments and IDOC type.

3.Create Message type in We81

4.Assign the message type to IDOC type in WE82 T code

5.Create the process code in We41 (for Outbound) WE42 (for Inbound)

6.Create A fun module in SE37 starting with ZIDOC_OUTPUT_.. by copying some Inbound (for Inbound) Outbound Fun module

7.Create Workflow setting if needed ..

8. Assign the fun module to Idoc Type, Message Type and WF object (if it is there0

9.Define setting for fun module in BD51

10.In BD51 Define the settings for Fun module..

10.Assign the Processs Code to Fun mod`ule

with regards,

Hema Sundara.

pls give points if helpful.

Former Member
0 Kudos

Also have this sample,

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.

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

with regards,

Hema,

pls give points if helpful.