The purpose of ALE IDOC is to help the ABAP Developers to get an idea on how to setup all the necessary configs needed to send and receive idocs. This is the MUST guide for you if you are wondering where to start with the ALE IDOC Development and this pretty much covers around all the required business cases. All the below steps are explained in detail.
Complete ALE IDOC Tutorials for Beginners & advanced users
Understanding and Configuring the client to client setup:
Walks you through defining logical system, assign logical system to the client, create RFC Destination and preparing distribution model, generating partner profile, view partner profile created in the sender system, view port information in sender, how to distribute customer distribution model and generate partner profile in the receiving client and a sample example of configuring and distributing material master across other systems.
System to system ALE setup
Create Logical Systems for both sender and Receiver, Assign Logical Systems to Clients, Create RFC Destination, Maintain Customer Distribution Model, Generate Partner Profile, Distribute Customer Distribution Model, Generating Partner Profile in the Receiving Logical Systems, Create /Change Material master records, Distributing Records in the Receiving logical system, Checking IDoc status in the receiver system and Check Material in Receiver System.
Two-way server to server communication
Practical examples of customizing for Sending Vendor master from one client to another, additional customizing required to send material master from one system to another and customizing for receiving iDOcs from another system.
Covers other important topics on IDOCS
T-RFC Reporting, Setting up Audit Reporting, Manually Process IDoc in Receiving System, Collect IDoc and Transfer, Creating Filter Objects, Segment Filtering, Creating Reduced message type, Change Pointers Technique, Reprocessing IDocs not posted due to errors & Processing Idiocy waiting in the queue.
Developing and Transmitting new IDoc
Prepare data container in both sender and receiver, Prepare Segments(WE31), Prepare IDocs with the segments in both systems (WE30), Create new message type in both the systems (WE81), Link new message type with IDoc type in both systems (WE82), Maintain two logical systems, one for sender- another for receiver in both the systems (BD54) , Assign Logical System for Receiver to appropriate client in Receiver system and assign logical system for sender to appropriate client in sender system (SCC4) and Create RFC Destination for Receiver in sender system and for sender in receiver system(SM59), Create Customer Distribution Model for the Message type in sender systems(BD64), Generate the partner profile in the sender system(BD82), Distribute the CDM from sender system to the reciver system(BD64), Create the outbound program in sender system to populate and distribute the Idocs(SE38) , Develop Inbound Function Module in the Receiver System(SE37), Create new Idoc Object in Business Object Repository(SWO1) in Receiver system, Create a new task based on Application Idoc object(PFTC) in Receiver system, Allocate Function Module to the Message type(WE57) in Receiver system, Define settings for Inbound FM in Receiver system(BD51), Create New Process code for the Inbound process(WE42) in Receiver system, Assign Input Methods(BD67) in Receiver System & Generate Partner Profile in Receiver System(BD82).
Standard IDOC Extension
Building Append structure, adjusting exits to populate data in the extended idoc structure, linkage with the message type and the basic idoc type in sender system, adjusting partner profiles, testing, writing code in the receiving system and checking if the data has been received correctly.
Creating change documents
for the new information & Configuring and developing for change pointers for a custom message type.
Downloading IDoc into Application Server
Creating the file port, changing outbound partner profiles, trigger the outbound process.
Download the document on ALE IDOC Tutorial for ABAPers. All the thanks & credits to the author for making this document.
Rules for ALE Optimization
- Review of ALE Integration Scenarios
- Understanding ALE Technology
- Optimizing ALE by understanding top 10 ALE Performance hits
- Optimizing / Sizing ALE interfaces during the design phase
Download/view the presentation on ALE Optimization.
Successfully Leveraging IDOCS
- Understand and follow the evolution of SAP Integration technology
- Examine and review ALE/IDOC interfacing technology
- Using ALE/IDOC for Application for technology and cool tools
- Apply ALE/IDOCS with R/3 and mySAP
- Q & A
Download/view the presentation of Leveraging IDOCS
Working with IDocs
- Understand the basics of IDOC, Basic Type, Message Type.
- Quick Reference transactions (SALE, WEDI, WE02, PFAL, BD21, BD22, WE19, BD73, WE60, BD53)
- Partner Profiles
- Creating Reduced Message Type using BD53
- Maintain distribution model
- How to read an IDOC
- Testing Inbound/Outbound IDOC
- Useful Function Modules
Download the document on IDOC Overview
Useful EDI Transactions
- VOE1 Translation between EDI categories and SD item categories
- VOE2 Table EDSC view. Customer link to sales area detail.
- VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc.
- VOE4 Table view EDPAR. Link external partner number with our internal number.
- OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement, sold-to partner.