hi hope it will help you. +*Reward if help.

*+ 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.h
tm 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..
https://www.sdn.sap.com/irj/sdn/thread?forumID=50&threadID=217884&messageID=2402859 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.ht
m 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.h
tm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.h
tm http://www.allsaplinks.com/idoc_sample.html http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.ht
m 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.ht
m 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.h
tm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.h
tm http://www.allsaplinks.com/idoc_sample.html http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.ht
m 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/conte
nt.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.

hi

hope it will help you.

Pls reward if help.

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