You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Status

  Approved

OwnerFRUTEAU-ext, Sabrina 
Stakeholders
Jira Request ID

ERP-945 - Getting issue details... STATUS

Jira Development ID

ERP-1455 - Getting issue details... STATUS

High- Level Specification

ParameterValue
Application System

SAP S/4HANA - [ECP] (China instance)

SAP S/4HANA - [ERP] (Rest of World instance)
Business Process Reference10.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 (business-as-usual, BAU) 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 BAU 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 project structures (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 object, specifically, 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.


Process Flow Diagram


Step

Description

Comment

1From My Timesheet application, user creates a new entry and selects a Statistical WBS element to record non project time. 
2Time is entered on the statistical WBS element. User submit the entry and save. When user submit the entry, the standard field Receiver Cost Centre is being populated by the cost center assigned to the personnel id (from HR record). 
3Entry is saved. The Receiver cost center is the sole cost receiver.  


Assumptions

Dependencies

ERP-164 CATS Enhancement for Intercompany Recharge: FS introducing the custom Posting WBS element field. 

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) during time entry, the system must recognize this selection for further processing.
  2. Field Synchronization ERP-164 There is a dependency with ERP-164 specification. 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.

  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).

    2. If the WBS element is not statistical, the system should take no further action regarding the Receiver Cost Center field.

  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

TableField NameComments/Calculation/Field Manipulation











Data Validation Considerations

TableField NameComments/Calculation/Field Manipulation













Custom Tables

Master Data

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

Field NameDescription

Select:

Data Type/LengthDefault Value/ Validation rule/ Value HelpSelection Logic













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. Field Synchronization:
    Functional Specification ERP-164 ensures that the selected Posting WBS element is synchronized with the standard Receiver WBS element field (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, 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 (from PERNR, check PA0001-KOSTL).
    • 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


Testing

How to Test

Test Conditions and Expected Results

IDConditionExpected Result










Test Considerations/Dependencies


Other Information


Development Details

Package

Package NameParent Package




Enhancement Implementation

Enhancement TypeStandard Definition NameCustom Implementation NameDesign Rationale Reference









Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign Rationale Reference








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.

ABAP

ZFIZMMZPSZCOZSDZBCZFIZCA
TABLESZFITZMMTZPSTZCOTZSDTZBCTZFITZCAT

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 5) Mar 25, 2026 08:15 TORRES-ext, Benedict
v. 30 Mar 25, 2026 08:14 TORRES-ext, Benedict
v. 29 Mar 24, 2026 09:01 FRUTEAU-ext, Sabrina
v. 28 Mar 23, 2026 14:27 FRUTEAU-ext, Sabrina
v. 27 Mar 13, 2026 08:04 FRUTEAU-ext, Sabrina
v. 26 Mar 13, 2026 07:45 FRUTEAU-ext, Sabrina
v. 25 Mar 13, 2026 07:43 FRUTEAU-ext, Sabrina
v. 24 Mar 13, 2026 07:43 FRUTEAU-ext, Sabrina
v. 23 Mar 10, 2026 07:54 FRUTEAU-ext, Sabrina
v. 22 Mar 10, 2026 07:52 FRUTEAU-ext, Sabrina

Go to Page History

  • No labels