FUNCTIONALSPECIFICATION ENHANCEMENT FS_OBJECTID_V0.

Functional Specification AR by Aging Buckets Report

Confidential Document

Note: DO NOT Delete any sections from the document. If they do not apply, please enter NA. Page 1 of 14

Client

FUNCTIONALSPECIFICATION ENHANCEMENT IP_ID 1 V1.0

DOCUMENT CONTROL

Project : Intellectual Property SAP Implementation

Approvals FUNCTION Functional Team Functional Team NAME Karen Smith /John Tsang Ashok DATE *SIGNATURE

Prepared by Reviewed by Approved by

Modification History Version No. Date <mm/dd/y y> Changes made Author Karen Smith / John Tsang Reviewers Docume nts Affected

Creation of Functional Specs doc

2 3

Confidential Document

Note: DO NOT Delete any sections from the document. If they do not apply, please enter NA. Page 2 of 14

Client

FUNCTIONALSPECIFICATION ENHANCEMENT FS_OBJECTID_V0.0

Review Comments

Review Comments Commen t No. 1 2 3 4 5 6 7 8 9 Category (Defect, Suggestion, Clarification) Defect category (Major, Minor) Status (Open, Closed) Other Comment (if any)

Logged by

Section

Description

Confidential Document

Note: DO NOT Delete any sections from the document. Client If they do not apply, please enter NA. Page 3 of 14

Functional Specification Overview Project ID Project Name Project Type Object ID Description Version Development Type Creation Date Development Type Priority Complexity GDM Process ID GDM Process Description Reference Document(s) Risk Category Comments on Risk Category Required by Date AR Aging By Aged Bucket Report Form Report Interface Conversion Enhancement Workflow High Medium Low Simple Medium Complex Very Complex New Development Change Fix Implementation Maintenance Rollout Upgrade

High

Medium

Low

Table of Contents BUSINESS OVERVIEW................................................................................................................................................... 6 1.1 1.2 2 3 4 5 BUSINESS DESCRIPTION:.............................................................................................................. 6 BUSINESS PROCESS: ................................................................................................................... 6

ASSUMPTIONS ......................................................................................................................................................... 6 OUTSTANDING ISSUES ......................................................................................................................................... 6 GLOSSARY ................................................................................................................................................................ 8 FUNCTIONAL REQUIREMENTS:....................................................................................................................... 8 5.1 5.2 5.3 5.4 5.5 BASE BUSINESS OBJECT (MENTION TRANSACTION CODES/ TABLE NAMES, IF POSSIBLE) ................... 8 TECHNICAL DETAILS .................................................................................................................... 8 FUNCTIONAL REQUIREMENT : ...................................................................................................... 11 FUNCTIONAL LOGIC: .................................................................................................................. 11 ADDITIONAL INFORMATION: ........................................................................................................ 11

6: TEST CONDITIONS ................................................................................................................................................. 13 MENTION SPECIFIC TEST SCENARIOS/TEST CASES THAT NEED TO BE RUN THROUGH TO ENSURE THE CORRECT FUNCTIONING OF THE DEVELOPMENT, IF ANY (E.G. SPECIFIC ORGANIZATION STRUCTURE VALUES TO BE USED ETC.). THESE INPUTS WILL BE USED BY THE DEVELOPMENT TEAM TO GENERATE THE DETAILED UNIT AND SYSTEM TEST PLANS. .. 13 7: ENHANCEMENT SPECIFICATIONS ................................................................................................................... 13 8: WORKFLOW ENHANCEMENT SPECIFICATIONS ........................................................................................ 13

Business Overview
1.1 Business Description:

Client is a financial unit that will have sales of Intellectual Property to both Intercompany and External customers. This report will be used to analyze the Open Accounts Receivable balances and the age of the receivables. .

1.2

Business Process: Run the report on demand

Assumptions
No. 1 2 3 4 5 6 7 8 9 Assumption Field mapping to SAP involve direct field mappings and calculated values This report will be written in ABAP and assigned a transaction code The report can be downloaded into excel Invoice amounts will be reported by document currency This will be printed on a pre-set print layout of Landscape Report will display detailed line items, the tally of lines will match with table BSID Line item aging will be on the top portion of the report. A totaled aging summary by customer will be on the bottom of the report The report will compile line items by company code separately and then in customer number order. The summary at the bottom will also be by company code, separately and then in customer number order

Outstanding Issues
No 1 2 3 4 Issue Responsible Due Date Closed Date

Glossary
Term IP Intellectual Property Division Description

Functional Requirements:
1.3 Base Business Object (Mention Transaction Codes/ Table Names, if possible)
Invoice data will be extracted out of table BSID. The report will have a front end selection screen to select by customer, company code, and key date(As of Date). A mock up of the

report is attached. 1.4 Technical Details

AR AGING BY AGED BUCKETS REPORT.xlsx

The report will be run on demand. The title of the Report will be AR Aging by Aged Buckets. The second line of the title will be As Of: MM/DD/YYYY, the date being copied from the key date on the selection screen. The report columns for the detailed portion of the report are as follows: 1. Company Code 2. Customer Number 3. Customer Name 4. Currency 5. Invoice Number 6. Invoice Date 7. Due Date 8. 9. 10. 11. 12. 13. ADL Outstanding Amount Current (Not Due) 1 30 Days Past Due 31 60 Days Past Due 61 90 Days Past Due

14. 91 180 Days Past Due 15. 181 360 Days Past Due 16. Over 360 Days Past Due Program will pull data from table BSID based on the key date and company code specified in selection screen. Extract logic for each column is as follows:

DATA MAPPING: Column Number 1 Company Code 2 Customer Number 3 Customer Name Extract Logic Pull from company Code in selection screen BSID-KUNNR Match BSID-KUNNR to Table KNA1-KUNNR and pull field Name 1 (KNA1-NAME1) BSID-WAERS Invoice Number is designed as Document Number BSIDBELNR BSID-BLDAT This is a calculated date using baseline date plus Days 1 (BSID-ZFBDT plus BSIDZBD1T) This is a calculated field using key date from selection screen as date of reference BSID-WRBTR This is a calculated field using key date from selection screen as date of reference. The formula is key date minus baseline date plus Days 1. If value is zero or negative, put the Outstanding Amount (BSID-WRBTR) into column 10 The formula is key date minus baseline date plus Days 1. If value is 1 to 30, put the Outstanding Amount (BSID-WRBTR) in column 11 The formula is key date minus baseline date plus Days 1. If value is 31 to 60, put the Outstanding Amount (BSID-WRBTR) in column 12 The formula is key date minus baseline date plus Days 1. If value is 61 to 90, put the Outstanding Amount (BSID-WRBTR) in column 13 The formula is key date minus baseline date plus Days 1. If value is 91 to 180, put the Outstanding Amount (BSID-WRBTR) in column 14 The formula is key date minus baseline date plus The formula is key date minus base line date plus Days 1. Put value in this field Content Table Fields

4 Currency 5 Invoice Number

6 Invoice Date 7 Due Date

8 ADL

9 Outstanding Amount 10 Current (Not Due)

11 1 30 Days Past Due

This is a calculated field using key date from selection screen as date of reference.

12 31 60 Days Past Due

This is a calculated field using key date from selection screen as date of reference.

13 61 90 Days Past Due

This is a calculated field using key date from selection screen as date of reference.

14 91 180 Days Past Due

This is a calculated field using key date from selection screen as date of reference.

15 181 360 Days Past Due

This is a calculated field using

key date from selection screen as date of reference.

16 Over 360 Days Past Due

This is a calculated field using key date from selection screen as date of reference.

Days 1. If value is 181 to 360, put the Outstanding Amount (BSID-WRBTR) in column 15 The formula is key date minus baseline date plus Days 1. If value greater than 360, put the Outstanding Amount (BSID-WRBTR) in column 16

The bottom, summarized portion of the report, will have the columns as follows: DATA MAPPING: Column Number 1 Company Code 2 Customer Number 3 Customer Name Extract Logic Pull from company Code in selection screen BSID-KUNNR Match BSID-KUNNR to Table KNA1-KUNNR and pull field Name 1 (KNA1-NAME1) BSID-WAERS Keep column blank Keep column blank Keep column blank Keep column blank BSID-WRBTR This field will be a total of the outstanding amount of the customer This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer This is a calculated field using The formula is key date minus baseline date plus Days 1. If value is zero or negative, put the Outstanding Amount (BSID-WRBTR) into column 10 The formula is key date minus baseline date plus Days 1. If value is 1 to 30, put the Outstanding Amount (BSID-WRBTR) in column 11 The formula is key date minus baseline date plus Days 1. If value is 31 to 60, put the Outstanding Amount (BSID-WRBTR) in column 12 The formula is key date Content Table Fields

4 Currency 5 Invoice Number 6 Invoice Date 7 Due Date 8 ADL 9 Outstanding Amount

10 Current (Not Due)

11 1 30 Days Past Due

12 31 60 Days Past Due

13 61 90 Days Past Due

key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer 14 91 180 Days Past Due This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer This is a calculated field using key date from selection screen as date of reference. This field will be a total of the outstanding amount of the customer

minus baseline date plus Days 1. If value is 61 to 90, put the Outstanding Amount (BSID-WRBTR) in column 13 The formula is key date minus baseline date plus Days 1. If value is 91 to 180, put the Outstanding Amount (BSID-WRBTR) in column 14 The formula is key date minus baseline date plus Days 1. If value is 181 to 360, put the Outstanding Amount (BSID-WRBTR) in column 15 The formula is key date minus baseline date plus Days 1. If value greater than 360, put the Outstanding Amount (BSID-WRBTR) in column 16

15 181 360 Days Past Due

16 Over 360 Days Past Due

Configurations Screen Shot: There is no configuration for this report.

1.5

Functional Requirement:
This report will be created in ABAP with a Z transaction code that can be assigned to designated users.

1.6

Functional Logic:
No extra configurations are needed, invoice data already exists in table BSID. Report column are a mixture of field mappings and calculated values. Additional Information: Report will be run on demand. Report access will be controlled by security.

Related Customization (if any)

Expected Data Volumes

Security Considerations

Exception Handling

Error Handling

IT department will monitor if a program errors out.

Re-run Option Additional Comments

Yes

No

6: Test Conditions Mention specific test scenarios/test cases that need to be run through to ensure the correct functioning of the development, if any (e.g. specific Organization Structure values to be used etc.). These inputs will be used by the development team to generate the detailed Unit and System Test plans.
No 1 Test Condition Description Run the report and reconcile with FBL5N and/or Table BSID Run the report and reconcile the detail by customer with the summary by customer Expected Results The totals by company code/customer/aging bucket will matchts The totals of the detail by customer will match the summary by customer.

3 4 5 6

7: Enhancement Specifications
Enhancement Type User Exit Screen Exit Menu Exit Field Exit Table Exit Function Exit Workflow Use (Fill Next Section)

Name of the SAP Exit Initiating Transaction

8: Workflow Enhancement Specifications

Enhancement Type Name of the Workflow Initiating Transaction Detailed description of Workflow Workflow

Enhancement Check/Start Conditions (Explain any special conditions that will need to be considered) Triggering/Terminating Events (Explain in detail what are the trigger points and also conditions will need to terminate an In progress workflow) Agent Assignments (Identify in detail for every dialog step the agent or processor) Deadline Monitoring/Escalation process (Describe any deadline or escalation requirement) Workflow Reporting Requirements (Identify any workflow specific reporting requirements, many standard SAP WF reports exist already)