You are on page 1of 12

Form Functional Design Specification

Object ID Object Type Object Title Business Unit Module and Subarea Complexity SAP Transaction Frequency Data Volumes

FR_7001 Form In-House Check printing Record to report Record to report/Accounts Payable Low F110 As needed Average of 43 per month Medium High

71722345.doc

Table of Contents
Table of Contents.......................................................................................................1 1.Document History....................................................................................................1 1.Document History....................................................................................................1 2.Document Sign Off..................................................................................................1 2.Document Sign Off..................................................................................................1 3.Open Items.............................................................................................................2 3.Open Items.............................................................................................................2 4.Contact List............................................................................................................2 4.Contact List............................................................................................................2 5.Executive Summary.................................................................................................2 5.Executive Summary.................................................................................................2 5.1Requirement Overview.........................................................................................2 5.2Business Driver...................................................................................................3 5.3Change Management Considerations/Roles and Volumes..........................................3 Roles...................................................................................................................3 5.4Business Risks/Issues..........................................................................................3 6.Process Information ................................................................................................4 6.Process Information ................................................................................................4 6.1Process Description and Flow................................................................................4 6.2Processing Options..............................................................................................4 6.3Dependencies.....................................................................................................4 Environment / Configuration..................................................................................4 Development Dependencies...................................................................................5 Run/Execution Dependencies..................................................................................5 6.4Assumptions.......................................................................................................5 7.Additional Form Information......................................................................................5 7.Additional Form Information......................................................................................5 7.1Standard or Custom............................................................................................5 7.2Generating the Form...........................................................................................6 Access Method or Path for Form..............................................................................6 Selection Screen (If Applicable)..............................................................................6 Data Selection/Validation.......................................................................................6 7.3Output of Form...................................................................................................7 Output Layout......................................................................................................7 Printing Requirements...........................................................................................7 7.4Performance Requirements...................................................................................8 7.5Additional Information.........................................................................................8 Special Form Functions .........................................................................................8 Additional Information...........................................................................................8 8.Security and Controls ..............................................................................................8 8.Security and Controls ..............................................................................................8
71722345.doc

8.1Security Requirements.........................................................................................8 8.2Auditing and Controls Requirements......................................................................9 9.Unit Test Requirements............................................................................................9 9.Unit Test Requirements............................................................................................9 9.1Data Requirements..............................................................................................9 9.2Test Cases.........................................................................................................9

71722345.doc

1. Document History
Version 1 Change Description Initial Creation Author Misty Bertulli Date Released

2. Document Sign Off


The individuals listed here will be required to review and approve this document.

Reviewed By:
The Reviewed By signature indicates the individual(s) who reviewed this document for content and clarity, and to the best of their knowledge, this document satisfactorily achieves the purpose and scope defined herein: Name Reviewed By Signature Reviewed By Signature Manohar Bondili Swapna Satwik Title/Role <Designation, Department> RTR Team (Deloitte) Date: Offshore Lead Date:

Approved By:
The Approved By signature indicates the individual(s) who approved this document for content and clarity, and to the best of their knowledge, this document complies with corporate policies and procedures: Name Approved By Signature Approved By Signature Ron Zanco Peter Uncovsky Title/Role <Designation, Department> RTR Lead (Deloitte) Date: RTR Lead (Univar) Date:

1 71722345.doc

3. Open Items
Date Opened Description Assigned to Due Date Status

4. Contact List
Name Sidonye Washington Cassandra Regener David Lundin Misty Bertulli Team / Organization Accounts Payable Specialist Accounts Payable Supervisor Director - Corporate Payables RTR Team/Univar Email Sidonye.Washington@univarusa.com Cassandra.Regener@univarusa.com David.Lundin@univarusa.com Misty.Bertulli@univarcorp.com

5. Executive Summary
Complete a summary explaining the contents of this document and the overall intent of what this document should capture. It should include the objective of the document and what purpose it will serve with respect to the project implementation. The business requirement is to be able to print and make same day payments by in-house check printing on an as needed basis.

