High- Level Specification

Parameter	Value
Application System	SAP S/4HANA - CUI instance Image RemovedSAP S/4HANA - China instance Image RemovedSAP S/4HANA - Rest of World instance
Business Process Reference	10.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. 

 Image RemovedImage Added

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 IC RelevantCross System. The user will be selecting the WBS elements to book time against from this table. 

Process Flow Diagram

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/ANot Applicable

Special Requirements

N/ANot Applicable

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

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

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

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

To ensure accuracy and avoid confusion, search results list must exclude WBS elements with inactive statuses. 

If Inactive /SYQ/CATSACINAC = Yes then exclude record from the search result. 

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

User exit CATS0002 (Supplement recorded data):

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 following logic:

1. Check the company code of the Posting WBS element selected in the table /SYQ/T_CATSIC, field /SYQ/CATSCOMPCOD

2. Fetch the company code of the Personnel ID (PERNR). Function module HR_GET_COMPANY_CODE can be used. 

3. If PERNR’s company code = Posting WBS element’s company code → copy the Posting WBS element ID into CATSD-RPROJ.

4. If PERNR’s company code ≠ Posting WBS element’s company code → Assign CATSD-RPROJ (Receiver WBS element) to the WBS element in PRPS where:

   • Company code PRPS-PBUKR = PERNR’s company code, and

   • Project type PRPS-PRART = 15 Intercompany Recharge

   • Trading partner = Posting WBS element company code (from /SYQ/T_CATSIC)
   • If multiple WBS elements responding to the above criteria, select the WBS element with system and user status all active. 

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 /SYQ/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"

Recommended UI Technology

1. Field creation in CATSDB

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 /SYQ/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 Fiori app (Front-end)

Refer to the SAP note: 

3515362 - My Timesheet V4 Search helps - SAP for Me

3. Auto-populate the Standard field Receiver WBS element (back-end)

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

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

BAdI CATS_RECORDING → method CHECK_REC_DATA can be used. 

5. Assign Receiver WBS element which is active:

If PERNR’s company code ≠ Posting WBS element’s company code, a WBS element is retrieved to be assigned to the field Receiver WBS element. Ensure that the retrieved WBS element is active: 

• Company code PRPS-PBUKR = PERNR’s company code, and

• Project type PRPS-PRART = 15 Intercompany Recharge

• Trading partner = Posting WBS element company code (from /SYQ/T_CATSIC)
• If multiple WBS elements responding to the above criteria, select the WBS element with system and user status all active. 

 the function module STATUS_READ can be used to check the status of the retrieved WBS element: 

pass the object number (OBJNR) of the WBS element (from table PRPS). It returns a table of statuses (JSTAT) for that object. This includes:

• System statuses (e.g. CRTD, REL, CLSD, TECO, LKD, HOLD, DLFL, etc.)
• User statuses ( e.g. “IN_EXEC”, “ON_HOLD”, etc.)

Each row tells you whether the status is active or inactive.

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 /SYQ/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 /SYQ/CATSWBS, fetching table /SYQ/T_CATSIC.
2. User hits the save button.
3. System Reads the company code assigned to selected entry in table /SYQ/T_CATSIC field /SYQ/CATSCOMPCOD.
4. Read the user's Personnel id (PERNR)’s company code
5. If PERNR’s company code = company code assigned to Posting WBS element (table /SYQ/T_CATSIC field /SYQ/CATSCOMPCOD)
• Copy Posting WBS element ID (/SYQ/CATSWBS)  into standard CATS field Receiver WBS element RPROJ.
6. Else

• • check table PRPS: 
    • project type (PRART) = 15 Intercompany Recharge 
    • company code (PBUKR) = PERNR’s company code
    • Trading partner (PRPS-ZX03) = Posting WBS element company code /SYQ/CATSCOMPCOD

• • Insert WBS element fetched from PRPS into field Receiver WBS element RPROJ

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

• • If /SYQ/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

Custom Tables

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

Master data

 Configuration table

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.

• - 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

Not Applicable

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

Custom Tables

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

Master data

 Configuration table

Tooltips

Not Applicable

Front-End

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

Mobile Services

Not Applicable

Authentication & Authorization

Refer to Security Integrity and Control section

Accessibility

Not Applicable

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

Performance Consideration

Error Handling

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

Test Considerations/Dependencies

N/A

Other Information

Development Details

Package

UI Implementation

API Implementation

Other Development Objects

Appendix

See also

Change log