Functional SpecificationScenario (Business Area): Business Process: < Name >

Project Identification

Project NameCPI/Project NumberProject Type(CBI, Implementation, CSS, Upgrade, Internal, other)

Customer NameCustomer NumberPlanned Start/Finish

SAP Customer PartnerProject SponsorProgram Manager

SAP Project ManagerCustomer Project ManagerPartner Project Manager

How to use the Template[This chapter gives only explanations on the template. Remove it before completing the template.]

This document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical specification. This document has three main sections General Object information, to be filled in for all RICEFW objects Object specific section, only relevant sections need to be filled in, e.g. if this document specifies a report fill out the general information, the report specific and the test condition section at the end.This document builds and refers to two preceding documents Requirements - BPR Solution design BPDIn addition, all RICEFW object are consolidated in the RICEFW list

The project manager and the quality manager have to revise this template before it is used for the project and especially before it is given to the customer. Sometimes instructions, guidelines, explanations, hints, and tips are provided. It should always be removed from the template for the project.Top-level chapters may not be deleted or inserted; required additions should be made as sub-chapters to existing chapters to provide a consistent representation of this document to the customer. ]

Table of contents

How to use the Template1Purpose of this document3General Object Overview4Process Requirements Reference5Generic WRICEF Descriptions5Object Specific Design7Reporting (operational and analytical)7Interfaces11Data Conversion / Historical Data14Enhancements16Output (e.g. forms)17Workflow19Test Conditions20Document History21

Purpose of this documentThe Specification is the basis for the developments that will be done in SAP. Customer Name has to verify and approve it formally. Realization starts only after approval.Within the SAP Custom Development Methodology, the Specification is the link between the business requirements (normally given in the solution proposal) and the technical design (a separate document). It has the following goals: Reference to the business requirements (customer requirements) given in the solution proposal. Show the mapping into standard SAP products. Describe the solution from an external (user or customer) point of view.Implementation details (database model, report names, and so on) are generally NOT part of the Specification. [Customers shall be enabled to recognize that all their requirements are taken into consideration. For approval of the Specification they have to understand the solution.]

General Object Overview

Object Overview

Object IDBusiness Process

SAP ReleaseSAP Module

Object Type( ) Report( ) Interface( ) Conversion( ) Enhancement( ) Form( ) Workflow

Object Title

Object Description

Mock Up ID / Name

Cycle of Testing / Sprint CycleC1 / C2 / C3 / C4Required Development Completion DateDDMONYY

Complexity of ObjectSimple / Medium / ComplexPriorityLow / Medium / High

SAP Transaction Name(following naming convention guidelines)SAP Program Name

Similar SAP TransactionSimilar SAP Program

FS Control

Functional Consultant Author and Phone NumberLast Name, First Name Process Owner and Phone NumberLast Name, First Name

Planned Date of FS CompletionDDMONYYActual Date of FS CompletionDDMONYY

FS Approved ByLast Name, First NameFS Approval dateDDMONYY

Other Contact and Phone NumberOther Contact and Phone Number

Process Requirements ReferenceProcess Reference

Requirement ID

Requirement Description

Gap to be addressed

Alternative SAP Standard Solution

Generic WRICEF DescriptionsJustification

[Provide a high level description reason from deviation from standard SAP reports or BW reports.

Functional Description / Design

[Provide a high level description of the Report and the business requirement that will be addressed.]

Example:The report will allow users to display contracts that are due to expire and to view the details of these contracts

Transaction Volume

[Please provide an indication of the expected number of records that will need to be read and displayed using this report]

Example:The expected number of records to be displayed on this report is between 10 and 30 from approximately 200 current contracts

Frequency & Timing

[Please indicate the frequency that the report should run; i.e.) Ad Hoc, Daily, Weekly, Quarterly etc, and any timing considerations that should be applied; i.e.) must be run before 7am Monday morning]

Example:The report will be run on a monthly basis on the last day working day of the month.

Dependencies

[Predecessors and successors]

Authorization Requirements

Related Documentation (attach OSS notes, emails, download of existing report, etc)

Object Specific DesignReporting (operational and analytical)

Reporting

WRICEF-IDDescriptionReport Type (ABAP, BI, BOBJ)Data ElementsRelevant KPIOwner

XX-xx-R001

Selection Criteria

[Please enter the selection criteria that should be available to users before running the report. Indicate if the criteria are optional or mandatory and if any data restrictions should apply]

