FOPC_BTC_REPORTS SAP (Background Reports in System) Table details
Dictionary Type: Table
Description: Background Reports in System
Description: Background Reports in System
ABAP Code to SELECT data from FOPC_BTC_REPORTS
Related tables to FOPC_BTC_REPORTS
Access table FOPC_BTC_REPORTS
Related tables to FOPC_BTC_REPORTS
Access table FOPC_BTC_REPORTS
Table field list including key, data, relationships and ABAP select examples
FOPC_BTC_REPORTS is a standard SAP Table which is used to store Background Reports in System data and is available within R/3 SAP systems depending on the version and release level.
The FOPC_BTC_REPORTS table consists of various fields, each holding specific information or linking keys about Background Reports in System data available in SAP. These include REPORT_GUID (GUID in 'CHAR' Format in Uppercase), STATE (Status of Requested Report), SEND_WORKFLOW (Send Work Item), CREATE_USER (User Name).. 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: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can Be Enhanced (Deep)
SAP FOPC_BTC_REPORTS table 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 | |||
| REPORT_GUID | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
| STATE | Status of Requested Report | FOPC_BTC_REPORT_STATE | CHAR | 1 | FOPC_BTC_REPORT_STATE | ||||
| SEND_WORKFLOW | Send Work Item | FOPC_BTC_SEND_WORKFLOW_FLAG | CHAR | 1 | FOPC_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 | FOPC_REP_TYPE | CHAR | 3 | FOPC_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 | FOPC_BTC_ATTACHMENT_TYPE | CHAR | 10 | FOPC_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 | FOPC_BTC_REPORT_KIND | CHAR | 1 | FOPC_BTC_REPORT_KIND |
| Key field | Non-key field |
How do I retrieve data from SAP table FOPC_BTC_REPORTS using ABAP code
The following ABAP code Example will allow you to do a basic selection on FOPC_BTC_REPORTS to SELECT all data from the tableDATA: WA_FOPC_BTC_REPORTS TYPE FOPC_BTC_REPORTS.
SELECT SINGLE *
FROM FOPC_BTC_REPORTS
INTO CORRESPONDING FIELDS OF WA_FOPC_BTC_REPORTS
WHERE...
How to access SAP table FOPC_BTC_REPORTS
Within an ECC or HANA version of SAP you can also view further information about FOPC_BTC_REPORTS 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