cancel
Showing results for 
Search instead for 
Did you mean: 

doubts

Former Member
0 Kudos

Hello SAP Prof,

1.what is the relevance of vendor Tab in customer master and in which scenario you will use this tab

2.What is the use of ALE and IDOC for functional consultants

3.Can you explain about actual GI (gods issue) date and planned GI date? Can actual GI date differ from planned GI date?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

<b>Vendor Tab:</b>

Some cases a customer can be VENDOR, so the vendor master number for the corresponding customer will be assigned to customer.

<b>Planned date + Actual date:</b>

Planned GI Date : It is the date on which the goods must be physically dispatched from the shipping so that it can reach customer on the Requested Delivery Date (RDD) or on-time. It can be calculated as follows :

Planned GI Date = RDD - (pick/pack time + loading time + transit time)

Actual GI Date : Actual date on which physical goods movement happens from shipping point. Goods issue document to account for the outgoing inventory is normally created on Actual GI Date

<b>ALE:</b>

Application Link Enabling is a set of business processes and tools that allow applications on different computer systems to be linked. This can be done between different SAP systems as well as between SAP and non-SAP systems.

Benefits of ALE

Integration of Distributed Systems.

Integration with Non-SAP Systems.

Reliable Distribution.

Release Upgrade.

Autonomy.

How ALE works

ALE allows the user to perform an SAP transaction in the sending system, after which the following steps occur:

One or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database.

An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent.

These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer.

This layer performs an RFC call using the port definition and RFC destination determined through the customer model.

The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems.

IDOC

1An IDOC is not a process. It is simply a container that can be used to exchange information between any two processes.

2An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC serves as an input to create application document.

3In the SAP system IDOCs are stored in the database tables.

4Every IDOC is assigned a unique number.

5IDOC are independent of the sending and receiving systems. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.

This just overview of ALE

regards,

Arun prasad

Message was edited by:

arun prasad

Answers (2)

Answers (2)

Manoj_Mahajan78
Active Contributor
0 Kudos

Rajesh,

1) In SAP you would have him as a vendor and also as a customer. This field is used to link both the vendor code and customer code so as to identify that it is the same person or organization.

2)Please check this links for good documentation

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

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

Reward useful points

siva

Message was edited by:

SivaKumar

Naveen Bathini

Posts: 2,484

Questions: 0

Registered: 9/2/06

Forum points: 4,692

Re: ALE & IDOC

Posted: Jun 13, 2007 12:31 PM in response to: rao b Reply E-mail this post

Dear Rao,

ALE and IDOC:

ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .

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.

It is the the combination of Segements.

Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).

Idocs Type is a Structure by lot of segments.

IDOC is generared at the time of run time .

It will have the data.

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.

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

3) Planned goods issue date is when you expect the goods to be dispatched to the customer and actual goods issue date is when the goods issue is executed in real time.

REAWRD IF THIS HELPS...

Regds

MM

Former Member
0 Kudos

Hi Rajesh,

1) In some case your vendor could also purchase goods from you, maybe the end product. So in SAP you would have him as a vendor and also as a customer. This field is used to link both the vendor code and customer code so as to identify that it is the same person or organization.

2) IDOC and ALE are more on the technical side. IDOC is used when you want to send information via EDI. Check the following links for more details.

http://articles.techrepublic.com.com/5100-6329-1051228.html

http://www.sap-img.com/abap/ale-bapi.htm

http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp

3) Planned goods issue date is when you expect the goods to be dispatched to the customer so that it can meet the delivery commitment and actual goods issue date is when the goods issue is executed in real time. The dates could differ for various reasons. You could plan a GI for the 1st of a month and actually execute it on the 5th due to some delay.

Regards

Nadarajah Pratheb