Escolar Documentos
Profissional Documentos
Cultura Documentos
M-080
PLANNED ORDERS: SHOWING ‘SISTER’ PRODUCTS
VERSION HISTORY
VERSION AUTHOR DATE DESCRIPTION
0.1 Production team 30/06/2008 Initial Migration
1.0 NEW 19-09-2007 Draft Version 1
2.0 NEW 30/10/2007 Include changes made by H. Has
Page 1/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Table of Content
1 Functional Specification.................................................................................................................3
1.1 Request Administration....................................................................................................................3
1.2 Change History..................................................................................................................................3
1.3 Priority and Complexity.....................................................................................................................3
1.4 Alternative Solutions.........................................................................................................................3
1.5 Effort Estimate...................................................................................................................................4
1.6 Initial Development Approval...........................................................................................................4
1.7 Final Development Approval............................................................................................................4
1.8 Assumptions......................................................................................................................................4
1.9 Legacy Systems.................................................................................................................................4
1.10 Business Requirements..................................................................................................................5
1.11 Interface / Conversion Requirements..........................................................................................10
1.12 Report specification......................................................................................................................11
1.12.1 General Specifications..............................................................................................................11
1.12.2 Data Fields................................................................................................................................12
1.12.3 Report Layout and/or Example..................................................................................................19
1.13 Test Plans.......................................................................................................................................20
1.14 Functional Specification Approval...............................................................................................20
2 Technical Specification.............................................................................................................................20
2.1 Program Information.......................................................................................................................20
2.2 Program Structure...........................................................................................................................22
2.3 SAP Script Forms............................................................................................................................23
2.4 Enhancements.................................................................................................................................23
2.5 Modification......................................................................................................................................24
2.6 Custom Development......................................................................................................................24
2.7 Technical Specification Approval...................................................................................................26
Page 2/26
FUNCTIONAL & TECHNICAL SPECIFICATION
1 FUNCTIONAL SPECIFICATION
Priority: ( X ) Critical
( ) High
( ) Medium
( ) Low
Complexity ( ) Low ( ) Medium ( X ) High
Page 3/26
FUNCTIONAL & TECHNICAL SPECIFICATION
1.5 EFFORT ESTIMATE
Technical Estimate Planning Estimate Revised Estimate
1.8 ASSUMPTIONS
Definitions, Acronyms, Abbreviations: Any term associated with this spec that may not be commonly used
Short description:
Page 4/26
FUNCTIONAL & TECHNICAL SPECIFICATION
1.10 BUSINESS REQUIREMENTS
1.10.1 Business Driver (Purpose):
Overview where planned orders for the production of Finished Goods (FG’s) are grouped by their
semi-finished product. FG’s which need the same semi-finished product (=same formula) are called
‘sisters’; usually the same mix in different packagings (
Page 5/26
FUNCTIONAL & TECHNICAL SPECIFICATION
The selection of finished/sem-finished orders can either happen by MRP controller, required material
(semi-finished) or requirering material (finished). It is also possible to get a combination of these
options. The main table that should be used is MDRS which contains most of the information needed
for this report.
Second criteria is the time period.
Additionally the user has to descide which period (day, week, month, selection prerod) he wants sum
criteria for the required and produced quantity of semi-finished product. This selection should appear
as radio buttons.
Selection screen:
Required Material
1) Selection via MRP controller (The selection sequence is just one possible solution and
should be adjusted if for performance reasons another selection sequence is more suitable)
a. Select all materials (MATNR) from table MARC where the MRP controller (DISPO)
Requiring Material
and plant (WERKS) is equal to the selected values
b. For all entries (MATNR) found check table MARA to get the materials with a material
type (MTART) equal to “ZSFG” – these are the semi-finished goods.
c. Check table MAST for each material number found in 1b), selected plant (WERKS)
and BOM Usage (STLAN) = “1”. If yes set the indicator to “Y”
d. With the results of 1c) check table STPO whether field ITSOB is not equal to “50”
(meaning the material is not a phantom BOM).
e. Read table MDRS with the found entries (MATNR) in 1d), Requirement type
(BDART) equal to “AR” or “SB”, the selected plant (WERKS) and date (BDTER) to
get the accordant production orders (AUFNR) or planned orders (PLNUM).
Additionally read the pegged requirement – “sister product” (BAUGR), requirement
quantity (BDMNG), Base Unit of Measure (MEINS) and requirement date (BDTER)
Material Controller
for each order.
f. For each production order (AUFNR) – MDRS-BDART = “AR” – read AFKO to get the
target quantity (GAMNG) and the Base Unit of Measure (GMEIN).
g. For each planned order (PLNUM) – MDRS-BDART = “SB” – read table PLAF to get
the Planned order qty (GSMNG) as well as the Base Unit of Measure (MEINS).
h. For each “sister product” and the selected plant (WERKS) check table MARC to get
the corresponding MRP controller (DISPO)
Page 6/26
FUNCTIONAL & TECHNICAL SPECIFICATION
2) Selection via semi-finished materials
a. Read table MDRS with the selected materials (MATNR), Requirement type (BDART)
equal to “AR” or “SB”, the selected plant (WERKS) and date (BDTER) to get the
accordant production orders (AUFNR) or planned orders (PLNUM). Additionally read
the pegged requirement – “sister product” (BAUGR), requirement quantity
(BDMNG), Base Unit of Measure (MEINS) and requirement date (BDTER) for each
order.
b. For each production order (AUFNR) – MDRS-BDART = “AR” – read AFKO to get the
target quantity (GAMNG) and the Base Unit of Measure (GMEIN).
c. For each planned order (PLNUM) – MDRS-BDART = “SB” – read table PLAF to get
the Planned order qty (GSMNG) as well as the Base Unit of Measure (MEINS).
d. For each selected semi-finished material or “sister product” and the selected plant
(WERKS) check table MARC to get the corresponding MRP controller (DISPO)
e. To get the premix indicator (internal parameter) check table MAST for each selected
material number, selected plant (WERKS) and BOM Usage (STLAN) = “1”. If yes set
the indicator to “Y”
3) Selection via finished products (sister product)
a. Select the bill of material (STLNR) from MAST where the material numbers
(MATNR) is equal to the selected materials and the BOM Usage is equal to “R”.
b. For each found BOM ((STLNR) read table STPO to get the BOM components
(IDNRK)
c. Check table MARA with the found components (MATNR) for the material type
(MTART) equal “ZSFG” – these are the semi-finished goods.
d. To get the premix indicator check table MAST for each material number found in 1c),
selected plant (WERKS) and BOM Usage (STLAN) = “1”. If yes set the indicator to
“Y”
e. With the results of 1d) check table STPO whether field ITSOB is not equal to “50”
(meaning the material is not a phantom BOM).
f. Read table MDRS with the found entries (MATNR) in 1e), Requirement type
(BDART) equal to “AR” or “SB”, the selected plant (WERKS) and date (BDTER) to
get the accordant production orders (AUFNR) or planned orders (PLNUM).
Additionally read the pegged requirement – “sister product” (BAUGR), requirement
quantity (BDMNG), Base Unit of Measure (MEINS) and requirement date (BDTER)
for each order.
g. For each production order (AUFNR) – MDRS-BDART = “AR” – read AFKO to get the
target quantity (GAMNG) and the Base Unit of Measure (GMEIN).
h. For each planned order (PLNUM) – MDRS-BDART = “SB” – read table PLAF to
check whether the planned order is convertible (PLAF-UMSKZ is flagged). For these
get the Planned order qty (GSMNG) as well as the Base Unit of Measure (MEINS).
i. For each “sister product” and the selected plant (WERKS) check table MARC to get
the corresponding MRP controller (DISPO).
The result screen should be interactive in a way that it is possible to double-click one of the found
process orders (either prduction of semi-finished product or finished product using the semi-finished)
and open this one in change mode (transaction C202)
1.10.3 List the Business Process Documents related to this development: ( If applicable)
2nd Review RM BPD_M-080_070628_V10-Final_HHA.doc
REP_M-080-001_20070411_V02_HHA.xls
Page 7/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Page 8/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Production planner - Plant - Production planner will only plan 'his' plant.
Page 9/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Business Owner:
Mapping Attachment: ( ) No ( ) Yes -
Sample Data Attachment: ( ) No ( ) Yes -
None
Page 10/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Offline Reporting:
Offline Reports are pre-calculated reports stored within the system or broadcasted
via email or paper to the appropriate report recipients, e.g. Sales Force user.
Access via Amount of users for pilot countries Amount of expected users for EBS
Europe
BW BEx Analyzer (*.xls)
BW Web Analyzer (*.html)
ABAP xx xx
Offline Properties
Report Volume (How many lines, on an average, are on the report?)
( ) <10 to 100>
( ) <101 to 1.000>
( ) <1001 to 10.000>
( ) <More then 10.000>
( ) <More then 65.000>
Page 11/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Data Sources
System Area Amount of History Amount of History
at Golive ongoing
PP-PI • Planned order (PLAF) 1 month 1 month
• Process orders (AFKO)
• Dependent requirement
(MDRS)
• Material Master (MARA,
MARC)
• BOM (MAST, STPO)
Page 12/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Prompt Mandatory (M) Range (R) or
Characteristic Variable
Description or Optional (O) Value (V)
Sum Period PER_DAY M V
PER_WEEK
PER_MONTH
PER_PERIOD
(Please put in order needed on report: Rows/Columns from top to bottom/left to right.
Add lines as needed.)
Key figures are numeric values. They can stand alone, be summed or used as a value in
another calculation. Often, they are accompanied by a currency or unit of measure (e.g.
gross sales, committed quantity, net postings, etc.)
Sequence number is based on above columns as well. For example, you may want to have a
calculation placed to the right of a column listed above. The column listed above is number
4. The sequence number in this section would have a 5 in it.
Calculat Form
Se ion (C) at /
q or Required Calculation and
Calculated Field Calculation Deci Scal
Nu Restricti Source Fields (BMC ID) /
Description Variable mal e
m on (R) Required Restriction
Place
s
Page 13/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Page 14/26
FUNCTIONAL AND TECHNICAL SPECIFICATION
(Please put in order needed on report: Rows/Columns from top to bottom/left to right. Add lines as needed.)
Characteristics are business dimensions and are often considered master data. Some examples of characteristics are cost centers, accounts,
material groups, company codes, plants, order types, etc.
A “Key” is information such as a customer number (0808907703) that uniquely identifies an entry in a table. A “Description” describes the
“Key”, a name such as “American Airlines”. If both “Key” and “Description” (0808907703 American Airlines) were selected, you would be
able to sort on both the elements on the report, i.e., by name and then by customer number.
ROW Definition
Page 15/26
FUNCTIONAL & TECHNICAL SPECIFICATION
4 Premix C K D -- Y
Column Definition
Page 16/26
FUNCTIONAL & TECHNICAL SPECIFICATION
PLAF-MEINS
MDRS-
MEINS
PLAF-MEINS
Page 17/26
FUNCTIONAL & TECHNICAL SPECIFICATION
1.12.2.5 Free Characteristics (BW Online only)
If a characteristic is defined as a drilldown / free characteristic, it will not be displayed in a row or column, but in a section above the report results area.
However, you will be able to have it appear in a row or column by drilling into it. For instance, if cost center is a characteristic in the row area of the report
and cost element is a drilldown / free characteristic, you will be able to select a single cost center and then drilldown to all the cost elements that make up
that cost center.
Specific time
scenario for
relationships Key & Description,
Characteristic Limit to: specific value
between Key Only, or
Description or variable option
characteristics Description Only
(current or
historical)
Page 18/26
FUNCTIONAL AND TECHNICAL SPECIFICATION
Please attach a copy of the layout you want for the initial view of the report and if necessary
for additional navigation steps as well. Make sure to include information described in the
above sections. (Rows, Free Characteristics, Columns, Calculations)
If a screenshot or attached document is not sufficient enough to specify the layout, please
use the section below as well to describe the layout.
Sample:
Batch
number of
Semi-finished semi-finishe
Example:
Product product
Sorting:
The materials 207589 and 207590 are both using 904210 as component. To smoothen the production of
semi-finished product the timewise correlant orders for finished product should be displayed accordingly.
The sorting should be happen per semi-finished product, date for each period (day, week, …), semi-
63 3087TE012
finished product order and finished product order . The order for finished product should be sorted to the
semi-finished order they “belong to”.
In the described example above we have two orders for 904210 for the 10/01 and the 10/04. For the
finished product we have requirement dates for the 10/01, 10/03, 10/05 and 10/06.
63 3087TE012
In our case the finished goods order from the 10/01 and the 10/03 belong logically to the semi-finished
order from the 10/01 and so on.
63
Threshold: 3087TE012
We have a process order over 480 kg for the 10/01 of semi-finished 63. Against this quantity we have
63 3087TE012
demands over 48 kg of this material on the 10/02 and a second over 460 kg on the 10/03. As this
accumulated quantity of 48 + 460 is more than the produced quantity of 480 kg this cell should be marked
in red.
2 TECHNICAL SPECIFICATION
Page 20/26
FUNCTIONAL & TECHNICAL SPECIFICATION
2.1.1 Program Information
Program Name
What SAP
transaction(s) do the
interface/ conversion
involve?
Menu path for
transaction(s)
Report Transaction
Select Options Field Name Default
Page 21/26
FUNCTIONAL & TECHNICAL SPECIFICATION
1. Type of interface
2. Direction of interface:
( ) Real-Time ( ) Batch
3. Frequency:
( ) Inbound ( ) Outbound ( ) Both
( ) Daily ( ) Weekly ( ) Monthly
( ) Other: _______________________
Page 22/26
FUNCTIONAL & TECHNICAL SPECIFICATION
(Attach a excel spreadsheet with how to map data between different systems. Include conversion and
validation rules. The Excel mapping template is: TBD )
SAPScript Forms: (This section to be deleted if request does not belong to this classification)
If copied from Standard Form Name, Standard Form Name:
Describe changes to the layout set: (Paragraph formats, windows, page windows, page sequence,
pages and character formats)
2.4 ENHANCEMENTS
Enhancements: (This section to be deleted if request does not belong to this classification)
Enhancement Project Name:
Page 23/26
FUNCTIONAL & TECHNICAL SPECIFICATION
2.5 MODIFICATION
Modification: (This section to be deleted if request does not belong to this classification)
List the name and type of the SAP Objects that need to be modified:
Describe Modification: (Also mention the impact of the object modified on other processes. Refer to created
objects)
Page 24/26
FUNCTIONAL & TECHNICAL SPECIFICATION
Domain Description Data Type/ Output Lower Check
Name Length Length Case Table
2.6.5 Describe new transactions: (Provide a description of each screen include fields, possible User
actions and any Processing that should happen)
Field Definition:
Screen Field Type(Field, Field Format Input List of Possible Validati
Values and on
No. Name Push Button, Text Masks Context Error
Or Table Control) Sensitive Help Actions
2.6.6 Describe the Update Method for Tables: (Method, sequence, function modules, update processes,
locking requirements)
Page 25/26
FUNCTIONAL & TECHNICAL SPECIFICATION
2.7 TECHNICAL SPECIFICATION APPROVAL
Technical Specification Approval:
Signature Date
Technical Approval
Process/Workstream Approval
Page 26/26