/SDF/IVIS_DC_MESSAGE_XI_731_DB SAP (Copy of XI message data structure) Structure details
Description: Copy of XI message data structure
Related tables to /SDF/IVIS_DC_MESSAGE_XI_731_DB
Access table /SDF/IVIS_DC_MESSAGE_XI_731_DB
Structure field list including key, data, relationships and ABAP select examples
/SDF/IVIS_DC_MESSAGE_XI_731_DB is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Copy of XI message data structure" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_/SDF/IVIS_DC_MESSAGE_XI_731_DB TYPE /SDF/IVIS_DC_MESSAGE_XI_731_DB.
The /SDF/IVIS_DC_MESSAGE_XI_731_DB table consists of various fields, each holding specific information or linking keys about Copy of XI message data structure data available in SAP. These include PID (Integration Engine: Pipeline ID), MSGSTATE (Integration Engine: Message Status), QOSMODE (Integration Engine: Quality of Service), INITTIMEST (UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)).. 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:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)
SAP /SDF/IVIS_DC_MESSAGE_XI_731_DB structure 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 |
MSGGUID | 0 | ||||||||
PID | Integration Engine: Pipeline ID | 0 | |||||||
MSGSTATE | Integration Engine: Message Status | 0 | |||||||
QOSMODE | Integration Engine: Quality of Service | 0 | |||||||
INITTIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
EXETIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
ADAPT_TYP | Pipeline Service Type | 0 | |||||||
ADAPT_TP_I | Pipeline Service Type | 0 | |||||||
PARENTMSG | 0 | ||||||||
QUEUEINT | queuename | 0 | |||||||
ACK_STATE | XI: Acknowledgment Status | 0 | |||||||
OB_PARTY | XI: Communication Party | 0 | |||||||
OB_PARTY_TYPE | XI Partner: Identification Schema | 0 | |||||||
OB_PARTY_AGENCY | XI Partner: Agency | 0 | |||||||
OB_SYSTEM | Sending System | 0 | |||||||
OB_NS | Outbound Interface Namespace | 0 | |||||||
OB_NAME | Outbound Interface Name | 0 | |||||||
OB_OPERATION | Operation of Service Interface | 0 | |||||||
IB_PARTY | XI: Communication Party | 0 | |||||||
IB_PARTY_TYPE | XI Partner: Identification Schema | 0 | |||||||
IB_PARTY_AGENCY | XI Partner: Agency | 0 | |||||||
IB_SYSTEM | Receiving System | 0 | |||||||
IB_NS | Inbound Interface Namespace | 0 | |||||||
IB_NAME | Inbound Interface Name | 0 | |||||||
IB_OPERATION | Operation of Service Interface | 0 | |||||||
ERRCAT | XI: Error Category | 0 | |||||||
ERRCODE | XI: Error ID | 0 | |||||||
ERRLABELID | XI: Status Detail: Identifier | 0 | |||||||
ERRTXT | 0 | ||||||||
MSGTYPE | Integration Engine: Message Type | 0 | |||||||
SENDTIMEST | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
QUEUEGUID | ID for Message Queue | 0 | |||||||
ADAPT_STAT | Integration Engine: Adapter Status | 0 | |||||||
CHILDCOUNT | 0 | ||||||||
CLIENT | Client ID | SYMANDT | CLNT | 3 | Assigned to domain | MANDT | |||
ADMINUSER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
GEN_ENTRY | XMS: Flag (true/false) | 0 | |||||||
RETRYCOUNT | 0 | ||||||||
REST_VERS | Sequence Number for a Message Log ID | 0 | |||||||
REF_TO_MSG | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
REF_TO_REC_MSG | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
REORG | Reorganization Status | 0 | |||||||
VERS | Sequence Number for a Message Log ID | 0 | |||||||
SECURITY | Security Flag | 0 | |||||||
QUEUESTATE | Integration Engine: Queue Status | 0 | |||||||
STATUS_TYPE | XI: Type of a Status | 0 | |||||||
MANUALSTAT | Single-Character Flag | 0 | |||||||
JOB_ID | Job ID | 0 | |||||||
STATUS | Job Processing Status | 0 | |||||||
PERSIST_ID | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
SERVICEDEFINITION | 0 | ||||||||
APPCOMPONENT | Application component ID | UFPS_POSID | CHAR | 24 | UFPS_POSID | ||||
SWCOMPONENT | Software Component | DLVUNIT | CHAR | 30 | Assigned to domain | DLVUNIT | H_CVERS | ||
SEQUENCEID | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
SEQUENCENUMBER | 0 | ||||||||
BUSINESSMSG | XMS: Flag (true/false) | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure /SDF/IVIS_DC_MESSAGE_XI_731_DB using ABAP code?
As /SDF/IVIS_DC_MESSAGE_XI_731_DB is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on /SDF/IVIS_DC_MESSAGE_XI_731_DB as there is no data to select.How to access SAP table /SDF/IVIS_DC_MESSAGE_XI_731_DB
Within an ECC or HANA version of SAP you can also view further information about /SDF/IVIS_DC_MESSAGE_XI_731_DB 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