FUNCTIONAL SPECIFICATION wricef

Scenario (Business Area): sd

Business Process:

PROJECT IDENTIFICATION

Project Name Project Number

For SSDP
Customer Name Customer Number

SAP Project Manager Customer Project Manager

<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)

<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Confidential

1 of 24
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 24
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 24
2. General Object Overview

Object Overview

Business
Object ID
Process

ECC6 SAP SD
SAP Release
Module
( ) Report
( ) Interface
( ) Conversion
Object Type
( ) Enhancement
( ) Form
( ) Workflow
2nd Choice Stock Report
Object Title
2nd Choice Stock Report
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 24
2.1 Process Requirements Reference

Process Reference
Requirement ID 8000245234/1000005230
Requirement Welfare Open PR &PO Report
Description
Gap to be
addressed
Alternative SAP
Standard Solution

2.2 Generic WRICEF Descriptions

Justification

FUNCTIONAL DESCRIPTION / DESIGN

[Welfare users need do get details about open PR and OP quantities about non stock items
for open sales orders materials.

TRANSACTION VOLUME

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

<Every authorization object needs to be documented to provide the security administrator the
information on the purpose and use of the object. The following sections are the minimal
documentation requirements.>

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

REPORT, ETC)

` 6 of 24
3. Object Specific Design

3.1 Reporting (operational and analytical)

<reference to the RICEFW section in the BPD.>

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

Selection Criteria

` 7 of 24
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
TVKO VKORG Select Mandator Sales
Option y Organi
zation
TVTW VTWEG Select Mandator Distrib
Option y ution
Chann
el
TSPA SPART Select Mandator Divisio
Option y n
TVAK AUART Select Mandator Sales
Option y Docu
ment
Type
VBAK ERDAT Select Mandator Order
Option y Type
T178T VTEXT Select Optional Materi
Option al
Pricing
Group
MARA MATNR Select Optional Materi
Option al
MARA MTART Select Optional Materi
Option al
Type
MARA MATKL Select Optional Materi
Option al
Group

Functional Design, Validation and Variants

` 8 of 24
Select VBAK-VBELN (Sales Document)
Where
VBAK- ERDAT (Created on) = <Selection Screen>
VBAK- AUART (Sales Doc. Type) = <Selection Screen>
VBAK- VKORG (Sales Org.) = <Selection Screen>
VBAK- VTWEG (Distr. Channel) = <Selection Screen>
VBAK- SPART (Division) = <Selection Screen>

Then pass the selected VBAK-VBELN to the VBUK table as,

VBUK- VBELN (Sales Document) = VBAK-VBELN

Then fetch the data according to following conditions

If VBUK- GBSTK (Overall status) = C
Then select relevant VBUK- VBELN and pass to the LIPS table as,
LIPS- VGBEL (Reference doc.) = VBUK- VBELN
And fetch the
LIPS- VBELN (Delivery)

Next get the DISTINCT LIPS- VBELN (Delivery) by grouping against VBUK- VBELN

Then pass the set of selected DISTINCT LIPS- VBELN (Delivery) to the VBUK table as,
VBUK- VBELN (Sales Document) = LIPS- VBELN (Delivery)

Then check VBUK- WBSTK (TotalGdsMvtStat)

If VBUK- WBSTK (TotalGdsMvtStat) = C for all LIPS- VBELN (Delivery)

Delete VBUK- VBELN
If set VBUK- WBSTK (TotalGdsMvtStat) C for any LIPS- VBELN (Delivery)
Take in to account that LIPS- VBELN and pass that value to the LIPS as LIPS- VBELN and fetch
the
LIPS- VGBEL (Reference doc.)
LIPS- VGPOS (Reference item)
Then assign to below variable,
Var_Sales_Doc = LIPS- VGBEL (Reference doc.)
Var_Sales_Item = LIPS- VGPOS (Reference item)

Else

` 9 of 24
 Then select relevant VBUK- VBELN and pass to the VBAP table as,
