topic Re: Background in Application Development and Automation Discussions

Background

Former Member — Wed, 16 May 2007 08:06:12 GMT

Plz send me material abt Background ?

Re: Background

Former Member — Wed, 16 May 2007 08:08:09 GMT

hi,

There are two ways for you to handle,

one manually setting up the job through SM36 which is better and convinient,

secondly through program using FM's JOB_OPEN, SUBMIT, JOB_CLOSE.

Find below steps in doing both:

Procedure 1:

1. Goto Trans -> SM36

2. Define a job with the program and variant if any

3. Click on start condition in application tool bar

4. In the pop-up window, click on Date/Time

5. Below you can see a check box "Periodic Job"

6. Next click on Period Values

7. Select "Other Period"

8. Now give '15' for Minutes

9. Save the job

In SM37 u can check the status of the jobs that u have assigned to background...

Here u mention the job name or the report name to check the status of the job...

After mentioning the job name or program name u just execute it.. ( without any name also u can execute then it gives u all the jobs set by your user name..

the status colud be released,active,finished etc..

Procedure 2 via Program:

Below is a sample code for the same. Note the ZTEMP2 is the program i am scheduling with 15mins frequency.

DATA: P_JOBCNT LIKE TBTCJOB-JOBCOUNT,
      L_RELEASE(1) TYPE c.
 
   CALL FUNCTION 'JOB_OPEN'
     EXPORTING
       JOBNAME                = 'ZTEMP2' 
    IMPORTING
      JOBCOUNT               = P_JOBCNT
    EXCEPTIONS
      CANT_CREATE_JOB        = 1
      INVALID_JOB_DATA       = 2
      JOBNAME_MISSING        = 3
      OTHERS                 = 4.
   IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
 
   SUBMIT ZTEMP2 VIA JOB 'ZTEMP2' NUMBER P_JOBCNT
          TO SAP-SPOOL WITHOUT SPOOL DYNPRO 
          WITH DESTINATION = 'HPMISPRT'
          WITH IMMEDIATELY = SPACE
          WITH KEEP_IN_SPOOL = 'X' AND RETURN.
 
   CALL FUNCTION 'JOB_CLOSE'
     EXPORTING
       JOBCOUNT                          = P_JOBCNT
       JOBNAME                           = 'ZTEMP2' 
       STRTIMMED                         = 'X'
       PRDMINS                          = 15
    IMPORTING
      JOB_WAS_RELEASED                  = L_RELEASE
    EXCEPTIONS
      CANT_START_IMMEDIATE              = 1
      INVALID_STARTDATE                 = 2
      JOBNAME_MISSING                   = 3
      JOB_CLOSE_FAILED                  = 4
      JOB_NOSTEPS                       = 5
      JOB_NOTEX                         = 6
      LOCK_FAILED                       = 7
      INVALID_TARGET                    = 8
      OTHERS                            = 9.
   IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.

Hope the above helps you.

Kind Regards

Reshma

Re: Background

Former Member — Wed, 16 May 2007 08:42:13 GMT

Hi,

Check the following LInk,

http://www.sappoint.com/basis/bckprsng.pdf

http://www.planetsap.com/Jobs_main_page.htm

http://www.redwood.com/PDF/Epson.pdf

http://www.redwood.com/PDF/Cronacle_for_SAP_solutions.pdf

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21f20e32-0901-0010-65aa-faca8ed043ef

/people/naresh.pai/blog/2005/06/16/parallel-processing-in-abap

http://help.sap.com/saphelp_webas610/helpdata/en/22/0425c6488911d189490000e829fbbd/frameset.htm

Regards,

Padmam.

Re: Background

Former Member — Wed, 16 May 2007 08:54:47 GMT

Hi,

pls go through

1.....................

You can define and schedule background jobs in two ways from the Job Overview:

· Directly from Transaction SM36. This is best for users already familiar with background job scheduling.

· The Structure linkJob Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.

Procedure

1. Call Transaction SM36 or choose CCMS ® Jobs ® Definition.

2. Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.

3. Set the job’s Structure linkpriority, or “Job Class”:

· High priority: Class A

· Medium priority: Class B

· Low priority: Class C

4. In the Target server field, indicate whether to use system load balancing.

· For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.

· To use a particular application server to run the job, enter a specific target server.

5. If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.

6. Define when the job is to start by choosing Structure linkStart Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.

7. Define the Structure linkjob’s steps by choosing Step, then specify the ABAP program, Structure linkexternal command, or Structure linkexternal program to be used for each step.

8. Save the fully defined job to submit it to the background processing system.

9. When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll Structure linkmanage jobs from the Job Overview.

Note: Structure linkRelease the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.

II method

There are two ways to schedule a job from a program:

1. the "express" method using the BP_JOBVARIANT_SCHEDULE function module

2. the "full-control" method using the JOB_OPEN, JOB_SUBMIT, and JOB_CLOSE function modules.

With this method, you have full control over such job options as printing, start time options, and so on.

To schedule a job from within a program using the express method, you need only call the BP_JOBVARIANT_SCHEDULE function module.

With BP_JOBVARIANT_OVERVIEW, you can offer your users a simplified display and management function for their "express-method" jobs.

call function 'BP_JOBVARIANT_SCHEDULE'

exporting

title_name = 'Documentation Check' " Displayed as title of

" of scheduling screens

job_name = 'DocuCheck' " Name of background

" processing job

prog_name = 'RSTWGZS2' " Name of ABAP

" report that is to be

" run -- used also to

" select variants

exceptions

no_such_report = 01. " PROG_NAME program

" not found.

call function 'BP_JOBVARIANT_OVERVIEW' " List the jobs that

exporting " have been scheduled

title_name = 'Documentation Check' " Displayed as title

" of overview screen

job_name = 'DokuCheck' " Jobs with this name

" are listed

prog_name = 'RSTWGZS2'

exceptions

no_such_job = 01.

For further information check the link below

http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a80eb505211d189550000e829fbbd/frameset.htm

2.................................

We can submit a job in background using SM36 that is one way.

Progamaticcaly ,which is the "full-control" method using the JOB_OPEN, JOB_SUBMIT, and JOB_CLOSE function modules.

With this method, you have full control over such job options as printing, start time options, and so on.

Sample code for how to use these function modules.

Create your job with JOB_OPEN. The module returns a unique job
number. Together with the jobname, this number identifies the
job. Other parameters are available, but are not required.

JOBNAME = 'Freely selectable name for the job(s) you create'.

CALL FUNCTION 'JOB_OPEN'

EXPORTING

JOBNAME = JOBNAME

IMPORTING

JOBCOUNT = JOBNUMBER

EXCEPTIONS

CANT_CREATE_JOB = 01

INVALID_JOB_DATA = 02

JOBNAME_MISSING = 03

OTHERS = 99.

IF SY-SUBRC > 0.

ENDIF.

Add a job step: ABAP program

CALL FUNCTION 'JOB_SUBMIT'

EXPORTING

AUTHCKNAM = SY-UNAME " Runtime authorizations

" user

JOBCOUNT = JOBNUMBER " Value from JOB_OPEN

JOBNAME = JOBNAME " Value from JOB_OPEN

REPORT = 'REPORT' " Report to be run

VARIANT = 'VARIANT' " Variant to use with

" report

PRIPARAMS = USER_PRINT_PARAMS " User printing options

ARCPARAMS = USER_ARC_PARAMS " User archiving options

" Both sets of options

" come from

" GET_PRINT_PARAMETERS

EXCEPTIONS

BAD_PRIPARAMS = 01

INVALID_JOBDATA = 02

JOBNAME_MISSING = 03

JOB_NOTEX = 04

JOB_SUBMIT_FAILED = 05

LOCK_FAILED = 06

PROGRAM_MISSING = 07

PROG_ABAP_AND_EXTPG_SET = 08

OTHERS = 99.

IF SY-SUBRC > 0.

ENDIF.

Submit job for processing: immediate start

CALL FUNCTION 'JOB_CLOSE'

EXPORTING

JOBCOUNT = JOBNUMBER " Job identification: number

JOBNAME = JOBNAME " and name.

STRTIMMED = 'X' " Schedules the job for

" immediate start. The job

" is started immediately

" only if the user has the

" RELE authorization to

" release a job to run.

IMPORTING

JOB_WAS_RELEASED = JOB_RELEASED " If user has authorization

" to release jobs to run, job

" is automatically released

" when it is scheduled. This

" field is set to 'x' if the

" job has been released.

" Otherwise, the job is sche-

" duled but must be released

" by an administrator before

" it can be started.

EXCEPTIONS

CANT_START_IMMEDIATE No longer used. Replaced by IMPORTING
parameter JOB_WAS_RELEASED.

INVALID_STARTDATE = 01

JOBNAME_MISSING = 02

JOB_CLOSE_FAILED = 03

JOB_NOSTEPS = 04

JOB_NOTEX = 05

LOCK_FAILED = 06

OTHERS = 99.

IF SY-SUBRC > 0.

ENDIF.

Check the job status through SM37 transaction.

pls reward if it helpful

Regards,

Vana