/SOMO/JOSCHEDLDSP SAP () Structure details
Dictionary Type: Structure
Description:
Description:
ABAP Code to SELECT data from /SOMO/JOSCHEDLDSP
Related tables to /SOMO/JOSCHEDLDSP
Access table /SOMO/JOSCHEDLDSP
Related tables to /SOMO/JOSCHEDLDSP
Access table /SOMO/JOSCHEDLDSP
Structure field list including key, data, relationships and ABAP select examples
/SOMO/JOSCHEDLDSP 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 "" 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_/SOMO/JOSCHEDLDSP TYPE /SOMO/JOSCHEDLDSP.
The /SOMO/JOSCHEDLDSP table consists of various fields, each holding specific information or linking keys about data available in SAP. These include SOLUTION (), SID (), JOBMONID (), PCOUNTER ().. 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 /SOMO/JOSCHEDLDSP 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 |
| SOLUTION | 0 | ||||||||
| SID | 0 | ||||||||
| JOBMONID | 0 | ||||||||
| PCOUNTER | 0 | ||||||||
| JCOUNTER | 0 | ||||||||
| STEPCOUNT | 0 | ||||||||
| SCHEDULEDATE | 0 | ||||||||
| CLIENT | 0 | ||||||||
| EXECUSER | 0 | ||||||||
| JOBNAME | 0 | ||||||||
| JOBCOUNT | 0 | ||||||||
| JOBMONSTAT | 0 | ||||||||
| PROGNAME | 0 | ||||||||
| VARIANT | 0 | ||||||||
| XPGPROG | 0 | ||||||||
| XPGPARAMS | 0 | ||||||||
| PREC_JOBNAME | 0 | ||||||||
| EVENTID | 0 | ||||||||
| EVENTPARM | 0 | ||||||||
| SDLSTRTTM | 0 | ||||||||
| STRTDATE | 0 | ||||||||
| STRTTIME | 0 | ||||||||
| STATUS | 0 | ||||||||
| ENDDATE | 0 | ||||||||
| ENDTIME | 0 | ||||||||
| SENDDATE | 0 | ||||||||
| SENDTIME | 0 | ||||||||
| DURATION | 0 | ||||||||
| BPROCESSOBJNO | 0 | ||||||||
| BPROCSTEPOBJNO | 0 | ||||||||
| PARAPROC | 0 | ||||||||
| NUMPARAJOB | 0 | ||||||||
| JOBLOGANA | 0 | ||||||||
| PTIMEWINS | 0 | ||||||||
| PTIMEWINE | 0 | ||||||||
| JOBLOG | 0 | ||||||||
| CRITICAL | 0 | ||||||||
| STARTDELAY | 0 | ||||||||
| ENDDELAY | 0 | ||||||||
| ANUMPARAJOB | 0 | ||||||||
| CHGTIME | 0 | ||||||||
| CHGDATE | 0 | ||||||||
| CHGALERT | 0 | ||||||||
| ALERTDELAY | 0 | ||||||||
| DELAYMSGNO | 0 | ||||||||
| ALERTWINDOW | 0 | ||||||||
| WINDOWMSGNO | 0 | ||||||||
| ALERTDELEND | 0 | ||||||||
| DELENDMSGNO | 0 | ||||||||
| ALERTDURATION | 0 | ||||||||
| DURATIONMSGNO | 0 | ||||||||
| ALERTSTATUS | 0 | ||||||||
| STATUSMSGNO | 0 | ||||||||
| ALERTPARA | 0 | ||||||||
| PARAMSGNO | 0 | ||||||||
| ALERTLOG | 0 | ||||||||
| ALERTNOTSTARTED | Alert Job not started | 0 | |||||||
| CUSSTRTTM | Customizing start time | 0 | |||||||
| STARTDELAYTECH | Technical start delay | 0 | |||||||
| EXTFLAG | Flag for external scheduled jobs | 0 | |||||||
| MSG1COUNTER | Counter 1 for certain message variables | 0 | |||||||
| MSG2COUNTER | Counter 2 for certain message variables | 0 | |||||||
| MSG3COUNTER | Counter 3 for certain message variables | 0 | |||||||
| NAM_RULE | Rule for custom jobname determination | 0 | |||||||
| CHKTIMNOTSTARTED | Checktime for job not started alerttype | 0 | |||||||
| ALERTJOBACTIVE | Alert Job active | 0 | |||||||
| JOBACTIVEMSGNO | Message number of alert type job active | 0 | |||||||
| NOTACTIVETIME | Time job not active in minutes | 0 | |||||||
| LASTJOBNAME | Name of previous job - used for job active alert type | 0 | |||||||
| LASTJOBCOUNT | Job count of previous job - used for job active alert type | 0 | |||||||
| LASTSTATUS | Job status of previous job - used for job active alert type | 0 | |||||||
| LASTENDDATE | Job end date of previous job - used for job active alert typ | 0 | |||||||
| LASTENDTIME | Job end time of previous job - used for job active alert typ | 0 | |||||||
| SIDLONG | Name of SAP System | SYSYSID | CHAR | 8 | SYCHAR08 | ||||
| JOBTYPE | Type of job space, BH, BE, JH, JE | 0 | |||||||
| RJOBMONID | Reference Job Monid | 0 | |||||||
| CHAIN_ID | BW Chain ID | 0 | |||||||
| TYPE | BW Process Type | 0 | |||||||
| VARIANTE | BW Chain Variante | 0 | |||||||
| LOG_ID | Log Id BW Process Chain | 0 | |||||||
| REC_SEND | Number of records send (e.g. by BW process chain) | 0 | |||||||
| REC_INSR | Number of records inserted (e.g. by BW process chain) | 0 | |||||||
| ARECPROC | Alert records processed | 0 | |||||||
| RECPROCMSGO | Alert message records processed | 0 | |||||||
| PROCSTATUS | Processing status (e.g. by BW process chain / element) | 0 | |||||||
| AFAILSTAT | Alert failed process status | 0 | |||||||
| FAILSTATMSGNO | Alert message failed process status | 0 | |||||||
| INFO_PKG | Number of info packages processed | 0 | |||||||
| AINFOREC | Alert info packages processed | 0 | |||||||
| INFORECMSGO | Alert message info packages processed | 0 | |||||||
| LASTMONDATE | Last monitoring date for the job | 0 | |||||||
| ALERTTYPELEVEL | Indicator if an alert type is selected for Job or job step | 0 | |||||||
| STRTDATESTEP | Start date of job step aoccording to job log | 0 | |||||||
| STRTTIMESTEP | Start time of job step aoccording to job log | 0 | |||||||
| STATUSSTEP | Job step status according to job log | 0 | |||||||
| ENDDATESTEP | End date of job step aoccording to job log | 0 | |||||||
| ENDTIMESTEP | End time of job step aoccording to job log | 0 | |||||||
| CHGALERT2 | Log key for alert changes | 0 | |||||||
| BPROCOBJDSCR_LONG | 0 | ||||||||
| BPROCOBJDSCR_SHRT | 0 | ||||||||
| BPROCSTPDSCR_LONG | 0 | ||||||||
| BPROCSTPDSCR_SHRT | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure /SOMO/JOSCHEDLDSP using ABAP code?
As /SOMO/JOSCHEDLDSP 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 /SOMO/JOSCHEDLDSP as there is no data to select.How to access SAP table /SOMO/JOSCHEDLDSP
Within an ECC or HANA version of SAP you can also view further information about /SOMO/JOSCHEDLDSP 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