Changing the Height of CAT2 Worklist

Symptom
You want to change the height of CAT2 worklist.
Solution
To increase the number of lines displayed in the worklist of transaction CAT2 please
perform the following manual changes below, which is also described in the longtext of
note 838688. Even if the note validity only refers to previous releases, this procedure is
also valid for other release.
1. Go to transaction SE80 and specify function group as CATS.
2. Go to screen 2020 and select the layout button to go to the layout of the screen.
3. Double click on the subscreen CATS001. Go to the Attributes and change the Min.
Lines to 8.
4. Double click on the subscreen CATS002. Go to the Attributes and change the Min.
Lines to 8.
5. Go to screen 2100 and select the layout button to go to the layout of the screen.
6. Double click on the table control TC_CATSW. Go to the Attributes and change the
Height to 9.
The Database table for the Time Sheet - CATSDB
Definition:
The database table for the Time Sheet (CATSDB) contains all the data that has been
recorded using the Time Sheet.
Use:
As soon as a user has entered and saved dat in the time sheet, the system writes the
record to CATSDB. When the records
have the processing status 30 (Approved) or 60 (Canceled), the system writes them to
the relevant interfaces tables in Human
Resources, Controling, Plant Maintenace/Customer Service, Project System, and
Material Mangement based on the working time
attributes that have entered.
Structure:
Listed below are important fields which are filled fro ecah record regardless of its
working time attributes or in the case of the

reference counter, can be filled:

Personnel number

Processing status

Counter
Each record that is stored in CATSDB is assigned a counter. The counter is assigned
by the system and is 12 digits long.
Reference counter If a record with the processing status 30 (approved) is changed,
the system also assigns it a reference counter
The reference counter is also 12 digits long.
A reference counter is assigned as follows: The original record is retained and its
processing status is chnaged from 30 (Approved)
to 50 (changed after apporval) or 60 (canceled). At the same time, the system
creates a new record to reflect the changes. The
new record is assigned the processing status 10 (in process), 20 (released), or
30 (approved), depending on profile settings. The
new record is assingned a reference counter to link it to the original record, which
now has the status 50 or 60. The reference counter
corresponds to the counter of the original record.

Document Number.
As soon as a record has the corresponding status 30 (approved), the system
assigns it a document number. The document number is
assigned sequentially and is 10 digits long. The document number represents the
key fro identifying the record, even after it has been
transfered to the target components.
In addition, the system also provides information on the person who created the record,
when the record was created and, if necessary, on
person who changed the record and when it was changed. You can also see whether a
short or long text exist for the record.

1.

ERP Human Capital Management

2.

3.

Getting Started in CATS

Cancelation of Time Sheet Data
Use
A user can cancel data that has already been recorded and saved in the time sheet by
deleting, or changing to zero ("0), the cell contents (hours, unit of measurement,
amount) and, if necessary, the start and end clock times and the full day indicator. If you
want the system to treat the record as canceled , the following fields must be blank in
the database table fo time sheet (CATSDB). CATSHOURS (hours). CATSQUANTITY
(number Unit), CATSAMOUNT (Amount), BEGUZ (start time), ENDUZ (End Time) and
ALLDF (full day indicator).
Cancelation Process in relevant tables.

The database table for the Time Sheet (CATSDB). The original record is
assigned the processing status 50 (change after approval) or 60 (canceled).
Wich of these statuses the system first assigns depends whether or not the record
must be approved. If appproval is requered, the system first assigns the record status
50 adn then 60 once it has been approved. If no approval is required fro the record, it is
asiggend status 60 straight away.
The system creates a new record for the canceled record. The new record is linked to
the original record by a reference counter. The reference counter of the new (canceled)
record corresponds to the counter of the original record. Depending on your customizing
settings, the new record may also need to be released or approved.
The same principle applies to records whose cell content (number of hours, unit of
measurement, amount) is changed after approval to an amount other than zero.

The Interface tables of CO, HR,PM, PS.

In the interface tables, the system creates an almost identical record with cancelation
indicator (STOKZ) for a record in CATSDB with the processing status 60 (canceled).
The new record has the same number of hours and document number in the interface
tables as the original record and, in addition, a cancelation indicator.
The system use the document number from the link between the original and the
cancelation record. The codument number is stored in the Human Resources interface
tables (PTEX200 and PTEX2010) in the AWKEY field. In the other interface tables, you
can find the document number in the BELNR field.
If you cancel a record before it is transfered to the target components, the system
transfers neiter the original nor the cancelation record. In Human Resources, both
records reamin in the interface tables for the Human Resources. In the other traget

