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

Compare with Current View Page History

« Previous Version 27 Current »

Status

  Lead Approval

OwnerFRUTEAU-ext, Sabrina 
Stakeholders
Jira Request ID

ERP-164 - Getting issue details... STATUS

Jira Development ID

ERP-126 - Getting issue details... STATUS

High- Level Specification

ParameterValue
Application System

SAP S/4HANA - China instance

SAP S/4HANA - Rest of World instance
Business Process Reference10.02.03.04. Manage Project Time Allocation

Functional Overview

The intent is to make a WBS elements available for timesheet booking when resources are required from another company code or from a different SAP instance (cross-instance).
This FS focuses on adapting the CATS and My Timesheet applications to capturing the time and cost against a Posting WBS element, and when necessary, redirect it to a Receiver WBS element, which will be used for IC recharge. 


 

Scope and Objectives

CATS only allows booking against a single WBS element using the standard Receiver WBS field, which is insufficient for intercompany scenarios.

To address this, the solution must:

  • Capture 2 WBS : the Posting WBS element selected by the user, and the Receiver WBS element used for financial posting.

  • Keep the process simple for users, who will only select the Posting WBS element.

  • Ensure the system automatically derives and populates the Receiver WBS element according to defined rules.

The objective is to enhance CATS/My Timesheet application so that it supports intercompany service recharges seamlessly, allowing users to continue booking time easily while ensuring costs are posted correctly to the appropriate WBS element.

A custom table /SYQ/T_CATSIC is created under Jira ID ERP-165. This table stores all WBS elements generated locally (in the same system where users record their time) as well as WBS elements originating from other systems that are flagged as Cross System. The user will be selecting the WBS elements to book time against from this table. 


Process Flow Diagram


Step

Description

Comment

1

User can create time entry records against:

  • A WBS element within the user's company code
  • A WBS element that belongs to another company code. 

2User creates an entry in My Timesheet V4.User only sees one field to book time against: Posting WBS element. 
3

User searches for the Posting WBS to book time against. Search help offers different criteria:

  • Posting WBS element ID 
  • Posting WBS element Description
  • Related Project id
  • Related project definition
  • Person Responsible 
  • Project type

A custom table /SYQ/T_CATSIC was created under Jira ID ERP-165. This table stores all WBS elements generated locally (in the same system where users record their time) as well as WBS elements originating from other systems that are flagged as Cross System. The user will be selecting the Posting WBS elements to book time against from this table. 

The result list will exclude the entries which are not relevant for time entry (Inactive status). 

4User selects the Posting WBS element.

The system automatically populates the standard field Receiver WBS element:

See functional requirement section for details.

5Assign time and Save the entry.

Entry can be save and is visible in CATSDB. Standard field Receiver WBS element and custom field Posting WBS element are populated in the table CATSDB.


Assumptions

WBS elements with Project type = 15 Intercompany code Recharge are created for each company codes in scope for Time entry and each Trading Partners possible.

Dependencies

  • ERP-165 Multi Instance Data Sync - CATS Enhancement for Intercompany Recharge:  A custom table /SYQ/T_CATSIC is defined. This table stores all WBS elements created locally (in the same system where users record their time) as well as WBS elements originating from other systems that are flagged as Cross System. The custom table stores all the possible entries for the user to select the Posting WBS element, which will be used to derive the Receiver WBS element while saving the time entries. 
  • ERP-511 WBS element search help custom search help for Posting WBS element.
  • ERP-1455 CATS enhancement auto populate Posting CC for statistical WBS element

Security, Integrity and Controls

Posting WBS element is to be used by all users with My Timesheet access, with Time entry role. 

Configuration Requirements

  • CATS configuration with Time entry and Administrator data entry profile must be created. 
  • Once the custom field is created, the Data entry profile must be configured with the custom field in order to be used in My Timesheet. 

Language Requirements

N/A

Special Requirements

N/A

