Technical aspects of a background job

Hi!
Can anyone perhaps tell me where I can find documentation on the technical aspects of a background job. For example, I want to know if there are any differences in a database update when running a program in foreground or in background. What about table locks or screen input? What difference does it make what user you choose when running a program as a background job? What rules apply when running a BDC in background? In short, I want to know what I need to keep in mind when developing programs that will be run in foreground and in background.
If there is no documentation freely available on this, can someone post the answers to these questions or recommend any books that might help me better understand the technical details of background jobs?
Thank you!
Iwan Ferreira

I want to know if there are any differences in a database update when running a program in foreground or in background.What about table locks or screen input?
There is no difference in the database updates or locks. It works same as if you run in foreground. Only difference is in background it runs when a background process space is free. Screen inputs you will be passing using variants.
What difference does it make what user you choose when running a program as a background job? What rules apply when running a BDC in background?
The user you choose for the step should have the required authorization to run the report. Say you are performing VA01 BDC in background then the step user of the job should have authorization for VA01.
Regards
Farzan

Similar Messages

Can ABAP proxy to consume WSDL file be run as background job for every10min

Hi all,
I have a requirement where I need to build an interface which gatheru2019s the purchase order details and send to external third party software in their required format (as an XML file).
So I should be the first point of contact and should trigger the interface each time a purchase order is generated.
So I am thinking that I should develop a background job for every 10 minutes which will look for new purchase orders and gathers the information of the purchase orders and send them to external third party software in their required format.
I have gone through all the SAP forums and e-Learning but still I have confusion in regards to how is it possible technically? Can some one guide me with some information on the same.
I have a little bit of confusion and want to know few things.
1)     Should I create a web service or should I consume a web service?
2)     If I need to consume a web service, then can I write an ABAP proxy to be run in background fro evry 10 minutes? I mean can we run ABAP proxy as a batch job in the background?
3)     Is there a difference between consuming an XML file and WSDL File?
Any Help will be highly appreciated.
Regards,
Jessica.

There are two options (as I know) to generate XML file.
1. Use XML TRANSFORMATION to get the XML string based your TRANSFORMATION. You can input your data and get back the XML string. Download this string to a file
Test XML generation program is:
types: begin of ty_data,
       num   type i,
       end   of ty_data.
DATA: itab TYPE standard table of ty_Data,
      la_data like line of itab,
      xmlstr TYPE string.
DO 3 TIMES.
la_data-num = sy-index.
APPEND la_data TO itab.
ENDDO.
CALL TRANSFORMATION ztest_np1
SOURCE table = itab
RESULT XML xmlstr.
CALL FUNCTION 'DISPLAY_XML_STRING'
EXPORTING xml_string = xmlstr.
My ZTEST_NP1 transformation. To create a transformation, click on the transformation in the "CALL TRANSFORMATION ztest_np1" statement. Select Simple transformation type.
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
<tt:root name="table"/>
<tt:template>
    <table>
      <tt:loop ref=".table">
        <item>
          <tt:value ref="NUM"/>
        </item>
      </tt:loop>
    </table>
</tt:template>
</tt:transform>
XML string is like:
<?xml version="1.0" encoding="utf-8" ?>
<table>
<item>1</item>
<item>2</item>
<item>3</item>
</table>
To use this option, you have to create a transformation and than use it to generate the XML string.
Check this SAP Help
http://help.sap.com/saphelp_nw04s/helpdata/en/e3/7d4719ca581441b6841f1054ff1326/frameset.htm
2. You can concatenate and create an XML string and download that string into a file.
Regards,
Naimesh Patel

How to Execute WebDynpro Applications as Background Job ?

Hi Gurus,
We have developed a lot of WDJ applications with component reusage; ie,
quite a lot of business logic are wrapped in WDJ Components which are
re-used by other WD UIs.
Now we'd like to automate some of the processes with background jobs
and faced with a few problems :
#1. How can we write a background WD application which can be
triggered by external mechanism and without presenting any UI?
#2. If we write the background program in a Java DC, how can we
invoke existing methods in WD components ?
Anyone got a clue ??
Ying-Jie Chen

Hello Amit,
> Well I can think of a workaround in this case.If you are aware
> of the suspend-resume functionality of the WD application then
> its possible to run the WD application virtually in background.
[ stuffs deleted ...]
It sounds like a possible alternative to our requirement, I'll
spend some time to investigate on the WD suspend-resume mechanism !
> Also let me know why are you preffering the WD if you dont
> require its UI
Our application requires the process to be performed with UI interaction;
with some instances it should be run as a background job. Either case involves
RFC calls to backend SAP R/3 and it's easy for RFC access with WD
Component. Though it's also possible to use CAF application service for
RFC access; due to some technical constrains, we did not use CAF
framework. Therefore it ends up where we are now ...
Thanks for your tip!
Ying-Jie Chen

