TMSJOBLOG SAP (TMS: Job Log Information) Structure details
Description: TMS: Job Log Information
Structure field list including key, data, relationships and ABAP select examples
TMSJOBLOG 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 "TMS: Job Log Information" 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_TMSJOBLOG TYPE TMSJOBLOG.
The TMSJOBLOG table consists of various fields, each holding specific information or linking keys about TMS: Job Log Information data available in SAP. These include SYSNAME (TMS: System Name), TMSJOB (), JOBNAME (Background job name), JOBCOUNT (Background job number).. 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 TMSJOBLOG 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 |
DOMNAME | TMS: Transport Domain | TMSDOMNAM | CHAR | 10 | Assigned to domain | TMSDOMNAM | |||
SYSNAME | TMS: System Name | TMSSYSNAM | CHAR | 10 | SYSNAME | ||||
TMSJOB | 0 | ||||||||
JOBNAME | Background job name | 0 | |||||||
JOBCOUNT | Background job number | 0 | |||||||
JOBGROUP | Summary of jobs for a group | 0 | |||||||
INTREPORT | Name of internal report for batch job | 0 | |||||||
STEPCOUNT | Job step ID number. | 0 | |||||||
SDLSTRTDT | Planned Start Date for Background Job | 0 | |||||||
SDLSTRTTM | Planned start time for background Job | 0 | |||||||
BTCSYSTEM | Target system to run background job | 0 | |||||||
SDLDATE | Date of job/step scheduling | 0 | |||||||
SDLTIME | Time of a scheduled job/step | 0 | |||||||
SDLUNAME | Initiator of job/step scheduling | 0 | |||||||
LASTCHDATE | Date of last job change | 0 | |||||||
LASTCHTIME | Time of last job change | 0 | |||||||
LASTCHNAME | Last job change made by | 0 | |||||||
RELDATE | Release date for background schedule | 0 | |||||||
RELTIME | Release time of scheduled background job | 0 | |||||||
RELUNAME | User that released scheduled batch job | 0 | |||||||
STRTDATE | Job start date | 0 | |||||||
STRTTIME | Batch job start time | 0 | |||||||
ENDDATE | Job start date | 0 | |||||||
ENDTIME | Batch job start time | 0 | |||||||
PRDMINS | Duration period (in minutes) for a batch job | 0 | |||||||
PRDHOURS | Duration period (in hours) for a batch job | 0 | |||||||
PRDDAYS | Duration (in Days) of Batch Job | 0 | |||||||
PRDWEEKS | Duration period (in weeks) for a batch job | 0 | |||||||
PRDMONTHS | Duration period (in months) for a batch job | 0 | |||||||
PERIODIC | Periodic jobs indicator ('X') | 0 | |||||||
DELANFREP | Job deletion indicator after processing | 0 | |||||||
EMERGMODE | Emergency Job operation indicator (content 'X') | 0 | |||||||
STATUS | State of Background Job | 0 | |||||||
NEWFLAG | New job ID creation flag | 0 | |||||||
AUTHCKNAM | Background user name for authorization check | 0 | |||||||
AUTHCKMAN | Background client for authorization check | 0 | |||||||
SUCCNUM | Number of subsequent job(s) | 0 | |||||||
PREDNUM | Number of previous jobs | 0 | |||||||
JOBLOG | TemSe object name | 0 | |||||||
LASTSTRTDT | Latest run date for batch job | 0 | |||||||
LASTSTRTTM | Latest run time for batch job | 0 | |||||||
WPNUMBER | Work process number | 0 | |||||||
WPPROCID | Work process ID | 0 | |||||||
EVENTID | Background processing event | 0 | |||||||
EVENTPARM | Background event parameters (e.g. Jobname/Jobcount) | 0 | |||||||
BTCSYSREAX | Target system to run background job | 0 | |||||||
JOBCLASS | Job classification | 0 | |||||||
PRIORITY | Job priority | 0 | |||||||
EVENTCOUNT | Event number | 0 | |||||||
CHECKSTAT | Job status check indicator for subsequent job start | 0 | |||||||
CALENDARID | Factory calendar ID for background processing | 0 | |||||||
PRDBEHAV | Period behavior of jobs on non-workdays | 0 | |||||||
EXECSERVER | Server name | 0 | |||||||
EOMCORRECT | Correction field for calc. job execution (end-of-mth, cal.) | 0 | |||||||
CALCORRECT | Correction field for calc. job execution (end-of-mth, cal.) | 0 | |||||||
REAXSERVER | Server name | 0 | |||||||
RECLOGSYS | Logical system | 0 | |||||||
RECOBJTYPE | Object type | 0 | |||||||
RECOBJKEY | Object key | 0 | |||||||
RECDESCRIB | Describe flag | 0 | |||||||
JOBLOG | TemSe object name | 0 | |||||||
SELJOBS | 0 | ||||||||
OK_CODE | GUI Status | SYPFKEY | CHAR | 20 | GUI_STATUS |
Key field | Non-key field |
How do I retrieve data from SAP structure TMSJOBLOG using ABAP code?
As TMSJOBLOG 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 TMSJOBLOG as there is no data to select.How to access SAP table TMSJOBLOG
Within an ECC or HANA version of SAP you can also view further information about TMSJOBLOG 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