Design Rationale


Functional Requirements

The requirement can be divided into 4 main sections: 

1.Create a custom field in CATS database and in My Timesheet V4:

A new custom field Posting WBS Element must be available in CATS (SAP GUI) and My Timesheet (Fiori V4).

This field will serve as the primary input for users to record the WBS element against which their time should be booked.

Add the custom field directly to the CI_CATSDB structure, which extends the core CATSDB table for customer-specific data.

Refer to SAP note: https://me.sap.com/notes/3515819/E

  • Table: CATSDB, Customer Include: CI_CATSDB
  • Reference Table: /SYQ/T_CATSIC - field CATSWBS

Map custom field to Data entry profile via configuration.

The field needs to be mapped to the CATS custom field holders via configuration.

SPRO → Cross-Application Components → Time Sheet → Settings for All User Interfaces → Customer-Specific Enhancements → Customer-Specific Fields

Add the custom field to CDS views for My Timesheet V4 (Front-end)

Extend CDS views to include the custom field for:

  • Form entries (time recording)

  • Assignments

Refer to SAP note: https://me.sap.com/notes/3515819/E


2.  Search help extension in My Timesheet V4 (Front-end): 

Enable search Posting WBS element search help with the below attributes from table /SYQ/T_CATSIC

WBS element search help is defined in Jira id ERP-610 WBS element search help

3. Automatically populate the CATS standard field Receiver WBS element (backend): 

3 possible scenarios: 

3.1 If the selected WBS element "Posting WBS elements" is assigned to the same company code as the Personnel id then Receiver WBS element = Posting WBS element

3.2 If the selected WBS element "Posting WBS elements" is set as statistical and is assigned to a different company code as the Personnel id then Receiver WBS element = Posting WBS element.

Standard error message will occur when submitting the entry: "Receiver WBS element does not exist" or "Receiver and sender have different company codes". The entry cannot be saved. 

3.3 If the selected WBS element "Posting WBS elements" is not set as statistical and is assigned to a different company code as the Personnel id then Receiver WBS element = Recharge WBS element assigned to the personnel id's company code. When submitting the entry, a warning is displayed "You are booking time to a WBS element in a different company code than your own. Please confirm this is correct before submitting.". The user can confirm and the system proceeds with saving. 

User exit CATS0002 (Supplement recorded data): Here you can modify the record entered by the user, and add the Receiver WBS element before saving.

Once the user selects a Posting WBS element via the custom field, the system must populate the standard CATS field Receiver WBS element (CATSD-RPROJ) according to the processing logic.

4. Control at saving, check if Posting WBS element status is active (Back-end). 

 Before saving the entry, check if the Posting WBS element is active in the table /SYQ/T_CATSIC, field CATSINAC. 

If active, proceed to saving. 

If not active, no saving, return an error message "Posting WBS element { XXXX } is not active for booking. Please enter a valid WBS element. Entries cannot be saved"

BAdI CATS_RECORDING → method CHECK_REC_DATA can be used. 

Recommended UI Technology


Processing Logic

Search for a Booking WBS element

1. User opens the search help dialog

2. The search help displays the fields referring to /SYQ/T_CATSIC which can be used for search. 

3. User enters a value in some of the proposed fields

4. System lists the Posting WBS elements responding to the search criteria, and exclude the ones set to Inactive in /SYQ/T_CATSIC field CATSACINAC.

5. User selects the Posting WBS element for time entry.


Auto-populate Receiver WBS element field / Check if Booking WBS element is active

