<Enter document title here>

337346217.doc

<Enter version here>

Coty Green
Report Functional Design
17 November y
Hazardous Substances Report
RICEFW 25
- Create one document for each RICEFW object

Modified: 17/11/y 20:16

Page 1 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Document Control
Location: <Enter SolMan Location here>

Document Owner
Owning Team

Author

WM COE

Ester Rubio

MFG global team

Ruben Garca Zarza

WM global team

Roberto Martnez Arauzo

Document History
Author

Date

Version

Comment

Sergio Espino

25.05.2016

1.0

Initial Version

1.1

Final Version

Roberto Martnez
Arauzo

Related Documents

Comment

Title

Modified: 17/11/y 20:16

Page 2 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Document Review & Signoff

Name

Position

Action

Marta
Gomez
Munoz

Coty IT Lead

Guillaum
e Scolan

Coty Business Lead

Ester
Rubio

CoE Commercial Lead

Roberto
Martnez
Arauzo

WM Global TL

Alberto
Gallardo
Doate

WM Global TM

FR

Approved

S = Signed Approval Required, QA= Quality Assurance Review Required, FR = Formal Review
Required, IR = Informal Review, I = For Information.

Modified: 17/11/y 20:16

Page 3 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Table of Contents
1.
1.1.
1.2.
1.3.
1.4.
1.5.

OVERVIEW............................................................................................................................... 5
BUSINESS RATIONALE...............................................................................................................5
DESIGN RATIONALE.................................................................................................................. 5
RELATED PROCESSES..............................................................................................................5
GENERAL REFERENCES............................................................................................................5
GENERAL INFORMATION............................................................................................................6

2.

REPORTING AREA.................................................................................................................. 6

2.1.
2.2.
2.3.
2.4.

FUNCTIONAL DESCRIPTION.......................................................................................................6
ASSUMPTIONS.......................................................................................................................... 6
DEPENDENCIES/CONSTRAINTS..................................................................................................7
REPORT CONTENT................................................................................................................... 7
2.4.1. Selection Criteria........................................................................................................7
2.4.2. Data Fields................................................................................................................. 8

3.

DETAILED FUNCTIONAL REQUIREMENTS REPORT [NAME]..........................................9

3.1.
3.2.
3.3.

GENERAL INFORMATION............................................................................................................9
PURPOSE / DESCRIPTION.......................................................................................................... 9
FUNCTIONAL SPECIFICATION.....................................................................................................9
3.3.1. Selection Criteria......................................................................................................11
3.3.2. Sub Heading............................................................................................................ 14
3.3.3. Totalling / Process Logic...........................................................................................14
3.3.5. Sorting...................................................................................................................... 15
3.3.6. Detailed Layout Design............................................................................................15
3.3.7. Existing Sample Reports..........................................................................................15
3.3.8. Security and Authorisation........................................................................................15
3.3.9. Report Variants........................................................................................................ 15
3.3.10. Interactive Capabilities.............................................................................................15
3.3.11. Performance Considerations....................................................................................16
3.4. ERROR HANDLING.................................................................................................................. 17
4.
4.1.
4.2.
4.3.
5.

TESTING REQUIREMENTS...................................................................................................17
CONFIGURATION FOR TESTING................................................................................................17
BUSINESS TEST CONDITIONS..................................................................................................17
TEST DATA............................................................................................................................. 18
APPENDIX.............................................................................................................................. 19

Modified: 17/11/y 20:16

Page 4 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

1.

Overview

1.1. Business Rationale

The necessity of having a report of dangerous goods in the plants, is due to legal local
requirements that does not allow to store high levels of dangerous materials, this report will allow
us to know what are the volumes and manage the storage.
1.2. Design Rationale
Background: The usage of dangerous materials in the warehouse creates the neccesity to have a
very specific control about them, be it as free raw material, or as part of bulks or finished goods.
Options: Actually there is no standard report and it is a government legal requirement. Standard
SAP wise, it would be possible to implement hazardous materials but it is not part of Coty
Operations standard. As for the solution, it is possible to have individual materials stock report in
alternative units of measure, but not as a mass report.
Recommendation and decision: Generate a report for dangerous goods with up to date information
for materials and volume that is stored in the warehouses.

