cancel
Showing results for 
Search instead for 
Did you mean: 

idocs and Edi ?????????

Former Member
0 Kudos

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.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

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

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

REWARD if helpfull

Thanks & Regards

Narayana

Answers (3)

Answers (3)

madhan_narlapuram
Contributor
0 Kudos

IDOCs are safe to transfer data, but less volume of data.

User is not allowed to access(modify) the data like PSA.

IDOCs have 3 parts.

1. Control Record - SOURCE & TARGET details,

2. Data Record - Here comes your query....

Info IDOC - It contains all the technical details related to the data load i.e. Request NO, No of Data Packages, USER, DATE, TIME, LOGICAL SYSTEM, etc. Info IDOC is also ONE segment, the 1 sr segment.

Here data will not be there.

Data IDOC - These are the ones which hold the data. The total no of records are made into Data IDOCs i.e. if 99 records are there then 99 Data IDOCs will be there and all these will be divided into 99 segments.

Hence the total number of Segments in IDOC is 100.

Info IDOC + Data IDOCs = Total no of Segments

1 + 99 = 100.

3. Status Record - Here the status of the data transfer will be available.

ALE:

Pl go thr below links as they provide all the required info on ALE & IDOC's:

ALE / IDOC:

Please check this online document for ALE and IDoc.

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

Also check this links for additional information.

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

u will have enough material from above .....

mostly SD consultanct doesnot deal with EDI , Idocs but its allways good to have knowledge ,,,,

reward points if u think it was atleast some useful

thanks

Madhan

Former Member
0 Kudos

Why implement EDI?

*

Improves data accuracy: You can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors. It is estimated to be one-tenth the cost of handling its paper equivalent.

*

Reduces technical complexity: With EDI, companies use standardized data formats to exchange documents. EDI allows companies using different systems to achieve computer-to-computer electronic exchange of business documents.

*

Lowers personnel needs: EDI can help companies reduce the need for personnel involved in paper business transaction processing.

*

Accelerates information exchange: The lead time between start and completion of order processing is greatly reduced. By timeous scheduling companies can plan production more accurately and thus reduce stock inventories.

Basically you need to concentrate on how to configure/set up idocs...

get familiarized with we02 we41 we42 we81 we20 we19 transactions

go thru user menu WEDI

then how to trigger an idoc using the output

Regards,

Rajesh Banka

Former Member
0 Kudos

Dear Sriram,

concerning EDI concept in SD: the EDI concept is intended to realize the sales and distribution process completely automatically with the help of electronical documents. These documents are sent from one customer to another, are processed mostly on the background and give a possibility to realize the sales process extremely efficiently.

If MM-customer would like to purchase the goods then he creates the IDOC of type ORDERS and send it to SD-customer. On the SD-side the IDOC is processed via the function module IDOC_INPUT_ORDERS and creates the sales order. As confirmation the SD-side can send to MM-side the Order-Response IDOC (function IDOC_OUTPUT_ORDERS). The MM-customer can every thime send a change to the existiong order, then on SD side the ORDCHG IDOC will be processed. It can change the order like in VA02. The creation of the invoice can be made via IDOC of message type INVOIC (function IDOC_OUTPUT_INVOIC).

So, the process can be realized completely automatically between SD and MM partners with the help of IDOCs: ORDERS, ORDCHG, ORDRSP, INVOIC.

That's all concerning the SD-EDI.

Additional processes in SD, where EDI are used:

1) application of delivery schedules to the scheduling agreement: IDOC of type DELINS

2) creation of a delivery order to the scheduling agreement: IDOC of type DELORD

3) creation of external agent service delivery to scheduling agreement: IDOC of type EDLNOT

4) creation of credit advice / credit memo in the frames of self-billing: IDOCs of type GSVERF, SBWAP and for external invoice creation SBINV.

It is all processes which are realized in the SD module via EDI.

I hope this info helps.

Kind regards,

Akmal Vakhidov

Development Support SAP, Walldorf/Germany