Fd Report Sasmple

Report Functional Design AP353

For O-I SAP Implementation Project

September 2, 2010

Version 1.1

CONFIDENTIAL. This document contains trade secret information. Disclosure, use or

reproduction outside O-I and inside O-I, to or by those employees who do not have a need to

know is prohibited except as authorized by O-I In writing. (Copyright O-I, Incorporated 2010. All

rights reserved.)

rordosgo, 30/08/10,

Introduction. A Functional Design (FD) is a document used in a pre-development phase to translate all notes, concepts, and scope into a complete requirements document. The document can include anything from flowcharts, screenshots, and data specifications . At a minimum, an FD will contain an organized list of requirements that can be used for development, testing, and client sign-off. To create a FD you will need the following documents : BP315 (Business SubProcess Design) and the AP215 (Fit/Gap Analysis). A FD with a Technical Design (TD) are needed to create a RICEFW object. A RICEFW object could be : R = Report I = Interface C = Conversion E = Extension F = Forms W = Workflow

document.docO-I SAP Implementation Project

Table of Contents1 Document Information..............................................................................................................................................42 RASCI Information...................................................................................................................................................43 Document History.....................................................................................................................................................5

3.1 Change History..............................................................................................................................................53.2 Review Detail................................................................................................................................................53.3 Approval Detail..............................................................................................................................................5

4 Overview and Scope................................................................................................................................................64.1 Functional Description / Overview.................................................................................................................6

4.1.1 Detailed Requirements...................................................................................................................64.1.2 Gap in Standard SAP Filled by This Item.......................................................................................64.1.3 Solution Alternatives.......................................................................................................................74.1.4 Proposed Solution...........................................................................................................................74.1.5 Initiating Process/Transaction/Program..........................................................................................74.1.6 If ECC, the data is primarily in what table(s)...................................................................................74.1.7 Transaction Volume........................................................................................................................74.1.8 Frequency and Timing....................................................................................................................74.1.9 Processing Type.............................................................................................................................84.1.10 Performance...................................................................................................................................84.1.11 Output Type (Online/Print/Spreadsheet).........................................................................................8

4.1.10 Retention Requirements................................................................................................................................84.1.11 Audience and Distribution...............................................................................................................8

4.2 Business Benefit............................................................................................................................................94.3 Score Card....................................................................................................................................................94.4 Scope............................................................................................................................................................ 9

4.4.1 Functionality....................................................................................................................................94.4.2 Region or Localization Considerations.........................................................................................10

4.5 Dependencies/Constraints..........................................................................................................................104.6 Assumptions................................................................................................................................................10

5 ECC Detailed Functional Requirements................................................................................................................115.1 Functional Specification..............................................................................................................................115.2 Process Flow Diagram................................................................................................................................125.3 Initiating Process/Transaction/Program......................................................................................................125.4 Report Layout..............................................................................................................................................135.5 Report Fields...............................................................................................................................................13

5.5.1 For ECC Fields:............................................................................................................................135.5.2 Other.............................................................................................................................................16

5.6 Selection Criteria.........................................................................................................................................165.7 Main Heading..............................................................................................................................................165.8 Sub Heading................................................................................................................................................165.9 Totalling.......................................................................................................................................................175.10 Sorting......................................................................................................................................................... 175.11 Page Breaks................................................................................................................................................17

5.13 Interactive Capabilities................................................................................................................................175.14 Retention Requirements..............................................................................................................................175.15 Audience and Distribution...........................................................................................................................175.16 Language Considerations...........................................................................................................................185.17 Custom Tables/Fields Specifications..........................................................................................................18

5.17.1 Table 1: <TABLE NAME>.............................................................................................................185.18 Initial Data Set-Up, Conversion Requirements............................................................................................185.19 Configuration Requirements........................................................................................................................185.20 Error Handling.............................................................................................................................................185.21 Security and Authorization..........................................................................................................................195.22 Existing Sample Reports.............................................................................................................................195.23 Reconciliation Procedures and Audit Requirements...................................................................................19

5.23.1 Approach.......................................................................................................................................19

of 30 Printed: 11-Apr-238:16 AM


5.23.2 Metrics...........................................................................................................................................205.24 Processing and Operational Considerations...............................................................................................20

5.24.1 Processing Type...........................................................................................................................205.24.2 Transaction Volume......................................................................................................................205.24.3 Frequency and Timing..................................................................................................................205.24.4 Performance.................................................................................................................................205.24.5 Batch Requirements.....................................................................................................................205.24.6 Data Maintenance Requirements.................................................................................................215.24.7 Re-use Details..............................................................................................................................215.24.8 Multi-company, Multi-jurisdiction Considerations..........................................................................22

6 BW Detailed Functional Requirements..................................................................................................................226.1 Functional Specification..............................................................................................................................22

6.1.1 Summary Report..........................................................................................................................226.2 Process Flow Diagram................................................................................................................................236.3 Report Layout..............................................................................................................................................236.4 Report Fields...............................................................................................................................................23

6.4.1 Rows..................................................................................................................................................236.4.2 Columns.............................................................................................................................................23

