| Status | Approved |
|---|---|
| Owner | UPADHYAY-ext, Anjali |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID | ERP-511 - Getting issue details... STATUS |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | S/4Hana ROW, S/4Hana China, S/4Hana CUI |
| Business Process Reference | 10.01.01.04. Identify Initiatives and Items 10.02.01.01. Manage Project/WBS changes 10.02.03.04. Manage Project Time Allocation |
Functional Overview
Functional specification covers primarily 2 requirements.
- WBS elements are the cost objects used for booking different type of transactions such as timesheet, journal, PRs etc. It is vital for a user to chose the correct WBS element without having to remember the WBS ID or description. Therefore, Syensqo specific search help is required to search the WBS element based on key criteria to ensure accuracy and ease of finding right WBS.
- The assignment of various stakeholders on Bucket, Initiative, PPM item, Project definition and WBS elements will be via HR Position rather than a named user. This ensures the information remains correct regardless of individuals moving in or out of a Position. In order to assist the user to find the correct position, search is required for position the based on the person holding the position.
Scope and Objectives
There are multiple processes defined in Syway design, where the user is required to search the objects based on certain criteria for processing. Standard SAP search help are not sufficient to cover all possible scenarios for Syensqo's business processes. Therefore, custom search helps are required to be implemented. This functional specification covers below 2 search helps
- WBS search help - Required to search WBS elements based on WBS ID, WBS Description, Project ID, Project description, Project type, Person resp and company code
- Position search help - Required to search position by Person Name and/or ID for Bucket Approvers, Program Managers, Project Owners, Project Financial Controllers, Project Managers at Bucket, Initiative, Item, Project definition and WBS element level
N/A
Use Cases
| Use Case | Description | Comment |
|---|---|---|
1 | User open an Item and navigate to Project Owner field | Position search by Person no, Last Name, First name appears |
2 | User enters one or more of the search criteria | Relevant position is displayed for selection |
| 3 | User open a transaction with WBS as an entry field ( CJ20N or CN41N) | Syensqo search appears ( WBD ID, WBS descp, Project ID, Project descp, Person resp, Project type, Company code) |
| 4 | User enters one or more of the search criteria | Relevant WBS element is displayed for selection |
Assumptions
- Custom search help will be added as separate search help to the standard and custom fields referencing WBS element and Position (Project owner/ Project Financial Controller) and will be available in both GUI and FIORI UIs
- Each HR Position is linked to only 1 active Person at a given point of time
Dependencies
- Stakeholder fields such as Bucket Approver, Program Manager, Project owner and Project Financial controller fields are available as per ERP- 64
Security, Integrity and Controls
Standard authorization checks associated with the relevant transaction will be applied.
Configuration Requirements
- Project Types (V_TCJ1- PRART) dropdowns are configured
Language Requirements
WBS master data is maintained in English only, therefore its expected that the search will be in English only
Special Requirements
N/A
Design Rationale
Functional Requirements
Custom search help is required for below
- WBS element - WBS element can be searched by
- WBS ID
- WBS Description
- Project ID
- Project Description
- Project Type
- Project Owner (person responsible) - this will further allow search based on 2. and 3. below
- Company code
- Position - Positions available in dropdown as Bucket Approvers, Program Managers, Project Owners, Project Financial Controllers, Project Managers, Person responsible and Applicant fields can be searched by
- Person ID holding the position
- Person Name - (last name, first name, wild card)
It is required that the custom search help will
- be available on all GUI and Fiori UIs that requires the use of WBS data element. The list of GUI/Webdynpro/Fiori apps will be updated once all of the other requirements have already been confirmed.
- be available on the Standard and Custom fields wherever the respective data object is used
- allow wildcard search based on description or ID
Mockup of the Position Search
Mock up of WBS search
Proposed Technology to Use
Search Exit and CDS extensions can be used.
Data Source Considerations
Search is returned based on below table and fields
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
| PRPS | POSID | WBS element |
| PRPS | POST1 | WBS description |
| PRPS | PSPHI | Project ID |
| PROJ | POST1 | Project Description |
| PRPS | PRART | Project Type |
| PRPS | VERNR | Person Responsible |
| PRPS | PBUKR | Company Code |
| HRP1001 | OBJID | Position ID, Person ID |
| HRP1000 | STEXT | Position Name, Person Name |
Data Validation Considerations
N/A
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
N/A
Master Data
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
N/A
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
N/A
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
WBS search
- Entered selection is passed in the PRPS table as per the data source table and the PRPS -POSID and PRPS -POST1 is displayed where the entered criteria is matched.
Position Search
- Entered selection is passed in the HRP1001 - OBJID or HRP1000 -OBJID where Object Type = P , as per data source table and the HRP1001 - OBJID and HRP1000 - STEXT is displayed where the entered criteria is matched.
Volumetrics
WBS and Position are high volume data. Exact volumes unknown at this point.
Performance Considerations
N/A
Error Handling
N/A
Testing
How to Test
Portfolio Items, Initiatives, Bucket, Project Definition, WBS elements and Position IDs are required to test the data
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
| 1 | Open Portfolio Bucket using "Buckets" Tile and search for Bucket Approver | Bucket Approver search help appears with Position ID, Position Name, Person ID and Person Name |
| 2 | Search using Wild card for one by one for each search criteria | search returns the valid results |
| 3 | Repeat step 1 and 2 for Program Manager at Initiative level Project Owner at PPM item level Project Financial Controller at PPM item level Person Resp at Project definition Level Applicant at Project Definition level Person Resp at WBS Level Applicant at WBS level | Search help appears with Position ID, Position Name, Person ID and Person Name and return valid results |
| 4 | Go to Project builder and Open WBS search | Search help appears with WBS ID, WBS Disc, Project ID, Project Disc, Project Type, Person Resp, Company code |
| 5 | Search one by one for each search criteria | search returns the valid results |
| 6 | Search using by Person responsible | Search based on Person ID and Name appears |
| 7 | Search using Person name or ID | Valid Position ID appears |
Repeat Step 4 to 7 for below Fiori Apps, GUI Txns
| Search help appears with WBS ID, WBS Disc, Project ID, Project Disc, Project Type, Person Resp, Company code and return valid results | |
Test Considerations/Dependencies
- Ensure Positions are assigned Persons
- Ensure only 1 active assignment of person to position
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 |