KP97 background job trigger after an event

In Tcode KP97, need to create a background job which triggers after an event y_plan_event .I need this job to run whenever the event is triggered in R/3 .
Right now what is happening is I create one background job and it gets released only once.
Kindly let me know how to go about to make this KP97 job run whenever the event triggers( ie scheduled).
There is no way i can create Variant for the first screen of Kp97

<FONT FACE = "Tahoma", Font Color = "Blue">
Hi<br>
Modify the job in SM37 by making it Event Dependent. Event can be created using transaction SM62.
<br><br>
Hope it helps.<br>
Cheers Abhijit</FONT><FONT FACE = "Verdana", Font Color = "Red">
Please assign Reward Points if I deserve them in your opinion
</FONT>

Similar Messages

Trigger a background job immediately after a file is placed in App Server

Hi all,
I have a program ZPGM1 that needs to be executed in background when a file is placed in an application server.
I know i can schedule ZPGM1 to trigger in background after an event say ZEVENT1.
Also i know i raise the event ZEVENT1 using FM BP_EVENT_RAISE but my problem is who would raise the event.
The file is being dropped in application server at random time by 3 party vendor. I need to execute my ZPGM1 immediately after the file is placed in Application Server.
Is ther a way that this can be achieved. Let me know
Thanks
Kajol

You will need to develop a custom, non-SAP "listener" program or a script. This program/script will need to check if the file is present (e.g. by using an OS-level event) and, if so, start SAPEVT.EXE program with corresponding parameters.
SAP Help on raising events externally:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e6b543b11d1898e0000e8322d00/frameset.htm
There is also third-party software available, but it is very expensive:
http://www.redwood.com/

How to identify what are all the events are created in background jobs?

Hi all,
how to identify what are all the events are created for background jobs. And what events gets triggered for a particular job.
thanxs
haritha

Hi Haritha,
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.
Also Pls check DB02 for database performance and ST03 for workload .
Analyse u will have an idea ,
*pls assign points,if info is useful**
Regards
CSM reddy
null

How to submit a program after completion of a background job

Hi Experts,
I have a small issue. In my report program i am calling one transaction using call transaction it will trigger a background job. After completion of this background job i need to submit another program, Because the background job updating few values, using this value only the second program functionality will works.
Currently when i execute my report its calling 1st program and triggering the background job. Once the job started again the program triggering the next program. Here after competion of the background job only this program should submit next program. Anyone kindly suggest some clue.
    CALL TRANSACTION 'ZSAPRCK60' USING    zbdcdata
                            OPTIONS FROM g_s_options
                            MESSAGES INTO msg_tab.
SUBMIT SAPRCK10    VIA SELECTION-SCREEN
                    WITH kalaid = p-kalaid
                    WITH kaladat = sy-datum
                    WITH PARALLEL = 'X'
                    WITH SERVNUM = '10'
                    WITH backgr = 'X'
                    AND RETURN.
Mohana

Hi,
There is one function module there which gives you the job status .. if the job is finished then the value will be 'F'.I don't exactly remember the FM but then you can search with BDLSTATUS or BDSTATUS in SE37..
do.
call fm BD****STATUS
IF STATUS (IMPORT PARAMTER) eq 'F'.
exit.
endif.
enddo.
Regards,
Nagaraj

Triggering background job event from Unix script

Hi all,
I am having one question regarding triggering of background job in SAP using Events from Unix script. Is this possible? If so, can anyboy provide some sample code related to Unix script and how do we communicate to SAP from Unix system. Actually, here the backend of R/3 system is MSSQL. I am having a program in R/3 system which is scheduled as a background job based upon event trigger. I want to trigger that even from the unix script.
Appreciate for your help in advance.
Thanks,
Adithya K

Hi,
Check if this can help you
http://help.sap.com/saphelp_sm32/helpdata/en/fa/096e6b543b11d1898e0000e8322d00/content.htm
Regards,
Atish