1.3. Related Processes

Business Process
reference

Process (where used)

1.4. General references

References

Description

Project Name

Coty Green

Company codes
involved

All Operations Companies

References

Description & Link

Reference in RICEFW

Modified: 17/11/y 20:16

Page 5 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

inventory
Reference to other
RICEFW
SAP Business object(s)
reference (where
applicable)

1.5. General Information

Reporting Area
Functional Team
(Commercial,
Operational, Finance)
Workstream (P2P, OTC,
RTR, TCM )
Reporting Area
Description / Report
Name

2.

Material Management and Warehouse Managment

All Warehouse

Hazardous Substances Report

Reporting Area

N/A
2.1. Functional Description
The report should contain basic information about the materials and plant with which a series of
searches of relevant information and conversion units will be done, the report will add equal
conversion units and we will know the volumes of the dangerous goods that are stored in the
warehouse, this is required to validate that the authorized quantities have not been surpassed.
Having this information will allow the management team to take decisions about the quantity and
volumes managed in the warehouse and prevent risks.
2.2. Assumptions
No.
1.

Assumption detail
The report should be by plant

Modified: 17/11/y 20:16

Page 6 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

2.

The articules should have the correct conversion units

3.

All master data should be loaded correct

4.

1.3. Dependencies/Constraints
No.
1.

Dependency detail
Master Data

2.
3.

1.4. Report Content

.
2.2.1. Selection Criteria

DATA
ELEMENT

DESCRIPTION

Material

Material Number

Plant

Plant

Material Type

Material Type

Material Group

Material Group

MRP Controller

MRP Controller (Materials Planner)

Storage Location

Storage Location

Special Stock
Type

Special Stock Indicator

Special Stock
Number

Special Stock Number

Alternative UoM

Hazardous Substance Conversion

Modified: 17/11/y 20:16

Page 7 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

1.1.2. Data Fields

Modified: 17/11/y 20:16

Page 8 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

3. Detailed Functional Requirements Report [name]

2.3. General Information

Report Information
RICEFW ID

Report_FS_ID_25_Hazardous Substances Report

Report Name

Hazardous Substances Report

Report Description

To have a report of dangerous goods and their component volumes

Process ID

1.2. Purpose / Description

2.4. Functional Specification

Detailed
Requirement

Source Data
System

Task Description

Where the data needs came from:

- SAP

Comments

<The purpose of this question is to know

if there is a Standard R/3 report that can
answer the requirement, but for same
reason (performance) that must be built
in the BI side
This is not the case for this. We would
be looking at whether the data is
available the report question is 2 down.

Number of SAP
modules involved

How many SAP modules are involved in the report

construction:

Is there any
Standard SAP
report for this
requirement?

Indicate if exists any Standard SAP report which answer

this requirement:

Standard BI
component level
for this
requirement

Indicate level of match per Content Check tool

- ONE

- YES, MMBE but one material at a time

- NONE

Modified: 17/11/y 20:16

Page 9 of 18

<The purpose of this question is if for

instance to know if there is a Standard
SAP Report (ECC,SRM,SCM) report that
can answer the requirement, but for
same reason (performance) that must be
build in the BI side>
<This information should come from the
gap complexity analysis afterwards only
in you have available this information>

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>
Detailed
Requirement

Information
Update

Task Description

Indicate the type of processing used by the report:

- REAL TIME (legal limit check at any given moment)

Comments

<REAL TIME information should be for

ABAP reports requirement> Remove the
comment about ABAP.
Insert Real time data is when the data
must be available instantly as the
information is created.
We need to state that any real time or
near real time requirement must have a
business justification attached.
If Other is requested then description is
required as well as a business
justification.
For near real time please indicate the
greatest age of the information that
would be acceptable.
- 1 min
- 5 min
- etc

