EDX_OUTBOUND SAP (EDX: Outbound Messages (Messages Ready to Be Sent)) Table details
Dictionary Type: Table
Description: EDX: Outbound Messages (Messages Ready to Be Sent)
Description: EDX: Outbound Messages (Messages Ready to Be Sent)
Table field list including key, data, relationships and ABAP select examples
EDX_OUTBOUND is a standard SAP Table which is used to store EDX: Outbound Messages (Messages Ready to Be Sent) data and is available within R/3 SAP systems depending on the version and release level.
The EDX_OUTBOUND table consists of various fields, each holding specific information or linking keys about EDX: Outbound Messages (Messages Ready to Be Sent) data available in SAP. These include BELNR (EDX: Document Number), CHANGE_COUNTER (EDX: Change Counter for Purchase Order Changes), DOC_TYPE_OUT (Outgoing Message Type), BUKRS (Company Code).. 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_OUTBOUND 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 | |||
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_OUT | Outgoing Message Type | EDX_DOC_TYPE_OUT | CHAR | 3 | EDX_DOC_TYPE_OUT | ||||
BUKRS | Company Code | EDX_BUKRS | CHAR | 4 | T001 | BUKRS | |||
IDOC_NUMBER | EDX: IDoc Number for This Message | EDX_IDOC_NUMBER | NUMC | 16 | EDI_DOCNUM | ||||
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 | |||
CREATION_DATE | EDX: Date Message Created | EDX_CREAT_DATE | DATS | 8 | |||||
CREATION_TIME | EDX: Time Message Created | EDX_CREAT_TIME | TIMS | 6 | |||||
STATUS | EDX: Message Status | EDX_STATUS | CHAR | 2 | EDX_STATUS | ||||
SEND_DATE | Send Date of Message | EDX_SEND_DATE | DATS | 8 | |||||
SEND_TIME | EDX: Time Message Sent | EDX_SEND_TIME | TIMS | 6 | |||||
ERRTEXT | EDX: Description of Message Processing Error | EDX_ERR_TEXT | CHAR | 255 | |||||
ARCHIVED | EDX: Archiving Identification | EDX_ARCHIVE_FLAG | CHAR | 1 | XFELD | ||||
KEYPP | EDX: End Digit for Parallel Processing | EDX_KEYPP | CHAR | 1 | CHAR1 | ||||
SHIPMENT_ID | EDX: Shipment Identification | EDX_SHIPMENT_ID | CHAR | 50 | EDX_SHIPMENT_ID |
Key field | Non-key field |
How do I retrieve data from SAP table EDX_OUTBOUND using ABAP code
The following ABAP code Example will allow you to do a basic selection on EDX_OUTBOUND to SELECT all data from the tableDATA: WA_EDX_OUTBOUND TYPE EDX_OUTBOUND.
SELECT SINGLE *
FROM EDX_OUTBOUND
INTO CORRESPONDING FIELDS OF WA_EDX_OUTBOUND
WHERE...
How to access SAP table EDX_OUTBOUND
Within an ECC or HANA version of SAP you can also view further information about EDX_OUTBOUND 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