5.1 Requirement Overview


Describe the business requirement that will be satisfied by this development. This section should answer the question What needs to be done? See sample text below. This document details the requirements of the check to be printed on plain stock with preprinted logos and stock number this document number does not match the stock number. The fields items to be printed from the microprinter are: company address, bank name, address, routing and bank account number, system generated check number, electronic signature and remittance advice. Separate check lots need to be set up for in-house and outsourced checks.
2 71722345.doc

The current printer in use is an HP LaserJet P4015n.

5.2 Business Driver


Explain the potential impact to the business this development will have. Explain how this development will improve business operation. This information can be found in the original description from the development request list. This section should answer the question Why this needs to be done? See sample text below. Most payments will be processed through the automatic payment process in SAP and paid according to the payment terms. On occasion, a payment may need to be expedited or a business officer may need a same day check to be presented at a charitable function. In such a case a check will be printed in-house along with the remittance advice.

5.3 Change Management Considerations/Roles and Volumes


Describe any change management issues regarding users and volume. Make sure to note if the use of this development will require additional communication and/or training. Also specify what the volume requirements will be by the go-live date. This section should answer the question Are there any changes to the role and work? See sample text below. The business intends to continue with the ability to print same day checks in-house. Check printing will now be done in SAP for in-house checks. Volumes are expected to remain the same.

Roles
Complete the table below with the correct project-specific information for this functional specification. Instructions are in the middle row, and a sample entry is in the bottom row. Role List name of role; should come from the list of security roles AP Payment Processor Estimated Volume Enter the estimated volume Approx. 43 per month

5.4 Business Risks/Issues


Describe the business risks and issues associated if this development object is not created. Be sure to highlight those that are key to business operation. This section should answer the question What if we dont develop this object? See sample text below.

3 71722345.doc

Same day checks could be processed through the bank for a minuscule cost if the transmission is made according to the bank deadline in which case payment may not be made same day- which is the basic requirement.

6. Process Information
Provide a brief introduction to the process (from Print or other process modeling tool) that will be affected by this form. For example, invoicing has a direct impact on the process Sell from Stock.

6.1 Process Description and Flow


Explain the process for when this development object will be used. If this is tied back to a certain task within a process you may insert the Task Profile document here as well. This section should answer the question What process is involved? See sample text below.

6.2 Processing Options


Indicate the Processing Mode, Frequency, and Lifetime of Development by selecting and placing an X in the box next to the correct options below.

Processing Mode (Check all that apply)


Batch Online via Transaction Code Online via Menu Path

Frequency (check all that apply)


Annually Weekly Quarterly Daily Monthly

Other (If other, describe here) Could be executed any day for any employee through ECC or ESS.

6.3 Dependencies
Environment / Configuration
List the configuration work that must be considered during the development of this object and that needs to be in place before this requirement can be tested. This section should answer the question What are the configurations needed for this object? See sample text below.
4 71722345.doc

Development Dependencies
List other work that must be considered during the development of this object. This section should answer the question What other RICEFW object this development depends on? See sample text below.

Run/Execution Dependencies
Once in production, this development object may need to be executed before or after another system event. List other system events that this development object should follow or precede. See sample text below.

6.4 Assumptions
Specify any assumptions that were made while preparing this document. Highlight those assumptions which may have a direct impact on the technical solution development.

7. Additional Form Information


Provide details about the Form itself in a summary of the form here. This section should explain what the form will include, what it will look like as well as if it is an Enhancement of a standard SAP form or a new custom one.

7.1 Standard or Custom


Modification of standard SAP report/form/program Name of standard form, if known:

SAP_CHECK.pdf

Custom form Have possible standard SAP forms been considered? Yes No

Check Form .pdf


5 71722345.doc

The Check Specifications .pdf contains the indentation, character and length data. Fields 13 and greater will be used for the remittance advice, whether its an additional page due to the quantity of invoices being paid or a reprinted remittance advice.

