Section B Functional Specifications

Priority: [ ] Low [ x ] Medium [ ] High [ ] Critical/SALT

Rough Order of [ ] Very Low (1-50 hours) [ ] Low (51 – 150)

Magnitude (ROM): [ ] Medium (151-300) [ ] High (301-500) [ ] Enh/Project
(500+)
Implementation [ ] Low [ ] Moderate [ ] High [ ] Extreme
Risks:
No Risk/Probability/Impact Contingency Plan

Eligible for Release: [ ] Minor [ ] Major [ ] Minnie [ ] Off-Cycle [ ]

N/A
RM Type: [ ] ENH: FastPass [ ] ENH: Standard [ ] Analysis/Discovery/POC

Acceptance UAT Test Sets:

Criteria/Testing Test Scripts TBD after solution provided.
Requirements
UAT:

Acceptance Regression Test Sets:

Criteria/Testing Test Scripts TBD after solution provided.
Requirements
Regression:

TT&C Slide
(SAP):

Expected Average: _________ Min: _________ Max: __________ Initial: _________

Data Volume: [ ] N/A

BPP Requirement [ ] Update [ ] New [ ] N/A

(SAP): BPP#____________ Hummingbird(CyberDocs)#____________

Section B Functional Specifications

SAP Security Job Role: YES NO

Requirements:
Auto posting not done in GL while transferring stock from
x
one plant to another plant in same company code
Movement type x
x
 Section B Functional Specifications
Are the assignments of any existing transactions, reports, or
x
workbooks to job roles being changed?
If any of the questions above were answered YES, then do the following:
 Fill out the Job Roles section below; and,
 See the Companion and Examples Document for SCT001/SCT002
requirements and contingencies.
New T-Code to
Job Roles Existing Role New Role
Place an “X” as appropriate

Master Data: YES NO

Are any new master data objects being created? x
If YES, then see the Companion and Examples Document for SCT003
requirements and considerations

Data-Level Group: YES NO

Will the changes to data-level groups require changes to the
x
assignments of data-level groups to users?
If YES, then see the Companion and Examples Document for SCT002
requirements and considerations

Security Functionality: YES NO

Are there functional requirements specifying that users
should be conditionally allowed to execute processes or x
access data?
If YES, then see the Companion and Examples Document for functionality and
development integration considerations

General Security Are there any data security related considerations?

Requirements: [ ] Yes [ x ] No Domestic Populations only
If Yes, please complete the following sections A, B, C and D.

A Regulatory and Security Compliance:

[ ] PII (Personally Identifiable Information)
[ ] Safe Harbor
[ ] PCI (Payment card Information)
[ ] SOX (Sarbanes-Oxley)
 [ ] GLBA (Gramm-Leach-Bliley)
[ ] Other: ___________________
[ ] Unknown

B List the classified data element types (i.e.: SSN, Credit Card Number, etc)

C Current data level classification:

[ ] Confidential
[ ] Internal Use
[ ] Public
[ ] Unknown

D Other comments / considerations