IDOC and EDI generation

Hello all,
I would like to know how IDOC and EDI gets generated. What is the purpose of using IDOC and EDI. which one gets triggered initially and is there any interface that has to be set for IDOC and EDI generation
Pl. post any docs/Link related to IDOCs and EDI.
Thanks,
Maxx

Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
For idocs in delivery processing:
http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

Similar Messages

Tax with the help of idoc and EDI

Dear gurus,
how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

Hi Amit,
I do not understand how a non-sap system having an idoc adapte?
Do you mean the non-sap system has the ability to understand the IDOC files?
If yes, then your scenario is typically a IDOC-to File scenario.
Read this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
Regards,
Ravi

Idoc and EDI for FI

Hi all,
Can anyoune help me out with the topics.
Idoc and EDI and how this are related to FI.
I was looking for some scenario.
How to process inbound idoc and outbound idoc.
Thanks advance for help.
Regards,
sha

Idocs can be triggered internally by standard coding logic. It can also be triggered by output.
For idocs in delivery processing:
http://help.sap.com/saphelp_erp60/helpdata/en/38/c1853488601e33e10000009b38f83b/frameset.htm
LE-SHp -> printing and communication -> Delivery interface. (here these idocs are generated by output).

Relation between idoc and EDI,ALE

Hi,
I am new to IDOC. Can u please tell me whether there is any relation between IDOC and ALE or IDOC and EDI. If so what is the relation between them.

Hi Buvana,
ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B.
EDI ->
EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
Info shuttle - "I was implementing EDI at a customer and I wanted some real data to test with in Development, so I asked the Project Manager to see if he could arrange something. Literally, 20 minutes later he came back and said that there were 10 new orders in Development, together with the customer master records related to the order, the carrier vendor master record, the material master records, ... were all there. I asked him how he had done it so quickly which led me to my first exposure with Infoshuttle, a tool that does this for you using the ALE functionality. As an ALE consultant I know how to do this stuff but I also know how long it would take to set that up.
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc for further details on ALE.
Check this link.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Regards,
Priyanka.

IDOC and EDI

Hi,
Please send me some useful information on IDOC'S and EDI with relevance to SD module and comman errors with this documents.

