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 to enable tracking and reporting, without affecting project financials.

Statistical WBS Elements are utilized for logging hours not directly related to specific projects, primarily to monitor business-as-usual costs. These elements are created by Financial Controllers for reporting purposes only, with costs assigned to the employee’s or contingent worker’s cost center. This enhancement streamlines the process by automatically populating the Receiver cost center when users save their timesheet entries, 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, this approach would require creating duplicate WBS elements for each cost center, which is inefficient. To address this, 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. 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 field (CATSWBS) in My Timesheet application, the system must recognize this selection for further processing.

2. Receiver WBS element ERP-164 There is a dependency with ERP-164 CATS Enhancement for Intercompany Recharge. The field Receiver WBS element is auto-populated based on the Posting WBS element selected by the end user. Once the standard field Receiver WBS element is auto-populated, the system checks if the assigned WBS element is statistical (step 3).

3. Statistical Check and Cost Center Assignment After the Receiver WBS element (CATSDB-RPROJ) is populated, the system checks if this WBS element is statistical.

   1. If the WBS is a statistical WBS element, the system must automatically populate the Receiver Cost Center field with the employee’s home cost center (as maintained in the employee’s master data at the posting date).

   2. If the WBS element is not statistical, the system should take no further action.

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 ensures that the selected Posting WBS element derives the standard field Receiver WBS element (CATSDB-RPROJ) using the user exit CATS0002 (Supplement recorded data). This user exit enables modification of the user’s entry, allowing the Receiver WBS element to be set before saving.

3. Statistical Check and Cost Center Assignment:
   After the Receiver WBS element has been auto-populated via enhancement ERP-164 (step 2), the system verifies whether the Receiver WBS element (RPROJ) populated is statistical:

   • The value in CATSDB-RPROJ is checked against the PRPS table.
   • If the XSTAT indicator is set to ‘X’ (statistical), the CATS input field Receiver Cost Center CATSDB-RKOSTL field is automatically filled with the employee’s home cost center:
     • Get the Personnel id (PERNR)
     • check the assigned cost center PA0001-KOSTL for the validity date as per the posting date
     • posting date is the date selected by the user to post the time entry
   • If the WBS element is not statistical, no further action is taken.

4. Save Entry:
   The timesheet entry is then saved with the appropriate Receiver Cost Center populated as needed.

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 a statistical WBS element within the same company code as the user.

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