Batch Monitor -- Transaction Code?
Answers were Sorted based on User's Feedback
Answer / vickrant thakur
Transaction code SM37 is to monitor the background, batch jobs running in the system. From the initial screen, you can search by the job name, user name or program name accordingly with the time condition.
Note
• Planned - Job already been defined, but the start condition has not yet been defined.
• Released - The job has been fully defined, including a start condition.
• Ready - The start condition of a released job has been met. A job scheduler has put the job in line to wait for an available background work process.
• Active - The job is currently running. Active jobs can no longer be modified or deleted.
• Finished - All steps that make up this job have completed successfully.
• Canceled - The job has terminated. This can happen in two ways:
- An administrator intentionally terminates the job
- A job step contains a program that produces an error, such as:
* an E or A error message in an ABAP program
* a failure return code from an external SAPXPG program
Is This Answer Correct ? | 0 Yes | 0 No |
1.why dont use top of page. wat is the use?
What does an exec sql statement do in abap? What is the disadvantage of using it?
I want to disable a field in selection screen so that it does not appear while displaying.How can i do that?wat wud be the code?
how to create a button in selection screen?
Give few names of transparent tables ?
Explain the properties of selection screen?
use of chain and endchain?
What is an update type with reference to a match code id?
with table control?
How do you know that data is updated in call transaction
what is diffrence subroutine in report and subroutine in script.....
2 Table Maintenance generation & validation using events Create table lets say ZXXXX hold Object Locations. Field key data element Type Length Dec text MANDT x MANDT Clnt 3 0 Client ZCTRY x LAND1 Char 3 Country Key ZOLOC x ZOLOC Char 15 Object Location ZOLOC20 ZOLOC20 Char 20 Object Location short text ZOLOC40 ZOLOC40 Char 40 Object Location long text ZAWSYS LOGSYSTEM Char 10 Logical System ZSTREET AD_STREET Char 60 Street ZSTREET2 AD_STRSPP1 Char 40 Street 2 ZPOSTAL_CODE AD_PSTCD1 Char 10 City postal code ZCITY AD_CITY1 Char 40 City ZCOUNTRY ZLAND Char 3 Address Country ZOBJ_SIGN ZOBJ_SIGN Char 10 Object Sign ZREF1 ZREF1 Char 10 Reference 1 ZREF2 ZREF2 Char 10 Reference 2 ZREF3 ZREF3 Char 10 Reference 3 ZREF4 ZREF4 Char 10 Reference 4 ZNOTE1 ZNOTE1 Char 20 Note 1 ZNOTE2 ZNOTE2 Char 20 Note 2 ZCREAETDATE CREATEDATE Dats 8 Creation/Change Date ZCREATETIME CREATIETIME Tims 6 Creation/Change Time Create a table maintenance generator for ZXXXX. Create two events in Table Maintenance Generator: - To update the filed value SAP in ZAWSYS and creation date and time - To update change date and time after saving the entry Event ‘21’ – At Create: ZXXXX-ZAWSYS = SAP. ZXXXX-ZCREATEDATE = sy-datum. ZXXXX-ZCREATETIME = sy-uzeit. Event ‘01’- After Save ZXXXX-mandt = extract+0(3). ZXXXX-zctry = extract+3(3). ZXXXX-zoloc = extract+6(15). ZXXXX-zoloc20 = extract+21(20). ZXXXX-zoloc40 = extract+41(40). ZXXXX-zawsys = log_sys. ZXXXX-zstreet = extract+91(60). ZXXXX-zstreet2 = extract+151(40). ZXXXX-zpostal_code = extract+191(10). ZXXXX-zcity = extract+201(40). ZXXXX-zcountry = extract+241(3). ZXXXX-zobj_sign = extract+244(10). ZXXXX-zref1 = extract+254(10). ZXXXX-zref2 = extract+264(10). ZXXXX-zref3 = extract+274(10). ZXXXX-zref4 = extract+284(10). ZXXXX-znote1 = extract+294(20). ZXXXX-znote2 = extract+314(20). ZXXXX-zcreatedate = sy-datum. ZXXXX-zcreatetime = sy-uzeit. modify ZXXXX.