6.5 Filters........................................................................................................................................................... 246.6 Selection Criteria (Prompts)........................................................................................................................246.7 Calculations/Algorithms/Derivations............................................................................................................246.8 Global Calculated/Restricted Key Figures...................................................................................................246.9 Report-to-Report Interface Requirements (Jump Query)............................................................................246.10 Exceptions...................................................................................................................................................246.11 Conditions...................................................................................................................................................256.12 Existing Sample Reports.............................................................................................................................256.13 Reporting Variant Requirements (pre-populated prompts).........................................................................256.14 Query Properties and Formatting Requirements.........................................................................................25

4.14.1 Query Properties..............................................................................................................................254.14.2 Formatting Requirements.................................................................................................................25

6.15 Main Heading..............................................................................................................................................256.16 Sub Heading................................................................................................................................................256.17 Hierarchies..................................................................................................................................................256.18 Error Handling.............................................................................................................................................266.19 Security and Authorization..........................................................................................................................266.20 Currencies and Exchange Rate Requirement Matrix..................................................................................266.21 Processing and Operational Considerations...............................................................................................26

6.21.1 Performance.................................................................................................................................266.21.2 Batch Requirements.........................................................................................................................266.21.3 Data Maintenance Requirements.....................................................................................................266.21.4 Re-use Details..................................................................................................................................276.21.5 Multi-company, Multi-jurisdiction Considerations.............................................................................276.21.6 Other................................................................................................................................................27

7 Change Management Requirements.....................................................................................................................278 Testing Requirements............................................................................................................................................27

8.1 Key Business Test Conditions.....................................................................................................................278.2 Technical Test Conditions...........................................................................................................................288.3 Risk and Controls Test Conditions..............................................................................................................288.4 Testing Considerations/Dependencies........................................................................................................298.5 Test Data Requirements.............................................................................................................................29

9 Outstanding Issues................................................................................................................................................2910 Appendix................................................................................................................................................................ 30

10.1 Glossary of Terms.......................................................................................................................................3010.2 Additional Supporting/Reference Documentation.......................................................................................30



1 Document Information

The process team should complete any item with ‘blue’ text. The BI/ECC team will complete items with ‘black’ text.

FD Document Name R1_PTP_AP353_RXXXXX_ Storage Bin Search Report

Source Application ECC

Business Unit / Area

Team PTP

Business Process Owner

Report Name Storage Bin Search Report

Sub-Process / BP315

Complexity Medium

Target Environment

2 RASCI Information

Following is the typical list of roles involved in the creation of this document. The list may vary depending on the complexity of the design. This section to be completed by the BI/ECC Team

RASCI Role Name Phone / Email / Group Mail ID (if applicable)

R Functional Designer

S Integration Representative

S Technical architect

C Development Representative

C Application Architect

I Technical Designer

A Sub-Process Team Lead


rordosgo, 31/08/10,

R = Responsible - owns the problem / project. A = to whom "R" is Accountable - who must sign off (Approve) on work before it is effective (S = can be Supportive) - can provide resources or can play a supporting role in implementation C = to be Consulted - has information and/or capability necessary to complete the work I = to be Informed - must be notified of results, but need not be consulted

rordosgo, 30/08/10,

Name of the sub-process

rordosgo, 31/08/10,

BW or ECC ECC = ERP Central Components ERP = Enterprise Resource Planning


3 Document History

3.1 Change History Ver. Date Author Summary of Changes

1

3.2 Review DetailFollowing is a typical list of roles involved in the review of this document. The list may vary depending on the complexity and/or scope of the design.

Role Name Signature DatePeer Reviewer

Application Architect

Integration Representative

Technical Architect

Development Representative

Technical Designer

FD Coordinator

3.3 Approval DetailThis document requires approval from the following

Role Name Signature DateSub-Process Team Lead


rordosgo, 26/08/10,

Functional Approval by Partner System Owner .. e.g. file format

rordosgo, 26/08/10,

A member of the same team review the document, before issue it.

rordosgo, 29/08/10,

All changes in this document have to be documented here. Version 1 is the first draft.


4 Overview and Scope

4.1 Functional Description / Overview Provide a high-level description of the report and the business requirement(s) that will be addressed.

The Storage Bin Search Report is used to find physical items within Storage Locations in the event that SAP is unavailable due to planned or unplanned outages.

Due to the random binning approach used at many sites, there is no effective method to find most materials when the ERP system is unavailable. It is envisaged that this report will only be run and stored no more than 4 times per annum.

The report will be down loaded into a spreadsheet and stored either in as an electronic file or as a hard copy and accessed as required. There will be a Bin Location range selection so as to exclude areas not required as the physical material locations are obvious.

4.1.1 Detailed Requirements

Briefly describe the business requirements

The Storage Bin Search Report will return a list of materials against the specified storage bin with the bin balance.

