High- Level Specification

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 and routing, such as company code, 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

Dependencies

SAP PS related FS: 

• Cross System, custom field to be created upfront
• Responsible project to be fed by position id
• User statuses On Hold, ZCATS and Cancelled to be created

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 Closed or Cancelled.

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
• insert in PRPS 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 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. “IN_EXEC”, “ON_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, Cancelled (TXT04 value TBC), ZCATS Stops time recording, ON_HOLD (TXT04 value TBC) then set the field /SYQ/CATSINAC to Yes.

2.5 Last change date

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 > 1 year, 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.  

2.5 Synchronize entries with other 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 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

Volumetrics

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