Batch job scheduling based on Event AND for the job to complete

I am trying to schedule a background job based on an event AND based on the job finishing itself.
Example:
Job name: Send_Message
After Event: SAP_NEW_PROCESS Message
Program: Program xxxx
I want that the Send_Message job only runs when the Event SAP_NEW_PROCESS message happens AND the Send_Message job is not running.
Right now, I could only schedule it based on the event SAP_NEW_PROCESS Message which means that everytime this event happens the job runs and I end up having the job "Send_Message" in multilple intances where the others will immediately cancel since the first job is still running and so I end up with a lot of Cancelled job when it is not necessary to run them all when there is already 1 instance of the Job running.
How do I set it up in SAP?

Thanks but I am new to SAP having to set up a batch job.
The Event "SAP_NEW_PROCESS_MESSAGES" is a standard SAP Event. We used that such that when a new transaction comes in, the batch job will run but we don't want to run the batch job if the same batch job is already running.
YOu mentioned that I should set up Job_0. Do I need to create an ABAP prorgram to check if JOB_1 is running? How do I set up Job_0? What is the trigger for my Job_0 to run?
You also said that I set up Job_1 and trigger that based on the outcome of Job_0 AND at the same time be triggered by the event "SAP_NEW_PROCESS_MESSAGES". How do I set up this Job_1 so that it can be triggered by both Job_0 and a new transaction coming in(SAP_NEW_PROCESS_MESSAGES).
if you can provide me the step by step guide as I am new to this and I only know basic.
The current set up I have is
Job_1
Job Start:
      After Event
            Event: SAP_NEW_PROCESS_MESSAGES
      Step 1: program to run RCOCB002
I was thinking following your suggestion is this:
Job_0
Job Start
      After Event
            Event: SAP_NEW_PROCESS_MESSAGES
      Step 1: program to run - What will be my program to run?
Job_1
Job_Start
      After Event
            Event: What will be my trigger for Job_1 and how do I set it up?
      Step 1: program to run RCOCB002
Edited by: Shirley Te on Mar 10, 2010 3:25 PM

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

Periodic Scheduling of sequencial background job

I schedule monthly & weekly planning jobs. These jobs are scheduled one after another in a sequence. frequency of running these jobs is fix hence I want to schedule it on periodic basis. It possible for me to schedule single background job periodically but I don't know how to schedule sequncial backgorund jobs on periodic basis.
Regards,
Chetan

Dear Siva,
Thanks for your reply.
for execution of single job periodically I am following the same procedure mentioned by you.
I scheduled background jobs one after another by clicking on start condition & in pop-up select "After job". this way I schedule 7 to 8 jobs one after another.
So in first scheduled job you will find 7 to 8 successor jobs.
Now if I try to make it periodic, then only first job becomes periodic & successor jobs doesn't get released periodically.
I want to make entire chain of jobs to be scheduled peiodic.
Regards,
Chetan

Trigger a background job after executing tcode MMPV

Hi All,
I would like to trigger a background job after executing tcode MMPV. In MMPV, after closing a particular period and entering
new period, the transaction will be saved. After saving, the background job should be triggered. How to do it?
Regards,
Vinod

Depending what system you are on your best bet would be to create an enhancement point inside a form, that is called after the save has been performed, and raise an event within that form.
Events can be used to trigger background jobs are maintained in transaction SM62.
Cheers.

How to schedule a background Job based on events

Hi,
We are on 4.6 C.
We have a background job that has two ABAP programs.
We need to start the 2nd ABAP program only after the first one has run successfully.
If the second ABAP program does not run, the the job should have a status "FINISHED".
Help appreciated.
Thanks
Mala