Aggregation
Capability.

Specify requirements for aggregation capability:

- FULL DETAIL (document)
- AND AGGREGATION (EITHER)
(dimension/characteristic)

Analysis
Capability

Specify requirements for analysis capability:

Key Figure
Business Alert
Required

The ability to give a alert to the user about the key figure
values :

Time Frame
Analysis
(Long-term
historical data)

Please, select the expected extension of analysis in time:

Global or Local

Specify report as:

- YES (Material master) - Enabled navigation capability

Please explain the two options and

indicate that a description of the
selection aggregation or either is
required.

Describe what navigation capability

means.

- NO

- NO (current data),

- GLOBAL requirement

Type of
Requirement

Prioritise the need for this report to support the Core

Business Model:
- LEGAL

2.4.1. Selection Criteria

The report needs to be presented in ALV format, which need to contain the standard function that
allows select the fields show or remove from report
Modified: 17/11/y 20:16

Page 10 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Optional fields

Material Type
Material Group
MRP Controller
Special Stock
Type
Special Stock
Number
Material
Storage Location
-

Mandatory fields

Plant
Alternative UoM
-

If a selection range is possible

It is possible a selection range
Multiple selection
No data restrictions should apply
If the mandatory fields are no fulfilled completely, an error message is to be issued

Modified: 17/11/y 20:16

Page 11 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Type
Field

Description

(Select Options/

Mandatory

Single Value/

(Yes/No)

Default Value

Validation

check box)

Material

Material
Number

Select Options

NO

NO

Plant

Plant

Select Options

YES

NO

A data in the system should

exist

Storage
Location

Storage
Location

Select Options

NO

NO

A data in the system should

exist

Material
Type

Material
Type

Select Options

NO

NO

An existing material type

Material
Group

Material
Group

Select Options

NO

NO

An existing material
group

MRP
Controller

MRP
Controller
(Materials
Planner)

Select Options

NO

NO

An existing MRP
Controller in some plant

Special
Stock
Type

Special
Stock
Indicator

Select Options

NO

NO

A valid stock type

Special
Stock
Number

Special
Stock
Number

Select Options

NO

NO

Alternativ
e UoM

Alternativ
e Unit of
Measure
for
Stockkeep
ing Unit

Select Options

YES

NO

An existing UoM

Main heading field for the report: Hazardous Substances Report

Modified: 17/11/y 20:16

Page 12 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

2.4.2. Sub Heading

2.4.3. Totalling / Process Logic
The report should total all the materials that where extracted with the selected parameters, with
one column per stock status.
If the in the parameter alternative UoM field has multiple entries, the report should divide the
information by UoM.
The information of the quantities of each one of the materials and their status, will be extracted by
the following key fields:
TABLE

FIELD NAME

DESCRIPTION

MARC

MATNR

Material Number

MARC

WERKS

Plant

MARD

LGORT

Storage Location

T134

MTART

Material Type

T023

MATKL

Material Group

MARC

DISPO

MRP Controller (Materials

Planner)

LTAP

SOBKS

Special Stock Indicator

LTAP

LVS_SONUM

Special Stock Number

MARM

MEINS

Alternative Unit of Measure for

Stockkeeping Unit

The fields to extract for each one of the materials are the following:
The extraction of the special stock will be used as key fields MATNR, WERKS and LGORT in the
table MARD, they will be used as filters to shorten the search
TABLE

FIELD NAME

DESCRIPTION

MARD

LABST

Unrestricted

MARD

UMLME

Stock in tfr

MARD

INSME

In Qual. Insp.

MARD

EINME

Restricted-Use

MARD

SPEME

Blocked

MARD

RETME

Returns

The conversion of the quantities to the ones of the report is to be executed through BAPI
MATERIAL_UNIT_CONVERSION. If the conversions throws an error due to non-existant
Modified: 17/11/y 20:16

Page 13 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