The key fields being: Plant – to be nominated Storage location – to be nominated Storage Bin range (from / to) to be nominated (if left blank all to be Storage Bin’s for that Storage

Location to be nominated. Material Master Material Description Storage Bin Balance (Unrestricted Quantity)

4.1.2 Gap in Standard SAP Filled by This Item

Describe why standard SAP and/or configuration do not meet the requirements.

Report based on standard SAP transaction code MB52 – Display Warehouse Stocks of Material with the additional Storage Bin data to be displayed against the plant, material and storage location which do not exist in MB52 transaction.


rordosgo, 01/09/10,

If the report does not exist in standard SAP. Any standard SAP report will be used as base to create this report.

rordosgo, 26/08/10,

Business requirements for Why and What and the expected outcome

rordosgo, 01/09/10,

What is needed. What the report has to show.


4.1.3 Solution Alternatives

Briefly describe alternative solutions to meet the requirements, including any cross-team impact, if applicable.

The custom report will be developed for the specified requirements for Storage bin backup report.

4.1.4 Proposed Solution

Identify the proposed solution. Briefly describe why it is preferred. If the object is no longer required, explain the reason why (e.g. combined with another object, met by standard SAP, etc).

The custom report will be developed ALV format which is similar to MB52 output with additional required fields.

4.1.5 Initiating Process/Transaction/Program

Describe the process that triggers this report including the specific selection criteria. This could be a fixed time schedule or a specific event/action. When applicable, describe the initiating SAP transaction and program.

This report is initiated manually by the users on as need basis (Daily). Z Transaction Code (Z_xxxx) needs to be developed to execute this report.

4.1.6 If ECC, the data is primarily in what table(s)

Indicate the primary data table(s), where data on the report is maintained

Tables used in this program are as mentioned below:MARA – General Material DataMARC – Plant Data for MaterialMARD – Storage Location Data for MaterialMAKT – Material DescriptionsMCHB – Batch Stocks

4.1.7 Transaction Volume

Provide the number of records processed that will be read and output using this report.

The number of records that will be read will vary according to the size of the Storage Locations. It is envisaged that the maximum for a single report and considering future expansion would be 20,000.

4.1.8 Frequency and Timing

Provide the run frequency (i.e. Ad Hoc, Daily, Weekly, Monthly, Quarterly, etc.) and any timing considerations that should be applied (e.g., run before 7am Monday morning).


rordosgo, 01/09/10,

It depends on the selection criteria. The functional design team should know an approximate number of the volume of transactions that will be processed.

rordosgo, 30/08/10,

Accenture process team will help with this detail, for further assistance contact Tech Dev Team .

rordosgo, 01/09/10,

How this report will be run. Automatic, job scheduler, called by another program, manually

rordosgo, 26/08/10,

Specify alternate solutions to be considered if Primary solution is not technically viable


Should be run no more than 4 times and can be less at more stable Storage Locations.

4.1.9 Processing Type

Indicate the type of processing used by the report as determined by the required response (i.e. Batch (asynchronous response) or Real Time (synchronous response)).

The Storage Bin Search Report will run in real time on an ad-hoc basis.

4.1.10 Performance

Highlight any performance considerations that should be considered during the design, such as restrictions to expected execution time.

Report should be executed with the return of the results in a reasonable time depending on the volume.

4.1.11 Output Type (Online/Print/Spreadsheet)

Indicate the expected output method(s) for the report and whether the report is static or dynamic.

Output Method: Online - ALV Static / Dynamic: Static

The report will be downloaded to excel and saved to file and/or sent to print.

4.1.12 Retention Requirements

Identify any requirement to retain the report, for what period of time, and in what format. Also indicate any archiving requirements.

There are requirement to retain the information in SAP and only the most up to date report will kept externally

4.1.13 Audience and Distribution

Indicate who the intended audience is for the reports, and if known, the expected number of users and distribution methods employed. Also include any security/access restrictions

The report will be run and stored by Warehouse Supervisors and Warehouse Officers.

Other sample Below :


rordosgo, 31/08/10,

Indicate who the intended audience is for the reports, and if known, the expected number of users and distribution methods employed. Also include any security/access restrictions. Example: What is the use of this report and to whom need to distribute the report

rordosgo, 31/08/10,

In case we are creating spool from the report out put then need to consider how long this needs to be retain. Identify any requirement to retain the report, for what period of time, and in what format. Also indicate any archiving requirements. Example: Every time this report is run a hard copy will need to be printed out and kept for a minimum of six months. This is a security and controls requirement to validate that the process of running the report and verifying the changes is being completed.

rordosgo, 31/08/10,

Output Method: <Saved to File / Sent to print / Send to email account / Download to Excel Static / Dynamic: <Static / Dynamic> ALV : ABAP LIST VIEWER In case the report out put is changing as per selection criteria. Example: The best example displaying the pricing data. As the selection of condition table the columns will very as per the table fields and that needs to display dynamically.


Audience Group Use/Distribution Estimated # of UsersFSC Managers Review Report TBDAccounts Payable Supervisors (FSC or BU)

Review Report TBD

BU Controllers Review Report TBDBU Accounting Managers Review Report TBD

4.2 Business BenefitProvide an outline of the incremental benefit that this development brings to the business (e.g., cost savings due to automation of high volume processes, reduction of liability, shortening of average response time to customer, increased reliability, etc.).

Report based on standard SAP transaction code MB52 – Display Warehouse Stocks of Material with the additional Storage Bin data to be displayed against the plant, material and storage location which are not available in MB52.

4.3 Score CardPlease complete the score card to assist in quantifying the criticality of the report. This will be used to help understand the priority of the report.

4.4 Scope

4.4.1 Functionality

Provide a brief description of the scope of this report (e.g., limited to a single SAP, single type of process, i.e. only a certain type of payment, material type). Describe items that are outside the scope of this design



rordosgo, 01/09/10,

In this sample : All material types indicated on selection criteria or just print only active items.

rordosgo, 31/08/10,

The scorecard is similar to what we use in IT for project management. The score card was included in the spec as an aide to the teams who use this spec. The questions on the score cards can be thought of as 'mind ticklers' to stimulate some thought. It could help the person who is filling out the spec, or reading the spec, to look at the importance or priority of the report in a different way. This is not a mandatory item to be completed but could be useful.


4.4.2 Region or Localization Considerations

Provide an explanation of any country/region specific localizations and configurations that may need to be considered during the current or future phases of the project. Re-use possibilities? i.e. Special currency or conversion requirements, translations?

This report will be utilised in a standard format across all sites.e

4.5 Dependencies/ConstraintsIndicate any dependencies and/or constraints that may impact development (e.g. limited access to legacy systems, time constraints, data restrictions, system configuration, other activities, including designs). Identify applications and/or processes that that must be run prior to the execution of this report. For BI reports, include data source – ECC (with module, if known), legacy system, etc. Include any time-dependent hierarchies or Master Data objects (e.g. display the sales org based on the date of sale).

Stock Material Masters will have the ‘Plant data /stor. 1’ view with the Material Master Data conversion carried out correctly with materials belonging to the correct storage bins (i.e. MARD-LGPBE will never be blank)

4.6 AssumptionsDescribe any assumptions that have been made in the process of completing this design.

There will be multiple materials in a Storage Bin but a material will never be linked to multiple bins Reporting results will exclude materials with a Plant-sp.matl status for non-stock (please refer to

the DD_CFG_PTP_04.01.06 document for the key values) Materials flagged for deletion are excluded from this report


rordosgo, 26/08/10,

Anything that is not dependent or not constrained ... but NEW

rordosgo, 29/08/10,

Restriction per country, laws, government, etc


COMPLETE SECTION 5 FOR ECC REPORTS. GO TO SECTION 6 FOR BW REPORTS

ECC REPORTS (section 5 is only applicable for ECC reports)

5 ECC Detailed Functional Requirements

5.1 Functional SpecificationProvide a detailed description of the report. Provide additional details for custom development requirements (e.g. process flow diagram, detailed description of data manipulations, transactions required, screen flows) where appropriate. For custom tables/custom fields, provide the detailed specification in Section 5.17 below

The Storage Bin Search Report will return a list of materials against the specified storage bin with the bin balance.

The key fields being: Plant – to be nominated Storage location – to be nominated Storage Bin range (from / to) to be nominated (if left blank all to be Storage Bin’s for that Storage

Location to be nominated. Material Master Material Description Storage Bin Balance (Unrestricted Quantity)

The following logic will be used to determine the materials to return the report results.

1. Return materials against the selected plant and storage location and the correct storage bin from the material master (MARD-LGPBE).

2. For materials returned check if items have been flagged as non-stock in the Plant-sp.matl status field (MARC- MMSTA). If item has been flagged non-stock exclude from report.

3. Check if materials returned have been flagged deleted (MARD-LVORM). If item has been flagged deleted exclude from report.

5.2 Process Flow DiagramInsert a flow diagram describing the report procedure including screen sequences, any drill down options and navigation through the report screens


rordosgo, 26/08/10,

Specify the Process Flow Diagram here or a path to ARIS Process Flow Diagram

rordosgo, 01/09/10,

This is a Step by step instructions of the solution along with some technical information e.g. Tablename, Fieldnames, join conditions, filter conditions, transformations

rordosgo, 31/08/10,

ECC reports mean, executable programs that show data in ECC.

rordosgo, 01/09/10,

We already have a high level description of the requirements. In this section more details are needed, as flow diagrams, screen flows, etc


5.3 Initiating Process/Transaction/ProgramDescribe the process that triggers this interface, including the specific selection criteria. This could be a fixed time schedule or a specific event/action. When applicable, describe the initiating SAP transaction and program.

This report is initiated manually by the users on as need basis (Daily). Z Transaction Code (Z_xxxx) needs to be developed to execute this report.


rordosgo, 29/08/10,

Call, manual, scheduler job, etc.


5.4 Report LayoutProvide a sample layout for each reporting level. For each reporting level, provide a summary, details, and drill-down information. Include any charts required.

Reports will be in ALV style. ALV suite of buttons will be available.

Storage Bin Search Report Date:

Plant: Storage Location: User:

Storage Bin from: To:

Storage Bin Material Master Material Description Bin Balance

Number of records:

5.5 Report FieldsProvide the fields and their descriptions in the report layout.

5.5.1 For ECC:

Report/Form Field ID

Source System

SAP Table SAP Field Name

SAP Technical

Field Name

Rules/Notes

`Storage Bin Search Report

ECC Report Name – defaults on the header

Date ECC SYST DATUM Current Date of Application

Reports system date


rordosgo, 01/09/10,

Take the fields on 5.4 and describe them. Accenture functional team could help with also Tech team.

rordosgo, 26/08/10,

ABAP LIST VIEWER (ALV) Grid Control. Interactive report


ServerPlant ECC MARD WERKS Plant To be nominated

in Selection Criteria

Storage Location

ECC MARD LGORT Storage Location

To be nominated in Selection Criteria

User ECC SYST UNAME Username Defaults from User ID

Storage Bin ECC MARD LGPBE Storage Bin Additional field.

Assumption is that the material will never belong to multiple bins.

Material Master ECC MARD MATNR Material For materials returned check if items have been flagged as non-stock in the Plant-sp.matl status field (MARC- MMSTA).If item has been flagged non-stock exclude from report.

Check if materials returned have been flagged deleted(MARD-LVORM).If item has been flagged deleted exclude from report.

Material Description

ECC MAKT MAKTX Material Description

Look up the Material Description using the MARD-MATNR key field.

Bin Balance ECC MARD LABST Valuated Unrestricted-Use Stock

Get and display the unrestricted quantity by storage bin / batch

To get the item quantity by storage bin, get



the storage bin of the item in the material master (MARD-LGPBE) for the specified plant and storage location. Assumption is that the material will never belong to multiple bins

Consignment stock quantities considerations:If MARD-KLABS <> 0, then add MARD-LABST and MARD-KLABS as the input to the bin balance.

Batch Quantity ECC MCHB CLABS Unrestricted Get the item and unrestricted quantity for the specified plant and storage location in MCHB-CLABS by the batch entered in the selection parameter (MCHB-CHARG)

BUoM ECC MARA MEINS Base UoM Get the base unit of measure using the MARD-MATNR as key field

Material Description

ECC MARA MARA ZZLTEXT Optional ALV column view.

Please refer to Functional Design: DD_E_PTP_05 – ‘Z’ field for long material description text & custom search for confirmed field name.

Number of ECC ALV format should



Records have the ability to calculate the total and sub-totals for the number of records or the quantity.

5.5.2 Other

Report/Form Field ID

Source Table Source Field Name

Source Technical

Field Name

Rules/Notes

5.6 Selection Criteria Enter the selection criteria available to users before running the report. Indicate if the criteria are optional or mandatory and if any data restrictions apply. Please include any Exceptions or Conditional filters that should be applied to the report – e.g., Top 10 Customers, highlight revenue under $1MM, etc.

Name Table field / Check Box / Radio Button

Select-Option(S) or Parameter(P)

Mandatory( Y/N )

Default Value

Comments (Restriction / Except. / Cond.)

Material MARA-MATNR Select-Option(S) N N/APlant MARC-WERKS Parameter(P) Y N/AStorage Location

MARD-LGORT Select-Option(S) Y N/A

Storage Bin

MARD-LGPBE Select-Option(S) N N/A

Batch MCHB-CHARG Select-Option(S) N N/A

5.7 Main HeadingProvide the main heading field for the report.

Storage Bin Search Report

5.8 Sub HeadingProvide any required sub-headings and breaks required in the report.

A sub section under the repeated main heading in case of page breaks will detail the date and time the report was executed and the user’s username.

Column headings should repeat.


rordosgo, 31/08/10,

Subtitles, Break downs etc.

rordosgo, 29/08/10,

A screen window will be shown to the user, asking for some data values for selecting records that the user needs to see at the report.


5.9 TotallingList any totalling or other calculation requirements for the report.

Number of records and item quantity by total and sub totals

5.10 SortingList any sorting requirements for the report (e.g., contract type, vendor, etc.).

Standard ALV functionality for sorting by columns shall apply.

5.11 Page BreaksProvide details of any page breaking requirements that should be used in addition to field breaks.

Standard ALV functionality for sorting by columns shall apply.

5.12 Interactive CapabilitiesSpecify all required drill-down/interactive functionality

None

5.13 Retention Requirements

Identify any requirement to retain the report, for what period of time, and in what format. Also indicate any archiving requirements.

There is no requirement to retain the information in SAP and only the most up to date report will kept externally

5.14 Language Considerations.List all language requirements / issues.

N/A

5.15 Custom Tables/Fields SpecificationsProvide the specifications for the custom tables and/or custom fields required for this object.


rordosgo, 31/08/10,

Any additional Custom Tables that are required. Should be referred to in the “detailed functional specs” section. e.g Tables for summarizations, controls, totals, worktables, etc.

rordosgo, 31/08/10,

General requirements/compliance for Language will be followed. e.g the system will refer to the material description in that language and use it in the report.

rordosgo, 31/08/10,

On the grid control double click on one line to see more information about the record selected.

rordosgo, 31/08/10,

Grouping record to total them by sections, sub totals, etc

rordosgo, 30/08/10,

ALV reports already include this features for sorting and filtering records.


5.15.1 Table 1: <TABLE NAME>

Describe the custom table/field and the reason why this object requires it. Provide the field-level detail for the custom table as shown below (with examples). Specify whether the custom tables and/or custom fields will be system or user-maintained in the Notes column. Note the team expected to update each field: (FD = Functional Designer, TD = Tech Dev team).Refer to the Data Standards Considerations for more information on custom tables

N/A

Field (TD)

Description (FD) Primary Key (FD, TD)

Field Selection (Required, Optional, Display, Suppress) (FD)

Field Type (TD)

Field Length (FD)

Check Table (if existing table available to support values (FD)

Notes(FD, TD)

5.16 Initial Data Set-Up, Conversion RequirementsDescribe the conditions that need to be met for roll-out so they may be conveyed to the data conversion team. Include requirements for initial data set-up.

None

5.17 Configuration RequirementsProvide a detailed list of the configuration requirements for this design

Transaction Code to be created

5.18 Error HandlingInclude potential errors, notification procedures, and contingency procedures

Time-out message should appear in the event that the report is taking too long to execute.

5.19 Security and AuthorizationList all security/authorization checks to include for the report. Specific authorization objects such as plant, company code, sales area, etc.

Roles Stocktake Planner


rordosgo, 26/08/10,

Service account requirements, Functional Roles that will permit launching the interface on demand.

rordosgo, 31/08/10,

System errors that can be monitoring and handling. e.g. When data is being selecting some error could happens. This exception is caught internally and an message error is sent as follow : An error occurred applying SELECT to the table &table&.

rordosgo, 31/08/10,

Is there any data need to upload to execute this report or in case any dependency on data to execute the report.

http://teaming.cargill.com/sites/Tartan/DataAndBusinessIntelligence/Public/GBR/Data%20Standards/DBI_DS_Tartan%20Data%20Standard%20-%20Considerations.pptx


Stocktake Processor Stocktake Approver

Positions Warehouse Officers Warehouse Supervisor Stores Technician Senior Stores Technician

This Report is to be available for end-user granted the above roles for plant or site-specific data.

5.20 Existing Sample ReportsIf an existing program is available to be enhanced, provide details in this section

Program Name : RM07MLBS Menu/Transaction : MB52 Legacy Report Name Legacy Program Title Legacy Report Number Related Transactions

5.21 Reconciliation Procedures and Audit RequirementsWhat are the procedures to reconcile the output? Are there any audit requirements? (e.g. Need number of loaded records, number of failures, etc.)

None

5.21.1 Approach

Detail the method of data reconciliation (e.g., reports produced in SAP).

N/A

5.21.2 Metrics

Provide details on the metrics used to facilitate reconciliation (e.g., record count).

N/A

5.22 Processing and Operational Considerations

5.22.1 Processing Type

Indicate the type of processing used by the report as determined by the required response (i.e. Batch (asynchronous response) or Real Time (synchronous response)).

The Storage Bin Search Report will run in real time on an ad-hoc basis.


rordosgo, 29/08/10,

Batch or Real time processing

rordosgo, 29/08/10,

In this sample, the new report is based on SAP MB52.


5.22.2 Transaction Volume

Provide the number of records processed that will be read and output using this report.


5.22.3 Frequency and Timing

Provide the run frequency (i.e. Ad Hoc, Daily, Weekly, Monthly, Quarterly, etc.) and any timing considerations that should be applied (e.g., run before 7am Monday morning).

Should be run no more than 4 times and can be less at more stable Storage Locations.

5.22.4 Performance


Report should be executed with the return of the results in a reasonable time depending on the volume.

5.22.5 Batch Requirements

Include details required for batch processing (e.g., variant set-up, reconciliation requirements, etc.). (Need to list all batch requirements, including restart-recovery, timing, scheduling, etc.)

N/A Submission Scheduling Considerations Run Frequency Start Date Start Time Estimated Volume Per Run Parameters / File Dependencies Job Dependencies Constraints Variant Required

o Field Texto Suggested Valueo Description

5.22.6 Data Maintenance Requirements

List any requirements for the maintenance of data, if required.

None


rordosgo, 31/08/10,

An example is in case we are using custom table to read the data (e.g. flag) then that needs to be maintained as per requirement.

rordosgo, 29/08/10,

Information needed if the report will be scheduled

rordosgo, 30/08/10,

e.g. Time of the day for best running

rordosgo, 29/08/10,

It was described before in other section


5.22.7 Re-use Details

Include any information regarding the re-use of code and/or relevant documents/references from other projects.

Please re-use and base the custom report development on the SAP standard report MB52 – Display Warehouse Stocks of Material reusing the table and fields and logic identified in sections 3.4 and 3.6.

The additional data required are the Storage Bin data against the plant-storage location and material, the running storage bin balance and the material long text stored in the ‘z’ field (refer to Functional Design: DD_E_PTP_05 – ‘Z’ field for long material description text & custom search for confirmed field name).

The custom report should be in the ALV reporting format.

Standard SAP MB52 – Display Warehouse Stocks of Material

Report List results


rordosgo, 31/08/10,

Existent objects that can be re used e.g. subroutines, reports, pieces of other programs(includes), etc.


5.22.8 Multi-company, Multi-jurisdiction Considerations

Provide any variations to be considered for different companies, businesses, legal entities, and/or jurisdictions.

None

GO TO SECTION 7 TO COMPLETE THE FUNCTIONAL DESIGN DOCUMENTATION

COMPLETE SECTION 6 FOR BW REPORTS. GO TO SECTION 5 FOR ECC REPORTS

BW REPORTS (section 6 is only applicable for BW reports)

6 BW Detailed Functional RequirementsProvide a detailed description of the report. Provide additional details for custom development requirements (e.g. process flow diagram, detailed description of data manipulations, transactions required, screen flows) where appropriate. For custom tables/custom fields, provide the detailed specification in Section 5.17 below.

<Insert text here – Mandatory>

6.1 Functional Specification

6.1.1 Summary Report

6.1.2 Detail Report

6.2 Process Flow Diagram

Insert a flow diagram describing the report procedure including screen sequences, any drill down options and navigation through the report screens.

<Insert process flow here – Mandatory >

6.3 Report Layout

Provide a sample layout for each reporting level. For each reporting level, provide a summary, details, and drill-down information. Include any charts required.

<Insert report layout here - – Mandatory >


rordosgo, 29/08/10,

Custom requirements by country, company or localizations.


ID V a lue D escrip tion

xxxxx3

xxxxxxxxxxxxxxx

xxxxx4

xxxxxxxxxxxxxxx

xxxxxxxxxx5

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

R eport T itle D a te : xxxxx1

U ser: xxxxx2

6.4 Report Fields

6.4.1 Rows

Field Name Data Element

(Characteristic / Key Figure)

Calculation / Business

Rules(see section 4.7

for complex formulas)

Restrictions (values,

hierarchies, variables, etc.)

Display Properties (hidden, key/text, decimals, scaling,

suppress results etc.)

6.4.2 Columns

Field Name Data Element

(Characteristic / Key Figure)

Calculation / Business

Rules(see section 4.7

for complex formulas)

Restrictions (values,


Display Properties (hidden, key/text, decimals, scaling,

suppress results etc.)

6.4.3 Free Characteristics / Navigation BlockField Name Data Element Restrictions (values,


Display Properties (key/text, suppress results)

6.5 Filters Data Element Restrictions Comments



(values, hierarchies, variables, etc.)

6.6 Selection Criteria (Prompts)

Data Element Variable Name

Mandatory or

Optional

Prompt Type (Single value, Interval (range),

Selection Option, Multiple Single values, Select by Hier,

by Hier Node)

Default Value

6.7 Calculations/Algorithms/Derivations

Formula 1 = Formula 2 =

6.8 Global Calculated/Restricted Key FiguresKey Figure Name Restricte

d / Calculate

d

Restriction / Calculation Details

6.9 Report-to-Report Interface Requirements (Jump Query)Target Type Description of

Jump ToQuery Name Link Description

6.10 ExceptionsDescription Definition Operator Value

FromValue

ToAlert Level

Display

Active?

6.11 ConditionsDescription Key

FigureOperat

orValues Charact

erCharacterist

ic Assignment

Other

Active?



6.12 Existing Sample Reports

Insert sample report here - – Mandatory

6.13 Reporting Variant Requirements (pre-populated prompts) Functional Name Prompt

6.14 Query Properties and Formatting Requirements

4.14.1 Query Properties

4.14.2 Formatting Requirements

6.15 Main Heading

Provide the main heading field for the report.


6.16 Sub Heading

Provide any required sub-headings and breaks required in the report.


6.17 Hierarchies

Do you need to apply an ECC hierarchy to the data? Is so, what hierarchy will be used.


6.18 Error Handling

Include potential errors, notification procedures, and contingency procedures.

6.19 Security and Authorization



List all security/authorization checks to include for the report. Specific authorization objects such as plant, company code, sales area, etc.


6.20 Currencies and Exchange Rate Requirement Matrix

ValueCurrency Type

Document Local Group ActualPlan

6.21 Processing and Operational Considerations

6.21.1 Performance


<Insert text here>

6.21.2 Batch Requirements

Include details required for batch processing (e.g., variant set-up, reconciliation requirements, etc.). (Need to list all batch requirements, including restart-recovery, timing, scheduling, etc.)

Submission Scheduling Considerations Run Frequency Start Date Start Time Estimated Volume Per Run Parameters / File Dependencies Job Dependencies Constraints Variant Required

o Field Texto Suggested Valueo Description

6.21.3 Data Maintenance Requirements

List any requirements for the maintenance of data, if required.

<Insert text here>

6.21.4 Re-use Details

Include any information regarding the re-use of code and/or relevant documents/references from other projects.



<Insert text here>

6.21.5 Multi-company, Multi-jurisdiction Considerations

Provide any variations to be considered for different companies, businesses, legal entities, and/or jurisdictions.

<Insert text here>

6.21.6 Other

<Insert text here>

GO TO SECTION 7 TO COMPLETE THE FUNCTIONAL DESIGN DOCUMENTATION

7 Change Management RequirementsList any additional training or change management and communication requirements (e.g., describe any special training requirements needed by this development

Training of warehouse personnel when and how to execute the reporting transaction using the selection criteria.

8 Testing RequirementsIdentify business, technical and controls test conditions that need to confirm that the report performs as designed (ex. Material gets created in legacy system with new SAP number)

8.1 Key Business Test ConditionsIndicate the business level test conditions that should be used to verify successful operations of the report.

ID Condition Expected results Cycle Ref

1 Execute the report for specific plant and storage location

Report displays the materials against the Plant, Storage location, Storage Bin and bin quantity

2 Execute the report for specific plant, storage location and materials

Report displays the materials selected against the Plant, Storage location, Storage Bin and quantity

3 Execute the report for specific storage Report displays all the materials


rordosgo, 29/08/10,

Prepare a scenario for testing purposes, create a variant with default selection criteria

rordosgo, 29/08/10,

User manual is needed?


bins and materials selected against the Plant, Storage location, and the Storage Bins in the specified range with the quantity

4 Execute the report for specific plant, storage location and consignment materials

Report displays the consignment materials against the Plant, Storage location, Storage Bin and quantity

8.2 Technical Test ConditionsDocument all technical scenarios associated with this development. Examples would include testing an error-free run, testing the exception processes, and testing the error handling.


1 Execute the report for specific plant and storage location

Report displays the materials against the Plant, Storage location, Storage Bin and bin quantity

2 Execute the report for specific plant, storage location and materials

Report displays the materials selected against the Plant, Storage location, Storage Bin and quantity

3 Execute the report for specific storage bins and materials

Report displays all the materials selected against the Plant, Storage location, and the Storage Bins in the specified range with the quantity

4 Execute the report for specific plant, storage location and consignment materials

Report displays the consignment materials against the Plant, Storage location, Storage Bin and quantity

8.3 Risk and Controls Test ConditionsDocument all control scenarios associated with this development. Examples would include rounding of dollars and cents, audit trail processing, and reconciliation reporting.


1

2

3

8.4 Testing Considerations/Dependencies List any considerations that are essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how it should be tested, and list any insights as to how this component could be tested the most efficiently.


rordosgo, 30/08/10,

Need to prepared Any data or set up before run this report?

rordosgo, 30/08/10,

Test document set up


Execute report with converted live-data from legacy systems across all sites. Material Master records need to be set-up against the correct plant (site) and storage locations

(warehouse) Material Master records need to be set-up against the correct storage bin locations Material Master records for either catalogued stock/non-stock need to have the correct Plant-

sp.matl status in order for the report to identify which to include or exclude in the report output

8.5 Test Data RequirementsProvide test data for component and assembly testing. If not available, provide detailed guidelines on test data requirements.

Material data need to be set up along with plant, storage location and batch details.

9 Outstanding IssuesList any open issues that impact the completion of the design (e.g. Missing values for material groups).

N/A

Issue # Description Assigned To Status Impact Resolution

10 Appendix

10.1 Glossary of TermsProvide further definition of any acronyms or terms used in the document.


rordosgo, 29/08/10,

If exist any issue that could affects the results.

rordosgo, 29/08/10,

Some direction to test.


Acronym / Term Definition

10.2 Additional Supporting/Reference Documentation

Name Location / Link / Attachment

Some important references.

Templates at sharepoint.

O- I _SAP_P ro jec t > 4 . Des ign , Bu i l d , Tes t > 99 . De l i ve rab le Temp la tes > Func t i ona l Des ign Temp la tes

Funcional design naming convension.

https://ts2amr.accenture.com/sites/O-I_SAP_Project/Design%20Build%20Test/99.%20Deliverable%20Templates/O-I%20SAP%20Implementation%20Document%20Naming%20Convension.ppt

<Release>_<Process Team>_AP353_<RICEFW type><RICEFW ID>_Description

Sample

R1_OTC_AP353_R00240_Payment Terms and Remit To Address Changes




https://ts2amr.accenture.com/sites/O-I_SAP_Project/Design%20Build%20Test/Forms/AllItems.aspx?RootFolder=%2Fsites%2FO-I_SAP_Project%2FDesign%20Build%20Test%2F99.%20Deliverable%20Templates&View=%7BFB1F0A3D-6BEC-4B96-8174-708F6C751BAF%7D

https://ts2amr.accenture.com/sites/O-I_SAP_Project/Design%20Build%20Test/Forms/AllItems.aspx?View=%7BFB1F0A3D-6BEC-4B96-8174-708F6C751BAF%7D

https://ts2amr.accenture.com/sites/O-I_SAP_Project

Fd Report Sasmple

Documents

Transcript of Fd Report Sasmple