SMIF_S_QNAME_OUTBOUND_EXT SAP (Matching Interfaces: Qname Outbound - extended) Structure details
Description: Matching Interfaces: Qname Outbound - extended
Related tables to SMIF_S_QNAME_OUTBOUND_EXT
Access table SMIF_S_QNAME_OUTBOUND_EXT
Structure field list including key, data, relationships and ABAP select examples
SMIF_S_QNAME_OUTBOUND_EXT 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 "Matching Interfaces: Qname Outbound - extended" 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_SMIF_S_QNAME_OUTBOUND_EXT TYPE SMIF_S_QNAME_OUTBOUND_EXT.
The SMIF_S_QNAME_OUTBOUND_EXT table consists of various fields, each holding specific information or linking keys about Matching Interfaces: Qname Outbound - extended data available in SAP. These include VERSION (ABAP: Program Status (Active, Saved, Transported...)), KEY_ID1 (Matching Interface: Key-ID), OUTBOUND_QNAME (Matching Interfaces: Outbound Qualified Name), OUTBOUND_QNSPACE (Matching Interfaces: Outbound Qualified Namespace).. 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: Cannot Be Enhanced
SAP SMIF_S_QNAME_OUTBOUND_EXT 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 |
| MATCHING_OBJ | Matching Interfaces: Matching Object | SMIF_MATCHING_OBJ | CHAR | 30 | SMIF_MATCHING_OBJ | ||||
| VERSION | ABAP: Program Status (Active, Saved, Transported...) | R3STATE | CHAR | 1 | R3STATE | ||||
| KEY_ID1 | Matching Interface: Key-ID | SMIF_KEY_ID | NUMC | 10 | SMIF_KEY_ID | ||||
| OUTBOUND_QNAME | Matching Interfaces: Outbound Qualified Name | SMIF_OUTBOUND_QNAME | STRG | 0 | SMIF_STRING | ||||
| OUTBOUND_QNSPACE | Matching Interfaces: Outbound Qualified Namespace | SMIF_OUTBOUND_QNSPACE | STRG | 0 | SMIF_STRING | ||||
| OUTBOUND_HASHKEY | Machting Interfaces: Outbound Hashkey | SMIF_OUTBOUND_HASHKEY | CHAR | 100 | SMIF_HASHKEY |
| Key field | Non-key field |
How do I retrieve data from SAP structure SMIF_S_QNAME_OUTBOUND_EXT using ABAP code?
As SMIF_S_QNAME_OUTBOUND_EXT 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 SMIF_S_QNAME_OUTBOUND_EXT as there is no data to select.How to access SAP table SMIF_S_QNAME_OUTBOUND_EXT
Within an ECC or HANA version of SAP you can also view further information about SMIF_S_QNAME_OUTBOUND_EXT 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