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

Assumptions

Describe any assumptions that have been made in the process of completing this design. What functionality is expected of configuration or other developments that pass information to this development and/ or retrieve the information processed by it (performance, triggers, exceptions, etc.)

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

Detail the functional requirements that are desired to be achieved by the Enhancement compared to current functionality

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Include an overview of the source. Can be deleted if not needed.

Data Validation Considerations

Include an overview of the data validation requirement. Can be deleted if not needed.

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here. Can be deleted if not needed.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens. Can be deleted if not needed.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log