Error in background job for program RSGET_SMSY error message No active job

Hello!
I would like to set up the Change Request Management functionality in SAP Solution Manager.
The only red warning by executing Test-button in Tcode SOLAR_ADMIN_PROJECT is:
<b>Error in background job for program RSGET_SMSY error message No active job found</b>
Can someone please tell me how to solve this problem?
(tcodes, technical steps)
Thank you very much!
regards
Thom

Thank you very much!
Can you also help me with the warning "Errors occurred during synchronization of the system landscape" in tcode SOLAR_PROJECT_ADMIN" --> System landscape --> Change requests --> "Refresh"?
The second issue I cannot see any projects in Tcode "/TMWFLOW/CMSCONF"
according to the SPRO-step "Set Project Assignment of Requests as Mandatory"
Thank you!
regards

DP background jobs in local time zone

We are using APO DP in an international environment (SCM 4.1). We have setup up the system, that is using the local time zone (personal user settings), which is working fine in interactive planning (data views & macros). But when executing the macros
in background (APO background jobs triggered immediately by a process chain), the macro is run based on the server time and not in the local time zone. The ALEREMOTE user is set up in the same way online users regarding time zone settings.
Can someone explain, why the local time zone isn't used in the macros when executing in background, and tell me which setting we have missed.
Many thanks in advance
Marco

HI,
I understand the issue, the issue is the Australia gets days very first from the world.. it almost GMT+11 hrs. will almost a day difference to US.
I am not sure whether my proposal will make sense, but let me try
As the month completes we will copy the sales history for the closed month. where technically the the month is current month as per the system time.
Why can not change the macro to copy current period and run at system time? i am not sure aobut the otherconstriantes.
But looking at your question, it could be possible where your client has the local time zone defined. you can check the same from any APO screen, from menu > systems->status. you can see both time zone ( local) system time.
I suggest you check with basis if we can use the local time zone, we can use the localtimezone but agian everyone has to use our local time.. NO SENSE i guess..
Yarala

Background job with FTP

Hi,
I have devloped a program which takes the required data in internal table and places the file in FTP.
When i execute it manually, the file gets placed properly, but when i schedule the program in background, the program gets executed but the file dow

Hi,
You Must be using RFC destination as SAPFTP, when you see go to SM59 -> TCP/IP -> SAPFTP & double click on SAPFTP, go to Technical Setting tab, you have 4 option in Activation Type. Select Start on Application Server Option and then save the setting. Now test the Background job.
Regards
Sanjeev Pallan

Technical Monitoring: customizing cancelled batch jobs metric

We have recently implemented Solution Manager Technical Monitoring. We are struggling with the Number of cancelled jobs metric.
Our issue is that users have the ability to cancel their own background jobs. This of course triggers the alert. So, from that standpoint this alert can yield a lot of "false positives".
On the other hand, we do have jobs where we would like an alert - jobs by name, by ID, by program...etc.
However when I look at the Data Collection tab for the number of cancelled jobs metric(s), the parameters are very basic and don't provide any parameters to filter out jobs based on regular expressions as some other metrics do.
Does anyone have any insight into how this metric could be customized? Or, more ambitiously, could this be implemented as a brand new custom metric? If so, this seems to be a more involved process and we haven't seen a real comprehensive "guide" on how to create and implement a brand new custom metric so if anyone has any experience or documentation to share that would be greatly appreciated.
thanks,
Jeff Henke

Hi Jeff,
I have been through the exact scenario in my previous project and can relate to your frustration.
The issue is that Technical Monitoring only plays with numbers when it comes to Job monitoring. This is also because Jobs are considered more of a Business related function.
Therefore, the best option would be to go for BPMon for jobs monitoring. This is the way I went and got a lot of success with it.
Once you have setup the BPMon structure - basic setup etc, Solution etc.
Goto BPO Workcenter and configure the monitoring object of type Simple job.
Here you can specify wildcard within the jobs that you want to monitor. for eg, *ERP*SO* - this would monitor all Sales order jobs for all country etc.... you then have to (ofcourse) define all the other components like notifications etc settings.
A detailed document created in SCN - Job Monitoring using BPM
Now as the email notification that comes out of the alert is pretty standard and at least didn't meet my requirements, so I wrote a BADI and configured the same within the Monitoring object to call this BADI.
You can see a complete step by step implementation of my BADI in SCN Customize Email Subject in Solman 7.1 using BADI
Hope this helps
All the best
Regards
Deepak

Alert monitor for long running background jobs

Hello,
I have to configure an alert moniter for long running background jobs which are running more than 20000 secs using rule based. I have created a rule based MTE and assigend MTE class CCMS_GET_MTE_BY_CLASS to virtual node but i dont find a node to specify the time.
could any one guide me how can i do this.
Thanks,
Kasi

