High- Level Specification

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 , company code, Plant, Profit center , Capex/Opex, Account Assigned 
• WBS search Help for CATS - Required to search WBS elements based on WBS ID, WBS Description, Project ID, Project description, Project type, Person resp , company code, Plant, Profit centre, Capex/Opex, CLuster ID/Descp, Item type ID/Descp, Account Assigned
• 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

=X

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
• Custom WbS search will not be available in Concur
• This custom search is not available in Ariba

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

1. In all GUI/Fiori transactions WBS element - WBS element can be searched by
   1. WBS ID
   2. WBS Description
   3. Project ID 
   4. Project Description
   5. Project Type
   6. Project Owner (person responsible) - this will further allow search based on 2. and 3. below
   7. Company code
   8. Plant
   9. Profitcentre
   10. Capex/Opex
   11. Account assignment = X by default
2. 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
   1. Person ID holding the position
   2. Person Name - (last name, first name, wild card)
3. In MyTimesheet - Posting WBS element can be searched by
   1. WBS ID
   2. WBS Description
   3. Project ID 
   4. Project Description
   5. Project Type
   6. Project Owner (person responsible) - this will further allow search based on 2. and 3. below
   7. Company code Id/Des
   8. Plant ID/Des
   9. Profit Centre ID/Dec
   10. Capex/Opex
   11. Account assignment = X by default
   12. Cluster ID/Desc
   13. Item type ID/Desc

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

Data Validation Considerations

N/A

Custom Tables

N/A

Master Data

N/A

<Include an overview of the table and what it’s used for>

Configuration Table

N/A

Selection Screen Enhancement

N/A

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

Test Considerations/Dependencies

• Ensure Positions are assigned Persons
• Ensure only 1 active assignment of person to position

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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log