SE 5.

1 Functional SPECIFICATIONS
RICEFW (Reports)
NOTIFICATION WORKFLOW AFTER 2 DAYS
R.PM.210.31

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

1
PROJECT IDENTIFICATION

Project Name Project Code

Hilmar Cheese Business Transformation Program – Business Blueprint
HILMAR-SAPIMPL-BBPHASE
phase
Customer Name Customer Number
Hilmar Cheese Company
Wipro Project Manager Customer Project Manager
Amit Jain Carina Hernandez

DOCUMENT IDENTIFICATION

Author Document Location (repository/path/name)

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

REVISION HISTORY

Version Date Description

0.1 03-14-2013 Initial Draft

0.2

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

2
REVIEW AND APPROVAL

Name Date (YYYY-MM-DD)

Customer Project Manager

Name Date (YYYY-MM-DD)

Wipro Project Manager

Name Date (YYYY-MM-DD)

Key Stakeholder

Name Date (YYYY-MM-DD)

Key Stakeholder

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

3
Table of Contents

1. How to use the Template................................................................................................................5

2. General Object Overview................................................................................................................6
3. Process Requirements Reference....................................................................................................7
4. RICEFW Descriptions.......................................................................................................................7
5. Report Specific Design....................................................................................................................9
5.1. Report Example............................................................................................................................11
5.2. Report Output..............................................................................................................................11
5.3. Security Requirements and Authorization Details.........................................................................12
5.4. Recovery and Restart....................................................................................................................13
5.5. Assumptions.................................................................................................................................13
6. Use Cases......................................................................................................................................13
7. Issues............................................................................................................................................14
8. Performance Requirements..........................................................................................................14
9. Part B – Additional Details to be filled by Hilmar Cheese IS...........................................................15
9.1. Data Mapping Tables....................................................................................................................15
10. Validation and Test Scenarios.......................................................................................................15

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

4
1. How to use the Template

This document is intended to specify RICEFW object from a functional perspective. It will be followed by a technical specification
during Realization. A Functional Specification has three main sections with the purpose of describing the expected behavior of
the development object.
 Object information, to be filled in for all RICEFW objects
 Object specific details (Processing, calculations, and business logic for the development object)
 Report specific requirements

This document builds and refers to three preceding documents

 Business Process Design Document – BPD document
 Fit Gap Analysis – FGA
 Requirement Traceability Matrix - RTM

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

5
2. General Object Overview

Object Overview

R.PM.210.31 Business Process & PM_210

Object ID
Number

SAP Release ECC6 EHP 7 SAP Module PM

Object Type Report

Object Title Overdue notifications

Object Description Outstanding Notification for More than 2 Days

Complexity of Object Medium Priority High

IW22 - Following naming

SAP Transaction Name SAP Program Name SAPLIQS0
convention guidelines

Similar SAP Transaction IW21 Similar SAP Program N/A

Mode Online/ Background

Object Information
( ) SAP Query (x) ABAP Program ( ) BW Report
Report Created using ( ) BobJ Report ( ) Crystal Report ( ) Report Painter
( ) ECC ( ) Others ___________________
( ) Drilldown ( ) Buttons ( ) Sort
Characteristics Required (x) ALV Grid ( ) ALV List ( ) Entry File
( ) Others: Call Trasaction
( ) Legal requirements not fulfilled
Result if no reports are ( ) Lack of essential business information
created? (x) Lack of functions compared to Legacy system
( ) Other (specify):
Approximate duration for Is there an No
development work (in See development estimate alternative in the If Yes, describe the alternative
man days)? standard system Manually check reports
( ) Performance Problem
Why is alternative ( ) Complexity
not acceptable? (X) Other
_______________(Specify)

FS Control

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

6
 Functional Consultant – Yang, Yang <Customer> Process Verne, Taylor
Author and Phone Owner and Phone
Number Number

Planned Date of FS 03/14/14 Actual Date of FS 03/19/14

Completion Completion

FS Approved By Nguyen, Tin FS Approval date MM/DD/YY

