Can anybody help out in ALE?

Question

Hi friends,
              Can anybody help me out by giving the navigation steps of configuring the ALE.......Please urgent
Useful Answers will be definetly rewarded points.

Answer 1

hi,
1.     INTRODUCTION TO ALE DEVELOPMENT
To develop a new custom ALE scenario, comprises 5 steps:
1.     Design and develop the custom IDoc with it’s segments and a new message type
2.     Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3.     Develop the outbound process which does the following:
•     Populates the custom IDoc with control info and functional data
•     Sends the IDoc to the ALE layer for distribution
•     Updates status and handles errors
4.     Configure the ALE inbound side (partner profiles with inbound process code)
5.     Develop the inbound process which does the following:
•     Reads the IDoc into a BDC table; selects other data that is required
•     Runs transaction using call transaction or BDC session
•     Updates status and handles errors
2.1.     Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development
To create the IDoc type, follow these next few steps:
•     Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
•     Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
•     Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
•     Click on ZINVRV01 and then on the Create icon
•     Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
•     Enter a description for your segment type and create
•     Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
•     Save and generate, press back
•     To release the segment choose Goto, Release from the menu
•     Check the box on the line of your new segment
•     Save, back and enter
•     Your IDoc type structure should be displayed with your new segment
•     Save and back
•     To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar
procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2.     Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
•     Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
•     Choose Create logical message type by double clicking on it
•     Click on change icon to enter change mode
•     Click on New entries to add a new type
•     Enter the required message type, in our case it is ZINVRV and an appropriate description
•     Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1.     Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
•     Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
•     Click on change icon to enter change mode
•     Click on New entries to create the link
•     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
•     Save and exit
•     Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
•     Click on change icon to enter change mode
•     Click on New entries to create the link
•     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
•     Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2.     Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
•     Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
•     Type in your message type ZINVRV and press enter
•     Click on New entries
•     Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
•     Save and exit.
You have now created an object that we’ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3.     Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1.     Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
•     Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
•     Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
•     Choose the receiving systems to which the sending system must forward message type ZINVRV to.
•     For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
•     Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
•     Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2.     Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1.     Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
•     Make the settings for the communication with the other decentral systems, you have not set them yet.
•     Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
•     Create the output partner profile.
•     Distribute the customer model
•     Specify the name of the customer model.
•     You must specify the target system to which you want to distribute the customer model.
•     You must repeat this function for every distributed logical system.
2.3.2.2.     Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
•     Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
•     The customer model must be maintained.
•     RFC destinations must be maintained.
•     The customer model must be distributed.
•     To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4.     Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
Hope this helps, Do reward.