FUNCTIONAL SPECIFICATION wricef

Scenario (Business Area): MM

Business Process:

PROJECT IDENTIFICATION

Project Name Project Number

Camoplast
Customer Name Customer Number

SAP Project Manager Customer Project Manager

How to use the Template

Blue text is always intended as instructions, guidelines, explanations, hints, and tips. It has to be removed
when the document is finalized. To provide a consistent representation of this document to the customer,
chapters should not be deleted or inserted. Required additions should be made as sub-chapters to existing
chapters.
Chapters that are not relevant should be marked as such (that is, add not relevant or not applicable).

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 BPD
In 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

Be sure to delete these instructions when you have finished!

Author Document Location (repository/path/name)

1 of 27
Version Status Date (YYYY-MM-DD) Document Classification
0.1

REVISION HISTORY

Version Date Description

0.1
0.2

TABLE OF CONTENT

1. PURPOSE OF THIS DOCUMENT........................................................................................................4

2. GENERAL OBJECT OVERVIEW.........................................................................................................5
2.1 Process Requirements Reference.................................................................................................6
2.2 Generic WRICEF Descriptions......................................................................................................6
3. OBJECT SPECIFIC DESIGN............................................................................................................... 8
3.1 Reporting (operational and analytical)...........................................................................................8
3.2 Interfaces..................................................................................................................................... 12
3.3 Data Conversion / Historical Data................................................................................................15
3.4 Enhancements............................................................................................................................. 17
3.5 Output (e.g. forms)...................................................................................................................... 18
3.6 Workflow...................................................................................................................................... 20
4. TEST CONDITIONS........................................................................................................................... 21

` 2 of 27
1. Purpose of this document
The Specification is the basis for the developments that will be done by SAP. <Customer> 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.]

` 3 of 27
2. General Object Overview

Object Overview

Business
Object ID
Process

SAP
SAP Release
Module
( X ) Report
( ) Interface
( ) Conversion
Object Type
( ) Enhancement
( ) Form
( ) Workflow
List of Stock Values : Balances both in Local Currency and Group Currency
Object Title
List of Stock Values : Balances both in Local Currency and Group Currency
Object Description

Mock Up ID / Name

Required
Cycle of Testing / C1 / C2 / C3 / C4 Development
Sprint Cycle
Completion Date
Simple / Medium /
Complexity of Object Priority Low / Medium / High
Complex
SAP Transaction SAP Program
Name Name

Similar SAP Similar SAP

Transaction Program

FS Control
<Customer>
Functional Consultant
Process Owner
Author and Phone
and Phone
Number
Number

Planned Date of FS Actual Date of FS

Completion Completion

FS Approved By FS Approval date

Other Contact and Other Contact and

Phone Number Phone Number

` 4 of 27
2.1 Process Requirements Reference

Process Reference
Requirement ID
Requirement List of Stock Values : Balances both in Local Currency and Group
Description Currency

Gap to be
addressed
Alternative SAP
Standard Solution

2.2 Generic WRICEF Descriptions

Justification
Business requires a report in similar lines of MB5l Report along with output in both local
currency and group currency which is not provided by standard functionality.

FUNCTIONAL DESCRIPTION / DESIGN

Business requires a report in similar lines of MB5l Report but require the report output in both
local currency and group currency.

TRANSACTION VOLUME

` 5 of 27
FREQUENCY & TIMING

DEPENDENCIES

AUTHORIZATION REQUIREMENTS

RELATED DOCUMENTATION (ATTACH OSS NOTES, EMAILS, DOWNLOAD OF EXISTING

REPORT, ETC)

` 6 of 27
3. Object Specific Design

3.1 Reporting (operational and analytical)

Reporting
WRICE Description Report Type Data Elements Relevant KPI Owner
F-ID (ABAP, BI,
BOBJ)

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/ Field Name Format Defaul Table Select Mandator Field

Structur t Value/ Option or y or Labels
e Name Value Checkbox Paramet Optional
/ er
Radio
Button/
Radio
Button
Group
CKMLCR CURTP Drop down Currenc
y

` 7 of 27
Functional Design, Validation and Variants

` 8 of 27
Report Type - Hierarchical ALV
Report Name - ZRM07MBST
New transaction code - ZMB5l
Report Description : List of Stock Values : Balances both in Local Currency and Group Currency

Copy the selection screen of the exiting report - 'RM07MBST' and name it as 'ZRM07MBST' and please
imbibe the additional field to the new report and below is the sample picture shot of the selection screen.

Dorp Down List :

10 - Company Code Currency

30 - Group Currency

Sample :

Overall Selection screen :

` 9 of 27
Data Selection:

When business choose - Local currency in the selection screen

