High- Level Specification

Parameter	Value
Application System	SAP S/4HANA - CUI instance SAP S/4HANA - China instance SAP S/4HANA - Rest of World instance
Business Process Reference	10.02.03.04. Manage Project Time Allocation

Functional Overview

The Functional Specification ERP-164 defines the requirements for enabling an additional WBS element fields to be used in My Timesheet and for time entry records to be saved in CATS.

This specification addresses the creation and management of the custom table that will serve as the source table for Posting WBS elements, the field used by users to book time in CATS.

Scope and Objectives

The objective of this document is to define the requirements for creating and maintaining a custom table that controls which WBS elements can be used for time posting in CATS. The table will contain WBS elements created locally and consolidate WBS elements from all three SAP instances flagged as Cross system. In addition to the WBS identifier, the table will be enriched with attributes which will be used to facilitate the time booking process.

3 major steps: 

• Custom Table Creation: Designed based on WBS element' standard master data table (PRPS) and enriched with validation attributes.

• Population & Maintenance Logic: A program , executed as a scheduled batch job, will regularly update, add, or remove WBS entries based on their current status and attributes.

• Cross-System Synchronization: Ensures consistent replication of relevant WBS elements across the three SAP instances, including locally created and cross-system flagged entries.

Assumptions

• WBS element and Project descriptions are maintained in a single language only and are not translated. The language used by the user to create or maintain the descriptions is the one that applies to the WBS element and project description.
• WBS elements id number ranges are different on each instances. No duplication is possible. 

Dependencies

Related Jiras: 

• ERP-610 WBS element search help

• ERP-167 Sync Project Person Responsible & Applicant with HR Positions
• ERP-164 UI - CATS Enhancement for Intercompany Recharge

Security, Integrity and Controls

The custom table /SYQ/T_CATSIC is maintained by a custom program. 

The CATS/My Timesheet and SAP PS support teams should have SM30 access in all instances to manually correct entries in the custom table when required.

Configuration Requirements

N/A

Language Requirements

N/A

Special Requirements

N/A

Design Rationale

Functional Requirements

To support intercompany (IC) recharge and enable time booking against WBS elements created in other SAP instances, without confusing end users, a custom table, a supporting programs and a synchronization between instances are required.

The CATS / My Timesheet application will reference this custom table when users select a WBS element for time booking, ensuring that only eligible and active WBS elements are available for selection.

1. Posting WBS Element Custom Table

The value help in CATS / My Timesheet will read exclusively from this custom table.

The table will contain the key information needed to:

• Support search and selection of WBS elements in time entry,

• Control time posting based on status,

• Enable IC recharge based on company code logic described in FS ERP-164 UI - CATS Enhancement for Intercompany Recharge.

• Synchronize WBS entries across SAP instances, using the Cross System flag. 

(Refer to the Custom Table Definition section for detailed field descriptions.)

2. Custom Program to Feed and Update the Custom Table

A batch program will be developed and scheduled to automatically populate and maintain the table.

2.1 Identify and Add New WBS Elements in the same instance

The program will compare the custom table with the standard table PRPS to identify new WBS elements that should be added to the local custom table. 

Selection criteria:

• Account Assignment = X

• System/User status is not Created, On Hold, Template locked, Closed, or Cancelled

• Deletion Indicator set to X in PRPS

• Project Type ≠ 11 (Direct Asset Purchase), 35 (Capital Spares), 16 (Capital Lease), 15 (Intercompany Recharge), 20 (Contingency), 25 (Waste)

Entries meeting these criteria will be copied to the custom table, with Source System = the system where the program is executed.

2.2 Update Existing Entries

The following fields will be updated when changes occur in the standard WBS data:

• WBS Element Description

• Related Project ID / Description

• Cross-System Flag

• Responsible Position ID

• Project type

2.3 Update Status-Related Fields

For all entries where Source System = Current System, the program will:

• Refresh System and User Status,

• Set the Inactive Flag if the WBS status includes Closed, On Hold, Locked or Cancelled,

• Capture the Last Status Change Date when the WBS status includes Closed or Cancelled, as these entries may later be deleted.

2.4 Delete Obsolete Entries

The program will include an input parameter for the retention period.
If a WBS element is Closed or Cancelled and its Last Status Change Date is older than the retention period, the entry will be deleted from the custom table.

3. Synchronization Across Instances

Entries flagged as Cross-System = X will be replicated to the other SAP instances.

All attributes of the entry will be replicated to ensure consistency across systems. 
The Source System field identifies where each entry was originally created and determines the replication direction.

Target systems will reflect all changes in real time (or per scheduled synchronization), ensuring consistent data availability for time booking across all instances.

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Posting WBS element

The custom table will serve as the central repository of Posting WBS elements eligible for time posting in CATS. It contains all WBS element created locally as Account assigned, and it consolidates WBS elements from all three SAP instances flagged as Cross System, along with attributes needed for validation and reporting such as company code, system and user statuses, responsible person, and related project information. 

Configuration Table

Selection Screen Enhancement

Processing Logic

1. Create custom table

• • Table id: /SYQ/T_CATSIC
  • Table name: Posting WBS elements
  • Field catalog: see Custom table section below. 

2.  Custom program to maintain Posting WBS elements /SYQ/T_CATSIC table:

2.1 Add new entries:

The program will compare PRPS with /SYQ/T_CATSIC.

Identify the entries existing in PRPS but missing in /SYQ/T_CATSIC, responding to the below conditions :

