High- Level Specification

Functional Overview

Functional specification covers primarily 2 topics.

• 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 ‘Project Owner' and ‘Project Financial Controller’ against a PPM item and WBS Element 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. However,  it is easy for the user to find position the based on the person holding the position. Therefore, a search help is required which allows search of the position based on person name and ID.

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 Project owner/ Project financial Controller by Person Name and/or ID

Insert the flowchart and fill in the steps

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

• 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 dropdowns are configured

Language Requirements

N/A

Special Requirements

N/A

Design Rationale

Functional Requirements

Custom search help is required for below

1. 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
2. Project Owner /  Project Financial Controller - Position searched by
   1. Person ID holding the position
   2. Person Name - (last name, first name, wild card)
3. Person Responsible/ Applicant  - Position searched by
   1. Person ID holding the position
   2. 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 
• be available on the Standard and Custom fields which refers the data object WBS element. and Project Owner (person resp) /Project Financial Controller (Applicant)
• allow wildcard search based on description or ID

Proposed Technology to Use

Search Exit and CDS extensions can be used.

Data Source Considerations

Include an overview of the source. Can be deleted if not needed.

Data Validation Considerations

Include an overview of the data validation requirement. Can be deleted if not needed.

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

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

WBS and Position volumes are huge. Exact volumes unknown at this point.

Performance Considerations

N/A

Error Handling

N/A

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

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