Background:
An ALE IDoc Interface set-up requires series of configuration steps involved and often multiple transactions are to be accessed to check whether a particular configuration is as expected or not.
Problem:
Standard transaction BDM5 is available to check but will not fully solve the purpose.
Solution:
A custom transaction is developed which details out all configuration details pertaining to an interface. Details including Partner profile setup, Port setup, RFC connection details, Distribution model setup, Output message types configuration etc..
Explanation:
Input:
A simple selection screen which requires Partner system and IDoc direction.
As output it details below configuration data.
Output:
1. Partner system/Partner type:
Transactions: BD54, WE20
Tables: TBDLS
2. Message type/Message function/Message code:
IDoc type, Extension IDoc:
Transactions: WE81, WE82, WE20, WE30
3. Output mode, Packet size:
Transfer Immediately or Collect IDoc's
Transaction: WE20
Tables: EDP13, EDP12, EDP21
4.Port/ Port type:
Transactions: WE20, WE21
Tables: EDIPORT, EDIPOA
Output type configuration, requirement routines assigned:
Transactions: WE20, NACE
Tables: T683S
Change pointers enabled or not.
Transaction: BD50
Tables referred: TBDA2
Distribution model/Filters:
Transactions: BD64
Tables referred: TBD05, TBD06
Process code information:
Transactions: WE41 for OutBound, WE42 for InBound, WE64
Tables referred: TEDE1, TBD52, TBDME
RFC Destination, RFC type:
Transactions: WE20, WE21, SM59
Tables: RFCDES
Code:
Working as ALE IDoc Interface developer for quite some time, I believe this report will be helpful to check relevant technical details during post go-live setup and also to monitor existing configuration.