Table/Structure NameField NameFormatDefault ValueTable Value/Checkbox/Radio Button/Radio Button GroupSelect Option or ParameterMandatory or OptionalField Labels

Any grouping of selection screen fields into blocks? Title of Selection Screen Block?

Any preferred layout of the Selection Screen?

Functional Design, Validation and Variants

What is the data to be extracted? Does the Selection Criteria include the full primary keys of the tables from which data is to be extracted?

How should the data be processed in the program functional logic?

Report Output

Output Method[Please indicate the expected output method(s) for the report]

Example:Saved to File / Sent to print / Send to email account / Download to excel

Main Heading[Provide the main heading field for the report]

Example:The main report heading will be: Contracts Nearing Expiry

Sub Heading[Provide any required sub-headings and breaks required in the report]

Example:There will be a sub section under the main contract information detailing the date and time the report was executed and the users username

LAYOUT

Table/Structure NameField NameFormat(ie decimal places)Default ValueColumn NameTranslation Rule

Please list the sequence of the fields (SAP Field names) in which the output must be displayed?

DRILLDOWN REQUIREMENTS

TOTALING[List any totaling or other calculation requirements for the report]

Example:Number of contracts matching user selection criteria to be displayed at the bottom of the report

Any page-break requirements?

SORTING[List any sorting requirements for the report]

Example:Users will be able to sort on contract type and vendor. Default sort sequence will be by contract type.

Any page-break requirements?

PAGE BREAK[Provide details of any page breaking requirements that should be used in addition to field breaks]

Example:Page breaks will be used where necessary to prevent overflow of retrieved data

ERROR HANDLING[Include potential errors, notification procedures, and contingency procedures.]

Typical errors include: No data found for given selection criteria.

Interfaces

Interface

WRICEF-IDDescriptionInterface MethodApplicationsData ElementsFrequency / VolumesOwner

XX-xx-I001

Interface Process Flow Diagram, incl.Transfer Method/ Network Integration

[Please insert an interface flow diagram showing source and target systems with directions]This will include the screen flow diagram, specify the proposed load method (e.g. IDOC, batch transaction processing), and the proposed transfer program name and the inbound/outbound file format (e.g. .txt, .xls)]

File Specifics

[Filenames, delivery method, file type (ascii, comma-delimited, etc)

Mapping SAP Fields to Source / Target

[Please provide details of the expected mapping between the Source / Target system and SAP fields. This can either be done within a table in this document or as an attached Mapping Document.

Specifications for the following elements should be present on the Mapping document (where applicable):

SAP Transaction SAP Screen number SAP Table name SAP Field name (functional) SAP Field name (technical) SAP field length SAP field type Mandatory / Optional flag Source / Target Field ID Source / Target Field Name (functional / technical) Source / Target Field length Source / Target Field type Mapping Details Implementation Comments

Reconciliation Procedures & Audit Requirements

Reporting[Please describe any reporting that is expected to be provided in support of this interface]

Approach[Detail the method of data reconciliation e.g. reports produced in SAP]

Metrics[Provide details on the metrics used to facilitate reconciliation e.g. Record Count]

Error Handling[Include potential errors, notification procedures, and contingency procedures.]

Data Conversion / Historical Data

Conversions

WWRICEF-IDConversion ObjectSourceConversion Activities (e.g. cleansing)Conversion Method (manual / automated)# of Objects to be convertedOwner

XX-xx-C001

1Mapping SAP Fields to Source / Target

[Please provide details of the expected mapping between the Source / Target system and SAP fields. This can either be done within a table in this document or as an attached Mapping Document.

Specifications for the following elements should be present on the Mapping document (where applicable):

SAP Transaction SAP Screen number SAP Table name SAP Field name (functional) SAP Field name (technical) SAP field length SAP field type Mandatory / Optional flag Source / Target Field ID Source / Target Field Name (functional / technical) Source / Target Field length Source / Target Field type Mapping Details Implementation Comments

Reconciliation Procedures & Audit Requirements

Reporting[Please describe any reporting that is expected to be provided in support of this interface]

Approach[Detail the method of data reconciliation e.g. reports produced in SAP]

Metrics[Provide details on the metrics used to facilitate reconciliation e.g. Record Count]

Error Handling[Include potential errors, notification procedures, and contingency procedures.]

Enhancements

enhancements

WRICEF-IDDescriptionData Object (Sales Order)Functional GapAlternative SAP StandardReasonOwner

XX-xx-E001

Functional Design / Flow, Validation and Variants

Flow [Please provide the flow of object to be enhanced. For example in the program XYZ go to screen/Sub screen 101 there modify/add a field]

DesignHow should the data be processed in the program functional logic?

Output (e.g. forms)

Output

WRICEF-IDDescriptionData Object (Sales Order)Output Type (Form, EDI, etc.)FrequencyVolumesOwner

XX-xx-O001

Process Flow Diagram

[Please insert a flow diagram describing the form output procedure e.g. Purchase Order input using transaction ME21N; save Purchase Order automatically generates Purchase Order Form printout]

Form Layout

[Please provide a sample layout for first, subsequent and last pages, detailing actual positions of output fields, fonts, font sizes]

Please indicate if there is pre-printed stock and which portions are on the pre-printed stock

Example:

IDValueDescriptionxxxxx3xxxxxxxxxxxxxxxxxxxx4xxxxxxxxxxxxxxxxxxxxxxxxx5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxForm TitleDate: xxxxx1User: xxxxx2

Printer Requirements

Duplex Printing, label printing, label dimensions, standard, etc.

Legal Requirements

Determine if there is any text that is required legally on the form, including font size, text to be printed on the back of documents,

Existing Sample Forms

[If an existing program is available to be enhanced, provide details in this section] Program Name Menu / Transaction Legacy Form name Legacy Program Title Legacy Form Number Related Transactions

Workflow

Workflow

WRICEF-IDDescriptionBusiness / Data Object (Sales Order)Engaged PartiesOwner

XX-xx-W001

Process Flow Diagram

[Please insert a flow diagram of the workflow]

Trigger Events

Transactions and Batch Programs that trigger the workflow

Start Conditions

Rules and Determination

Standard RulesLatest End, Latest StartRequested End , Requested start

Test ConditionsBusiness Test Conditions (To be furnished by the Functional Consultant)

[Please indicate the business level test conditions that should be used to verify successful operations of the Report]

[Document all technical scenarios associated with this development. Examples would include 1) testing an error-free run; 2) testing the exception processes; 3) testing the error handling.]

