N2COMM_LOG_HEADER SAP (Structure: Status Record for Received Document) Structure details
Dictionary Type: Structure
Description: Structure: Status Record for Received Document
Description: Structure: Status Record for Received Document
ABAP Code to SELECT data from N2COMM_LOG_HEADER
Related tables to N2COMM_LOG_HEADER
Access table N2COMM_LOG_HEADER
Related tables to N2COMM_LOG_HEADER
Access table N2COMM_LOG_HEADER
Structure field list including key, data, relationships and ABAP select examples
N2COMM_LOG_HEADER 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 "Structure: Status Record for Received Document" 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_N2COMM_LOG_HEADER TYPE N2COMM_LOG_HEADER.
The N2COMM_LOG_HEADER table consists of various fields, each holding specific information or linking keys about Structure: Status Record for Received Document data available in SAP. These include TEMP_KEY (Key of Entry in Communication Log), DISPATCH_REQUEST (Dispatch Order ID), DIRECTION (Direction of Communication), DIRECTION_ICON (Transmission Direction (Icon+Tooltip)).. 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 N2COMM_LOG_HEADER 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| TEMP_KEY | Key of Entry in Communication Log | N2COM_KEY | CHAR | 32 | SYSUUID_C | ||||
| DISPATCH_REQUEST | Dispatch Order ID | N2_MV_DISPATCH_REQUEST | CHAR | 32 | SYSUUID_C | ||||
| DIRECTION | Direction of Communication | N2COM_DIRECTION | CHAR | 3 | N2COM_DIRECTION | ||||
| DIRECTION_ICON | Transmission Direction (Icon+Tooltip) | N2COM_DIR_ICON | STRG | 0 | |||||
| TYPE | Entry Type | N2COM_LOG_TYPE | CHAR | 15 | N2COM_LOG_TYPE | ||||
| IS_RESPONSE | Flag: Is the message a response? | N2COM_LOG_ISRESPONSE | CHAR | 1 | N2COM_LOG_ISRESPONSE | ||||
| STORE_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
| STORE_TIME | Time | UZEIT | TIMS | 6 | UZEIT | ||||
| SENDR_INST | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| SENDR_INSTNAME | Name of Institution | EINBZ | CHAR | 50 | TEXT50 | ||||
| SENDR_WARD | Identification Key of Organizational Unit | ORGID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
| SENDR_WARDNAME | IS-H: Organizational Unit Name | ORGNA | CHAR | 30 | TEXT30 | ||||
| SENDR_PERS_ID | Employee Responsible | N1MITARB | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | VMA | |
| SENDR_PERS_NAME | IS-H: Last Name/ 1st Name | GPNAM1 | CHAR | 35 | NAME | NA1 | |||
| SENDR_PERS_FNAME | First Name / Second Name | GPNAM2 | CHAR | 35 | NAME | ||||
| SENDR_PERS_TITLE | IS-H: Title | RI_TITEL | CHAR | 15 | Assigned to domain | TITEL | |||
| RECPT_WARD | Identification Key of Organizational Unit | ORGID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
| RECPT_PERS_ID | Employee Responsible | N1MITARB | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | VMA | |
| RECPT_PERS_NAME | IS-H: Last Name/ 1st Name | GPNAM1 | CHAR | 35 | NAME | NA1 | |||
| RECPT_PERS_FNAME | First Name / Second Name | GPNAM2 | CHAR | 35 | NAME | ||||
| RECPT_PERS_TITLE | IS-H: Title | RI_TITEL | CHAR | 15 | Assigned to domain | TITEL | |||
| PAT_NAME | IS-H: Last Name/ 1st Name | GPNAM1 | CHAR | 35 | NAME | NA1 | |||
| PAT_FNAME | First Name / Second Name | GPNAM2 | CHAR | 35 | NAME | ||||
| PAT_TITLE | IS-H: Title | RI_TITEL | CHAR | 15 | Assigned to domain | TITEL | |||
| SENDR_PERS_NAME_COMPLETE | Person Sending Document: Complete Name | N2COMM_SENDR_PERS_NAME_DIS | SSTR | 255 | |||||
| SENDR_WARD_NAME_COMPLETE | Care Unit Sending Document: Complete Name | N2COMM_SENDR_WARD_NAME_DIS | SSTR | 255 | |||||
| SENDR_INST_NAME_COMPLETE | Institution Sending Document: Complete Name | N2COMM_SENDR_INST_NAME_DIS | SSTR | 255 | |||||
| RECPT_PERS_NAME_COMPLETE | Person Receiving Document: Complete Name | N2COMM_RECPT_PERS_NAME_DIS | SSTR | 255 | |||||
| RECPT_WARD_NAME_COMPLETE | Care Unit Receiving Document: Complete Name | N2COMM_RECPT_WARD_NAME_DIS | SSTR | 255 | |||||
| RECPT_PAT_NAME_COMPLETE | Document Reception: Patient Name Display Field | N2COMM_PAT_NAME_DIS | SSTR | 255 | |||||
| EXT_KEY | External Key of a Transferred Object | N2COM_EXTKEY | CHAR | 120 | N2COM_EXTKEY | ||||
| EXT_VR | Version of Dispatch Object Used in Partner System | N2COM_EXTVR | CHAR | 5 | |||||
| OBJ_KEY | Internal Key of a Transferred Object | N2COM_INTKEY | CHAR | 120 | N2COM_INTKEY | ||||
| OBJ_VR | Internal Version of Dispatched Object | N2COM_INTVR | CHAR | 5 | |||||
| PARTNER_SYS | ID of a Communication Partner (Display Field in Log) | N2COM_LOG_PARTID | SSTR | 255 | |||||
| INST | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| STATUS | Dispatch Status ID | N2COM_LOG_STATUS | CHAR | 15 | Assigned to domain | N2COM_LOG_STATUS | N2COM_LOG_STATUS | ||
| STATUS_TYPE | Status Type in Dispatch Log | N2COM_LOG_STATTYPE | CHAR | 1 | N2COM_LOG_STATTYPE | ||||
| STATUS_ICON | ICON and Quick Info Transmission Status | N2COM_STAT_ICON | STRG | 0 | |||||
| STATUS_TXT | Status Text | STATUS_ICON_TXT | CHAR | 60 | CHAR60 | ||||
| REF_TEMP_KEY | Key of Entry in Communication Log | N2COM_KEY | CHAR | 32 | SYSUUID_C | ||||
| HAS_NOTE | Flag: Does processing procedure log exist? | N2COM_HAS_NOTE | CHAR | 1 | FLAG | ||||
| HAS_NOTE_ICON | Does a transmission log exist? | N2COM_NOTEICON | STRG | 0 | |||||
| HAS_MORE_INFO | Additional Info for Doc Dispatch (e.g. About Sender) Exists? | N2COM_HAS_MORE_INFO | CHAR | 1 | FLAG | ||||
| MORE_INFO_ICON | Is further communication information available? | N2COM_MOREINFO_ICON | STRG | 0 | |||||
| STORE_USER | User Name | UNAME | CHAR | 12 | UNAME | ||||
| MIME_TYPE | MIME Type | N2MIME | CHAR | 50 | Assigned to domain | N2MIME |
| Key field | Non-key field |
How do I retrieve data from SAP structure N2COMM_LOG_HEADER using ABAP code?
As N2COMM_LOG_HEADER 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 N2COMM_LOG_HEADER as there is no data to select.How to access SAP table N2COMM_LOG_HEADER
Within an ECC or HANA version of SAP you can also view further information about N2COMM_LOG_HEADER 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