Unable to create Background job

Hi All,
I am trying to create a background job for standard program RFBIBL00 from a client QP1-231. But I am not able to do it as I am getting a message that the client differs from the original client qp1-020.
I AM ABLE TO CREATE THE BACKGROUND JOB FROM QP1-020,but not from QP1-231.
Please look into the matter and let me know why I am not able to creat the job from QP1-231.
I promise to reward.

Hi,
Please check with your basis team whether you have authorization for the same.
Raghav

Similar Messages

How to create Background job for Dialog program

Hi Experts,
I have copied Standard tcode to Z-tcode (CS12 tcode).
Now my requirement is to create background job for this program (but program is not a 'E' type its 'I').
How we can schedule Dialog program to Background.
Pls suggest me.
Regards
SK

Hi do as below :
Reefer below :
Bakcground Job Creation
You will have to submit your report using Submit statement ,
then inside the submitted report write open_job.
Regards,
Uma

OWB maping execution :- ORA-20213: Unable to create standalone job record

Hi,
When I am running an owb mapping from sqlplus, I am getting the following error:
SQL> DECLARE
2 RetVal NUMBER;
3 P_ENV WB_RT_MAPAUDIT.WB_RT_NAME_VALUES;
4 BEGIN
5 RetVal := UII_D_MAP_SPC_WIPBIN.MAIN ( P_ENV );
6 dbms_output.put_line('RetVal is '||RetVal);
7 END;
8 /
DECLARE
ERROR at line 1:
ORA-20213: Unable to create standalone job record - there may be no task
defined for this map
ORA-06512: at "UII_OWB_REP.WB_RT_MAPAUDIT", line 1266
ORA-06512: at "UII_OWB_REP.WB_RT_MAPAUDIT", line 2098
ORA-06512: at "UII_ODS_OWNER.UII_D_MAP_SPC_WIPBIN", line 3851
ORA-06512: at "UII_ODS_OWNER.UII_D_MAP_SPC_WIPBIN", line 3993
ORA-06512: at line 5
Previously, I had unregistered the target schema from "OWB Runtime Audit Browser" logging as a QA user and registered to a new schema from OWB DEPLOYMENT MANAGER.
I am able to deploy the mapping from Owb Deployment Manager and the deployment goes OK.
I have also gone through the links:
OWB execution error : ORA-20213: Unable to create standalone job record
Re: ORA-20213 during execution
But, did not find the solution.
When I execute the mapping from Owb Deployment Manager after right clicking on it, it is working fine. But, above execution method is not working.
We want to run the mappings in the above way, because all our mappings in our other projects are running fine in the above sql run procedure.
Can you please help me out, how to fix the above errors?
Thanks & Regards,
lenin

Good morning Lenin,
Since the other threads do not apply, you've gotten yourself into a strange situation.
I'm not familiar with the method you use to run the mapping, have you tried running the mapping using the SQL-template that OWB provides or - like I do - the run_my_owb_stuff script provided by the OWB time? If not, could you try that please?
Apart from that, I don't have any experience with your exact error message so it's hard to share anything concrete, I can only suggest things. Maybe there are other users on this forum that do, who knows...
If you want concrete support, log a TAR with Metalink, they are obligated to help you if you have a CSI :-)
Good luck, Patrick

Create background job

Hi,
is it possible to create background job of a program with POO, i had a look on class, i found CL_BP_ABAP_JOB or CL_BP_JOB but i don't use them.
Otherwise i will use 'JOB_OPEN' but i like POO
Can you help me ?

I answer myself...
The class to use is cl_bp_abap_job.

ORA-20213: Unable to create standalone job record

We are currently in the process of upgrading our repository from 9.0.2.56.0 to 9.2.0.2.8 and we have moved our mappings into new repository by importing an MDL file. We have successfully deployed a mapping from new repository but when we attempt to execute this mapping using:
DECLARE
retval NUMBER;
BEGIN
retval:=Map_Wm_Osa_Fund_Pl.Main(F_Initialize_Owb);
END;
we get the following:
ORA-20213: Unable to create standalone job record - there may be no task defined for this map
ORA-06512: at "PRM_OWB_RUNTIME.WB_RT_MAPAUDIT", line 1252
ORA-06512: at "PRM_OWB_RUNTIME.WB_RT_MAPAUDIT", line 2084
ORA-06512: at "PRM.MAP_WM_OSA_FUND_PL", line 3832
ORA-06512: at "PRM.MAP_WM_OSA_FUND_PL", line 3913
ORA-06512: at line 4
Any help on this would be much appreciated.