[Document all control scenarios associated with this development. Examples would include 1) Rounding of dollars and cents; 2) Audit trail processing; 3) Reconciliation reporting]

Scenario #Input Selection CriteriaExpected Result

Document HistoryAuthors & Participants

RoleName

Business System Analyst

Project Process Owner

Business Unit Process Owner

Consultant

Workshop Participant

Revision History

DateDocument VersionDocument Revision DescriptionAuthor

>1.0Draft for customer review>

Reviewed and Approved By

NameTitleDateApproved

Business System Analyst

Project Process Owner

Business Unit Process Owner

Corporate Process Owner

Internal Audit

21

0000000

Instructions#Instructions1To enter the field map, click on the 'Field Map' tab page.2Enter the name (I.e. Vendor Master) in the Data Type.3A comment is inserted on the column heading. To view the comment, just lace the cursor on the column heading. A popup description should be displayed.4To display the SAP program and screen name, click on the menu option in the SAP application screen and select System>Status.5To display SAP field information click the mouse on 'Technical Information'.6The acronym PT (Process Team), LSA (Legacy System Analyst), and CD (ABAP Code Developer) are the group of people should be filling in the columns. These acronyms are just above the column headers.

GuidelinesThis document identifies the columns on the Field Mapping spreadsheet, that are not self-explanatory.Data Type:Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.T-CodeEnter the transaction code.Note Field UseAcceptable values for this field are:R for requiredO for optionalS for suppressedOrg. LevelSpecifies whether the data is client, company or plant related.SAP UsageDescribes how SAP uses the field. You will have to identify if the field is a primary key. (unique key)As Is UsageIf the field usage is different from what SAP has intended for the field, you need to document the existing implementation intention. You'll have to identify the domain for the primary key.The characteristic of the differences must be listed here in full.Project UsageIf the field usage is different from what SAP has intended for the field, you need to document the future implementation intention(ongoing project).You'll have to identify the domain for the primary key.ERP Best PracticeDescribes the ERP practice if any.The following columns are required to be REVIEWED by the legacy IS/IT.Conversion/Editing Logic:Enter any logic to be followed by the conversion developer, such as: Handling of field lengths that are not equal, default values to use if the legacy field is empty or not valid,legacy fields to be used in conversion that do not directly map to SAP fields. Please refer to list of values if any.Conversion/Mapping Rule:Enter one of the following conversion rule:R0 - System Generated.R1 - Fill with Legacy's system.R2 - Fill with default, select value based on conversion logic.R3 - Fill with Legacy if available, else fill with default.R4 - Fill from prior screen.R9 - No Conversion. Manual online entry post go-live.If you do not know yet what rule to put in, leave this column blank.Data Cleansing Activities:Enter any specific data cleansing activities, that you planned/required to carry out for this field. e.g. Postal Codes, not aligned to standard SAP/country format, Descriptions not consistent with Bombardiers, standard etc.Legacy System:Enter the name of the legacy system, from which this legacy field will be extracted. i.e. Source system for the field.Source Screen or Program Name or ID:Enter the name or ID of the legacy screen, report or other output you are using to identify this legacy field.Source Field Name:Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Source Table Name:Enter the name or ID of the legacy system table or file where this field is located.Source Field Format:Enter the data format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format e.g. dd/mm/yyy)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any decimal, hyphens, slashes, spaces, etc.)Source Field Length:Enter the exact number of characters allowed for this field on the source table or file.

