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 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 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 such as company code, system and user status, responsible project and other information which will be used to facilitate the time booking process. This central repository will also support the IC recharge process. 

3 major steps: 

1. Creation of the custom table

The table will be populated from PRPS and enriched with attributes required for validation such as WBS element system and user status, responsible person, and related project information.

2. Population and maintenance logic

A program will be developed to feed the table with selectable time-booking WBS elements, update the relevant attributes on the existing entries, and remove entries that are no longer valid. This program will be scheduled to run as a regular batch job.

3. Cross-system synchronization

Because time entry and projects exist in 3 SAP instances, the solution must ensure consistent availability of relevant WBS elements across all of them. The synchronization will cover both WBS created locally and WBS received from other instances that are flagged as Cross System.

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.

Dependencies

Related Jiras: 

• ERP-610 WBS element search help

• ERP-167 Sync Project Person Responsible & Applicant with HR Positions

Security, Integrity and Controls

The custom table /SYQ/T_CATSIC is maintained by a custom program. No manual update is required. 

The CATS/My Timesheet and SAP PS support team should have access to display the table in all instances. 

Configuration Requirements

N/A

Language Requirements

Special Requirements

N/A

Design Rationale

Functional Requirements

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 active statuses retrieved must not contain Created, Closed or 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

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 stored and read by the program from a standard parameter table (TVARVC) or set 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 = Yes, are to be synchronized with other systems. 

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 IC-relevant, 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

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

1. Update table /SYQ/T_CATSIC with new entries: 
   1. Table comparison PRPS vs /SYQ/T_CATSIC 
   2. Identify entries missing responding to time entry criteria (see Functional requirement section)
   3. Duplicate missing WBS elements to /SYQ/T_CATSIC with related WBS fields. 
2. Update existing entries created in local system: The custom program will update the different fields (see Functional requirement section 2.2)
3. Update the System/User status field and the Inactive flag on entries created in local system:. 
   1. System/User statuses are obtained through FM and concatenated in one field (see Functional requirement section 2.2)
   2. The field Inactive is set for statuses CLSD closed, CNCL cancelled, or HOLD On-Hold
4. Update Status Last change date for Closed and Cancelled WBS elements, on entries created in local system:.
5. Delete the entries in the table created in local system with status Closed or Canceled and Status Last change date > Retention period (input parameter). 
6. Synchronize entries with Cross System activated with other systems. Entries deleted must also be deleted in other systems. 

Volumetrics

The volume for WBS elements is currently unknown. 

Performance Considerations

Error Handling

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