If business choose 'Company code ( Local) Currency' in the drop down the report output will be displayed in
company code currency i.e., as of exiting one.

Submit MB5l report .

If business Choose Group Currency : Please use the below logic to get the report output stock account
values

If business choose 'Company code Currency' in the drop down the report output will be displayed in
company code currency i.e., as of exiting one.

If business Choose Group Currency : Please use the below logic to get the report output stock account
values.

Retrieve MATNR , BWKEY ,KALN1, BKLAS from MBEW and pass KALN1 into KALNR field of
Function Module - 'CKMS_PERIOD_READ_WITH_ITAB'

` 10 of 27
Pick Stock quantity and Stock value from CKMLCR based on the currency key Group
Currency '30' and pass it into T_CKMLCR

Pass valuation class or valuation grouping code in table T030 to fetch G/l account

Tables - FAGLFLEXT

Total of transactions of the period in group currency :

Pass RBUKRS ( Company code ) , ( RACCT ) G/L account, (RYEAR) Fiscal year and period
maintained in the input parameters and get the corresponding period values using the
mapping fields mentioned below

Logic to get the stock

account balance -

ZBalance = Current period

- 1 to get previous periods

Zbalance = Zbalance +
Cumulative of all previous
period balances gives the
previous period balances

Zbalance +( Mapping field

balance ) + balance carry
forward (KSLVT) gives the
stock account balance

` 11 of 27
Output :
Use the same output as that of MB5l report but in group currency

Scope Of List

Totals Only is checked

Display report output only in totals

Negative Stocks is checked

Report output should only contain stock with negative stocks

Materials with zero stock is checked

Report output should display all materials with ' Zero' Stock

Valuation Area Level Only is checked

Report Output should be displayed at valuation area level

Sample Report Output:

` 12 of 27
` 13 of 27
Screen 1:

` 14 of 27
Screen 2 :

` 15 of 27
Report Output

Output Method

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

Main Heading

Example:
The main report heading will be: List of Stock Values : Balances both in Local Currency and Group
Currency

Sub Heading

LAYOUT
Table/Structure Field Format Default Value Column Name Translation Rule
Name Name (ie
decimal
places)

` 16 of 27
DRILLDOWN REQUIREMENTS

TOTALING

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

Any page-break requirements?

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

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

ERROR HANDLING

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

` 17 of 27
3.2 Interfaces
<Identify all interfaces required to provide inputs to or outputs from this part of the process. Provide a
functional description of the interfaces including the source and type of data.>

Interface
WRIC Description Interface Application Data Elements Frequency / Owner
EF-ID Method s Volumes

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

` 18 of 27
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

` 19 of 27
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.]

` 20 of 27
3.3 Data Conversion / Historical Data
<Note all master and transactional data conversion requirements. Please note specific fields that are unique
to this design and the business requirement that drives that design. Note whether manual and automated
data conversion requirements. Provide details of all data required from Legacy Systems (Consider System
name, level of detail, time dimension). Identify requirements for historical data conversion mandatory for the
process. This is not meant to be an exhaustive functional spec but a place to list conversions related to this
process.>

Conversions
WWRIC Conversio Source Conversio Conversion # of Owner
EF-ID n Object n Activities Method Objects to
(e.g. (manual / be
cleansing) automated) converted
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

` 21 of 27
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.]

` 22 of 27
3.4 Enhancements
<Specify the enhancement based on the proposed gap resolutions listed in the Detailed Requirements and
Design documents. Provide as much detail on the requirements and design considerations as you can. If
there is a large enhancement then consider detailing that in a separate design or functional spec. document.
>

enhancements
WRIC Description Data Object Functional Alternative Reason Owner
EF-ID (Sales Order) Gap SAP Standard

Functional Design / Flow, Validation and Variants

Flow

Design

` 23 of 27
3.5 Output (e.g. forms)
<Identify outputs and forms>

Output
WRIC Description Data Object Output Type Frequency Volumes Owner
EF-ID (Sales (Form, EDI, etc.)
Order)

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:

Form Title Date: xxxxx1

User: xxxxx2

ID Value Description
xxxxx3 xxxxx4 xxxxxxxxxx5
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx
xxxxx xxxxx xxxxxxxxxx

` 24 of 27
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

` 25 of 27
3.6 Workflow
<Identify workflow requirements for this process. Provide detailed requirements for the workflow. e.g., purchase order
approval process and authority levels etc.>

Workflow
WRIC Description Business / Data Object Engaged Parties Owner
EF-ID (Sales Order)

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 Rules

Latest End, Latest Start

Requested End , Requested start

` 26 of 27
4. Test Conditions

BUSINESS 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 Criteria Expected Result

` 27 of 27