• • the WBS elements with Account Assignment BELKZ activate
  • for each entries identified, check System/User status. The statuses retrieved must not contain Template Locked TLCK, Created CRTD, Closed CLSD, On Hold HOLD or Cancelled CANCELLED.
  • Exclude the WBS elements which are assigned to project type PRART = 11 Direct Asset Purchase, 35 Capital spares, 16 Capital lease, 15 Intercompany recharge, 20 Contingency, 25 Waste
  • Exclude WBS elements with deletion flag LOEVM (PRPS) set to X 

Entries identified responding to above conditions and which do not already existing in /SYQ/T_CATSIC are copied from PRPS to /SYQ/T_CATSIC. 

The copy includes the below fields from PRPS: 

Update the field Source system /SYQ/SOURSYS = Current system and client id. 

Update the field /SYQ/CATSRPROJD Related project description by: 

• read value copied in /SYQ/CATSRPROJ Related Project id
• insert in PROJ as POSID
• the value for field POST1 is the Related project description - /SYQ/CATSRPROJD

2.2 Update attributes on existing entries

Some WBS attributes can be changed only before the WBS element gets released and some can be changed at any stage.

To ensure that we hold the latest information in /SYQ/T_CATSIC, the program will update the fields mentioned 2.1 for the existing entries, for which /SYQ/SOURSYS = Current system and client id. 

 2.3 Update Posting WBS element status

For all the entries in /SYQ/T_CATSIC with Source system = Current system, the status fields below need to be updated. This update will cover new entries added in step 2.1 and existing entries. 

• •  /SYQ/CATSSTAT - System/User status  
  • /SYQ/CATSSTATLC - Status last changed
  • /SYQ/CATSINAC - Inactive flag

2.4 Update status and Inactive flag :

For all the entries in /SYQ/T_CATSIC with Source system = Current system

• • For each Posting WBS element id, Get OBJNR from PRPS
  • Use FM BAPI_BUS2054_GET_STATUS to obtain System and User statuses assigned and currently valid. It returns a table of statuses for the requested objects.

This includes:

• • • System statuses in format TXT04-TJ02 (e.g. CRTD, REL, CLSD, TECO, etc.)
    • User statuses TXT04-TJ30 ( e.g. “HOLD”, “”, etc.)

• • Concatenate all the statuses values received in the field /SYQ/CATSSTAT, with space in between.

Example: If for a given WBS element the FM BAPI_BUS2054_GET_STATUS returns the below statuses:

• • • System statuses : REL AUC
    • User status: ON_HOLD

Then the field System/User status /SYQ/CATSSTAT will be updated with: REL AUC ON_HOLD

• • If /SYQ/CATSSTAT contains CLSD, CNCL cancelled or HOLD On-Hold, then set the field /SYQ/CATSINAC to Yes.

2.5 Last change date

For all the entries in /SYQ/T_CATSIC with Source system = Current system

If the field System/User status /SYQ/CATSSTAT contain CLSD - Closed or Cancelled, the field /SYQ/CATSSTATLC - Status last changed date should be updated with:

Last change date for these statuses in table JCDS field UDATE. 

Entries with System/User status containing Closed or Cancelled entries are eligible for deletion, 1 year after their closure or cancelation date. This date will be used by the program to identify these entries.

2.6 Delete obsolete entries 

If the field System/User status /SYQ/CATSSTAT contain CLSD - Closed or Cancelled and SYQ/CATSSTATLC - Status last changed date > Retention Period*, then delete the entry from /SYQ/T_CATSIC. If the entry is flagged as Cross System /SYQ/CATSICR = Yes, then it should also delete the entries in the other systems.  

*Retention Period = Instead of hardcoded, the retention period can be read by the program as an input parameter available in the selection screen. 

2.5 Synchronize entries with other instances

For all the entries in /SYQ/T_CATSIC with Source system = Current system

The entries with /SYQ/CATSCS Cross system = X, are to be synchronized with other systems. 

Volumetrics

The volume for WBS elements is currently unknown. 

Performance Considerations

N/A

Error Handling

Run Report (Batch Execution Summary)

To monitor outcomes and diagnose issues, the program produces an execution summary after each run, highlighting new inserts, updates, deletions, replications triggered, and errors/skips.

• ALV list when run online

• Optional CSV/XLSX downloadable

Header (single record per run)

• Execution timestamp, variant, system, input parameters

• Totals: Read | Inserted | Updated | Deleted | Replicated | Skipped | Errors

Sections 

• Inserted from PRPS

  • • Shows WBS entries detected in PRPS but missing in the custom table.

    • Indicates whether each entry was successfully inserted into the custom table; if not, displays the reason.

• Changed (Updates to Existing Records)

  • • Lists entries where attributes were updated, with old → new values per field.

    • Indicates whether each update succeeded; if not, shows the reason.

• Deleted Entries

  • • Lists entries removed due to retention rules or status (e.g., Closed/Cancelled beyond cutoff).

    • Confirms successful deletion or provides error details.

• Replications Triggered

  • • Shows entries sent for cross-system synchronization with action type (Create/Update/Delete).

    • Records the message/queue/IDoc number (if relevant) and the result (Success/Failed/Pending).

• Errors & Skips

• • • For any entry where processing fails, logs the attempted action, error message, and standardized reason code.

    • The program skips to the next entry; the run continues without global termination.

Testing

How to Test

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