Hi *,
I think the missing bit is where to set the maximum runtime. The runtime is set in the collection method and not the MTE class.
process: rz20 --> SAP CCMS Technical Expert Monitors --> All Contexts on local application server --> background --> long-running jobs. Click on 'Jobs over Runtime Limits' then properties, click the methods tab then double click 'CCMS_LONGRUNNING_JOB_COLLECT', in the parameters tab you can then set the maximum runtime.
If you need to monitor specific jobs, follow the process (http://help.sap.com/saphelp_nw70/helpdata/en/1d/ab3207b610e3408fff44d6b1de15e6/content.htm) to create the rule based monitor, then follow this process to set the runtime.
Hope this helps.
Regards,
Riyaan.
Edited by: Riyaan Mahri on Oct 22, 2009 5:07 PM
Edited by: Riyaan Mahri on Oct 22, 2009 5:08 PM

CCMS Monitor to Pager for Failed Background Jobs

Hello Experts,
I am currently leveraging Central CCMS monitoring to alert us via email whenever a background job fails in production using the MTE Class R3BPServerSpecAbortedJobs.
I am trying to find a way that I can tweak the monitor to alert me ONLY when specific background jobs fail.
We want this alert to notify the oncall pager only when a handful of critical jobs fail. Does anyone know how I can delimit this MTE?
For example, we will be creating jobs that begin with Z_ALERT* that I will tie to an auto-react method that will email a pager.
Thanks in advance.
Bill

Hi Sundara.
From following link, you can download step by step setup information.
So please check following documents.
http://www.service.sap.com/bpm
=>Media Library=>Technical Information
=>1. Business Process Monitoring - Setup Roadmap
=>2. Setup Guide - Business Process Monitoring
Before you start setup, I recommend you to check
SAP Notes 521820 to ensure whether you already fulfill
prerequestions.
Basically what you have to do is following.
1. Describe your business process under following area.
   (T-CD DSWP =>Solution Landscape =>Solution landscape maintenance)
2. Setup BPMon session.
   (T-CD DSWP =>Operation Setup => Solution Monitoring =>
    Business Process Monitoring)
   in BPMon session, select job monitoring. And define background
   job that you want to monitor.
   In BPMon job monitoring, you can monitor, cancel, delay, duration,
   unexpected parallelization, also job log and so on.
I hope this information help you.
Best Regards
Keiji Mishima

Problem in getting spool number of a background job.

Hi all,
In a Z program I am calling a standard program to run as background job. I need to get the report o/p of the standard program. For this I need the spool no of the background job. Now I am querying on table tbtcp by giving jobname. Program name and run date and getting the spool no. but the cache is that the table is not getting updated with the spool no as soon as the job finishes. It is taking some time to update the table ( The time depends on the no of background jobs scheduled. ). So of we query on the table immediately after the background job finishes we are getting spool no as 0. so I am unable to read the spool into Internal tables. Even the table tsp01 is also behaving in the same way. ( it is taking time to update ) .
Any pointers to this will be appreciated .
Regards,
Shiva....

This is some prototype that I put together from separate pieces, so it looks funky, but might be helpful. The first step is to SUBMIT the program with EXPORTING LIST TO MEMORY. The next FM reads the list from memory and the next one (optional) converts it to a text format. You might want to search for other FMs in SE37 by 'LIST*'.
DATA list_tab TYPE TABLE OF abaplist.
SUBMIT RPR_TRIP_HEADER_DATA
USING SELECTION-SET 'OLD_LIST'
EXPORTING LIST TO MEMORY
              AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = list_tab
EXCEPTIONS
    not_found = 1
    OTHERS     = 2.
types : t_txt(1000) type c.
DATA: i_txt2 type table of t_txt,
i_txt type list_string_table.
call function 'LIST_TO_ASCI'
EXPORTING
*   LIST_INDEX               = -1
   WITH_LINE_BREAK          = 'X'
IMPORTING
   LIST_STRING_ASCII        = i_txt
*   LIST_DYN_ASCII           =
TABLES
   LISTASCI                 = i_txt2
   LISTOBJECT               = list_tab
EXCEPTIONS
   EMPTY_LIST               = 1
   LIST_INDEX_INVALID       = 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.
Also check this links:
http://sap.ittoolbox.com/groups/technical-functional/sap-dev/spool-number-of-previously-printed-abap-list-635173#

Background jobs html output not allowed 1 MB size

hi experts,
We are facing an issue with backgrounds jobs HTML output. we are running some backgrounds jobs for Std reports, and we are facing if the HTML output is <1 MB, the std sap is cutting/reducing the content only 1 MB. I think somewhere the background jobs HTML output is fixed 1MB, request kindly let us know how & where we can modify/allow the HTML output <1 MB size for background jobs.
Please help.
thanks in advance
Srihari

thanx so much for the solution, but i wanted to fix permanently at the time of html output after the job is finished itself, but when i change the parameters from 1 to 9999 pages, it is showing information message and SAP recommends the spool output is fixed from 1 to 10 pages only, if i go beyond 10 pages, i get message memory slow and impact on memory, etc.,
I wud like to know expert opinion whether doing from 1 to 100 pages thru SP01, what are consequences are to be faced wrt to memory and other aspects. Also i wanted to know these permanent changes will affect entire system or only specific jobs?
I wanted for 2 to 5 background jobs, which are having more than 10 to 30 pages,
Please advise
thanx in advance
srihari

IDoc failure in background job

Hi,
I have developed a customized program and sending outbound IDocs to other SAP system using Function Module MASTER_IDOC_DISTRIBUTE. When I am running this program in background mode IDocs are failed with reason 'Entry in outbound table not found'.
But when I am running the same program in foreground then IDocs are getting posted properly. Partner Profile and port are set properly.
Please anyone could give me reason behind IDocs failure in background Job.
Many Thanks.

Hi,
Message Number for the message is "Entry in outbound table not found' E0 - 400. This Mesasge used
in the below programs.
Programs asying that there is no Entry in EDP13(Partner Profile : Outbound(Technical Parameters)) Table. Debugg the Background job in SM37 by entering JDBG in the command field then it will go to debugging mode. Then put break point for "MESSAGE".
Thanks,
Naresh Mochi

Difference between Batch jobs and background jobs...

hi APO Gurus ....
This may sound a very silly question. What is the exact difference between a batch run and executing a background job ?

If i understand correctly your question is executing a program (for example) in background and running in a batch jobs. You can execute a program in background while you are online, go to menu program->execute in background and enter print parameter, schedule parameter. System creates and starts job dynamically. You can check in SM37. Batchjob is you create job using SM36 (with program and Variant) define run frequency. System automatically run job in specified frequency. I my experience, technically both are same, system behaves exactly same. One dynamically creates job other one runs on predefined freq.
Thanks,
Niranjan

Difference between batch job and Background Job

Hi Forum,
Can anyone distinguish between batch job and background job for me please ?
SK

Hi,
Batch Job:
A batch job is a process that runs in the background, often deferred and unattended, to process data in groups (batch) rather than by individual transactions (e.g. a monthly phone bill rather than a bill for each individual phone call). A batch job executes a sequence of programs and technical instructions that are stored in a command file. Progress and error messages are output to a log file allowing users to determine, at any time, if the batch job completed successfully or identify the cause of the problem. Because batch jobs run in the background they are less visible to the end user.
In a business-computing context, batch job scheduling implies the automatic execution of background tasks (batch jobs) at pre-determined points in time (e.g. every day at 8pm, midday on Wednesday).
3 types of batch job scheduling can be distinguished: native, basic and advanced batch job scheduling.
Most operating systems and some business solutions software come equipped with native batch job scheduling tools that provide a limited service (e.g. Windows Scheduled Tasks, UNIX crontab, SAP CCMS) locally to each installation. However, business processes may span multiple platforms, applications, countries and companies. Their complexity may require much more functional power as provided by basic batch job scheduling including national and regional variations in the working calendar, sequence variations according to the day of the month, triggering of jobs by the successful completion of preceding jobs, elimination of gaps and reduced batch windows. Major benefits of basic batch job scheduling are enhanced productivity, operations reliability and cost-reduction. For e-business applications that require real-time processing, the distance between interactive individual processing and batch processing tends to decrease. Advanced batch job scheduling can handle these advanced requirements: event-driven scheduling for a real-time synchronization with interactive processing, just-in-time scheduling to run operations as soon as possible, cross-platform and cross application services for the entire IT landscape, real-time overall monitoring to track background operations for all applications on all servers.
The standard benefits of batch job scheduling are drastically amplified when job schedulers can handle the end-to-end automation and monitoring requirements for all background operations.
To schedule a back ground job follow the below steps:
1. Use Transaction SM36.
2. Assign a job name.
3. Set the jobs priority, or Job Class:
High --- Class A
Medium --- Class B
Low ---Class C
4. Here you can specify,when the job is to start by choosing Start Condition. If you want the job to repeat, or be periodic, check the box at the bottom.
Else click on the immediate and save this.
5. Now,define the jobs steps by choosing Step.
Here you need to give the ABAP program that has been used and the name of the variant thats being used.
6. Save the fully defined job to submit it to the background processing system.(You need to click save button on the main screen i.e SM36)
7. When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
8. Release the job so that it can run.
The job, even those scheduled for immediate processing, can not run without first being released.So,do remember to release.
Hope this helps you.
Regards,
Rakesh

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.

Technical aspects of a background job

Similar Messages

Maybe you are looking for