Skip to end of metadata
Go to start of metadata

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.


 

  • No labels