Skip to Content

Optimize CATS data transfer jobs with system variables

In this short document I will illustrate the use of system variables that can minimize the number of error messages during CATS data transfer to application components, as well as show the background job setup with Job Wizard function.

During CATS data transfer to the application components such as PS and PM modules the common error is about accounting period being closed.  Same time there are many business situations when users should report or correct time in past periods.  Both CAT5 and CAT9 data transfer transactions are using a working date as default posting date.  Such default system approach is reasonable for the current period, but for past periods the posting date should be adjusted to avoid the above mentioned error.

My recommendation is to run at least one daily background job for CATS transfer.  It helps to keep a data volume relatively low as opposed to month-end job, as well as the cost can be reflected at controlling objects in PS/PM info system with a minimum delay.  And that also means the BI system will get that information faster too (if applicable).

The idea is to run not a single job, but two different jobs.  One job will be dealing with the time reported for past periods (and those records will require a change of the Posting date). Another job will be dealing with time reported for the current period (and we can keep default logic for the Posting date).

While business users are also allowed to report a future time, that can be related either to the early month-end closing process or to periods of future absence, in my example time beyond the current period is not transferred.

My selection variant for CAT9 job accounting for Previous Periods would look like below:


The Posting and Cancellation dates are defaulted to the first day of the current period.

My selection variant for CAT9 job accounting for Current Period would look like this:


For the Current period variant I am not defaulting any fixed Posting Date/Cancellation date.

Next I can create and schedule daily background jobs for both variants in transaction code SM36

To create a background job I do recommend using the Job wizard as it offers quite a user-friendly experience.

From the icon bar select the Job Wizard on the right hand side as shown on the below screen:


Few next screens are covering the process sequence from the Job wizard, where you have possibility to browse forward or backwards at any time:









Click on the Complete button to finish the setup.

For the second job the process is exactly the same, except that you can use a different start condition to pair them together:


You are welcome to suggest improvements to this content.

Thank you for reading,


You must be Logged on to comment or reply to a post.
  • Hi Paulo,

    Nice Article as always.. Just one thought here.. Instead of using CAT5 or CAT7 or CAT9.. users will be better off using CATA and transfer to each of the components in one job..

    Instead of creating separate jobs for each target components..



    • Thank you, Sammar!  Yes, basically there are 4 components: HR, CO, PS, PM/CS.  The last 3 are never combined together, so it is just HR that can be used on top of any other from last 3.

      I never came across the setup when CATS data is used for Payroll or Time Management information in HR.  Maybe you can share your experience about HR transfer!

      • I remember using CATA in BELL, but don't recollect now whether it was for PM and PS orders or HR.. was long back..

        Now thinking @ the point you mentioned. makes sense to go with individual processing.. easy to handle errors for each area.. 🙂



    • Hi Sammar,

      Actually CATA does not cover all the scenarios.  There is CATM for the transfer to MM-SRV and I think it should be automatic for cProjects with ALE connection.