Check specifications.pdf

7.2 Generating the Form


Access Method or Path for Form
Select the correct execution path below by placing an X in the checkbox next to it and completing the description that follows. Check all that apply and add any other execution methods if required. Execution: Custom Transaction Code Menu Path Standard Transaction Code Other : : : : ________ ________ F110____ ________

Selection Screen (If Applicable)


Complete the table below to describe the fields on the selection screen.
Field Title/Screen Label Type Size Mandatory Range Required Reference Field Name Criteria Validations

Enter the field title/screen label

Enter the type

Ente r the size

Enter yes or no depending on whether mandatory

Enter yes or no dependin g on whether range required.

Enter the reference field name

Enter any criteria validations at the field level

Data Selection/Validation
When the selection criteria is entered in the selection, explain if there is any data validation that should be completed before the selected data is displayed on the form. This section would typically contain validations required across multiple fields on the selection screen.

6 71722345.doc

7.3 Output of Form


Output Layout
Complete the table below to describe each field.
Field Sequence No. Output Field Name SAP Source Table/Field Logic for determining field value Format specification (Totals, subtotals, decimal, left/right justification, calculations/formulas, etc.)

Enter the field sequence number 1 2 3 4

Enter the output field name

Enter the SAP Source Table/Field

Explain the logic for determining the field value

List any format specifications for this specific field

Title of Form (for discussion purposes, not to be printed on form): Benefits Confirmation Form, Future SAP Screen Title for output preview: ________________________ Example Correspondence: Initial Collection Letter Form Attachment: Attach sample form here (may be hand-drawn), and include numbers on the illustration that correspond to the sequence number listed in the table above. Also attach any relevant information such as approved corporate colors, list of field names with descriptions, fonts, logos, etc.

Company Logo Required? Output methods: Print

Yes

No

Printing Requirements
List any printing requirements for this specific development object. See sample text below.
7 71722345.doc

7.4 Performance Requirements


Specify if the report is required to meet certain specific performance requirements. In particular, if the report isexpected to be run in the background, any expectation on the maximum time that it should complete should be specified.

7.5 Additional Information


Special Form Functions
List any special form functions required for this specific development object. This could include where the logo should appear, the use of letter heads, address printing formats, interactive functionality, etc. See sample text below.

Additional Information
Enter any additional information that could be helpful in developing this form. If known, the following types of information may also be included. Existing layout set Existing print program Path to customization See sample text below.

8. Security and Controls


8.1 Security Requirements
Describe any security requirements that need to be put in place as a result of using this development object. This could include security access to affected transactions or new transactions that may result from this development. This section should answer the question Are there SOX compliance requirements? See sample text below.

Complete the table below to reflect the security requirements outlined above. Role List name of role; should come from the list of security roles Transaction Code(s) List the transaction code(s) that will be executed by this role Level of Security Enter the level of security

Specify whether this Form needs to have explicit authority checks in place. If yes, then please provide the level at which the authority needs to be checked for. Normally, if the
8 71722345.doc

form is configured for standard output determination in an application area, this check would not be required as SAP Standard Authority Checks will be in place. In case of custom programs being developed to trigger the form output, an explicit authority check may be necessary.

8.2 Auditing and Controls Requirements


Explain what the error handling rules would be if there are any for this development. This section should answer the question What is needed for audit control? For example, if a form is scheduled to be printed and it does not, what should a user do to get this corrected?

9. Unit Test Requirements


Provide the necessary information to enable the technical team to carry out complete unit testing of the object.

9.1 Data Requirements


Provide sample data from the test system / client which can be used to test this object. This section should answer the question What sample test data can be used for testing?

9.2 Test Cases


List all the test cases which must be executed to validate that the business requirement is met. Provide both positive and negative test cases which check for programming accuracy. Be sure to provide at least one test case for every business requirement. This section should answer the question What is the expected result for each requirement?

S.No

Business Requirement

Data to be used for the test case

Expected Results

9 71722345.doc