SAP table TBD52 (Function modules for inbound ALE-EDI)
SAP table TBD52 has 2 primary key fields being MANDT,EVCODE.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
---|---|---|---|---|---|---|---|
MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |
EVCODE | Process code for inbound processing | CHAR | 30 | 0 | TEDE2 | EDI_EVCODE | |
FUNCNAME | Name of function module for inbound IDoc | CHAR | 30 | 0 | TBD51 | FUNCTNNAME | |
MAXRETRIES | Maximum number of repetitions for inbound IDocs | NUMC | 2 | 0 | MAXRETRIES | ||
EVENT_TYPE | Individual input event for further processing | CHAR | 32 | 0 | EVENT_TYPE | ||
MASS_EVENT | Mass input event for further processing | CHAR | 32 | 0 | MASS_EVENT | ||
PACKETOBJT | Object type for IDoc packet | CHAR | 10 | 0 | TOJTB | PACKETOBJT | |
IDOCOBJTYP | Object type for IDocs | CHAR | 10 | 0 | TOJTB | IDOCOBJTYP | |
APPLOBJTYP | Object type for application objects generated | CHAR | 10 | 0 | TOJTB | APPLOBJTYP | |
EVENT_END | Event: Individual input ended | CHAR | 32 | 0 | EVENT_END | ||
APPL_EVENT | Event: Application object to be processed further | CHAR | 32 | 0 | APPL_EVENT | ||
EVENT_SUCCESS | Single Inbound Event for Successful Processing | CHAR | 32 | 0 | EVENT_SUCCESS |
TBD52 foreign key relationships
Table | Field | Check Table | Check Field | |
---|---|---|---|---|
0 TBD52 | APPLOBJTYP | TOJTB | Business object repository: Basic data | NAME |
1 TBD52 | EVCODE | TEDE2 | EDI process types (inbound) | MANDT |
0 TBD52 | FUNCNAME | TBD51 | Attributes of IDoc inbound function modules | FUNCNAME |
1 TBD52 | IDOCOBJTYP | TOJTB | Business object repository: Basic data | NAME |
0 TBD52 | PACKETOBJT | TOJTB | Business object repository: Basic data | NAME |