Alright, here's the work around for this, I'm also using the following to run mapping.
DECLARE
RetVal NUMBER;
P_ENV WB_RT_MAPAUDIT.WB_RT_NAME_VALUES;
BEGIN
-- P_ENV := NULL; Modify the code to initialize this parameter
RetVal := SCHEMA.MAPPING.MAIN ( P_ENV );
END;
My mapping was running fine until I have tried to deploy it under a different location.
Somehow OWB Runtime remembered my old location and was confused between the two. That's why you see this error.
Option 1.
Rewrite your mapping, this is ok if it's a small mapping.
Option 2.
1. Export your mapping(s) (MDL file)
2. Delete your mapping from the repository.
3. Import a backup of your mapping before the second location was created. (It’s doesn't matter if it's a old backup)
(At that point you should be able to run the old mappings without error)
4. Import the good backup over the old mapping, (use merge option during import)
Your mapping should run now.
Jean

Create Background jobs

How can i create background jobs and link them to the Event so that they will be triggered? I have no clue on this, can anyone explain in a detailed manner with the Transaction codes for each.
Thanks in advance.

Hi laitha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
_List of Background Jobs_
BIREQU - Load of a Request/Reconstruction of a request
BI_AGGR4 - Aggregates activation
BI_BTCH - Any batch job like ABAP program run in background
BI_DELR - Deletion of request
BI_HIER - Hierarchy loading/activation
BI_ODSA - ODS activation
BI_PROCESS_ABAP - ABAP program in process chain
BI_PROCESS_LOADING - Data Loading in process chain using nfopackage
BI_PROCESS_ODSACTIVAT - ODS actiavation in Process chain
BI_PROCESS_TRIGGER - Trigger job for process chain
BI_PSAD - probably PSA deletion
BI_STAT - Building statistics
BI_STRU - Change run job
BI_WRITE_PROT_TO_APPLLOG - Application log job
RANATL_ACCT_CACHE_WARMUP
Use tcode SM62 to create User events.
Use tcode SM64 to trigger the event.
Wizards for Event Creation :pls chk this link
http://help.sap.com/saphelp_erp2005vp/helpdata/en/f7/d1c20a02d511d3a6550060087a79ea/frameset.htm
*pls assign points,if info is useful**
Regards
CSM reddy

Problems creating background job for program (job open, submit and close)

Hi gurus,
im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
Below goes my code,
any ideas will be rewarded
CLEAR: stdt_modify_type, stdt_output.
CALL FUNCTION 'BP_START_DATE_EDITOR'
       EXPORTING
            stdt_dialog                    = 'Y'
            stdt_input                     = stdt_input
            stdt_opcode                    = 14
       IMPORTING
            stdt_modify_type               = stdt_modify_type
            stdt_output                    = stdt_output
       EXCEPTIONS
            fcal_id_not_defined            = 1
            incomplete_last_startdate      = 2
            incomplete_startdate           = 3
            invalid_dialog_type            = 4
            invalid_eventid                = 5
            invalid_opcode                 = 6
            invalid_opmode_name            = 7
            invalid_periodbehaviour        = 8
            invalid_predecessor_jobname    = 9
            last_startdate_in_the_past     = 10
            no_period_data_given           = 11
            no_startdate_given             = 12
            period_and_predjob_no_way      = 13
            period_too_small_for_limit     = 14
            predecessor_jobname_not_unique = 15
            startdate_interval_too_large   = 16
            startdate_in_the_past          = 17
            startdate_is_a_holiday         = 18
            startdate_out_of_fcal_range    = 19
            stdt_before_holiday_in_past    = 20
            unknown_fcal_error_occured     = 21
            no_workday_nr_given            = 22
            invalid_workday_countdir       = 23
            invalid_workday_nr             = 24
            notbefore_stdt_missing         = 25
            workday_starttime_missing      = 26
            no_eventid_given               = 27
            OTHERS                         = 28.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    MOVE 'X' TO gv_flag.
