Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Jobs and Variants

Former Member
0 Kudos

Hi,

In SM35 a batch job gets executed with the name changing on a daily basis. For eg

1st time it runs the name is T102973_DRI_001_C. Next time it runs the name is T102974_DRI_001_C. These jobs call the same program, CONVERT_CALL_FUNCTION. But the variant is always different and numeric. For eg &0000000089460 then the next time &0000000089461. However the program does not have any variant.

My questions are:

1) How are these jobs created so that the names change dynamically

2) The program does not have any variants, so where and how are these variants created.

3) How can I see the contents of these dynamic variants.

Thanks in advance.

Mick

1 ACCEPTED SOLUTION

brad_bohn
Active Contributor
0 Kudos

1 - the job name simply mirrors the name of the session from SM35 - whether it's a custom program or a SAP standard program, you can assign any 12 char name desired. Most likely there's a number range or other sequence counter storage involved.

2 - '&' indicates a dynamic variant - meaning that the program was run in background given a set of parameters (without a static variant)

3 - Go to SM37, display the job step, then Goto -> Variant

4 REPLIES 4

brad_bohn
Active Contributor
0 Kudos

1 - the job name simply mirrors the name of the session from SM35 - whether it's a custom program or a SAP standard program, you can assign any 12 char name desired. Most likely there's a number range or other sequence counter storage involved.

2 - '&' indicates a dynamic variant - meaning that the program was run in background given a set of parameters (without a static variant)

3 - Go to SM37, display the job step, then Goto -> Variant

Former Member
0 Kudos

Thanks Brad.

Extremely helpful.

Can you clarify what do you mean by the statement that the job name mirrors a batch session in SM35.

Points awarded.

MIck

brad_bohn
Active Contributor
0 Kudos

You said 'SM35' so I assumed you were referring to a batch session run in background (which creates a background job with the same name). However, I see that the name you specified is longer than 12 characters, so you must have meant 'SM37' instead. Sorry for misunderstanding.

You can create jobs dynamically via a program and specify the job name (such as with JOB_OPEN, SUBMIT, then JOB_CLOSE). If you don't use an explicit variant, you'll see the dynamic variant naming convention.

Former Member
0 Kudos

Thanks Brad for clearing my doubts.

Points awarded.

Mick