Hi,
How to schedule a background Job based on events,please refer to the follow SAP help:
You can use events that have already been defined, or you can create new events for scheduling background jobs.
If you wish to use new events, do the following to implement the event scheduling:
Define and transport the event as a user event with transaction SM62.
You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
Do this to transport an event:
Create a transport request.
Start the editor in the transport request and enter the following:
R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event IDs that you have created.
Save and release the transport request. Ensure that it is imported into your production system(s).
To trigger an event, add:
the function module BP_EVENT_RAISE to your ABAP program, or
the program SAPEVT to your external script, batch file, or program.
When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
Schedule the jobs that are to run when your events are triggered.
You can schedule jobs for one-time start or to be started whenever an event is triggered.
Regards,
collysun

How to schedule a background job using the Event concept..?

Hi Folks,
I have a requirement that, I need a schedule a background job.
Once after the previous job successful only, new job should get triggered. How to go ahead with this..?
For Eg, I am scheduling a job called ZTEST periodically for 1 minute. If the job is not get completing with in 1 minute, I dont want to start my new job. Only after the success of my old job, I want my new job to run.
Waiting for ur replies.
Regards,
Savi.

Hi,
You can use events that have already been defined, or you can create new events for scheduling background jobs.
If you wish to use new events, do the following to implement the event scheduling:
Define and transport the event as a user event with transaction SM62.
You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
Do this to transport an event:
Create a transport request.
Start the editor in the transport request and enter the following:
R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event IDs that you have created.
Save and release the transport request. Ensure that it is imported into your production system(s).
To trigger an event, add:
the function module BP_EVENT_RAISE to your ABAP program, or
the program SAPEVT to your external script, batch file, or program.
When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
Schedule the jobs that are to run when your events are triggered.
You can schedule jobs for one-time start or to be started whenever an event is triggered.
Regards,
Raj.

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

How to trigger an existing background job in ABAP program?which fm?

Hi experts,
    how to trigger an existing background job( defined in SM36 ) in ABAP program?which fm?
    seems that FM 'JOB_OPEN' / 'JOB_SUBMIT' / 'JOB_CLOSE' can only create a new job.

Hi,
    now my requirement is that sap has generated one job automatically, and then i will have a job name
'XXX'. and then i want to schedule the job in abap program,. which function module could i use ?
my expected fm is that the system will trigger the job after i give the job name and start condition.
i have tried job_open, but it seems just to create a new job. any advice ?

What to add to an program code in order to trigger an background job

Hi there
I wander what to add to an program code in order to trigger an event which consequently can trigger an background job
thx in advance

Check this code:
DATA : v_jobhead LIKE tbtcjob.
DATA : v_jobcount LIKE tbtcjob-jobcount.
DATA : v_eventparm LIKE tbtcjob-eventparm.
DATA : v_flg_released TYPE c.
DATA: e_error.
DATA: running LIKE tbtcv-run.
TYPES: esp1_boolean LIKE boole-boole.
CONSTANTS: esp1_false TYPE esp1_boolean VALUE ' ',
           esp1_true TYPE esp1_boolean VALUE 'X'.
CONSTANTS: true TYPE boolean VALUE esp1_true,
                          false TYPE boolean VALUE esp1_false.
PARAMETERS: v_jobnam LIKE tbtcjob-jobname,
            v_report LIKE sy-repid,
            v_varian LIKE raldb-variant,
            v_uname LIKE sy-uname.
START-OF-SELECTION.
* add the new job
CALL FUNCTION 'JOB_OPEN'
       EXPORTING
*            delanfrep        = 'X'
            jobname          = v_jobnam
       IMPORTING
            jobcount         = v_jobcount
       EXCEPTIONS
            cant_create_job = 1
            invalid_job_data = 2
            jobname_missing = 3
            OTHERS           = 4.
IF sy-subrc <> 0.
    e_error = true.
ELSE.
    CALL FUNCTION 'JOB_SUBMIT' " or you can use SUBMIT statement as well.
         EXPORTING
              authcknam               = v_uname
              jobcount                = v_jobcount
              jobname                 = v_jobnam
              report                  = v_report
              variant                 = v_varian
         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.
      e_error = true.
    ELSE.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
