GRPCRBTC_REPORTS_DISPLAY SAP (Display Table FOPC_BTC_REPORTS) Structure details
Description: Display Table FOPC_BTC_REPORTS
Related tables to GRPCRBTC_REPORTS_DISPLAY
Access table GRPCRBTC_REPORTS_DISPLAY
Structure field list including key, data, relationships and ABAP select examples
GRPCRBTC_REPORTS_DISPLAY 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 "Display Table FOPC_BTC_REPORTS" 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_GRPCRBTC_REPORTS_DISPLAY TYPE GRPCRBTC_REPORTS_DISPLAY.
The GRPCRBTC_REPORTS_DISPLAY table consists of various fields, each holding specific information or linking keys about Display Table FOPC_BTC_REPORTS data available in SAP. These include TRAFFIC_LIGHT (Single-Character Indicator), LINE_COLOR (Not More Closely Defined Area, Possibly Used for Patchlevels), STATE_TXT (Char 20), REPORT_TYPE_TXT (Char 20).. 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 GRPCRBTC_REPORTS_DISPLAY 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 |
CHANGE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
TRAFFIC_LIGHT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
LINE_COLOR | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
STATE_TXT | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
REPORT_TYPE_TXT | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
CREATE_TIME_TXT | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
START_TIME_TXT | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
REPORT_KIND_TXT | Char 20 | CHAR20 | CHAR | 20 | CHAR20 | ||||
WF_EXISTS | New Input Values | XFLAG | CHAR | 1 | XFLAG | ||||
WF_EXISTS_ICON | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
REPORT_INPUT_SIZE | Size (KB) | DDSIZED | DEC | 15 | DEC15 | ||||
REPORT_OUTPUT_SIZE | Size (KB) | DDSIZED | DEC | 15 | DEC15 | ||||
REPORT_PRINT_SIZE | Size (KB) | DDSIZED | DEC | 15 | DEC15 | ||||
IN_HASH_STATUS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
IN_HASH_ICON | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
OUT_HASH_STATUS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
OUT_HASH_ICON | Not More Closely Defined Area, Possibly Used for Patchlevels | CHAR4 | CHAR | 4 | CHAR4 | ||||
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
REPORT_GUID | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
STATE | Status of Requested Report | GRPC_BTC_REPORT_STATE | CHAR | 1 | GRPC_BTC_REPORT_STATE | ||||
SEND_WORKFLOW | Send Work Item | GRPC_BTC_SEND_WORKFLOW_FLAG | CHAR | 1 | GRPC_BTC_SEND_WORKFLOW_FLAG | ||||
CREATE_USER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
CREATE_TIME | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
START_USER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
START_TIME | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
END_TIME | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
REPORT_MIC_USER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
REPORT_TYPE | Report Type | GRPC_REP_TYPE | CHAR | 3 | GRPC_REP_TYPE | ||||
BTC_JOBNAME | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
BTC_JOBCOUNT | Job ID | BTCJOBCNT | CHAR | 8 | CHAR8 | ||||
BTC_STARTOPTIONS | 0 | ||||||||
REPORT_INPUT | MIC Report Input, Serialzied Type fopcr_s_report_input | 0 | |||||||
REPORT_OUTPUT | MIC Report Output, Serialzied Type fopcr_s_report_output | 0 | |||||||
IN_STRUCT_HASH | Hash Value (160 Bits) | HASH160 | CHAR | 40 | |||||
OUT_STRUCT_HASH | Hash Value (160 Bits) | HASH160 | CHAR | 40 | |||||
ATTACHMENT_TYPE | Requested Report: Document Type | GRPC_BTC_ATTACHMENT_TYPE | CHAR | 10 | GRPC_BTC_ATTACHMENT_TYPE | ||||
ATTACHMENT_IOTY | KW Framework: IO type | SKWF_IOTY | CHAR | 1 | SKWF_IOTY | ||||
ATTACHMENT_CLASS | Document class | SDOK_CLASS | CHAR | 10 | Assigned to domain | SDOK_CLASS | |||
ATTACHMENT_ID | ID for documents and relations | SDOK_DOCID | CHAR | 32 | SDOK_DOCID | ||||
WRKFLW_RECIPIENT | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
BTC_REPORT_KIND | Type of Requested Report | GRPC_BTC_REPORT_KIND | CHAR | 1 | GRPC_BTC_REPORT_KIND | ||||
BTC_DATASHEET_ID | GRPC ID of the individual object | GRPC_API_OBJECT_ID | CHAR | 50 | GRPC_API_OBJECT_ID |
Key field | Non-key field |
How do I retrieve data from SAP structure GRPCRBTC_REPORTS_DISPLAY using ABAP code?
As GRPCRBTC_REPORTS_DISPLAY 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 GRPCRBTC_REPORTS_DISPLAY as there is no data to select.How to access SAP table GRPCRBTC_REPORTS_DISPLAY
Within an ECC or HANA version of SAP you can also view further information about GRPCRBTC_REPORTS_DISPLAY 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