SAP Field MAPData Type: [Data Concept]SAP FIELDSTRANSLATION/EDITING LOGICNON-SAP FIELDSPTPTPTPTPTPTPTE2EPTLSALSALSALSALSAField DataData Element InformationNo. ofNoteDefault ValueFormatTranslation RuleField DataLengthFormatDecimal PlacesTable /FieldShort TextDataNo. ofDecimalFieldTable /FieldStructIDTypeChar'sPlacesUsageStructIDTransaction Code:File Name:Create: Initial Screen(Dynpro and Screen Number)Create: HeaderDocument HistoryCreated By:Date Created:Reviewed By:Date Reviewed:Approved By:Date approved:Modification HistoryDate ModifiedRev#Modified ByBrief Description of change

&C&"Arial,Bold"&12BDB entERPrise ProjectInterface Field Map&L&8&F&R&8&DPage &P of &NProcess Team memberProcess Team memberProcess Team memberProcess Team memberProcess Team memberBombardier:Enter number of decimal places for numeric fields only.Process Team memberLegacy Systems AnalystLegacy Systems AnalystLegacy System AnalystLegacy System AnalystLegacy System AnalystGo to screen in SAP.Highlight field.Press F1 and then Technical InfomationEnter table name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Enter field name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Highlight data element in Help screen, double click to open.Enter short text from data element screen.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationHighlight data element, double click to open.Enter data type from data element screen.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationHighlight data element, double click to open.Enter No. of characters from data element screen.Bombardier:The number of decimal places required for a numeric data type field.Enter any logic to be followed by the conversion developer, such as:how to handle field lengths that are not equalwhat default value to use if the legacy field is empty or not valid.legacy fields to be used in conversion that do not directly map to SAP fields.Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Enter the format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any hyphens, slashes, spaces, etc.)Enter the exact number of characters allowed for this field on the source table or file.Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.Acceptable values for this field are: R for requiredO for optionalS for suppressedEnter any specific data cleansing activities, that you planned/required to carry out for this field. e.g. Postal Codes, not aligned to standard SAP/country format, Descriptions not consistent with BDBs standard etc.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationEnter table name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Enter field name from field data section in Help screen.

0000000

Instructions#Instructions1To enter the field map, click on the 'Field Map' tab page.2Enter the name (I.e. Vendor Master) in the Data Type.3A comment is inserted on the column heading. To view the comment, just lace the cursor on the column heading. A popup description should be displayed.4To display the SAP program and screen name, click on the menu option in the SAP application screen and select System>Status.5To display SAP field information click the mouse on 'Technical Information'.6The acronym PT (Process Team), LSA (Legacy System Analyst), and CD (ABAP Code Developer) are the group of people should be filling in the columns. These acronyms are just above the column headers.