ENDIF.
DATA jobname LIKE tbtcjob-jobname.
DATA jobcount LIKE tbtcjob-jobcount.
DATA job_release LIKE btch0000-char1.
DATA job_imediate TYPE c.
CLEAR: jobname, jobcount, job_release.
CONCATENATE 'MAPAEXEC' sy-uname sy-datum
               INTO jobname SEPARATED BY space.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = jobname
       IMPORTING
            jobcount         = jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ENDIF.
SUBMIT z_mapa_execucao_orcamental
         VIA JOB jobname NUMBER jobcount
         WITH ano EQ ano
         WITH so_perio IN so_perio
         WITH so_date IN so_date
         WITH so_org EQ so_org
         WITH so_num IN so_num
         AND RETURN.
IF stdt_output-startdttyp EQ 'I'.
    CLEAR job_imediate.
    job_imediate = 'X'.
ENDIF.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            calendar_id                 = stdt_output-calendarid
            event_id                    = stdt_output-eventid
            event_param                 = stdt_output-eventparm
            event_periodic              = stdt_output-periodic "?
            jobcount                    = jobcount
            jobname                     = jobname
            laststrtdt                  = stdt_output-laststrtdt
            laststrttm                  = stdt_output-laststrttm
            prddays                     = stdt_output-prddays "??
            prdhours                    = stdt_output-prdhours "?
            prdmins                     = stdt_output-prdmins "??
            prdmonths                   = stdt_output-prdmonths
            prdweeks                    = stdt_output-prdweeks "?
            predjob_checkstat           = stdt_output-checkstat
            pred_jobcount               = stdt_output-predjobcnt
            pred_jobname                = stdt_output-predjob
            sdlstrtdt                   = stdt_output-sdlstrtdt
            sdlstrttm                   = stdt_output-sdlstrttm
            strtimmed                   = job_imediate
            targetsystem                = stdt_output-instname
            start_on_workday_not_before = stdt_output-notbefore
            start_on_workday_nr         = stdt_output-wdayno
            workday_count_direction     = stdt_output-wdaycdir
       IMPORTING
            job_was_released            = job_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
            OTHERS                      = 8.
IF sy-subrc <> 0.
    MESSAGE i003(zmapas).
    EXIT.
ELSE.
    MESSAGE i004(zmapas) WITH jobname.
ENDIF.
Thanks in advance,
Best Regards
João Martins

Hello João.
In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
Check this code:
CALL FUNCTION 'JOB_OPEN'
      EXPORTING
           jobname          = w_jobname
      IMPORTING
           jobcount         = w_jobcount
      EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
CHECK sy-subrc = 0.
CLEAR seltab_wa.
MOVE: t_jobs-param TO seltab_wa-selname,
t_processar-line+34 TO seltab_wa-low.
APPEND seltab_wa TO seltab.
seltab_wa-selname = 'P_LOJA'.
seltab_wa-low = t_processar-ficheiro+7(4).
APPEND seltab_wa TO seltab.
*** Submete o programa para o JOB
SUBMIT (t_jobs-repid)
WITH SELECTION-TABLE seltab
USER sy-uname
   VIA JOB w_jobname NUMBER w_jobcount
   AND RETURN.
*** Encerra o JOB
l_hora = sy-uzeit.
ADD 60 TO l_hora.
CALL FUNCTION 'JOB_CLOSE'
   EXPORTING
      jobcount           = w_jobcount
      jobname           = w_jobname
      sdlstrtdt            = sy-datum
      sdlstrttm           = l_hora
      targetserver       = w_servidor
   IMPORTING
      job_was_released     = l_liberado
   EXCEPTIONS
      cant_start_immediate = 1
      invalid_startdate    = 2
      jobname_missing      = 3
      job_close_failed     = 4
      job_nosteps          = 5
      job_notex            = 6
      lock_failed          = 7
      OTHERS               = 8.
Regards.
Valter Oliveira.

Create Background Job after data saved in module