components, the system deletes the original record and the cancelation record form the
interface tables.
If you cancel a record that has already been tranfered to the target components, the
system also transfer the cancelation record, that is the record assigned the cancelation
indicator.
For Material management: If a record is canceled after it has been transfered. the
cancelation record cannot be transfered to Materil management. In this case, the record
must be canceled in Materials Management.

Posting Canceled records in the target components.

If a record is canceled before it is transfered to the traget componnets, the system
transfers neither the original or the cancelation record to the target components. If the
record is canceled after it has been transfered, the cancelation records are posted in the
target componnets as follows:

1.

Controling: the system post the cancelation record as a negative record. If the
original records, contains, for example, 8 hours, the system post the cancelation record
with -8 hours.

2.

Human Resources: The cancelation indicator enables the system o recognize

that both original records cancel each other out. The system deletes the original record
form the relevant infotypes (PA2001, PA2002 and PA2010) based on this information.

3.

Plan Maintenace (PM) and projects system (PS): The system creates a reversal
document in the relevant target component. Transfering canceled data to PM can
adversely affect system performance. There are more information about into the reprots
RCATSTPM or RCATSTPS.

4.

Material Management: A cancelation record cannot be transfered to Materisl

Management. For this reason, you should only make chnages to records that have
already been transafered in the Material Management component.

CAC1 customizing and System reaction in CATSDB

Purpose:
Into the CAC1 transactions you can control the system reaction into the process, Save,
Release, approval, cancel or change one entry in CAT2. Here we have different
scenarios related to the CATSDB table entries.

Overview:
With the customizing into the checks "Release on Savin" and "Approval Required" of
the CAC1 transaction, we can find 4 different scenarios or system reactions, about how
the information is saved into the data base table CATSDB.
Scenario 1:
If into the CAC1, for the CATS Profile, the check are:

"Release on Saving" is Set

"Approval Required" is not Set

CATSDB Table reaction:
Action

Record

Hours
CATSHOURS

Status

Counter

Enter
Data

New

30

1000

100

Change

Original

60

1000

100

Changed

30

1001

1000

101

Scenario 2:
If into the CAC1, for the CATS Profile , the check are:

"Release on Saving" is not Set

"Approval Required" is not Set

Refcounter

Doc.No.
BELNR

CATSDB Table Reaction:

Action

Record

Enter
Data

New

Release

Change

Release
d

Hours
CATSHOUR
S

Statu
s

Counte
r

10

2000

Original

30

2000

200

Original

50

2000

200

Change
d

10

2001

2000

Original

60

2000

200

Change
d

30

2001

2000

201

Scenario 3
If into the CAC1, for the CATS Profile , the check are:

"Release on Saving" is Set

"Approval Required" is Set

CATSDB Table Reaction:
In case the Approval is granted:

Refcounte
r

Doc.No
BELNR

Action

Record

Enter
Data

New

Approve

Change

Approve

Hours
CATSHOURS

Status

Counter

Refcounter

Doc.No
BELNR

20

3000

Original

30

3000

300

Original

50

3000

300

Changed

20

3001

3000

Original

60

3000

3000

300

Changed

30

30001

301

In case the Approval is denied:

Enter Data

New

20

3010

Reject

Original

40

3010

Change rej.
records

Original

20

3010

Scenario 4
If into the CAC1, for the CATS Profile , the check are:

"Release on Saving" is not Set

"Approval Required" is Set

CATSDB Table Reaction:

In case the Approval is granted:

Action

Record

Enter Data

New

Release

Status

Counter

10

4000

Original

20

4000

Approve

Original

30

4000

400

Change

Original

50

4000

400

Changed

10

4001

4000

Original

50

4000

Changed

20

4001

Original

60

4000

Release

Approve

Hours
CATSHOURS

Refcounter

4000

Doc.No
BELNR

400
-

400

Action

Record

Hours
CATSHOURS

Changed

Status

Counter

30

4001

Refcounter

Doc.No
BELNR

4000

401

In case the Approval is denied:

Enter Data

New

10

4010

Release

Original

20

4010

Reject

Original

40

4010

Change rej.
records

Original

10

4010

About SCN
Downloads
Industries
Training & Education
Partnership
Developer Center

Lines of Business
University Alliances
Events & Webinars
Innovation

Skip to content

Skip to breadcrumbs

Skip to header menu

Skip to action menu

Skip to quick search

Spaces

Browse

Quick Search

1.

ERP Human Capital Management

2.

3.

Getting Started in CATS

Impact of Data Entry Profile (DEP) in CATS

Skip to end of metadata

Created by Kumud Singh, last modified by Marlene Guberner on Jul 11, 2014
Go to start of metadata
Purpose
How does Data Entry Profile impact inserting data into database table CATSDB.
Overview
Exploring different sections of DEP screen and understanding their significance.
Data Entry Profiles while updating CATSDB
Transaction code: CAC1.
Related transparent table: TCATS

In Tcode CAC1 all the configured profiles for CATS can be seen.
SAP-Press book Integrating CATS by Martin Gillet can be a good start for more details.
DEP explicitly controls defaulting of values, approval procedure, error conditions while
inserting records into CATSDB.Certainly its impact is not limited to the one mentioned.

When a user makes a timesheet entry for any day, the entry has to be released. This
can be defaulted with DEP. When an employee makes a timesheet entry either the entry
can be sent to manager for approval or the entry can be auto approved. (status is 30 in
table CATSDB). This can be controlled by DEP. As already highlighted that DEP
controls whether records of multiple employees can be updated at one shot or not.

Default values section determines the values to be defaulted while making entry in
timesheet. An entry can be made in Timesheet via Tcode CAT2.

Few Error conditions returned by BAPI too can be controlled by DEP. For e.g. there can
be a situation an employee can work simultaneously on multiple activities (labor and
machine operations). In that condition BAPI should not throw any error.
1.

ERP Human Capital Management

2.

3.

Getting Started in CATS

Fixed Columns in the Table Control of CAT2
Skip to end of metadata

Created by Jonatas Silveira, last modified by Marlene Guberner on Jul 11, 2014
Go to start of metadata
Purpose
The purpose of this page is to describe how to fix columns in the data entry of CAT2
and explain further how the configuration works so that you can set up the system
correctly.
Overview
When using CAT2 transaction, depending on how many columns are displayed for the
user an horizontal scroll bar appears in the data entry. This can lead users to scroll left
and right several times to input their working times in CAT2. In this page we describe
how to fix some columns of the data entry and how this configuration works.

Fixing columns in the Data Entry

In order to fix columns in the Data Entry of CAT2 you need to follow the steps below:
a) Click on the configuration button (it's on the right corner of the Time Sheet);
b) Click in the "Administrator" button*;
c) Modify the "No. of fixed columns" field;
d) Click Activate;

e) Create a new display variant by entering a name into the regarding text-field;
f) Click on "Create" button;

g) Your variant name will appear in the settings fields;

h) Now click on "Save" button;

*This function is linked to the authorization object 'S_ADMI_FCD'. So you need enough
authorizations in order to have this button available.
Did it work?
It is possible that after reproducing the mentioned steps you have not reached the
expected behavior. So here we will explain how this works so that you can configure

accordingly.
When you set a number, e.g. 10 in the "No. of fixed columns" field, you are configuring
the system to fix the first 10 available columns. No matter if they are visible or not. So,
back to the first provided screenshot, if we set 10 for the fixed columns the "visible"
result is only 2 fixed columns: CATSFIELDS-ASTERISK (this is always visible) and
CATSD-SEBELN (the only visible one among the 10 first).
Furthermore, please bear in mind that the area of fixed columns is set to scrollable if the
fields of your variant activated via CAC2 use more than 2/3 of table control. If you would
like, you could increase the factor to up to 9/10. The area which cannot be scrolled is
90% then. If you do not have any fixed columns or want only a small number of fixed
columns, you can reduce the factor as appropriate. Please have a look at the SAP
Note 138267, which describes the corrections to be fulfilled. Although the note is for old
releases, this is still valid for the ongoing one.

More information on the CATS traget components

Purpose:
The prurpose of this wiki article is a description of the Non HR tables that are involve into the CATS process of CAT2, CAT5,
CAT7 and CAT9 transactions.

Overview:
The interface tables for the TIme Sheet are used to provide time sheet data for transfer information to the corresponding
traget components, like Controling, Material Management, Plant Maintenance/Customer Service and Project System.

1. Controlilling Tables
Two other tables are important for Controlling: CATSCOSUM ( Data Transfer: Time Sheet -> Co Summarization Table) and
CCATSCOSUM (Settings: Summarization Time Sheet Data -> CO). You use these tables to control how records are
summarized when filling CO documents.

Table CCATSCOSUM is the Customizing table in which you enter whether and, if so, how the timesheet data is
summarized.

The system uses table CATSCOSUM to form a link between a CATSDB record and the CO document in which the
record is transferred. This table is only filled if you have determined that records are to be summarized for transfer.
If your Customizing settings determine that the transfer timesheet data is summarized, the Counter field in CATSCOSUM
corresponds to the field with the same name in CATSCO. However, when the records are summarized, there is no longer a
1:1 relationship between the Counter (COUNTER) and Document number (TRANS_NO) refers in most cases to several
counters (COUNTER) in CATSCONSUM. Table COBK (CO Object: Document Header) is the table in Controlling to which

the time sheet data is transferred. This table contains one entry in the Reference document number (_REFBN)_ for each
different document number (TRANS_NO) in CATSCONSUM.

In the CATSCONSUM tabble, counters 100, 101, 102, 110 ,114 and 120 are stored with the document number
(TRANS_NO) 10 and counters103 to 109 and 113, 122 with_ document number_ (TRANS_NO) 11. In table COBK then,
there are two entries in the Reference document number field (REFBN): 10 and 11.
If you specified in your Customizing settings that time sheet data is not summarized for transfer to controlling, CATSCUSUM
is not filled with these records. In this case, there ia a 1:1 relationship between the document number (BELNR) in CATSDB
and Reference document number field (REFBN) in COBK.
If there are inconsistencies in the data Controlling, we recommend you call the Display CO Cost Segmentes transaction
(RKASHOW). You can use this transaction to display information on data statutes and tot6als records in Controlling tables.
For information on how to proceed if confirmations lead to CO documents with erros, see the note 0155282 (CO Docs fro
Confirmations: Corrections Programs).
Other tables in Controlling that you should be familiar with in this context are:

COEP (CO Object: Line Items, by period)

COSS (CO Object: Cost Totals for Internal Postings)

COEPL ( CO Object: Line Items for Activity Types by Period)

COSL (CO Object: Activity Type Totals)

A CO document consists of line items, which represent the values of a record. The line items are stored in tables COEP or
COEPL. Tables COSS and COSL contain the period totals of all the actual postings to a CO object.

2. Materials Management
When time sheet data is trabsfered to Materials Management, table ESLL (lines of Service Package) and table ESSR
(Service Entry Sheet Header Data) are supplied with data. The Package number (PACKNO) field forms the link between the
two tables.
The time sheet record is referenced in table ESLL by the Document number (BELNR) field. However, in Material
Management, you can only identify the record uniquely in connection with table ESSR.

3. Plant Maintenance/Customer Service and Project System

If you transfer data to Plant Maintenance/Customer Service (PM/CS) or to Project Sysytem (PS), you trigger an internal
activity allocation. For this reason, the data is also transafered to Controlling. If goods movements are defined in your order,
the data can also be relevant for Materials Managament (MM). If data is transafered successfully, the system writes it to the
relevant tables in the target components. For PM/CS and PS the relevant table is AFRU. For controlling the table is COBK
and for Materials Management they are MKPF and MSEG.
If errors occur when data is transfered to PM/CS os PS, the system stores the data containing errors in the follwoing tables:

Confirmations with errors: AFRH, AFRV

Actual cost with errors: AFRC

Goods movements with errors: AFFW

Once you processed the errors, the system post the data in the target components.

Overview on CATS
1) first of all , you have to config the cats profile by using tranx CAC1 , if any approvals , ask to workflow consultant and get
the Task id, assign into profile.
you have to discuss with FICO guys and get he cost center, acivity type
and discuss with PS consultant and get the reciever WBS element.
Our part , config. the att.type in time side.
2) go to transaction - CAT2 and enter the time sheet based on above details.
3) trans: CATS_APPR and approve timesheet
if you want transfer the att.hours to hr master data (IT2002),
you have to active the checkbox under HR TIme
4) process CAT5,CAT6 and CAT7 (post to the desired component )