GRPCRTA_XML_HEADER SAP (Structure for XML Header Data) Structure details
Description: Structure for XML Header Data
Related tables to GRPCRTA_XML_HEADER
Access table GRPCRTA_XML_HEADER
Structure field list including key, data, relationships and ABAP select examples
GRPCRTA_XML_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 for XML Header Data" 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_GRPCRTA_XML_HEADER TYPE GRPCRTA_XML_HEADER.
The GRPCRTA_XML_HEADER table consists of various fields, each holding specific information or linking keys about Structure for XML Header Data data available in SAP. These include HOST_NAME (Application Server), CLIENT (Client), EXECUTION_DATE (Date), EXECUTION_TIME (Time in CHAR Format).. 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 GRPCRTA_XML_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 |
| USER_NAME | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
| HOST_NAME | Application Server | SYHOST | CHAR | 32 | HOST_ID | ||||
| CLIENT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| EXECUTION_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
| EXECUTION_TIME | Time in CHAR Format | TIME | CHAR | 6 | CHAR6 | ||||
| TOTAL_DEFICIENCY_HIGH | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| TOTAL_DEFICIENCY_MEDIUM | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| TOTAL_DEFICIENCY_LOW | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| TOTAL_DEFICIENCY_COUNT | Natural Number | INT4 | INT4 | 10 | INT4 | ||||
| OVERALL_STATUS | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
| CONTROL_ID | Comment | CHAR50 | CHAR | 50 | TEXT50 | ||||
| CONTROL_DESCRIPTION | 0 | ||||||||
| RULE_ID | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
| RULE_DESCRIPTION | Rule Description | GRPCRTA_RLEDESC | CHAR | 132 | GRPCRTA_RLEDESC | ||||
| SCRIPT_TYPE | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
| SCRIPT_TYPE_TEXT | Explanatory short text | DDTEXT | CHAR | 60 | DDTEXT | ||||
| SCRIPT_CATEGORY | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
| SCRIPT_CATEGORY_TEXT | Explanatory short text | DDTEXT | CHAR | 60 | DDTEXT | ||||
| PROCESS_ID | Comment | CHAR50 | CHAR | 50 | TEXT50 | ||||
| PROCESS_NAME | 0 | ||||||||
| SUB_PROCESS_ID | Comment | CHAR50 | CHAR | 50 | TEXT50 | ||||
| SUB_PROCESS_NAME | 0 | ||||||||
| PERIOD_TYPE | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| FREQUENCY | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
| PERIOD | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
| TIMEFRAME_DESC | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
| PERIOD_YEAR | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| FROM_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
| TO_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
| VERSION | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
| SIGNIFICANT_AMOUNT | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
| CURRENCY_KEY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| TARGET_CONNECT_ID | Character field, length 32 | CHAR32 | CHAR | 32 | CHAR32 | ||||
| GRC_CONNECT_ID | Character field, length 32 | CHAR32 | CHAR | 32 | CHAR32 | ||||
| VARIANT_NAME | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
| ORGUNIT_ID | Comment | CHAR50 | CHAR | 50 | TEXT50 | ||||
| ORGUNIT_NAME | 0 | ||||||||
| LANGUAGE | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| OLSP_ID | Character field of length 40 | CHAR40 | CHAR | 40 | CHAR40 | ||||
| OLSP_NAME | 0 | ||||||||
| NO_RECORD | 0 | ||||||||
| MORE_DATA | Flag to indicate more data | GRPCRTA_MORE_DATA | CHAR | 1 | XFELD | ||||
| MAXREC | Maximum No of Records | GRPCRTA_MAX_RECORD | NUMC | 12 | |||||
| TOTAL_ROWS | Total number of records analyzed | GRPCRTA_TOTALROWS | INT4 | 10 | |||||
| RISK_VALUE_REVEL | Risk Value Relevance Indicator | GRPCRTA_RISKVALUERELEVANCE | CHAR | 1 | GRPCRTA_RISKVALUERELEVANCE |
| Key field | Non-key field |
How do I retrieve data from SAP structure GRPCRTA_XML_HEADER using ABAP code?
As GRPCRTA_XML_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 GRPCRTA_XML_HEADER as there is no data to select.How to access SAP table GRPCRTA_XML_HEADER
Within an ECC or HANA version of SAP you can also view further information about GRPCRTA_XML_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