Step-by-Step Logic

  1. User selects the Posting WBS element CATSWBS, fetching table /SYQ/T_CATSIC.
  2. User hits the save button.
  3. System checks if WBS element is a statistical WBS element: table /SYQ/T_CATSIC field CATSXTAT = X then no further action. If CATSXSTAT = " " then proceed with next steps.
  4. System Reads the company code assigned to selected entry in table /SYQ/T_CATSIC field CATSCOMPCOD.
  5. Read the user's Personnel id (PERNR)’s company code
  6. If PERNR’s company code = company code assigned to Posting WBS element (table /SYQ/T_CATSIC field CATSCOMPCOD)
    • Copy Posting WBS element ID (CATSWBS)  into standard CATS field Receiver WBS element RPROJ.
  7. If PERNR’s company code is different than company code assigned to Posting WBS element (table /SYQ/T_CATSIC field CATSCOMPCOD) and Posting WBS element is statistical CATSXSTAT = X
    • Copy Posting WBS element ID (CATSWBS)  into standard CATS field Receiver WBS element RPROJ.
    • This will trigger a standard error message and the time cannot be saved. 
  8. If PERNR’s company code is different than company code assigned to Posting WBS element (table /SYQ/T_CATSIC field CATSCOMPCOD) and Posting WBS element is not statistical CATSXSTAT = " " 

check table PRPS: 

      • project type (PRART) = 15 Intercompany Recharge 
      • company code (PBUKR) = PERNR’s company code
      • Trading partner (PRPS-SYTRADE_CC) = Posting WBS element company code CATSCOMPCOD
    • Insert WBS element fetched from PRPS into field Receiver WBS element RPROJ
    • When submitting the entry, a warning is displayed "You are booking time to a WBS element in a different company code than your own. Please confirm this is correct before submitting.". The user can confirm and the system proceeds with saving. 

7. Check if Posting WBS element CATSWBS selected by user is set to Inactive in /SYQ/T_CATSIC field CATSACINAC

    • If CATSACINAC = Yes, error message "Booking WBS element { XXXX } is not active for booking. Please enter a valid WBS element. Entries cannot be saved". 
    • Else Save the entries.


Application Screen

Wireframe or Mock-Up

Standard Fiori app My Timesheet screens.

 Screen Behavior

Standard behavior is not changed.

Screen Navigation

Standard navigation is not changed.

Data Integration


FieldTable-Field NameComments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help
/SYQ/T_CATSICCATSWBSPosting WBS element
PRPSRPROJ, PBUKR, OBJNR, SYTRADE_CCRetrieve Receiver WBS element, based on company code and status, and auto-populate Receiver WBS element.
/SYQ/T_CATSICCATSWBSDESCWBS element description
/SYQ/T_CATSICCATSSTATSystem / User Status
/SYQ/T_CATSICCATSCOMPCODCompany code 
/SYQ/T_CATSICCATSRPROJRelated Project id
/SYQ/T_CATSICCATSRPROJDRelated project description
/SYQ/T_CATSICCATSPRESPPerson Responsible Name
/SYQ/T_CATSICCATSACINACInactive
/SYQ/T_CATSICCATSXSTATStatistical
JESTSTAT, OBJNRused to retrieve Receiver WBS element, based on status

Custom Tables

Custom table /SYQ/T_CATSIC  used is defined in FS Multi Instance Data Sync - CATS Enhancement for Intercompany Recharge.

Master data

FieldDescriptionData Type/LengthValidation rule / Value help 




 Configuration table

FieldDescriptionData Type/LengthValidation rule / Value help 




Tooltips

N/A

Front-End

SAP Fiori app My Timesheet can be used on Desktop, Mobile. 

Mobile Services

N/A

Authentication & Authorization

Refer to Security Integrity and Control section

Accessibility

N/A

Volumetrics

The volume of WBS elements is currently unknown.

Performance Consideration

N/A

Error Handling

Error handling mentioned in Processing logic section. 

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.

Test Conditions and Expected Results

IDConditionExpected Result
1.1

Non-recharge scenario:

Create an entry in My Timesheet and search for a Posting WBE element.

The custom field appears. Pop-up to search for Posting WBS element. 
1.2Search for a Posting WBS element with Inactive flag = YesNo results returned.
1.3Search for a WBS element using each of the fields for selection criteria.Result returns active WBS element responding to criteria.
1.4Select a WBS element in the result list with company code = User's personnel id's company code.