Hello,
I have a program that has a start selection screen with material group, you enter your data, execute. When it has finished you get a ALV of sales order with items where you can make changes to dates and other details and save. I would like to add a save in background option. Is this possible? I assume it would be difficult because of the container.. it uses a bapi to save sale orders...
The employees run this job which takes a little while.. at the end of the day.. they go home and of course SAP has timed out. If they can run it in the background then no problem....
Thanks,
AJ

well, you can pass the data from the same to an other program and submit it in background.
Just create a job.
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
            jobname          = gv_jobname
       IMPORTING
            jobcount         = gv_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
*   no error required
ENDIF.
submit your program with job name and job count.
CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
            jobcount             = gv_jobcount
            jobname              = gv_jobname
            strtimmed            = 'X'
       EXCEPTIONS
            cant_start_immediate = 1
            invalid_startdate    = 2
            jobname_missing      = 3
            job_close_failed     = 4
            job_nosteps          = 5
            job_notex            = 6
            lock_failed          = 7
            OTHERS               = 8.
IF sy-subrc <> 0.

Inbound IDoc creating background job even for trigger immediately setup

All,
I have a very serious problem in our production system.
Scenario:
Vendor is chagend in system A (Outbound) and the same is interfaced to System B (Inbound) and i am using trigger immediately option, but still I am seeing a background job is created for 'RBDAPP01' and creating the spool request. The issue is I am sending 1000 of idocs and the spool number is increasing daily in system B.
So, can any one explain me why the background job is getting triggered even though I set the partner profile settings as 'Trigger Immediately'.
The above issue is not happening in our quality system it simply updagtes vendor information in system B with out creating any background job. Please note that the same settings are maintained in both the systems.
Your immediate inputs are really valuable for me.
Regards,
Suman

This is an performance issue on the receiving system. In case the system does not have enough resources to process the IDoc immediately it will always schedule a background job to ensure the processing of data.
You need to check whether the system has enough work processes available during the time when 1000 of IDocs are received or send the IDocs in packages with some time in between.
Regards,
Kai

Create background job triggered by another job

Hi experts,
I want to run FCHU in background everytime I finished run F110.
I'm thinking to use background job creation SM36 - triggered by job. But the problem is, job created from F110 the job name is not fixed.
Please anyone can give better idea ??
Thanks,
Melissa

Hi melissa,
The suggestion given by Prem is perfectly Ok.
I would suggest you to create an event by sm62 and then create an event triggered background job which will run the FCHU in Back ground.
So you need to get an enhancement point in F110 and put the code of triggering the event .
If there is no enhancement then you can create a program which will call the Transaction F110 by using CALL TRANSACTION statement and after F110 processing the control will get back to your program and you can write a code for triggering the event by using the FM SWE_EVENT_CREATE.
I hope this will help you

Hi friends need some help while creating background job

I need to run a batch report in background in SM36 when any cancellation of sales order is done in VL09.
i.e when a cancellation of sales order is done i have to run a batch report which will call an IDOC outbound generation function module that will create the IDOC.....
Please tell me how to do this.....

Hi,
To submit backgroud jobs.
Call Function 'Job_Open'.
SUBMIT <report name>
WITH <input variants>
USER sy-uname
VIA JOB <job name>
AND RETURN.
If sysubrc eq 0.
Call Function 'Job_Close'.
Reward if helpfull.

Is there a possibility create background jobs for transaction SP01?

We are creating spool requests (status 'to be processed') for specific printers that are located in different time zones. We want to schedule print jobs by printer to make sure the prints come out at a time the user specifies to us. I am looking for a program with the possibility to make variants by printer that I can include in a job to be created via SM36.Looking forward to your suggestions!
kind regards
Angelique Heutinck

Hi,
Check this link It may help you.
https://forums.sdn.sap.com/click.jspa?searchID=4305151&messageID=2622788
Thanks.

How to Create event, background Job & Assing event to backgroud job to trig

Hi Experts,
I want to trigger events in Backgroud for data scheduling purpose to automate.
I can able to create event in SM62. then i want to create background job in SM36 then how to assign to event in Background to trigger.
can anybody give some suggestion on this.
Best Regards
Siri