alternative UoM for the material, then the material is completely skipped in the output report (not
even a line with quantity zero). The same for materials for which all the quantities are zero.
Which need to be included in the report with the quantities by status
1.1.5. Sorting
Classify by unit of measure, then material properties (Material Type, Group), then by Plant and
MRP Controller, then Storage location, finally by Material.
2.4.4. Detailed Layout Design
It must have the ALV report functionality that allows visualising each one of the selection fields and
the quantities of each material, the grouping method has to be by by UoM, this is the most
important information for warehouse to know the volume of each dangerous goods

The quantities in the report should include two decimals.

In should be grouped by alternative UoM

It should present the total by alternative UoM

It should allow to be exported as an excel file

The report should be executed on line or in batch

1.1.1. Existing Sample Reports

N/A

1.1.1. Security and Authorization

The program should be executed by plant personal which needs to be controlled by an
authorization object which needs to be created and regulated by plant level. The same
authorization objects as MB52 or MMBE need to be used (stocks per plant). Additionally,
authorization object Z_WM_WRK should be checked for each of the plants in the selection screen.
If any plant is not authorized, then it will be deleted from the selection parameter. If no plants exist
at the end of checks, then an error message needs to be issued No authorization for any of the
selected plants. If some plant still exists but some plants were deleted due to the authorization
check, issue a warning Authorizations restricted for some of the selected plants.
Modified: 17/11/y 20:16

Page 14 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

The report should be created by Z Transaction, which will be assigned to the same roles as MB52
or MMBE.

2.4.5. Report Variants

N/A
2.4.6. Interactive Capabilities
Table 3 BI / ECC T-Codes & Jump Targets
SAP Field

Material

T-Code / Jump Target

MM03

Description

Display Material Master

1.3.1. Performance Considerations

Performance characteristics

Should allow to be process online or in batch

The expected volume is once a day but the data volume is high because it should
contemplate all materials in the system
Aprox. material volume per plant = 20,000

Modified: 17/11/y 20:16

Page 15 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

1.1.

Error Handling

Notification Procedure

Error Code

Error
Description

Error
Resolution

Error Message
(English)

Screen

Log File

25

The material does

not exist in the
system

Contact the data

base
administrator

Material XXXX does not

exist

Yes

No

25-1

Plant does not

exist in the
system

Review the input

data

Plant XXXX does not

exist

Yes

No

25-2

Warehouse does
not exist in the
system

Review the input

data

Plant XXXX does not

exist

Yes

No

25-3

The report does

not contains the
information

Review the input

data

The report cannot be

generated because it
contains no information

Yes

No

Testing Requirements

2.

2.5.
Configuration for Testing
All WM+LE configuration must be completed.

2.6.
No
.

Business Test Conditions

Description

Expected Result

Enter a material that does not exist

The report will indicate that no data was found

Enter a plant, or storage location, or

material group, or material type, or
MRP Controller or special stock type
that does not exist

The report should send an error message

Correct information entered, one

material with UoM conversion, another
without it

Only the information for the material with the

UoM conversion is displayed

Modified: 17/11/y 20:16

Page 16 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

Test with high data volume

Consolidated information by unit of measure

2.1.
Test Data
Complete materials in system
Warehouse should have stock with their status
Report should be run with different materials
Report should be generated with high volume of data

The materials to be used for the test are:

Material

Description

Plant

R0029

Propylene Glycol

CU05

R0205

8108 Kahlwax
(WH.Beeswax)

CU05

R0286

Stearic acid 5P

CU05

R0364

Talc Italian Extra 5/0

CU05

R0753

PVP K30

CU05

R1374

Crosilk Powder

CU05

R2225

Oliwax

CU05

The volume of data for each plan can be around 8000 materials.
The report should only extract data from the plant which is authorized and should not read data
from other plants.

Modified: 17/11/y 20:16

Page 17 of 18

Last modified by:

<Enter document title here>

337346217.doc
<Enter version here>

3.

Appendix

Modified: 17/11/y 20:16

Page 18 of 18

Last modified by: