Hello @reimccabe 

I was studying the procedure that run behind the background job.

If you right click on the background job and select details. You can see the package name is  Batch_Sys.Fnd_Light_Cleanup.

After see the code, It looks like the job do some cleaning of Background Job depending the result per background job.

       tnum_ := to_number(Fnd_Setting_API.Get_Value('KEEP_DEFJOBS'));
      Transaction_SYS.Cleanup__(tnum_, 'Ready');
      tnum_ := to_number(Fnd_Setting_API.Get_Value('KEEP_DEFJOBS_WARNING'));
      Transaction_SYS.Cleanup__(tnum_, 'Warning');
      tnum_ := to_number(Fnd_Setting_API.Get_Value('KEEP_DEFJOBS_ERROR'));
      Transaction_SYS.Cleanup__(tnum_, 'Error');
      Transaction_SYS.Cleanup_Executing__;

Inside the Fnd_Setting_API.Get_Value() 

runs the following query where the parameter could be in ('KEEP_DEFJOBS','KEEP_DEFJOBS_WARNING','KEEP_DEFJOBS_ERROR','Error') but in Number 

SELECT value
         INTO  temp_
         FROM  fnd_setting_tab
         WHERE parameter = parameter_;

It will be something like this 

         select  value FROM  fnd_setting_tab
         WHERE parameter = 'KEEP_DEFJOBS_WARNING';
         
         SELECT value 
         FROM  fnd_setting_tab
         WHERE parameter = 'KEEP_DEFJOBS_WARNING';---- 30
         
         select  value 
         FROM  fnd_setting_tab
         WHERE parameter = 'KEEP_DEFJOBS';----- 7
         
         select  value 
         FROM  fnd_setting_tab
         WHERE parameter = 'KEEP_DEFJOBS_ERROR';---180

       select  value 
         FROM  fnd_setting_tab
         WHERE parameter = 'ERROR';

All of them return a varchar as a number but the T0_NUMBER will parse the data to Number into the tnum variable.

After that the =>

Transaction_SYS.Cleanup__(tnum_, ''); Start removing the old background job
 Transaction_SYS.Cleanup_Executing__; to execute the clean

I was wondering about the following lines inside the TRANSACTION_SYS.CLEANUP()

General_SYS.Check_Security(service_, 'TRANSACTION_SYS', 'Cleanup__');
   OPEN get_recs;
   LOOP
      FETCH get_recs BULK COLLECT INTO trans_id_ LIMIT 1000;
      FORALL i_ IN 1..trans_id_.count
         -- Remove old background jobs
         DELETE
            FROM transaction_sys_local_tab
            WHERE id = trans_id_(i_);

      FORALL i_ IN 1..trans_id_.count
         -- Remove status rows
         DELETE
            FROM transaction_sys_status_tab
            WHERE id = trans_id_(i_);
      -- Commit to avoid snapshot too old error
      --@ApproveTransactionStatement(2013-11-08,haarse)
      COMMIT;
      EXIT WHEN get_recs%NOTFOUND;
   END LOOP;

The limit is set up to 1000. I am wondering you have more than 1000.

Please, do not do any change to the code directly. I am giving an opinion. I am not a IFS employee with experience directly into the application. I was reading all the code created to remove the old background job. 

You should probably open an IFS ticket they can guide you in how to fix the issue.

I hope this help!

Thanks,

JL

Hello JGOTA, thanks for the quick response!  I am actually not a technical person but I think I see what it’s doing: you can have different deletion intervals set for jobs in state “ready” vs. error and warning and this is based on the system parameters.  The background jobs are currently getting cleared in PROD as expected but I was wondering if it is Light Cleanup that is doing it and it appears it is.  I think the job “background job cleanup” that we have scheduled is obsolete and we can disable it.  I’ll test it first.

I’m not interested in changing code, I just wanted a better list of what all light cleanup does and this answers part of that.

Mary

Hi @reimccabe 
Light cleanup removes data from Background Jobs, Foundation1 Session information and replicates IAL objects.

The Light Cleanup process will remove Background  jobs in state Ready, Warning and Error unless they are marked to be excluded from cleanup. 

More details available in the below IFS documentation
IFS Cloud Technical Documentation

-Kelum