GuidelinesThis document identifies the columns on the Field Mapping spreadsheet, that are not self-explanatory.Data Type:Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.T-CodeEnter the transaction code.Note Field UseAcceptable values for this field are:R for requiredO for optionalS for suppressedOrg. LevelSpecifies whether the data is client, company or plant related.SAP UsageDescribes how SAP uses the field. You will have to identify if the field is a primary key. (unique key)As Is UsageIf the field usage is different from what SAP has intended for the field, you need to document the existing implementation intention. You'll have to identify the domain for the primary key.The characteristic of the differences must be listed here in full.Project UsageIf the field usage is different from what SAP has intended for the field, you need to document the future implementation intention(ongoing project).You'll have to identify the domain for the primary key.ERP Best PracticeDescribes the ERP practice if any.The following columns are required to be REVIEWED by the legacy IS/IT.Conversion/Editing Logic:Enter any logic to be followed by the conversion developer, such as: Handling of field lengths that are not equal, default values to use if the legacy field is empty or not valid,legacy fields to be used in conversion that do not directly map to SAP fields. Please refer to list of values if any.Conversion/Mapping Rule:Enter one of the following conversion rule:R0 - System Generated.R1 - Fill with Legacy's system.R2 - Fill with default, select value based on conversion logic.R3 - Fill with Legacy if available, else fill with default.R4 - Fill from prior screen.R9 - No Conversion. Manual online entry post go-live.If you do not know yet what rule to put in, leave this column blank.Data Cleansing Activities:Enter any specific data cleansing activities, that you planned/required to carry out for this field. e.g. Postal Codes, not aligned to standard SAP/country format, Descriptions not consistent with Bombardiers, standard etc.Legacy System:Enter the name of the legacy system, from which this legacy field will be extracted. i.e. Source system for the field.Source Screen or Program Name or ID:Enter the name or ID of the legacy screen, report or other output you are using to identify this legacy field.Source Field Name:Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Source Table Name:Enter the name or ID of the legacy system table or file where this field is located.Source Field Format:Enter the data format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format e.g. dd/mm/yyy)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any decimal, hyphens, slashes, spaces, etc.)Source Field Length:Enter the exact number of characters allowed for this field on the source table or file.

SAP Field MAPData Type: [Data Concept]SAP FIELDSTRANSLATION/EDITING LOGICNON-SAP FIELDSPTPTPTPTPTPTPTE2EPTLSALSALSALSALSAField DataData Element InformationNo. ofNoteDefault ValueFormatTranslation RuleField DataLengthFormatDecimal PlacesTable /FieldShort TextDataNo. ofDecimalFieldTable /FieldStructIDTypeChar'sPlacesUsageStructIDTransaction Code:File Name:Create: Initial Screen(Dynpro and Screen Number)Create: HeaderDocument HistoryCreated By:Date Created:Reviewed By:Date Reviewed:Approved By:Date approved:Modification HistoryDate ModifiedRev#Modified ByBrief Description of change

&C&"Arial,Bold"&12BDB entERPrise ProjectInterface Field Map&L&8&F&R&8&DPage &P of &NProcess Team memberProcess Team memberProcess Team memberProcess Team memberProcess Team memberBombardier:Enter number of decimal places for numeric fields only.Process Team memberLegacy Systems AnalystLegacy Systems AnalystLegacy System AnalystLegacy System AnalystLegacy System AnalystGo to screen in SAP.Highlight field.Press F1 and then Technical InfomationEnter table name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Enter field name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Highlight data element in Help screen, double click to open.Enter short text from data element screen.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationHighlight data element, double click to open.Enter data type from data element screen.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationHighlight data element, double click to open.Enter No. of characters from data element screen.Bombardier:The number of decimal places required for a numeric data type field.Enter any logic to be followed by the conversion developer, such as:how to handle field lengths that are not equalwhat default value to use if the legacy field is empty or not valid.legacy fields to be used in conversion that do not directly map to SAP fields.Enter the name or ID of the legacy field that maps to the SAP field already entered on this row.Enter the format of the legacy field.Examples are:alpha - full text, alpha - abbreviated textdate (indicate exact format)alphanumeric (indicate exact sequence using a for alpha character, n for numeric character)numeric (indicate any hyphens, slashes, spaces, etc.)Enter the exact number of characters allowed for this field on the source table or file.Enter the type of data covered on this field map. For master data, enter Master Data - .For other data, enter description.Acceptable values for this field are: R for requiredO for optionalS for suppressedEnter any specific data cleansing activities, that you planned/required to carry out for this field. e.g. Postal Codes, not aligned to standard SAP/country format, Descriptions not consistent with BDBs standard etc.Go to screen in SAP.Highlight field.Press F1 and then Technical InfomationEnter table name from field data section in Help screen.Go to screen in SAP.Highlight field.Press F1 and then Technical Infomation.Enter field name from field data section in Help screen.