SCR Functional Design document

Specific Customer Requirement (SCR) link to Training material 

The workflow is the following one: Submit --> Filter --> Pre-approvers (can be 1-2 persons) ---> Approve by Product Manager --> Implement. 

The Filter can edit the fields and thus impact the approving process. Example: if "SCR Category" is changed, approvers can change (please refer to the routing matrix).

Link:

2024 implementations:

Email Alert Reminder for SCR Approvers upon SCR Submission - How To

• Excerpt: An email notification will be sent every 7 or 14 days from the date a SCR (Special Customer Requirement) has been submitted once "Submit for Approval" button has been clicked (as seen in the below image).

With the new process implemented, when an user creates a new SCR (Special Customer Requirement) record, under certain conditions, an email notification similar to the one in the below image, will arrive to his email after 7 or 14 days, as per steps showcased hereunder:

1.User needs to fill in all mandatory fields (red asterix), as usual, and save the newly created SCR

As a result of the above, the following notification error might show on the screen “The selected SCR Product Family is not equal to the Product Family of the selected Product.“; to ‘fix’ and continue the SCR creation process, the user needs to make sure to choose the same “SCR Product Family” on the SCR record as the “Product Family“ they have on the product they have added on the SCR record they are working on creating and click the "Save" button again

2.User needs to click the "Submit for approval" button

As a result of the above, the following error might show up “This approval request requires the next approver to be determined by the Filter/Gatekeeper field. This value is empty. Please contact your administrator for more information.” ; to ‘fix’ the error, the “Filter/Gatekeeper” field value needs to be the current user who created the SCR, therefore, the user who created the SCR will need to edit the newly created SCR, fill in the "Filter/Gatekeeper" field with their own user name and click "Save" again to update the new details

3.User needs to click the “Submit for approval” button again; once submitted, the button should no longer be available (disappears from its designated spot on the record)

4. After the above operation, the SCR would move into the next stage: “To be filtered”

5. If the "GBU Segment" field value is "Strategic KA" the approver will receive an email notification after 7 days, but if it is any other different value, the notification will arrive after 14 days.