Sie sind auf Seite 1von 15

<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Design Specification
Title:
Design Specification
ID: (Development
Request ID + Segment F-04
#.)
Document Location:

Approver:
(Print Name)

Signature/ Process Team Lead Development Unit Tester


Date: Coordinato
_______________ r _______________
__ ________________ _
Approver:
(Interface/Conversion
Only)
(Print Name)

Signature/ Data Team Lead N/A N/A


Date:

Confidential Page 1 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Business Overview

Prepared by: Krishna

Project: PEGA Systems SAP Implementation Service Request / Task:

Design Specification ID:


(Development Request ID + Segment #)

Business Description: Pegasystems requires a script to be developed to print Bank of America checks.

Business Area: FI-AP

Request Type: SAP Script form

Scenarios/Business Activity ID:

Submit Date: Due Date:

Business Analyst: Business Tester:

Development Coordinator:

Staff Day Estimate:

Confidential Page 2 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements

General:
Prepared By:

Business Driver: FI-Accounts Payable

What type(s) of business data will be contained in the Development Request?

Develop a SAP script for check printing.

Process Functionality - General: (Describe all process functionality/flow.)

When the payment program (Transaction Code F110) is executed with the payment method C Check,
the program should print the checks for all the vendor payments

Exception Processing:

Error Processing:

Testing: Run transaction F110 to print the check.

Business Assumptions/Risks/Impacts/Alternative Solutions:

1. Language printed on the check is always English.

Scheduling/ Frequency of Processing: Weekly Once

Location of Functionality: FICO---Account Payable

Expected Data Volume: 100 to 200 checks

Security Requirements: (If applicable.)

Special Requirements: If numbers of Invoices are more than 20, check should be print in second page.

Confidential Page 3 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements, Continued


General (Continued):
Describe the selection screen: (Specify selection fields, initializations of selection fields, and what
checks are needed after the user has entered data into the selection fields.)

Screen Reference Range or Value Attributes, Validation/ Comments


Label Field Default Value Checks
Label to be Intervals and Variant locking
displayed on extensions, requirements,
the selection default value context
screen. sensitive field
help, output
attributes
(check box or
radio button),
list of possible
values.

Existing Variants:

Confidential Page 4 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements, Continued


Part A: Report
Prepared By:

What is the access method or path for the report?

What is the distribution list for the report?

What are the printer requirements? (Identify printers, number of copies per printer, and print
immediately.)

What are other similar or related reports?

Data Selection: (What data should the report select? If any data manipulation should occur, specify it
here. Identify the list of fields that should be printed on the report.)

Column Field Name Description Calculations Formats

Describe Special Report Requirements:

Confidential Page 5 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements, Continued


Layout characteristics:

Where should sub-totals occur in the report, if any? (Specify if a page break occurs.)

Where should the totals occur in the report, if any? (Specify if a page break occurs.)

Header Information: (Report Title.)

Report Title 1:

Report Title 2:

Insert Report Layout Form:

Confidential Page 6 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements, Continued


Part B: Form - SAP Scripts
Prepared By: Satya

What is the access method or path for the SAPScript form? Check for SAP Standard layout, If doesnt
support our requirement then go for Z Form Layout .Use t.code SE71 for develop Form.

What are other similar or related SAPScript forms? F110_PRENUM_CHCK

Describe the form requirements, including all special characteristics:

Paying Company Code Address, Date, Check Number, Amount, Amount in words, Payee name and

check sample.pdf
Address, Bank Name and Address and MICR code.

ME Controlled
Disbursement Spec.pdf

State the output type, print program, entry form, and standard layout set: (What form needs to be
copied/modified.): RFFOUS_C

Printer Requirements: (Printer Type, Paper Type, Multiple Copies with impact printer, preprinted forms,
checks.)

Provide a description of the bar-coding, signatures, logo's, OCR, etc.:

1. Sample check attached


2. Digital signature should be Printed on all checks

IMG path/T-code to configure form:

Transaction Code FBZP Payment Methods in Company code Go to 1000 company code and double
click on the item with payment method C (Check) Expand Form Data section.

Output Format: (Attach sample printout, sketch changes.).

Sample Check.pdf

Confidential Page 7 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Logic:

1. Fetch the Check number CHECT from the table REGUD


2. Fetch the Reference number XBLNR from table REGUP
3. Fetch the Invoice number BELNR from table REGUP
4. Fetch the Invoice date BUDAT from table REGUP
5. Fetch the Invoice amount WRBTR from table REGUP
6. Fetch the Amount paid RWBTR from table REGUH
7. Fetch the Discount WSKTO from table REGUP
8. Net Check amount is difference between REGUP-WRBTR & REGUP-WSKTO
9. The check should have the company code address in the designated place of the check. The
information for the Address can be fetched as below:
a. Pick the address number from the table T001 ADRNR
b. Pass the same value in the Table ADRC and fetch the details that need to be printed in
the check at the designated place.
10. Details of the Bank Name and Address of the bank needs to be printed in the check at the
designated Place for which the detail can be fetched from the following details and as well in the
sequence mentioned below:
Bank Name (BNKA-BANKA)
Bank City (BNKA_ORT01) & Region Code (BNKA-PROVZ) & Pin Code (Hardcoded as 04106).
11. The Fractional R/T should be hard coded with the value as 52-153/112 in the place highlighted
in the attached sample

Identifyng Fractional
RT.doc

12. Fetch the Payment date ZLDAT from the table REGUH
13. Check number CHECT from the table REGUD
14. Fetch the amount RWBTR from the table REGUH.
15. Use the standard function module to translate the amount calculated in S.No.14 into text. Always
cents should in Numeric only and should not be converted into text followed by "/ 100".Before
Amount in words the word PAY should be hard code and after amount in words the word U.S
Dollars should be hard code
16. Fetch the Vendor Name ZNME1 , Vendor Street ZSTRA, Vendor city ZORT1, Vendor Postal
Code ZPSTL and Vendor Region ZREGI from the table REGUH.Before Vendor details the word
TO THE ORDER OF should be hard code
17. Digital Signature to be uploaded for Cheque's amount ranging less than 25, 000 $. If amount
greater than 25, 000$ Manual signature is necessary. As shown in Sample cheque the text beneath
the Signature should be displayed always 'Manual Signature is Required over 25, 000$'
18. Fetch the Bank Key UBNKY from REGUH Table and as well the Bank Account Number UBKNT
from the table REGUH. Place the same in the new form layout as suggested in the sample check .

Identifyng Bank key


and bakn Account number.doc

Confidential Page 8 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Functional Requirements, Continued


Part C: Interface/Conversion
Prepared By:

*(To be completed in conjunction with Interface Technology Team Representative.)

* What is the Interface Type? (ALE, EDI, Live Interface, Conversion.)

* Reference Model Name: (Name of the Prototype, If applicable.)

* If EDI/IDOC, please give the following information: (Transaction Set, Standard/Version,


Functional, and Acknowledgement Required Y/N.)

* Document Reference to obtain more detailed info about the systems, if applicable:

If the SAP transaction triggers (or depends on) other interface processes, list the Business
Activity Script ID and Design Specification ID for the related interface/conversion: (Script ID,
Specification ID.)

Describe error handling/audit trails/logging: (Workflow, error logs, and reports, notification processes.)

Confidential Page 9 of 15
<company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T007

Insert File Layout and Screen Flow:

Inbound - For each screen; list the fields that are being used:

Screen 1 Program - Screen


Name of Transaction: Initial Screen
Transaction Screen Field Description Table Field
Name/Value

[OK code] (Button, Function Key, Command Entered, i.e., VA01):

Screen 2 Program - Screen


Name of Transaction: Other Screen
Transaction Screen Field Description Table Field
Name/Value

[OK code] (Button, Function Key, Command Entered, i.e., VA01):

Confidential Page 10 of 15
<Company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T.004

Data Mapping, Conversion and Validation:

(Insert a table including how to map data between different systems. Include conversion and validation rules.)

Legacy Conversion Rules SAP


Field Field Name Data Type L Defaults Field Name/ Screen Name
Description e Translation
n Formatting
g Cross Reference
t Validation
h

Confidential Page 11 of 15
<Company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T.004

Functional Requirements, Continued


Part D: Enhancement - Changing of SAP Repository Objects by the
Customer Without Modification to SAP Objects by Use of SAP Supplied
User Exits
Prepared By:

SAP Object or Process to be enhanced: (i.e. VA01 - Create Order Entry Process.)

Type of Enhancement: (Program user exit, field exits, screen exits, menu exits, or table enhancement.)

Name the SAP Exits/Objects that need to be enhanced:

Describe Enhancement:

Confidential Page 12 of 15
<Company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T.004

Functional Requirements, Continued


Part E: Modification - Specific Changes to SAP Standard Software
Application Code
Prepared By:

SAP Object or Process to be modified: (i.e., VA01 - Create Order Entry Process.)

Name the SAP Objects that need to be modified:

Describe Modification: (Also include the impact of the object modified on other processes. Refer to
created objects.)

Confidential Page 13 of 15
<Company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T.004

Functional Requirements, Continued


Part F: Other Custom Development - Customer-specific Objects Within
the Customer Number Range to Accomplish a Business Process Not
Available in Standard SAP
Prepared By:

Is this an Online or Batch Customization?

What is the processing frequency?

What is the type(s) of business data will be processed? (Order data, Invoice data, Inventory data,
Shipping Papers, or Quality data.)

What are the security requirements?

Describe the customization in SAP Terminology: (Insert a process flow or screen flow diagram, if
necessary for clarification. Describe tables, transactions, reports, forms and other objects that need to
be created or modified.)

Describe Screen Layout: (Screen fields, screen texts, logical grouping of fields, context sensitive help.)

Describe the transaction that invokes/uses the customization:

What is the SAP Menu path/transaction for the customization?

Confidential Page 14 of 15
<Company Name> <ACCTID: PROJID >

SAP FUNCTIONAL SPECIFICATIONS ID: PRP-005-T.004

Functional Requirements, Continued


Part G: Web/Internet Design
Prepared By:

Who will be using the Internet functionality?

Does a standard Internet SAP scenario exist for the required functionality?

Provide a screen flow for the application: (Use Microsoft Word 97 if possible.)

List any special navigation requirements:

Describe what data is transferred between graphical Web layout and SAP. Describe the data in
detail:

Describe the volume and frequency of data usage:

New Development Required:

Describe any specific performance requirements for the Internet interface:

Special Requirements:

Additional Software:

Access:

Confidential Page 15 of 15