*               EVENT_ID                    = IC_WWI_WORKPROCESS_EVENT
*               EVENT_PARAM                 = V_EVENTPARM
*               EVENT_PERIODIC              = 'X'
                jobcount                    = v_jobcount
                jobname                     = v_jobnam
                strtimmed                   = 'X'
           IMPORTING
                job_was_released            = v_flg_released
           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.
        e_error = true.
      ELSE.
        DO.
          CALL FUNCTION 'SHOW_JOBSTATE'
            EXPORTING
              jobcount               = v_jobcount
              jobname                = v_jobnam
*            IMPORTING
*         ABORTED                =
*         FINISHED               =
*         PRELIMINARY            =
*         READY                  =
*              running                =
*         SCHEDULED              =
           EXCEPTIONS
             jobcount_missing       = 1
             jobname_missing        = 2
             job_notex              = 3
             OTHERS                 = 4.
          IF sy-subrc <> 0.
            e_error = true.
            MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
          ENDIF.
          IF running = space.
            EXIT.
          ENDIF.
        ENDDO.
      ENDIF.
    ENDIF.
ENDIF.

How to trigger a background job from BADI method.

hi friends,
i need to trigger a background job from the badi method CHANGE_AT_SAVE for the BADI BOM_UPDATE.
for this i think i need to create an event which i should give with parameters during job creation.
can you pls help me solve this issue.
thank u all.

Hi Saravanan,
Here is an example of what you have to do.
Regards,
Eric
Reward any helpful sugestion.
*&      Form generar_job
FORM generar_job .
Generar Variante
PERFORM generar_variante.
w_fecha = sy-datum + 3.
CALL FUNCTION 'DATE_COMPUTE_DAY'
    EXPORTING
      date = w_fecha
    IMPORTING
      day = w_weekday.
Si la fecha cae en sabado o domingo se debe continuar el lunes.
CASE w_weekday.
    when '1'.
      ADD 2 TO w_fecha.
    WHEN '6'.
      ADD 2 TO w_fecha.
    WHEN '7'.
      ADD 1 TO w_fecha.
ENDCASE.
w_jobname = 'ZQM_CIERRE_LOTE_INSPECCION'.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobgroup         = 'QUEUE'
      jobname          = w_jobname
    IMPORTING
      jobcount         = w_jobcount
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
IF sy-subrc EQ 0.
    CALL FUNCTION 'JOB_SUBMIT'
      EXPORTING
        authcknam               = sy-uname
        jobcount                = w_jobcount
        jobname                 = w_jobname
        report                  = 'ZQM_CIERRE_LOTE_INSPECCION'
        variant                 = w_var
      IMPORTING
        step_number             = w_stepnum
      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 EQ 0.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = w_jobcount
          jobname              = w_jobname
          sdlstrtdt            = w_fecha
          sdlstrttm            = w_hora
        IMPORTING
          job_was_released     = w_rel
        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 EQ 0.
        IF w_rel EQ 'X'.
          WRITE:/ w_jobname, 'FUE LIBERADO. VER SM37.'.
        Guardamos los destinatarios
          PERFORM destinatarios_job.
        Guardamos la información a utilizar al ejecutar el job
          PERFORM guardar_datos_job.
        ELSE.
          WRITE:/ w_jobname, 'NO FUE LIBERADO'.
        ENDIF.
      ELSE.
        WRITE:/ w_jobname, 'NO FUE CERRADO'.
      ENDIF.
    ELSE.
      WRITE:/ w_jobname, 'NO FUE ENVIADO'.
    ENDIF.
ELSE.
    WRITE:/ w_jobname, 'NO FUE CREADO'.
ENDIF.
ENDFORM.                    " generar_job

KP97 background job trigger after an event

Similar Messages

Maybe you are looking for