| Status | Revision in progress |
|---|---|
| Owner | FRUTEAU-ext, Sabrina |
| Stakeholders | |
| Jira Request ID | ERP-165 - Getting issue details... STATUS |
| Jira Development ID | ERP-126 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
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 intercompany (IC) relevant.
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 support the IC recharge process.
3 major steps:
- 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 IC relevant.
Step | Description | Comment |
|---|---|---|
| 1 | Custom table Posting WBS elements /SYQ/T_CATSIC is created with the below attributes: Posting WBS element id | |
| 2 | Update the table /SYQ/T_CATSIC. Identify missing WBS elements from /SYQ/T_CATSIC: In PRPS, identify:
Copy the WBS elements to /SYQ/T_CATSIC along with the below information: Posting WBS element id | WBS element created locally and flagged as "Account Assignment assigned" are eligible for Time booking. The ones that are active should get replicated to the custom table /SYQ/T_CATSIC. |
| 3 | Update new and existing entries in /SYQ/T_CATSIC with source system = current system. The program will update the below fields, in case a change has occurred on the WBS elements. The other fields will be deducted in a later stage:
| The table will contain entries created in the source system, and entries sent from different systems. The program will only update the entries created in the source system. |
| 4 | Update the System/User status and the Inactive flag: For all the Posting WBS elements (/SYQ/CATSWBS) with source system = current system, Update System/User status ( /SYQ/CATSSTAT). If WBS element status contains CLSD, Cancelled or On-Hold, set the Inactive flag (/SYQ/CATSINAC ) to YES.
| The Posting WBS element status is updated. The Inactive flag is used by CATS to identify the WBS elements which should no longer accept time records. |
| 5 | Update status last change date: For Entries with source system = current system and with Status contain CLSD or Cancelled, Update status last change date.
| This date is only necessary for entries which have a closed and cancelled status. The program will later delete these entries based on the closure/cancellation date. |
| 6 | For all the entries with source system = current system, Update Person responsible, based on the field Person responsible position id, for all the entries with source system = current system.
| From the Position id retrieved from PRPS and stored in the field Responsible position id, the program will obtain the First Name and Last Name. This can be used by time entry users when searching for the appropriate Posting WBS element to book time against. |
| 7 | For all the entries with source system = current system, update Related project name.
| The Related project id was retrieved from step 2. From the project id, we obtain the Project description from PRPS. This is also a useful field for users searching for the appropriate Posting WBS element to book time against. This will update the Related project description for the new entries created in step 2 and refresh the Related project description for existing entries created in the current system. |
| 8 | Synchronize the entries with Source system : Source system = Current system and IC Relevant = Yes These entries should be synchronized with other instances.
| |
| 9 | Delete obsolete WBS elements: Delete entries in /SYQ/T_CATSIC with:
| The deleted entries in one instance should also delete the entry in other instances. |
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |