sample functional spec

Project Trading Partner from CD to CFP

Development Request:

Title: Transfer Trading Partner to CFP from CD for Specific Accounts

Functional Specification

Reques t ID : BP060I0050

Table of contents

1 REQUEST OVERVIEW.............................................................................................................................................................4

1.1 INTRODUCTION.......................................................................................................................................................................41.1.1 Purpose...........................................................................................................................................................................4

1.2 REQUEST OVERVIEW..............................................................................................................................................................4

2 REVISION HISTORY.................................................................................................................................................................5

3 *FUNCTIONAL SPECIFICATION APPROVAL.........................................................................................................................5

4 TECHNICAL ESTIMATES.........................................................................................................................................................5

5 TECHNICAL SPECIFICATION APPROVAL.............................................................................................................................5

6 FUNCTIONAL SPECIFICATIONS.............................................................................................................................................6

6.1 FUNCTIONAL REQUIREMENTS..................................................................................................................................................66.1.1 *Business Driver..............................................................................................................................................................66.1.2 *General Process Description.........................................................................................................................................76.1.3 Alternative Solutions........................................................................................................................................................76.1.4 Assumptions....................................................................................................................................................................76.1.5 Issues..............................................................................................................................................................................76.1.6 *Related Business Processes:........................................................................................................................................86.1.7 Security/Authorization Requirements..............................................................................................................................86.1.8 Documentation Requirements.........................................................................................................................................8

6.2 FUNCTIONAL DESCRIPTION: REPORT AND FORMS.....................................................................................................................86.2.1 Report/Form Attributes....................................................................................................................................................86.2.2 Type of Development......................................................................................................................................................86.2.3 *Selection Screen (Report Selection Criteria)..................................................................................................................96.2.4 *Data Selection...............................................................................................................................................................96.2.5 *Report/Form Layout (if not provided in attachment above)............................................................................................96.2.6 *Exception Handling Rules..............................................................................................................................................96.2.7 Special Characteristics....................................................................................................................................................96.2.8 *Printing Requirements...................................................................................................................................................9

6.3 FUNCTIONAL DESCRIPTION: INTERFACE, DATA CONVERSION AND EDI.......................................................................................96.3.1 *Dependencies/Prerequisites........................................................................................................................................106.3.2 *Conversion/Interface Information.................................................................................................................................106.3.3 Legacy Systems Involved..............................................................................................................................................106.3.4 *Data Requirements......................................................................................................................................................106.3.5 Selection Screen..............................................................................................................Error! Bookmark not defined.6.3.6 *Processing Requirements (Source-Extraction, Target-Load).......................................................................................106.3.7 *Exception Handling Rules............................................................................................................................................116.3.8 Special Requirements...................................................................................................................................................11

7 FUNCTIONAL TEST...............................................................................................................................................................12

7.1 TEST SPECIFICATION............................................................................................................................................................127.2 *TESTING APPROACH............................................................................................................................................................127.3 TEST DATA & OTHER NEEDS................................................................................................................................................127.4 TEST SYSTEM & ENVIRONMENT.............................................................................................................................................127.5 *FUNCTIONAL TEST SCENARIOS............................................................................................................................................12

8 TECHNICAL SPECIFICATIONS.............................................................................................................................................14

8.1 TECHNICAL REQUIREMENTS..................................................................................................................................................148.1.1 *Business Driver............................................................................................................................................................148.1.2 *General Process Description.......................................................................................................................................148.1.3 Alternative Solutions......................................................................................................................................................148.1.4 Assumptions..................................................................................................................................................................148.1.5 Process Flow.................................................................................................................................................................148.1.6 Issues............................................................................................................................................................................158.1.7 Security Details.............................................................................................................................................................158.1.8 Exception handling........................................................................................................................................................158.1.9 Dependencies / Prerequisites........................................................................................................................................15

8.2 DETAILED TECHNICAL DESCRIPTION: REPORT, FORM AND QUERY...........................................................................................158.2.1 *Report, SAPScript Forms or Smartforms.....................................................................................................................158.2.2 *Selection Screen (Report Selection Criteria)................................................................................................................158.2.3 Special Requirements Processing.................................................................................................................................16

Conf iden t ia l 4 /10 /2023/ t t / f i l e_conver t /54 fd922b4a7959422b8b4613/document .doc


8.2.4 Attributes.......................................................................................................................................................................168.2.5 Variants Created and Data in Variants..........................................................................................................................168.2.6 *Program Flow and Pseudocode...................................................................................................................................16

8.3 DETAILED TECHNICAL DESCRIPTION: INTERFACE, DATA CONVERSION AND EDI........................................................................168.3.1 *Attributes......................................................................................................................................................................168.3.2 *Interface/Conversion Steps..........................................................................................................................................168.3.3 Data Requirements.......................................................................................................................................................168.3.4 *Scheduling Requirements............................................................................................................................................178.3.5 *Update Process (Required for inbound interfaces)......................................................................................................17

9 DATA DESCRIPTION..............................................................................................................................................................18

9.1 NEW STRUCTURE: ZFKKCK.................................................................................................ERROR! BOOKMARK NOT DEFINED.9.2 NEW STRUCTURE: ZFKKCK.................................................................................................ERROR! BOOKMARK NOT DEFINED.

10 TECHNICAL TEST PLAN.......................................................................................................................................................18

10.1 TESTING APPROACH.............................................................................................................................................................1810.2 COMPLETION CRITERIA.........................................................................................................................................................1810.3 TEST DATA & OTHER NEEDS................................................................................................................................................1810.4 TEST TOOLS & ENVIRONMENT...............................................................................................................................................1810.5 TEST DEPENDENCIES/CONSTRAINTS......................................................................................................................................1810.6 UNIT TEST CASES AND RESULTS...........................................................................................................................................18

11 Appendix A: Data Mapping...................................................................................................................................................19



1 Request Overview

1.1 Introduction

1.1.1 Purpose

This document will be used to capture AIG’s approved business requirements in a clear, concise and standardized format from which the technical specifications can then be developed.

Fields marked with an asterisk (*) and highlighted in red are mandatory and therefore must be completed by the functional analyst in order for the functional specification to be approved and moved to technical specification development stage. NOTE: Sections not relevant for the development request may be removed from the document.

Business and Technical signoff (Section 5) is considered AIG’s acceptance of this deliverable (specification). Modifications and/or additions to this specification subsequent to approval will be subject to a change order and must be processed via Change Control.

1.2 Request Overview*Date: SAP

Version: R/3 R/3 Module:

Dev. Request ID: Process Team:

*Title Transfer Trading Partner to CFP from CD

*Short Description

*Request Type: ( ) Form ( ) Report ( ) Interface

( ) Conversion (X ) R/3 Extension ( ) Workflow

( ) Query () Other Development

Systems Impacted: (X)R/3 and/or FSCD ( ) CRM ( ) BW

( ) Other

*Date Required:

*Complexity: ( ) High (X) Medium ( ) Low

*Business Owner: Mark Paffmann Ext.:

*Functional Analyst: Ext.:

*BE Team QA Ext.:

Technical Analyst/ Developer:

Ext.:



2 Revision History

To track changes to specification after it has been approved

Version # Date Modified Modified By Brief Description of Change

1.1 08/25/2010 Additional information

3 *Functional Specification Approval

Final Sign-off here indicates acceptance of functional specification. (Only upon successful completion of Functional Specification review.)

Signature Date

*Business Process Owner Approval:

*Business Engineering Process Lead Approval (BE Team QA):

*Application Lead Approval:

4 Technical Estimates

Technical Estimate Plan Revised

Technical Spec.

Development

Unit Test

QC Review

Total

5 Technical Specification Approval

Final Sign-off here indicates acceptance of technical specification. Signature Date

*Client Dev. Lead Approval:

*App. Dev. Approval:



6 Functional Specifications

6.1 Functional Requirements

6.1.1 *Business Driver List business requirements for this request. Currently for transactions posting to accounts listed in set YV_ICACCT only inter-company transactions are being populated to the trading partner field in CD only and not transferred to shadow GL (FI) so they can be included in file to CFP GL (program ZCLI_SAPGL_TO_CFP). Need trading partner to transfer to shadow GL and onto CFP GL, this will require validation in CD as well as FI (currently have files uploaded in FI that contain postings to GL accounts included in set YV_ICACCT). In CD Trading Partner field (FKKOP-VBUND) can be entered during clarification, disbursement, journal entry posting and reversal (Believe event 670 can be used for most of these transactions. In FI the Trading Partner field will need to be made available for posting on t-code FB01 and FB02 (did not see any other t-code available for posting entries that users have access to), this is required due to Treasury settling and reconciling inter-company transaction occuring in CD.

1. For GL Accounts sitting in the SAP CD set YV_ICACCT add validation to transaction codes in FI and CD module of SAP under R3P to force users to input trading partner.

2. Include trading partner in any summarization of similar GL postings when transferring items over from CD to FI (shadow GL) using FPG1.

3. GL accounts not included on the inter-company tables do not populate to the trading partner field in FI even though users are populating this field in CD. This is required as trading partner populated from inter-company transactions does populate the field.

4. Same validation being done in CD would be required for postings made to transaction codes FB01 and FB02 (also any other t-code currently not used that would allow user to make postings).

5. The trading partner should also populate the trading partner field on the file sent to DI Layer. Currently this field only populated when trading partner account posted to by SAP for inter-company transactions. Layout is attached for file sent to DI-Layer below:

6. There is also a file being uploaded on a monthly basis for PCG/WINS that post entries to these accounts through FI, will need to have trading partner field added to layout for upload file to ensure field is populated. Example of file being uploaded is in the 2 files above, Excel spreadsheet is file layout.

7. Any reversal of documents whether done in FI or CD should capture the trading partner



originally used in the reversal document.

8. Will also need to define trading partners in SAP CD and keep this table in sync with CFP GL (table T880).

6.1.2 *General Process DescriptionDescribe at a high level the process being requested. Description may include a process flow if deemed necessary.Any posting made to GL Accounts in set YV_ICACCT requires trading partner and trading partner for all non inter-company gl accounts should transfer from CD to FI and also populate file sent to DI Layer on interface report. Also any reversal of document used for inter-company should also capture and include trading partner stored in the original document being reversed.

6.1.3 Alternative SolutionsIf applicable, list any alternative solutions to the business requirements that were considered and reasons for their rejection.

6.1.4 Assumptions List factors that affect the requirements. These factors may not be design constraints, but may be areas in which future changes might drive change in the requirements.During the last week of the month Treasury makes request to remove automatic posting only for inter-company accounts to clear balances for CD transactions. Should continue to ensure that the trading partner field is validated for these transactions also.

6.1.5 Issues List any issues affecting completion of the Functional Specification.# Issue Resolution

1

2

3



6.1.6 *Related Business Processes: List the BPP(s) related to the process, sub-process and activities identified in this RequestProcess: Sub-Process: Activity:

BPP1:

Process: Sub-Process: Activity:

BPP2:

Process: Sub-Process: Activity:

BPP3:

6.1.7 Security/Authorization RequirementsProvide any special authorization checking or data security provisions required.

6.1.8 Documentation RequirementsProvide documentation expectations such as online documentation, release notes, etc.None.

6.2 Functional Description: Report and Forms

6.2.1 Report/Form Attributes

*Name of Report/Form/Query: N/A

*Type: ( ) ABAP report ( ) Form ( ) Query

*Report Layout attached/linked: ( ) No ( ) Yes – Filename:

*Run Mode: ( ) Foreground (Online)

( ) Background (Batch)

*Frequency: ( ) Real-time ( ) On-demand ( ) One-time

( ) Annually ( ) Quarterly ( ) Monthly

( ) Weekly ( ) Daily ( ) Other

Expected Data Volume (Records): TBD

Date test data will be available: Immediately

What SAP transactions are involved?

Menu path for transaction(s)

6.2.2 Type of Development

*Existing vs. Custom: ( ) Modification of Standard Report/Form ( ) Custom Report/Form

*Have you looked at possible standard Reports/Forms? ( ) Yes ( ) No

Name of Standard Report/Form:

Access or path for the Report/Form:



6.2.3 *Selection Screen (Report Selection Criteria)Describe the selection screen of the report. Specify the fields for the selection and what checks need to be done after the user has entered his or her criteria.Screen Label Referenced

FieldRange of Value

Attributes, Default Values

Validations / Checks

Comments/ Selection Criteria (options, parameters, radio buttons, checkboxes)

6.2.4 *Data Selection(Describe what data should selected by the report.)

6.2.5 *Report/Form Layout (if not provided in attachment above)Provide a layout of the form or report here if one has not been provided in a separate attachment. Note you may use screen captures as required. Layouts should include: Desired report headers and footers, report columns and field spacing. None.

6.2.6 *Exception Handling RulesDescribe the exception handling processes to support the rules. Include any error conditions, error messages, etc.None.

6.2.7 Special Characteristics(ex. Sorting, grouping, where total or subtotals should occur, if any, drilldown, etc.) List any special requirements such as signatures, logos, OCR, bar-coding, function keys, menu bars, special timing, language translations, etc.None.

6.2.8 *Printing RequirementsIdentify any printing requirements such as Special Paper, Preprinted Forms: (e.g. checks, multiple copies with impact printer, etc.)None.

6.3 Functional Description: Interface, Data conversion and EDI*Name of Interface or Conversion:

*Type: ( ) Interface ( ) Conversion

*Mapping Attachment: ( ) No ( ) Yes – Filename:



6.3.1 *Dependencies/PrerequisitesList any dependencies or other external requirements that must be met before the interface/conversion can be completed. Include both legacy and SAP system dependencies (e.g. R/3 upgrade/patch, files from other systems, condition of data, etc.)

Description Related Document(s)

6.3.2 *Conversion/Interface Information

*Direction of Interface: ( ) Inbound to SAP

( ) Outbound from SAP

( ) Bi-Directional

*Frequency: ( ) Real-time ( ) On-demand ( ) One-time

( ) Annually ( ) Quarterly ( ) Monthly

( ) Weekly ( ) Daily ( ) Other

Acknowledgement Required: ( ) No ( ) Yes

*Expected Data Volume: TBD

Date test data is to become available: TBD

6.3.3 Legacy Systems InvolvedList the existing Legacy systems along with a short description involved in this development effort.

6.3.4 *Data Requirements Describe the condition of data to be converted/transferred (if known). Provide a high level data map by identifying source or target fields in SAP. Data Condition: Data must match layout described in mapping document (below).

*Data Mapping

6.3.5 *Processing Requirements (Source-Extraction, Target-Load)NOTE: Do not include field-level details – these should be specified in the data mapping document.SAP Load/Extraction: For inbound interfaces describe how the inbound data should be processed, including a Transaction Code that should be executed / simulated, or a BAPI / Program if known. For outbound interfaces describe how the outbound data should be derived, including source tables, selection criteria, and list any relevant transactions / BAPIs.



6.3.6 *Exception Handling RulesSpecify instructions to be followed when errors occur, or any processing outside the normal process flow.

6.3.7 Special RequirementsProvide any special requirements related to this development effort such as language translations, configurability or personalization allowed, etc.None.



7 Functional Test

7.1 Test SpecificationThis portion of the document is used to plan the unit testing. It includes items such as defining the test participants, the test environment, the schedule, and scope of the testing event.Functional Test Lead: Victor Randolph

Additional Test Team Participant(s):

7.2 *Testing ApproachProvide a brief description of the overall approach and testing needs, including any sequencing dependencies.

7.3 Test Data & Other NeedsIf any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.

7.4 Test System & EnvironmentIdentify test system and client.Test System: R3D

Client: 120

7.5 *Functional Test ScenariosDocument test scenarios to test all of the functional requirements. Include a test scenario for each different business scenario that may occur.ID Test Scenario Expected

ResultsComments

1. Cash coming in from Company Code 0108 should get posted to 0165 with Trading Partner in 0407. Canadian currency to US currency.



2. Remove all Company Codes from all RSP Trading Partner table and only leave Company Code 0183. Posting allocation posting to 0165. All RSO’s Company Codes should be mapped to 0183.



8 Technical Specifications

8.1 Technical Requirements

8.1.1 *Business Driver List business requirements for this request.

8.1.2 *General Process DescriptionDescribe at a high level the process being requested

8.1.3 Alternative SolutionsIf applicable, list any alternative solutions considered and reasons for their rejection.

8.1.4 AssumptionsDescribe special issues and assumptions, which might impact the overall design or implementation of the software. Include any business product line considerations that will impact the manner in which the software is to be designed, implemented or tested.

8.1.5 Process FlowInclude a Visio diagram of the technical process flow including triggers, inputs, outputs and program flow.



8.1.6 Issues List any issues affecting completion of the Technical Specification.# Issue Resolution

1

2

8.1.7 Security DetailsDescribe processing required to address security requirements defined in the functional specification.None.

8.1.8 Exception handlingDescribe the exception handling components used to support the rules specified in the functional specification. Include any error conditions, error messages, exception classes, return codes, etc.

8.1.9 Dependencies / PrerequisitesList any dependencies or other external requirements that must be met before the development object can be completed. Include both legacy and SAP system dependencies (e.g. R/3 upgrade/patch, configuration requirements, files from other systems, condition of data, etc.)Description Related document(s)

8.2 Detailed Technical Description: Report, Form and Query

8.2.1 *Report, SAPScript Forms or Smartforms

*Report will be created via: ( ) ABAP Program ( ) ALV ( ) Smartform

( ) SAPScript ( ) BW ( ) Report Writer/Painter( ) Other

*Name of Report/Form: ( ) Report ( ) Form

Report/Form Layout Attachment: ( ) No ( ) Yes - Filename:________________________

8.2.2 *Selection Screen (Report Selection Criteria)Describe the selection screen of the report. Specify the fields for the selection and what checks need to be done after the user has entered his or her criteria.Screen Label Referenced

FieldRange of Value

Attributes, Default Values

Validations / Checks

Comments/ Selection Criteria (options, parameters, radio buttons, checkboxes)



8.2.3 Special Requirements ProcessingDescribe the processing required to support any special requirements defined in the functional specification. (e.g. signatures, logos, OCR, bar coding, function keys, menu bars, special timing, etc.)None.

8.2.4 Attributes

Logical Database: None

External Form Calls: None

Called Transactions: TBD

Function Group: None

Function Calls:

8.2.5 Variants Created and Data in Variants

None

8.2.6 *Program Flow and PseudocodeBriefly explain the program flow and provide pseudo-code.

8.3 Detailed Technical Description: Interface, Data conversion and EDI

8.3.1 *Attributes

*Interface Type: ( ) ALE( ) XML

( ) EDI( ) Other

(X) Flat File ( ) BAPI / RFC

Function Group: None

Posting Type: None

Called Transactions: TBD

BAPI Used: None

Logical Database: None

8.3.2 *Interface/Conversion StepsDescribe all manual and system steps to process this interface or conversion. This should include all the restart procedure.

8.3.3 Data Requirements

Data Mapping: Legacy/SAP Mapping document template provided in Functional Spec



8.3.4 *Scheduling RequirementsSpecify whether jobs should run during off-peak hours, frequency, manual or automatic start.None.

8.3.5 *Update Process (Required for inbound interfaces)Describe the process that will occur to update the proper data requested. A pseudo-code document may be attached.Update Program Name(s):

Transfer Mechanism: ( ) BDC ( ) Direct Input ( ) LSMW

( ) Call Transaction ( ) Function Module ( ) BAPI

( ) Other

Update Parameters:



9 Data Description

10 Technical Test Plan

This section of the document is used to plan the Technical Unit Test. It includes items such as defining the test participants, the test environment, the schedule, and scope of the testing event. Unit test cases and results will be documented in a separate document.

10.1 Testing ApproachProvide a brief description of the overall approach and testing needs

10.2 Completion Criteria How will you determine test completeness?

10.3 Test Data & Other NeedsIf any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.

10.4 Test Tools & EnvironmentIdentify test tools required for the technical testTest System R3D

Client 120

Tool N/A

Test Programs N/A

10.5 Test Dependencies/ConstraintsIndicate if there are any dependencies or constraints related to this object.No.

10.6 Unit Test Cases and ResultsUnit test cases and results will be documented in a separate document. Link completed Unit test results document below.



11 Appendix A: Data Mapping


sample functional spec

Documents