High- Level Specification

Parameter	Value
Application System	SAP S/4HANA - [ECP] (China instance) SAP S/4HANA - [ERP] (Rest of World instance)
Business Process Reference	10.02.03.04. Manage Project Time Allocation

Functional Overview

Time booking for projects is managed through the My Timesheet application. In certain situations, it is necessary to record time spent on non-project activities (such as Technical Assistance Service Global (TAS), Management, ATCO (Activités Techniques COmmunes), Union activities) to enable tracking and reporting, without affecting budgeted project financials.

Statistical WBS Elements are utilized for logging hours not directly related to specific budgeted projects, primarily to monitor business-as-usual costs. These projects are created by Financial Controllers for reporting purposes only.

When the statistical WBS element holds a posting cost center and is used for time booking, the CATS input field Receiver WBS element will receive the statistical WBS element and the actual cost is posted on the cost center mentioned as posting cost center on the WBS element. By default, the posting cost center held by the statistical WBS element is the Receiver cost center on the CATS posting. This is a SAP standard behavior. 

However, when no posting cost center is maintained on the statistical WBS element (field left blank), the system requires a Receiver Cost center to complete the posting. This enhancement will substitute the employee or contingent worker’s cost center to the Receiver Cost Center field.

This enhancement streamlines the process by automatically populating the Receiver cost center when users save their timesheet entries and when the statistical WBS element does not hold a cost center, eliminating the need for manual input.

Scope and Objectives

Statistical WBS elements are designed to capture non-project time for reporting. Since no costs are posted directly to statistical WBS elements, each time entry must specify a receiver cost center.

In standard SAP, the cost center can be derived from the WBS element itself. However, in some cases, this approach would require duplicating some of the statistical WBS elements which are meant to cover multiple cost centers, which is inefficient. To address this, when no posting actual cost center is assigned to a statistical WBS element, the receiver cost center should be automatically provided during the time posting process.

Assumptions

Dependencies

ERP-164 CATS Enhancement for Intercompany Recharge: FS introducing the custom field Posting WBS element and auto-populates the CATS standard field Receiver WBS element. 

Security, Integrity and Controls

N/A

Configuration Requirements

N/A

Language Requirements

N/A

Special Requirements

N/A

Design Rationale

Functional Requirements

This enhancement aims to streamline time entry for non-project activities by automatically populating the Receiver Cost Center field with the employee’s home cost center when a statistical WBS element is selected in CATS/My Timesheet and this statistical WBS element does not have a posted cost center assigned. By automating this process, the solution eliminates manual input, reduces errors, and ensures accurate cost allocation for business-as-usual time tracking.

1. WBS Element Selection When a user selects a WBS element in the custom Posting WBS element (CATSWBS) in My Timesheet application, the system must recognize this selection for further processing.

2. ERP-164 CATS Enhancement for Intercompany Recharge, assigns the standard field Receiver WBS element with the the Posting WBS element selected by the end user for all statistical WBS elements. This step therefore checks if the selected WBS element is statistical. 

3. If the WBS element was identified as statistical in step 2: 

   1. case 1: Users' company code = WBS element company code therefore Posting WBS element = Receiver WBS element (from step 2): check if the standard CATS input field Receiver Cost Center is populated with a cost center: 

      1. Receiver cost center is populated with a cost center: this means that the WBS element is maintained with a posting Cost center. So the entry can be submitted and saved with no further action. 

      2.  Receiver cost center is not maintained with a cost center: the system must automatically populate the Receiver Cost Center field with the employee’s home cost center (automatically set in the CATS field Sender Cost center). 

   2. case 2: Users' company code is different from WBS element company code therefore Posting WBS element = Receiver WBS element (from step 2): no cost center check is necessary. This case will issue a standard error at saving. 

4. Saving the Entry The timesheet entry (when statistical WBS element) must be saved with the Receiver Cost Center field populated as described above, ensuring accurate and automated cost allocation for statistical WBS elements.

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

The objective is to automatically populate the Receiver Cost Center field with the employee’s (PERNR’s) cost center when a statistical WBS element is selected.

1. WBS Element Selection:
   The user selects a WBS element from the custom Posting WBS element field (CATSWBS).

2. Receiver WBS element:
   Functional Specification ERP-164 checks if the WBS element selected is statistical or not and ensures that the selected Posting WBS element = Receiver WBS element (CATSDB-RPROJ) if the Posting WBS element is assigned to the same company code as the user. 

3. Cost Center check and assignment:

If the selected WBS element is statistical (step 2), and belong to same company code as the user (checked in step 2) check that the CATS standard input field Receiver Cost Center CATSDB-RKOSTL has no value received. 

• •  if CATSDB-RKOSTL is blank the system populates it with the value in Sender Cost Centre CATSDB-SKOSTL:
    • copy Sender Cost Centre CATSDB-SKOSTL into Receiver Cost Center CATSDB-RKOSTL

1. • If CATSDB-RKOSTL has a value assigned, no enhancement necessary.
   • The timesheet entry is then submitted and saved.

User exit CATS0002 (Supplement recorded data), also referred to in ERP-164 can be used. This user exit enables modification of the user’s entry, allowing the Receiver WBS element to be set before saving.

Volumetrics

N/A

Performance Considerations

Error Handling

N/A

Testing

How to Test

The test must be executed first in the CATS backend transaction (CAT2) and then My Timesheet V4 (Fiori application).

To ensure successful testing, the following conditions must be met for the tester’s user:

1. User–Personnel Link

   • The tester’s User ID must be linked to a valid Personnel Number (PERNR) through Infotype 0105 (Communication).

2. Personnel Master Data On the same Personnel ID:

   • Infotype 0315 (Time Sheet Defaults) must contain a valid Activity Type.

   • Infotype 0001 (Organizational Assignment) must contain an assigned Cost Center.

3. Costing Data

   • A valid price (rate) for the combination of Cost Center / Activity Type must be maintained for the testing period.

4. CATS Profile - User Parameter

   • User parameter CVR must be set to the Data Entry Profile that will be used for time entry.

5. Create 2 statistical WBS elements within the same company code as the user, one with a posting cost center assigned (different than the user's cost center) and one without. The WBS elements must be replicated in the custom table Posting WBS elements /SYQ/T_CATSIC.

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Change log