ALE/IDOC

Hi Raghuveer,

These are the steps in ALE-

1. Define Logical System SALE (BD54)

Enter the Name of Logical System and Save.

2. Assign Client to the Logical System SALE(SCC4)

Double click on Client name and assign Sender Logical system

3. Maintain RFC Destination - SM59

Click on Create

Give Name for RFC Destination, Description, Connection type (T/3) and Enter Details for R3 and TCPIP

For R/3 connection type, enter client, user, password, language, target host, system number.

You can verify the R/3 connection by Test connection or Remote logon.

4. Assign RFC Destination to Receiver Logical System -BD97

RFC destination of type TCP/IP is used for EDI interfaces.

Click on Receiver Logical system, then on Std BAPI destination and then assign RFC destination.

5. Create Distribution Model - BD64

Click on Create Model view, give the Name and Description.

Add message type – sender / receiver logical system and message type.

6. Port Creation - WE21

Select File, Click on create and give details for EDI.

7. Create partner profile - WE20

Give same Name as Receiver logical system, type LS and Save.

Give message type, idoc type, receiver port number, packet size.

You also need to add message type Synch when you create through WE20 manually.

The wizard will take care this.

8. Distribute the model - bd64(BD82)

Select Model View, goto to Edit – Model View and distribute.

Reward points if you find the answer useful.

Regards,

Tanuja.

Hi Raghuveer,

You can go to ALE setting thru: Transaction "SALE" or through IMG using transaction "SPRO".

Got thru these docs on ALE/IDOC:

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/printdocu/core/Print46c/en/data/pdf/SDEDI/SDEDI.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESIDOCXML/BCFESIDOCXMLSTR.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDED/BCFESDED.pdf

For inbound idoc in partner profiles if you set trigger immediately for a message type , whenever idoc comes from middleware , it will be processed automatically . for process success idoc status will become 53, if it is failed idoc status becomes 51.

at partner profiles if idoc process selected as process through background program , whenever idoc comes from middleware it goes to 64 status. for these idoc's we need to schedule RBDAPP01 program to process 64 status idoc's or we can process these idoc's from BD87 transaction

Check these links:

http://www.sapgenie.com/sapedi/idoc_abap.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/72/c18eff546a11d182cc0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/9c/2744f5fa7464429a13345be4050fb6/frameset.htm

http://www.sappoint.com/ppt/ale.ppt

below details might help you.

WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.

WE05 View IDocs

WE19 EDI test tool. Use to test inbound Function module changes.

WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing

WE30 Create IDoc extension type

WE31 Segment create

WE57 Assign function module to logical message and IDoc type

WE60 IDoc type documentation tool

WE82 Link Release detail to Extension IDoc Type

BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)

BALA ALE Application Distribution

BALM ALE Master Data Distribution

You can go to ALE setting thru: Transaction "SALE" or through IMG using transaction "SPRO". Some other useful transactions are.

WEDI - main transaction for all ALE settings

Hope this cud be of some use to you.

Reward points if useful.

Regards,

Amit.