BTCSELECTP SAP (Powerful job selection criterias) Structure details
Description: Powerful job selection criterias
Structure field list including key, data, relationships and ABAP select examples
BTCSELECTP 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 "Powerful job selection criterias" 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_BTCSELECTP TYPE BTCSELECTP.
The BTCSELECTP table consists of various fields, each holding specific information or linking keys about Powerful job selection criterias data available in SAP. These include JOBNAME (Background job name), USERNAME (Initiator of job/step scheduling), SELFAV (Background job personalized selection), FROM_DATE (Planned Start Date for Background Job).. 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: Not classified
SAP BTCSELECTP 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 |
| JOBNAME | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| USERNAME | Initiator of job/step scheduling | BTCSDLNM | CHAR | 12 | CHAR12 | ||||
| SELFAV | Background job personalized selection | BTCSELFAV | CHAR | 32 | CHAR32 | ||||
| FROM_DATE | Planned Start Date for Background Job | BTCSDATE | DATS | 8 | SYDATS | ||||
| FROM_TIME | Planned start time for background Job | BTCSTIME | TIMS | 6 | SYTIME | ||||
| TO_DATE | Planned Start Date for Background Job | BTCSDATE | DATS | 8 | SYDATS | ||||
| TO_TIME | Planned start time for background Job | BTCSTIME | TIMS | 6 | SYTIME | ||||
| EVENTID | Background Processing Event | BTCEVENTID | CHAR | 32 | CHAR32 | ||||
| JOBID | Background job name | BTCJOB | CHAR | 32 | CHAR32 | ||||
| OPMODEID | Name of Operation Mode | PFEBANAME | CHAR | 20 | TEXT20 | ||||
| F_DATE_E | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| F_TIME_E | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| T_DATE_E | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| T_TIME_E | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| ST_ACTIVE | Active tab signal | BTCACTIVE | CHAR | 1 | CHAR1 | ||||
| EN_ACTIVE | Active tab signal | BTCACTIVE | CHAR | 1 | CHAR1 | ||||
| BE_ACTIVE | Active tab signal | BTCACTIVE | CHAR | 1 | CHAR1 | ||||
| F_DATE_L | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| F_TIME_L | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| T_DATE_L | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| T_TIME_L | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| F_DATE_B | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| F_TIME_B | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| T_DATE_B | Job start date | BTCXDATE | DATS | 8 | SYDATS | ||||
| T_TIME_B | Batch job start time | BTCXTIME | TIMS | 6 | SYTIME | ||||
| PRELIM | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| SCHEDUL | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| READY | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| RUNNING | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| FINISHED | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| ABORTED | State of Background Job | BTCSTATUS | CHAR | 1 | CHAR1 | ||||
| DONTCARE | selection flag for selection of periodical jobs | BTCPERIOD | CHAR | 1 | CHAR1 | ||||
| PERIOD | selection flag for selection of periodical jobs | BTCPERIOD | CHAR | 1 | CHAR1 | ||||
| NON_PERD | selection flag for selection of periodical jobs | BTCPERIOD | CHAR | 1 | CHAR1 | ||||
| NRMONTHS | Duration period (in months) for a batch job | BTCPMNTH | NUMC | 2 | NUM02 | ||||
| NRWEEKS | Duration period (in weeks) for a batch job | BTCPWEEK | NUMC | 2 | NUM02 | ||||
| NRDAYS | Duration (in days) of DBA action | BTCPDAY | NUMC | 3 | NUM03 | ||||
| NRHOURS | Duration period (in hours) for a batch job | BTCPHOUR | NUMC | 2 | NUM02 | ||||
| NRMINUTES | Duration period (in minutes) for a batch job | BTCPMIN | NUMC | 2 | NUM02 | ||||
| ABAPNAME | ABAP Program Name | PROGNAME | CHAR | 40 | PROGNAME | ||||
| EXTPROG | Name of external program (possibly with access path) | BTCXPGPGM | CHAR | 128 | TEXT128 | ||||
| EXTCMD | Logical command name | SXPGLOGCMD | CHAR | 18 | CHAR18 | ||||
| AUTHCKNAM | Background User Name for Authorization Check | BTCAUTHNAM | CHAR | 12 | CHAR12 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BTCSELECTP using ABAP code?
As BTCSELECTP 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 BTCSELECTP as there is no data to select.How to access SAP table BTCSELECTP
Within an ECC or HANA version of SAP you can also view further information about BTCSELECTP 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