Other Contact and Phone Other Contact and

Number Phone Number

3. Process Requirements Reference

This section describes the business needs and specific requirements of the development object. The more details that are
included here, the fewer questions the developers will have. Processing, calculations, and business logic for the development
object must be fully described.

Process Reference
Requirement ID
Requirement If the notification is not being reviewed after 2 days, it should notify and escalate to Cost Center
Description Manager of the equipment cost center and the Maintenance Manager.
Gap to be addressed The requirement cannot be done through the workflow. So new report to be
developed and the same has to run on a daily basis by using a batch job.
Alternative SAP NA
Standard Solution

4. RICEFW Descriptions

Justification (Why a custom development is required?)

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

7
<List the reasons/justification why a custom development is required to fullfill the demand.>

Standard SAP does not support sending mail if a notification has not been reviewed after 2 days. This Report is
required for fulfilling that requirement.

Functional Description /Detail Functional Design

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

8
When a notification has not been reviewed after 2 days, system will automatically notify (by email) to Cost Center
Manager of the equipment and as well as Maintenance Manager.
1. Get the outstanding notification report based on the logic which is explained below with cost center.
2. Trigger email based notification for outstanding notifications selected to the cost center manager based on
below logic given.
3. Run the batch job on a daily basis. Frequency and timing is described in Frequency section below

The detailed logic is stated below:

If a notification has not been reviewed after 2 days from the creation date and time, it should notify and escalate to Cost
Center Manager of the equipment and Maintenance Manager.
- Get creation date and time of the Notification from VIQMELST.
- Get the VIQMEL-OBJNR and pass to Object Number (VIQMELST-OBJNR )
- Select the notifications based on the Plant VIQMELST -IWERK, VIQMELST - QMART and VIQMELST- STAT. The
status should be “OSNO – Outstanding Notification”.
- Get the VIQMELST- ERDAT, check the SYSDATE (System date) and compare with the VIQMELST- ERDAT. Then
calculate the difference in days.
- If SYSDATE - VIQMELST- ERDAT)>2 days, then trigger email to send the escalation mail to Cost Center Manager
and Maintenance Manager. Cost Center Manager can be located in cost center master data in user ID field.
Email template of the workflow is attached as below:
- Group the Notifications by the Cost center user responsible and then the maintenance manager.
- Cost center assignment can be found from the Account assignment segment in notification(IW23) as shown
below

-
- Cost center Manager (CSKS-VERAK_USER)can be located in the Cost centre Master data as shown below

Subject: Over 2 days - Outstanding Notifications

Body: Dear Responsible Area Manager,

This is an automated email notification sent to you to let you know that these notifications
under your responsible area are not yet processed into work orders and outstanding for over 2
days since they have been created:

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

9
Transaction Volume
Low: serveral hundreds

Frequency & Timing

<List the frequency and the timings of usage of the RICEFW object>

Daily at 1:00 PM
2 different job to be scheduled, per site, due to the different time zone.

Dependencies
<List all dependencies that need to be known/addressed while developing this RICEFW object.>
NA

Starting Conditions
When should the report be run? Does an interface need to be run before the report is valid, and (more
commonly), should it be a batch only program (with added security) or is it needed on-line as well?

This program will run on a daily basis. There is no input condition applicable here.

Authorization Requirements

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

Authorization object required to control access of the report.

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

10
 Error Handling

< List theDocumentation

Related expected errors and their OSS
(attach handling using
notes, error messages.
emails, downloadIf of
possible, provide
existing theetc.)
report, error message which
needs to be issued when error occurs.>

<Highlight all related documents that are required or will be input to the functional specification.>
5. Report Specific
Give the error
N/A Design
message if the execution is not successful. Error handling should be taken care during the
development.

Reporting
RICEFW- Description Report Type (ABAP, Data Elements Relevant KPI Owner
ID BI, BOBJ, etc)
R.PM.210. Outstanding ABAP
31 Notification for
More than 2
Days

Selection Criteria

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