Standard SAP format for electronic data interchange between systems (Intermediate Document).
Different message types (for example, delivery confirmations or purchase orders) normally represent the different specific formats, known as IDoc types. Multiple message types with related content can be assigned to one IDoc type
Example:
The IDoc type ORDERS01 transfers the logical message types ORDERS (purchase order) and ORDRSP (order confirmation).
Among other areas, IDocs are used in both Electronic Data Interchange (EDI) and for data distribution in a system group (ALE
Another
The EDI interface is used to connect an EDI subsystem to the SAP system. EDI subsystems perform all EDI-related tasks such as Converting the data Handling messages or interchanges Communications Managing the partner profiles Monitoring processing. The EDI interface is based on IDoc technology. IDoc technology is independent of EDI standards. All data is exchanged via files between the SAP System and the EDI subsystem. The synchronous RFC (remote function call) is used to define the time of transfer of the files between both systems. Via the EDI interface, the following data can be exchanged:
Outbound IDocs. IDocs are transferred from the SAP System to the EDI subsystem.
Inbound IDocs. IDocs are transferred from the EDI subsystem to the SAP System.
Status report. To inform the SAP System of the progress of processing of the outbound IDocs, the EDI subsystem transfers the status report to the SAP System.
The object of the certification is the technical test of the interface between SAP System and EDI subsystem. The transfer of outbound IDocs, inbound IDocs and the status report are tested. The test is performed for the EDI standard UN/EDIFACT. As an example, the messages used are:
Outgoing order (ORDERS)
Incoming order (ORDERS)
Outgoing order response (ORDRSP) and
Incoming order response (ORDRSP).
Regards

Idocs and Edi ?????????

hai
can any tell me
1. what is idocs?
2.structuture of an idoc ?
EDI
how it is used in real scenarios ? send some material or some links
helpful answers will be rewarded for sure .
regards
sriram.

HI.,
ALE is Applicfation linking & Enabling which enables to interface SAP with other modules
IDOCS are intermediary doccuments which are like CARRIERS of the data
In SAP These plays a major role
Go through this,You will get better idea on EDI,ALE,IDOCS
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
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.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
http://help.sap.com/saphelp_46c/helpdata/en/78/2173cf51ce11d189570000e829fbbd/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/8c/20e304493311d1894a0000e829fbbd/frameset.htm
ale/idoc
ALE/IDOC
http://www.sap-img.com/abap/ale-bapi.htm
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
http://searchsecurity.techtarget.com/generic/0,295582,sid21_gci1110008,00.html
http://www-1.informatik.fh-wiesbaden.de/~werntges/lv/edi/specs_EN/SAPdoc/IDoc_d.htm
ALE/IDOC : Basic Documents with Screen Shots
REWARD if helpfull
Thanks & Regards
Narayana

ALE IDOC AND EDI

Hi
Could u pls explain whats the use of these terminology in SAP and what's the prequisites, configuration setting and how these worked.
thanks

Hi,
Application Link Enabling:Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications. Applications are integrated using synchronous and asynchronous communication and not using a central database.
Application Link Enabling comprises the following three layers:
Application services , Distribution services , Communication services.
Intermediate document (IDoc) container for exchanging data between R/3, R/2 and non-SAP systems. ALE uses IDocs to exchange data between logical systems. Non-SAP systems can use IDocs as the standard interfacefor data transfer.
IDocs are created when message types and (object) methods are distributed. The message type is the format in which the data for a specific business process is transferred.
Electronic Data Interchange.
Electronic exchange of structured data, such as business documents, between domestic and international business partners that use different hardware, software and communication services. For this purpose, the data involved is formatted according to predefined standards.
In addition to this, the SAP ALE technology is available for data exchange within a company.
Prase

Difference btw idoc ale and edi

Hi all,
I'm a beginner in abap, can anyone send me the concepts of ALE, IDOC and EDI and the difference btw all the three.
Also do send some materials for the same.

Hi,
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
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 IDocs 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 programs 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 IDocs 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 modules 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).
IDOC:
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..
[Re: How to create IDOC;
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)
RFC:
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
[http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm]
check out the following link it might help you
[http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf]
EDI:
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
[http://www.erpgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.
check this.
[http://www.netweaverguru.com/EDI/HTML/IDocBook.htm]
[http://www.sapgenie.com/sapedi/idoc_abap.htm]
[http://www.sapgenie.com/sapedi/index.htm]
[http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm]
[https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp]
[http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/]
[http://www.erpgenie.com/sapedi/index.htm]
[http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd]
[ALE / IDOC / RFC / EDI]
[SAP ABAP and EDI/ALE/IDOC]
[Re: IDOC/BAPI/ALE/EDI]
Regards,
Dhruv Shah

IDOC Invoices and EDI Invoices

Hi Gurus,
Please help me in understanding the flow of IDOC Invoices and EDI Invoices.
What is the purpose of using IDOC and EDI? How it works?
Please revert asap.
Thank You

HI Verma,
You can post the invoices in SAP system through IDOCs.
Mostly, this activity is performed/triggered, when the invoice data is with third party.
Third party will have the invoice data base and sends a file to SAP.
SAP XI will map/convert the file(sent by third party) to fields in SAP and posting of invoice happens.
Please refer the below links for EDI Invoices
EDI invoices
Creating EDI Invoices
Hope this will help you in understanding IDOC invoices and EDI Invoices.
Regards,
Praisty
Edited by: Praisty on Dec 22, 2009 1:20 PM

Reg- ALE and EDI

Hi.
What is meant by ALE (and ALE-IDOC) and EDI nd what is the difference between them.
Kindly expectimg replies.

Hi Sathish,
ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B.
EDI ->
EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
Info shuttle - "I was implementing EDI at a customer and I wanted some real data to test with in Development, so I asked the Project Manager to see if he could arrange something. Literally, 20 minutes later he came back and said that there were 10 new orders in Development, together with the customer master records related to the order, the carrier vendor master record, the material master records, ... were all there. I asked him how he had done it so quickly which led me to my first exposure with Infoshuttle, a tool that does this for you using the ALE functionality. As an ALE consultant I know how to do this stuff but I also know how long it would take to set that up.
www.sapgenie.com/sapedi/edi_sap_training.htm
www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
http://www.onestopsap.com/interview-Question/edi/
IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc for further details on ALE.
Check this link.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Hope ur problem is solved now..
<b>Reward points if useful...</b>
Thanks & Regards
ilesh 24x7

IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

Hi All,
IDOC (Invoice) to EDI file scenario without Seeburger
Pls let me know if anybody have blogs for the same
EDI file to IDOC (Orders) scenario without Seeburger
Pls let me know if anybody have blogs for the same
Regards

Hi Rachit,
>>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
Also java code for IDoc to EDI have some problems:
1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
All the best
Regards
Suraj

Idocs ale and edi

Hello Experts,
       I am beginner in IDOCS,ALE AND EDI concepts, i would appreciate if some one can forward me material on these concepts, also some sample programs or examples on these.
Thanks.
Raghu

Hi,
ALE Process Steps:
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
IDOC
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/
EDI
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
reward points if useful
regards,
ANJI
Message was edited by:
        Anji Reddy Vangala

Whats the dfference between IDOC, ALE and EDI?

whats the dfference between IDOC, ALE and EDI?

Hi,
1)EDI
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
http://www.erpgenie.com/sapedi/index.htm
2) ALE
A means of creating and operating distributed applications.
Application Link Enabling (ALE) guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications.
Applications are integrated using synchronous and asynchronous communication - not by using a central database.
ALE consists of the following layers:
Application services
Distribution services
Communication services
Refer
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
Check this link ALE and EDI
http://www.onestopsap.com/interview-Question/edi/
IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at this for further details on ALE.
http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc
Check this link.
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
Regards,
Priyanka.

Data Fir IDOC ALE and EDI

Hello All,
    I am newly join in IT company (Name don't want to specify) . They have putted me in a consolidate project in which I do have to work on IDOC,ALE and EDI object.
yet in my career with SAP ABAP I haven't work on the above mention terms of SAP. Can some One please guide me and provide me some material to prepare my self best for the things.
Regards
Swati Namdev

Some use full Tcodes:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
WE02     List Of All Idocs Created. (Default, Additional, EDI)
WE05     List Of Idocs Created.    (Standard, Additional)
WE06     Active Monitoring For Idoc Processing.
WE07     Idoc Statistics.
WE08     Display View u201CFile Statusu201D:Overview-Path Name.
WE09     Idoc Search For Business Contents (Database).
WE10     Idoc Search For Business Contents (Archive).
WE12     Modification Of Outbound File, Triggering Inbound Processing.
WE14     Process All Selected Idocs.
WE15     Selection Program For Issuing Output.
WE16     Trigger Inbound Processing.
WE17     Trigger Status Processing.
WE18     Generate Test Status File For Outbound Idocs.
WE19     Test Tool For Idoc Processing
WE20     Partner Profile.
WE21     Ports In Idoc Processing.
WE23     Display Test Catalog Test Idoc Interface.
WE24     Maintain Table View. Direction-1.(Outbound)
WE27     Maintain Table View. Direction-2.(Inbound)
WE30     Develop Idoc Type.
WE31     Develop Idoc Segments.
WE32     View Development.
WE33     Maintain Table Views.
WE34     Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40     Display System Process Code.
WE41     Display View: Logical Msg Overview. For Outbund.
WE42     Display View: Logical Msg Overview. For Inbound.
WE43     Display Status Records.
WE44     Display Partner Types
WE45     Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46     Global Parameter For Idoc Interface.
WE47     Status Maintenance.
WE50     Display Text For Process Code System.
WE54     Idoc Function Module For File Name
WE56     Display Status Process Code
WE57     Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58     Text For Process Code Status.
WE60     Documentation For Idoc Type.
WE61     Documentation For Idoc Record Type.
WE62     Documentation For Idoc Segment Type.
WE63     Documentation For Idoc Record Types And Idoc Types (Parser).
WE64     Process Code In Idoc Inbound And Outbound.
WE70     Conversion Table For Basic Types.
WE71     Conversion Table For Extensions.
WE72     Conversion Table For Field DOCTYP.
WE73     Conversion Table For Logical Message Type.
WE81          EDI:Logical Message Type.
WE82     Message Types And Assignment To Idoc Types.
WE84     Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code     Description
BD10     Send Material (Matmas)
BD11     Get Material.
BD12     Send Customer.
BD13     Get Customers
BD14     Send Vendor.
BD15     Get Vendor.
BD16     Send Cost Center. (Cosmas)
BD17     Request Cost Center.
BD18     Send G/L Accounts.
BD19     Get Master Data G/L Accounts.
BD20     Inbound Processing Of Idocs Ready For Transfer.
BD21     Creating Idoc Types For Change Pointers.
BD22     Delete Change Pointers.
BD23     Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24     Send Cost Elements.
BD25     Send Activity Type (COAMAS)
BD26     Request Activity Type
BD27     Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28     Cost Center/ Cost Elements: Send Control Records.
BD30     Material Bom Distribution. (Bommat).
BD31     Document Structure Distribution. (Bomdoc)
BD32     Plant Allocation To Material Boms Distribution.
BD33     Distribution Of Material Variants. (STTMAT)
BD34     Distribution Of Boms (BOMORD)
BD35     ALE: Send Business Process Group.
BD36     ALE: Send Business Process.
BD37     ALE: Send Business Process Price.
BD40     Generate Idocs For Serialization Group From Change Pointers.
BD41     Dispatch Of Idocs Of Serialization Group.
BD42     Check Dispatch Status Of Idocs Of Serialization Group.
BD43     Processing Inbound Idocs Of Serialization Group.
BD44     Change View u201CSerialization Groupu201D.
BD47     Dependence Between Methods.
BD48     Dependence Between Methods And Message Type.
BD50     Activate Change Pointers For Message Type.
BD51     Characteristics Of Inbound Function Module.
BD52     Determine Work Area.
BD53     Reduce Message Type.
BD54     Change View: Logical Systems
BD55     Idoc Conversion.
BD56     Maintain Idoc Segment Filters.
BD57     Link Type And Serialization Type Of Message Type.
BD58     Convert Organizational Unit.
BD59     Allocation Of Object Type.
BD60     Additional Data For Message Type.
BD61     Activate Change Pointers Generally.
BD62     Display Conversion Rule.
BD63     Transport Of Ale Tables For A Message Type.
BD64     Display Distribution Model.
BD65     Maintain Idoc Type Required Fields.
BD66     Change Idoc Fields.
BD67     Function Module For ALE/EDI Overview.
BD68     Maintain List.
BD69     Assignment Of Idoc Type To Message Type.
BD70     Cross-System Comparison Of Number Range Objects.
BD71     Attributes For Receiver Determination.
BD72     Active Events For ALE/EDI
BD73     Start Error Handling For Non-Posted Idocs.
BD75     Status Conversion With Trfc Execution.
BD77     Generate Transport Requests For Distributing ALE Customizing Data.
BD78     Monitoring Ale Customizing Data Transport
BD79     ALE IDOC Segments - Conversion Rule
BD81     Filter Objects For BAPI Parameter Filtering
BD82     Generating Partner Profile
BD83     Re-Processing Incorrect Outbound Odocs.
BD84     Re-Processing Of Idocs After ALE Input Error.
BD85     Consistency Check: Reassignment Between Two System.
BD86     ALE Consistency Check: Create Purchase Order From Sales Order.
BD87     Select Idocs
BD89     Customizing Data Modeling For Distribution Model.
BD91     Distribute All Characteristics Via ALE.
BD92     Distribute Class Via ALE: Send Direct.
BD93     Distribution Of Classification Data Via ALE.
BD95     Ale Object View
BD96     Filter Object For Receiver Determination Of Methods.
BD97     Assign RFC Destination For Synchronous Method Calls.
BD98     Consistency Check With Workflow Link
BD99     Dependencies Between Message Types.
BD100     Display Serialized Idocs. (Serialization Using Object Types)
BD101     Serialization Using Object Types: Consistency Check.
BD102     Ale: Outbound Channel Registry.

MATERIAL ON IDOC,ALE AND EDI

hi,
IF U HAVE ANY MATERIAL ON IDOC,ALE AND EDI PLZ SEND TO MY MAIL ID([email protected]) OR GIVE ANY SITE ADDRESS?

hi,
for ALE/IDOC
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
For ALE -- IDoc's
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
ALE/ IDOC/EDI
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/ale/why_ale.htm
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
for EDI
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.onestopsap.com/interview-Question/ale/
http://www.onestopsap.com/interview-Question/edi/
http://www.allsaplinks.com/idoc_sample.html
http://www.sap-img.com/abap/ale-bapi.htm
http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Please check this link for EDI/ALE/IDoc online documentation.
http://www.easymarketplace.de/online-pdfs.php
good link
http://myweb.dal.ca/hchinni/sap/idocs/IDoc%20Cookbook%20for%20EDI%20and%20Interfaces.doc
If you need further info shoot me a test mail to [email protected]
Regards,
GNK

IDOC and EDI generation

Similar Messages

Maybe you are looking for