Area Menus :
ALE Folder under Tools in SAP Menu :
Transaction WEDI Transaction SALE
Transaction Code | Table Name | If you want to…………………………………………….. |
---|---|---|
WE30,WE60 | View an Idoc type’s structure and/or documentation | |
WE82 | EDIMSG | Find Idoc types relation with Message types and / or extensions Establish if there is a relevant Idoc Extension |
WE81 | EDIMSGT | View an message types structure description |
BD60 | Find the outbound function module for SMD process |
* Remember that Idocs can also be triggered through transactions and via scheduled programs. * Could also search in transaction SE37 for *MASTERIDOC*<Message Type>*
Transaction Code | Table Name | If you want to………………………………………………………………. |
---|---|---|
SALE | TBDA2 | Check if change pointers are set on globally for the client Check if change pointers are set on for the message. |
SCDO | BDCP,BDCPV | Establish what change document drives the change pointer process |
WE20 | EDP21 | Find Inbound Process Code |
WE42 | TBDBA | Find link between inbound process code and update function. Find which update function is called BAPI process code |
WE57 | Find link between message type/Idoc type and update function | |
SMOD,CMOD | Find if user-exits have been implemented in standard inbound/outbound process |
* Also search code for string ‘userexit’ and ‘call customer-function
Transaction Code | If you want to………………………………. |
---|---|
BD51 | Establish whether call transaction / Direct input has been used |
* This transaction should only be used as a guide, the best method of determining whether call transaction has been used is to scan the update function for the command ‘call transaction’.
Transaction Code | Table Name | If you want to…………………………………………………………. |
---|---|---|
BD64 | TB05/06 | View Distribution Model |
SM58 | View failed tRFC’s |
* Double click on the user name to view the data content of the message and establish ehat message type it is…
Transaction Code | If you want to…………………………………………………………. |
---|---|
WE19 | Idoc Test Tool |
Other SAP related areas, Useful transaction:
SM37 ——————————————————-Job scheduling SCDO—————————————————— change documents sets out which table fields are logged for changes. The change history is stored in table CDHDR and CDPOS. SM35, SHDB———————————————–Batch Input Recording and session management, fundamental to understand ‘call transaction’. SE80——————————————————–ABAP Workbench. SE30——————————————————–Runtime Analysis. SE11, SE16————————————————Data Dictionary and Table contents viewer.
referencia: SDN – http://wiki.sdn.sap.com/wiki/display/ABAP/Useful+Transactions+in+ALE