11
Table/ Field Format Default Table Select Mandatory Field Labels
Structure Name Value Value/ Option or or Optional
Name Checkbox/ Parameter
Radio
Button/
Radio
Button
Group
VIQMEL QMART Select Mandatory Notification
option by Type
F4
VIQMEL IWERK Select Mandatory Planning
option by Plant
F4
VIQMEL ERDAT Select Mandatory Created
option by Date
F4
VIQMEL KOSTL Select Optional Cost Center
option by
F4

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

12
 Sample Layout of the Selection Screen

VIQMEL QMART Range (From To)

VIQMEL IWERK Range (From To)
VIQMEL ERDAT Range (From To)
VIQMEL KOSTL Range (From To)

5.1. Report Example

Input report example, use Attachment if necessary

5.2. Report Output

Report Output

Output Method
ALV on screen report. Option to download to Excel is required.

Main Heading
Notifications not Reviewed

Sub Heading
NA

LAYOUT
Table/Structure Field Name Format Default Value Column Name
Name (ie decimal places)
VIQMEL QMART NA Notification Type
VIQMEL QMNUM NA Notification Number
VIQMEL QMTXT NA Description
VIQMEL KOSTL NA Cost Center

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

13
 DRILLDOWN REQUIREMENTS
<List any drilldown requirements>
NA

TOTALING
<List if there are any calculations needed>
NA

PAGE BREAK
< List the page break requirements>
NA

5.3. Security Requirements and Authorization Details

Enter Security and Authorization objects/ fields to be used and specify the User Groups.

Security Requirements and Authorization Details

<Details on the Security & Authorization>

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

5.4. Recovery and Restart

If the program fails half way through will this have an impact on any programs to be run after its completion? Who will
re-run the report if it does not function properly? Should anyone be alerted if certain validations fail?

5.5. Assumptions

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

14
 The functional designer should detail here all the procedures or configuration affecting the report that the developer
can take for granted. Other assumptions that the designer foresees with better focus on the scope of the program
should also be included here.
These are a very important part of the specification as they ensure that no unnecessary development work is
undertaken.
Example assumptions: All weights in the SAP system will be in LBs
If no assumptions are taken for this report, indicate “No assumptions taken”.

No assumptions taken.

6. Use Cases

Use case - How the RICEFW object will be used by the user or system

<A use case is series of steps showing how user will use this object>

Business process (steps) Created a notification using IW21 and save it.

Rules N/A

Solution Approach Run the developed report on a daily basis

Standard(Y/N) N

Enhancement Type (RICEFW) Report and sending mail to concerned person.

7. Issues

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

15
 This section should be used like a log during the creation of this document to outline any outstanding issues that need to be
resolved prior to continuing with the development work. Prior to sign-off there should be no issues remaining.

Issue Issue Date Issue Description Issue Resolution Resolved By &

# Owner Raised Date
N/A N/A N/A N/A N/A N/A

8. Performance Requirements

Performance Requirements

<Details on the performance requirements>

N/A

9. Part B – Additional Details to be filled by Hilmar Cheese IS

Fill in any details the designer believes to be of benefit to the developer here.

9.1. Data Mapping Tables

List of all the fields along with their details are to be mentioned here. Look and feel wise, a desired report design can also be
specified here.

Field Name Field Output Output Format Position SAP Screen No /

Description Length Type Field Name
N/A N/A N/A N/A N/A N/A N/A

10. Validation and Test Scenarios

Validation Requirements

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

16
 <List the data, totals, exceptions, etc. to be used for Report Validation.>

Validate the notification number is accurate for outstanding notification

Validate if entry date/time is greater than 2 days

Test Scenarios

ID Description
Normal Functionality – test cases that ensure the conversion requirement as it should
1 Create notifications and check back after 2 days
2 Move outstanding notification to release and see if it‘s still generating as overdue

Exception - special logic or exceptions

5 N/A
6 N/A
Error Handling - functionality in case of errors
7 N/A
8 N/A

© Hilmar Cheese Company Confidential | 2013 Wipro LTD | www.wipro.com |

17