EDX_INBOUND SAP (EDX: Inbound Messages (Processed Messages)) Table details
Description: EDX: Inbound Messages (Processed Messages)
Table field list including key, data, relationships and ABAP select examples
EDX_INBOUND is a standard SAP Table which is used to store EDX: Inbound Messages (Processed Messages) data and is available within R/3 SAP systems depending on the version and release level.
The EDX_INBOUND table consists of various fields, each holding specific information or linking keys about EDX: Inbound Messages (Processed Messages) data available in SAP. These include SENDER_PID (EDX: Sender Identifier at Service Provider), BELNR (EDX: Document Number), CHANGE_COUNTER (EDX: Change Counter for Purchase Order Changes), DOC_TYPE_IN (Incoming Message Type).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP EDX_INBOUND table fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| SENDER_PID | EDX: Sender Identifier at Service Provider | EDX_SENDER_PID | CHAR | 17 | ALPHA | EDX_PID | |||
| BELNR | EDX: Document Number | EDX_BELNR | CHAR | 35 | EDX_BELNR | ||||
| CHANGE_COUNTER | EDX: Change Counter for Purchase Order Changes | EDX_MSGCHG_COUNTER | INT2 | 5 | INT2 | ||||
| DOC_TYPE_IN | Incoming Message Type | EDX_DOC_TYPE_IN | CHAR | 3 | EDX_DOC_TYPE_IN | ||||
| BUKRS | Company Code | EDX_BUKRS | CHAR | 4 | Assigned to domain | BUKRS | |||
| BP_NR | EDX: Customer/Vendor Number of Business Partner | EDX_BP_NR | CHAR | 10 | ALPHA | EDX_BP_NR | |||
| BP_TYPE | EDX: Type of Business Partner | EDX_BP_TYPE | CHAR | 2 | Assigned to domain | EDI_RCVPRT | |||
| IDOC_NUMBER | EDX: IDoc Number for This Message | EDX_IDOC_NUMBER | NUMC | 16 | EDI_DOCNUM | ||||
| TOTAL_AMOUNT | EDX: Amount | EDX_AMOUNT | CHAR | 18 | CHAR18 | ||||
| CURRENCY | EDX: Currency | EDX_CURRENCY | CUKY | 5 | |||||
| RCV_DATE | EDX: Date Received | EDX_RCV_DATE | DATS | 8 | |||||
| RCV_TIME | EDX: Time Received | EDX_RCV_TIME | TIMS | 6 | |||||
| PROCESS_DATE | EDX: Processing Date | EDX_PROCESS_DATE | DATS | 8 | |||||
| PROCESS_TIME | EDX: Processing Time | EDX_PROCESS_TIME | TIMS | 6 | |||||
| INVOICE_DATE | EDX: Invoice Date | EDX_INVOICE_DATE | DATS | 8 | |||||
| ORDER_DATE | EDX: Purchase Order Date | EDX_ORDER_DATE | DATS | 8 | |||||
| INVOICE_TYPE | EDX: Billing Category | EDX_INV_TYPE | CHAR | 3 | EDX_INV_TYPE | ||||
| REL_DOC_TYPE_IN | Incoming Message Type | EDX_DOC_TYPE_IN | CHAR | 3 | EDX_DOC_TYPE_IN | ||||
| REL_BELNR | EDX: Document Number | EDX_BELNR | CHAR | 35 | EDX_BELNR |
| Key field | Non-key field |
How do I retrieve data from SAP table EDX_INBOUND using ABAP code
The following ABAP code Example will allow you to do a basic selection on EDX_INBOUND to SELECT all data from the tableDATA: WA_EDX_INBOUND TYPE EDX_INBOUND.
SELECT SINGLE *
FROM EDX_INBOUND
INTO CORRESPONDING FIELDS OF WA_EDX_INBOUND
WHERE...
How to access SAP table EDX_INBOUND
Within an ECC or HANA version of SAP you can also view further information about EDX_INBOUND and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects