Entering content frameBackground documentation Technical Background Information Locate the document in its SAP Library structure

The purpose of this section is to familiarize you with the technical processes in the Time Sheet. The graphic below shows which tables the system uses to process the recorded time sheet data.

Technical Processes of the Time Sheet

This graphic is explained in the accompanying text

 

1. All recorded time sheet data is stored in the database table for the Time Sheet, CATSDB.

2. The system automatically writes time sheet data that has the status 30 or 60 to the relevant interface tables.

The system determines which data belongs in which interface tables based on the working time attributes entered for the record.

3. When the data transfer report is executed, the data is transferred from the interface tables to the corresponding target components. Data is transferred to Materials Management using transaction CATM. The data is transferred from the interface tables to the following tables for the target components:

Human Resources

PA2001 (Absences infotype); PA2002 (Attendances infotype); PA2010 (EE Remuneration Info infotype).

Controlling

COBK (CO Object: Document Header)

Plant Maintenance/Customer Service

AFRU (Order Completion Confirmations)

Project System

AFRU (Order Completion Confirmations)

Materials Management

ESLL (Lines of Service Package)

Each of these tables contains a key, which corresponds to the BELNR (document number) field in table CATSDB. The system uses this key to form a link with the record in table CATSDB. The keys have the following names in the tables:

PA2001, PA2002, PA2010

AWREF

COBK

REFBN

AFRU

CATSBELNR

ESLL

BELNR

 

More information on the target components

Controlling

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.

If your Customizing settings determine that the transferred time sheet 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) fields in CATSCOSUM. A value in the Document number field (TRANS_NO) refers in most cases to several counters (COUNTER) in CATSCOSUM.

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 field (REFBN) for each different document number (TRANS_NO) in CATSCOSUM.

Example

In the CATSCOSUM table, counters 100, 101, 102, 110, 114, and 120 are stored with the document number (TRANS_NO) 10 and counters 103 to 109 and 113 and 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, CATSCOSUM is not filled with these records. In this case, there is a 1:1 relationship between the Document number field (BELNR) in table CATSDB and the Reference document number field (REFBN) in table COBK.

Note

If there are inconsistencies in the data in Controlling, we recommend you call the Display CO Cost Segments transaction (RKACSHOW). You can use this transaction to display information on data statuses and totals records in Controlling tables.

For information on how to proceed if confirmations lead to CO documents with errors, see note 0155282 (CO Docs for Confirmations: Correction Programs).

Other tables in Controlling that you should be familiar with in this context are:

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.

Materials Management

When time sheet data is transferred 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 Materials Management, you can only identify the record uniquely in connection with table ESSR.

Plant Maintenance/Customer Service and Project System

If you transfer data to Plant Maintenance/Customer Service (PM/CS) or to Project System (PS), you trigger an internal activity allocation. For this reason, the data is also transferred to Controlling. If goods movements are defined in your order, the data can also be relevant for Materials Management (MM).

If data is transferred 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, tables MKPF and MSEG.

If errors occur when data is transferred to PM/CS or PS, the system stores the data containing errors in the following tables:

Confirmations with errors

AFRH, AFRV

Actual costs with errors

AFRC

Goods movements with errors

AFFW

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

 

 

 

Leaving content frame