Booking WBS element ID is assigned to time entry field. 

1.5Enter time and save entry.

Value selected in /SYQ/CATSWBS is assigned to CATS standard field Receiver WBS element. 

Entry can be saved. 

2.1

Recharge scenario: 

Create a new entry and select a WBS element with company code <> User's personnel id's company code.

Posting WBS element ID is assigned to time entry field. 

2.2Enter time and save entry.

WBS element with project type = Intercompany Recharge and company code = User's personnel id's company code,  is assigned to the  CATS standard field Receiver WBS element. 

When submitting the entry, a warning is displayed "You are booking time to a WBS element in a different company code than your own. Please confirm this is correct before submitting.". The user can confirm and the system proceeds with saving. 

Entry can be saved. 

2.3Repeat the 2 above tests while creating multiple entries before saving.

Relevant WBS elements are assigned in the field Receiver WBS element. 

Entries can be saved. 

2.4Copy some entries posted on a past day, to another day. 

Relevant WBS elements are assigned in the field Receiver WBS element. 

Entries can be saved. 

3.1Create an assignments in My Timesheet and search for a Posting WBE element.The custom field appears. Pop-up to search for WBS element from the Z table shows up. 

3.2

Search for a WBS element with status = Closed / Canceled / LockedNo results returned.
3.3Search for a Booking WBS element using each criteria.Result returns relevant Posting WBS element.
3.4Select a WBS element in the result list with company code <> User's personnel id's company code. Save assignment.

WBS element ID is assigned to Posting WBS element. Assignment can be saved. 

3.5Select a WBS element in the result list with company code = User's personnel id's company code. Save assignment.

WBS element ID is assigned to Posting WBS element. Assignment can be saved. 

3.6Book time using the created assignments. Submit entries.

Relevant WBS elements are assigned in the field Receiver WBS element. 

When submitting the entry, a warning is displayed "You are booking time to a WBS element in a different company code than your own. Please confirm this is correct before submitting.". The user can confirm and the system proceeds with saving. 

Entries can be saved. 

4.1

Book time on a statistical WBS element: 

Select a WBS element which has been flagged as Statistical assigned to a different company code as user's personnel id and book time against. 

Receiver WBS element = Posting WBS element. System does not allow saving (standard error message). 

4.2

Select a WBS element which has been flagged as Statistical assigned to a different company code as user's personnel id and book time against. 

Receiver WBS element = Posting WBS element. System allows saving.

Test Considerations/Dependencies

N/A

Other Information


Development Details

Package

Package NameParent Package




UI Implementation

UI Type

UI Name

Fiori Catalogue

Design Rationale Reference





API Implementation

API TypeAPI NamePurpose / High Level LogicAPI ProductDesign Rationale Reference






Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign Rationale Reference








Appendix


See also

Change log

Version Published Changed By Comment
CURRENT (v. 27) Apr 22, 2026 06:48 TURAN-ext, Mert
v. 27 Apr 21, 2026 11:52 FRUTEAU-ext, Sabrina
v. 26 Apr 20, 2026 11:30 FRUTEAU-ext, Sabrina
v. 25 Feb 04, 2026 14:20 FRUTEAU-ext, Sabrina
v. 24 Feb 04, 2026 10:05 FRUTEAU-ext, Sabrina
v. 23 Feb 03, 2026 16:19 FRUTEAU-ext, Sabrina
v. 22 Feb 03, 2026 16:17 FRUTEAU-ext, Sabrina
v. 21 Oct 17, 2025 13:03 WENNINGER-ext, Sascha
v. 20 Oct 10, 2025 12:17 FRUTEAU-ext, Sabrina
v. 19 Oct 10, 2025 12:10 FRUTEAU-ext, Sabrina

Go to Page History

  • No labels