VBAP- VBELN (Sales Document) = VBUK- VBELN
And fetch the
VBAP- VBELN (Sales Document)
VBAP- POSNR (Item
Where
VBAP- ABGRU (RejectionReason) = <Blank>

Then assign to below variable,

Var_Sales_Doc = VBAP- VBELN (Sales Document)
Var_Sales_Item = VBAP- POSNR (Item)

Then pass the selected Var_Sales_Doc and Var_Sales_Item to the VBAP table and fetch the
VBAP-MATNR (Material) and
VBAP- KWMENG (Order Qty).
Where
VBAP- VBELN = Var_Sales_Doc
VBAP- POSNR = Var_Sales_Item
VBAP-MATNR (Material) = <Selection Screen>
VBAP- MATKL (Material Group) = <Selection Screen>

Next get the unique (Material) and sum of VBAP- KWMENG (Order Qty).

Then pass the selected VBAP-MATNR to the MARA table and fetch the
MARA-MATNR (Material)
Where
MARA-MATNR (Material) = VBAP-MATNR
MARA-MTART (Material Type) = MARA-MTART <Selection Screen>.

Then pass the selected MARA -MATNR to the MVKE table and fetch the MVKE-MATNR
where
MVKE-MATNR = MARA -MATNR
MVKE-KONDM (Material Pricing Gp.) = T178T-VTEXT <Selection Screen> and
MVKE- VKORG (Sales Org.) = <Selection Screen> and
MVKE- VTWEG (Distr. Channel.) = <Selection Screen>.

Sales Organization VBAK- VKORG (Sales Org.) where VBAK-VBELN = Var_Sales_Doc

Distribution Channel VBAK- VTWEG (Distr. Channel) where VBAK-VBELN = Var_Sales_Doc
Division VBAK- SPART (Division) where VBAK-VBELN = Var_Sales_Doc
Material MVKE-MATNR
Material Description Using the Function Module READ_TEXT, pass the following information,
o Text ID : 0001
o Language : EN
o Text Object : MVKE

` 10 of 24
 o NAME : MATNR, VKORG, VTWEG
(Ex: 1.1.1 <13 spaces> 110020)

Material Type Pass the selected MVKE -MATNR to the MARA table as MARA-MATNR and
fetch the value of MARA-MTART

Material Gp Pass the selected MVKE -MATNR to the MARA table as MARA-MATNR and
fetch the value of MARA- MATKL

Logical Gp Fetch the MVKE-MVGR2 by using MVKE MATNR and MVKE-VKORG =

<Selection Screen> and MVKE-VTWEG = <Selection Screen>.

Super Gp Fetch the MVKE-MVGR1 by using MVKE MATNR and MVKE-VKORG =

<Selection Screen> and MVKE-VTWEG = <Selection Screen>.

Material Pricing Gp Fetch the MVKE-KONDM by using MVKE MATNR and MVKE-VKORG =
<Selection Screen> and MVKE-VTWEG = <Selection Screen>.

Total Order Qty Sum of VBAP- KWMENG (Order Qty) for MVKE-MATNR

Stock Pass the selected MVKE -MATNR to the MARD table as MARD-MATNR and get
the sum of MARD- LABST (Unrestricted)

Balance Qty Stock - Total Order Qty

Pass the selected MVKE -MATNR to the MAKT table as MAKT MATNR
Short Description (Material). Then fetch the MAKT-MAKTX (Description) where MAKT SPRAS
(Language) = EN

Open PR Qty Fetch the

EBAN BANFN (Purchase Req.)
EBAN BNFPO (Requisn Item)
EBAN MENGE (PR Qty) and
EBAN BSMNG (PO Qty)
where
EBAN- MATNR (Material) = MVKE -VBELN (Material)
EBAN- LOEKZ (Deletion Ind.) X
EBAN-FRGKZ (Release ind.) 2 or X <<<check each PR fully released
or not>>>

Then check,

If EBAN MENGE (PR Qty) - EBAN BSMNG (PO Qty) = 0

Delete EBAN BANFN (Purchase Req.) and EBAN BNFPO (Requisn Item)
from the selection

Else if EBAN MENGE (PR Qty) - EBAN BSMNG (PO Qty) > 0

` 11 of 24
 Get the difference between EBAN MENGE (PR Qty) - EBAN BSMNG (PO
Qty) and count based on EBAN- MATNR (Material)

Finally display that values

Open PO Qty Fetch the

EKPO- EBELN (Purchasing Doc.)
EKPO- EBELP (Item)
EKPO MENGE (Quantity)
Where
EKPO- LOEKZ (Deletion Ind.) X
EKPO- ELIKZ (Deliv. Compl.) = <Balnk> and
EBAN- MATNR (Material) = MVKE -VBELN (Material)

Then pass the selected data to EKET table and fetch

EKET- MENGE (Scheduled Qty)
EKET- WEMNG (Delivered)
Where
EKET- EBELN (Purchasing Doc.) = EKPO- EBELN (Purchasing Doc.)
EKET- EBELP (Item) = EKPO- EBELP (Item)

Finally display,

Sum of EKET- MENGE (Scheduled Qty) Sum of EKET- WEMNG (Delivered)

by grouping EBAN- MATNR (Material)

Report Output

` 12 of 24
Output Method

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

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

Sub Heading

LAYOUT
Table/Structure Field Format Default Value Column Name Translation Rule
Name Name (ie
decimal
places)
EKET MENGE Scheduled Qty
EKET WEMNG Delivered
EBAN MATNR Material
VBAK VKORG Sales
Organization
VBAK VTWEG Distribution
Channel
VBAK SPART Division
MVEK MATNR Material
MARA MTART Material Type

MARA MAKTL Material Group

MVKE MVGR2 Logical Group
MVKE MVGR1 Super Group
MVKE KONDM Material
Pricing Gp

VBAP KWMENG Total Order

Qty

MARD LABST Stock

MAKT MAKTX Short
Description

` 13 of 24
DRILLDOWN REQUIREMENTS

TOTALING

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

Any page-break requirements?

SORTING

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.

` 14 of 24
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
[Filenames, delivery method, file type (ascii, comma-delimited, etc)

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

` 16 of 24
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.]

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

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

` 18 of 24
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.]

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

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

` 20 of 24
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)
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:

Form Title Date: xxxxx1

User: xxxxx2

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

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

` 22 of 24
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)
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 Rules

Latest End, Latest Start

Requested End , Requested start

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

` 24 of 24