Hi,
There are two cases
1) to raise an event after the completion of a job
This can be done by using ABAP coding, trigger the event using a program by the 'RAISE' statement. The job can be scheduled to run in the background daily or weekly(or anything as per the requirements)
2) to run a job after an event
in the start condition of the job, give the event name which should trigger that job in the after event field.
or if you want to run multiple jobs after one event completes, give that event in the start condition of all the jobs.. or model a process chain which will run this jobs..
I hope this clrifies your doubt...
Regards
Shilpa

Spool list is not getting created for background job

I am creating background job using JOB_OPEN and then submitting my z-report using submit statement and then closing job using JOB_CLOSE. for this job is getting creating in sm37 and also gets finished but it does not create spool list showing output.
Any idea how to do this?
Thanks in advance.

DATA: lv_jobname TYPE tbtcjob-jobname,
        lv_jobcount TYPE tbtcjob-jobcount,
        lv_variant TYPE variant,
        wa_var_desc TYPE varid,
        wa_var_text TYPE varit,
        it_var_text TYPE TABLE OF varit,
        it_var_contents TYPE TABLE OF rsparams.
REFRESH: it_var_contents, it_var_text.
CLEAR: wa_var_desc, wa_var_text.
CALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'
    EXPORTING
      curr_report     = sy-cprog
    TABLES
      selection_table = it_var_contents
    EXCEPTIONS
      not_found       = 1
      no_report       = 2
      OTHERS          = 3.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CONCATENATE sy-datum sy-timlo INTO lv_variant.
wa_var_desc-mandt       = sy-mandt.
wa_var_desc-report      = sy-cprog.
wa_var_desc-variant     = lv_variant.
wa_var_desc-transport   = 'F'.
wa_var_desc-environmnt = 'B'.
wa_var_desc-version     = '1'.
wa_var_desc-protected   = 'X'.
wa_var_text-mandt = sy-mandt.
wa_var_text-langu = sy-langu.
wa_var_text-report = sy-cprog.
wa_var_text-variant = lv_variant.
lv_jobname = lv_variant.
CONCATENATE 'Batch Job Variant -'(006)
              sy-uname INTO wa_var_text-vtext.
APPEND wa_var_text TO it_var_text.
Create the varaint for the back ground job.
CALL FUNCTION 'RS_CREATE_VARIANT'
    EXPORTING
      curr_report               = sy-cprog
      curr_variant              = lv_variant
      vari_desc                 = wa_var_desc
    TABLES
      vari_contents             = it_var_contents
      vari_text                 = it_var_text
    EXCEPTIONS
      illegal_report_or_variant = 1
      illegal_variantname       = 2
      not_authorized            = 3
      not_executed              = 4
      report_not_existent       = 5
      report_not_supplied       = 6
      variant_exists            = 7
      variant_locked            = 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.
Open the job.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobname          = lv_jobname
    IMPORTING
      jobcount         = lv_jobcount
    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.
submitt the job in background mode.
CALL FUNCTION 'JOB_SUBMIT'
    EXPORTING
      authcknam               = sy-uname
      jobcount                = lv_jobcount
      jobname                 = lv_jobname
      report                  = sy-repid
      variant                 = lv_variant
    EXCEPTIONS
      bad_priparams           = 1
      bad_xpgflags            = 2
      invalid_jobdata         = 3
      jobname_missing         = 4
      job_notex               = 5
      job_submit_failed       = 6
      lock_failed             = 7
      program_missing         = 8
      prog_abap_and_extpg_set = 9
      OTHERS                  = 10.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
close the job.
CALL FUNCTION 'JOB_CLOSE'
    EXPORTING
      jobcount             = lv_jobcount
      jobname              = lv_jobname
      strtimmed            = 'X'
    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 this will be helpful..

How can i get Background Jobs list which is made me?

I created background job using JOB_OPEN and SUBMIT and JOB_CLOSE.
I need to Background Job list which is made me..
Do u know any function or logic?
plz~

[BP_JOBVARIANT_OVERVIEW|http://help.sap.com/saphelp_45b/helpdata/en/fa/096ccb543b11d1898e0000e8322d00/frameset.htm]
BP_JOBLOG_READ

Unable to create Background job

Similar Messages

Maybe you are looking for