1. What is difference between ALE and EDI ?

One SAP system (eg ECC) to another SAP system (eg SAP
CRM/SRM/APO) = ALE
SAP system to Non-SAP system (external third party system) = EDI
2. Definition and Components of IDoc:
An IDoc stands for intermediate document; it is a container for exchanging
data between R/3, R/2 and non-SAP systems.
An Idoc type specifies the structure of the data.
A message type specifies the meaning of the data.
An IDoc type must be assigned to a Message type so that the data in the IDoc
is processed correctly.
Note: An IDoc contains only character fields.
PORT (WE21): Port, in the outbound process, determine the name of the EDI
subsystem program, the directory path where the IDOC file will be created at
the operating system level, the IDoc file names and the RFC destinations.RFC
Destination (SM59): Used to define the characteristics of communication
links to a remote system on which a functions needs to be executed.Partner
Profile (WE20): Partner profile specifies the various components used in a
process (Partner number, IDoc type, message type, Port, Process code), the
mode in which it communicates with the subsystem (batch or immediate) and
the person to be notified in case of errors.Message Control (NACE): Used in
pricing, account determination, material determination, output determination
etc. The message control component enables you to encapsulate business rules
without having to write ABAP programs.
3. IDoc Types:
Based on IDoc Status
01 49 for Outbound Process
50 75 for Inbound Process
Based on direction of data flow

4. Basic steps to performed:

On both sides
1. Define & Assign Logical System SALE (BD54)
2. Setup RFC destinations SM59
3. Port Destinations WE21
4. Partner Profile WE20

In Source system:
In Destination System:
1. Segment Creation WE31
1. First five steps in Source system
2. Basic Idoc Type Creation WE30
6. Creating/Leverage FM SE37
3. Message Type WE81
7. Assign FM to Logical Message WE57
4. Assign Msg Type to Basic WE82
8. Define i/p method for Inbound FM
BD51
5. Distribution Model BD64
9. Create Process Code WE42
6. Message control NACE (optional)
7. Programs
Note: Points to remember in Partner Profile Configuration

Trigger Immediately should be avoided.

To process the collected (Outbound) or background triggered
IDoc (Inbound), these two batch Jobs needs to be scheduled at
regular interval: RSEOUT00 and RBDAPP01 respectively
5. Where the Idoc information is saved?
Tables
EDIDC
EDID4
EDIDD
EDIDS
EDP13
EDP21

Description
Stores the Control Record information an IDOC
Stores the Data Records
Data Seg (EDI Intermediate doc)
Stores the Status of an IDOC
Partner Profile: Outbound (technical parameters)
Partner Profile: Inbound

6. How to re-process the IDoc?

Programs

Description

RBDMANI2
RBDMANIN
RBDMOIND
RSEOUT00
RBDAPP01
RBDAGAIN
RBDAGAI2

Reprocess Idocs manually

Posting of IDocs with Status 51
Outbound Idocs status 03->12
For Processing 30 Status IDocs
For Processing 64 Status IDocs
Reprocess Incorrect Outbound IDocs
Reprocessing of IDocs after ALE Input Error

Note: Cannot remember the programs names !!!!

Just remember one program name for Inbound Idocs
i.e. RBDINPUT.. easy.. huh!!!!
RBDINPUT : A menu with the different statuses possible for
inbound IDocs

7. IDoc monitoring T-Codes

Area Menu for Idocs
Area Menu for Idoc
List Of All IDocs Created. (Default, Additional, EDI)
Selection Program For Issuing Output
Process All Selected IDocs
Test Tool For Idoc Processing
Select IDocs
BD87
Idoc Search For Business Contents (Database)
All process codes (inbound/outbound)

WEDI
SALE
WE02
WE15
WE14
WE19

WE09
WE64

IDoc documentation
WE60
8. How to change the status of IDoc manually?
Use SAP standard program RC1_IDOC_SET_STATUS. Please use
judiciously!!

9. Statuses OK/Warning/Error/Harmless?