Unctional AND Echnical Pecification

FUNCTIONAL AND TECHNICAL SPECIFICATION
Prepared by: Production team Last Modification Date: 12/8/2021

Specification, Development,
Status: Draft Keywords:
Report, M-080, Sister, product
M-080
PLANNED ORDERS: SHOWING ‘SISTER’ PRODUCTS
VERSION HISTORY
Version Author Date Description
0.1 Production team 17/04/2011 Initial Migration
1.0 NEW 19-09-2007 Draft Version 1
2.0 NEW 30/10/2007 Include changes made by H. Has
PURPOSE OF DOCUMENT AND INSTRUCTIONS

The functional and technical specification document is used to collect and document all necessary
information for EBS Developments. In order to have a smooth implementation of the developments and to
enable the off-shore development of ABAP components the following rules need to be followed:
 One Document needs to be created for each development.
 The document will be created during Blueprint phase with the information listed below (when
possible references to existing documents should be used)
o 1.1 Request Administration
o 1.2 Change History
o 1.3 Priority & Complexity
o 1.4. Alternative Solutions (If applicable)
o 1.5 Effort Estimate
o 1.6 Initial Approval
o 1.8 Assumptions
o 1.9 Legacy Systems (If applicable)
o 1.10 Business Requirements
o 1.11 Interface / Conversion Requirements
o 1.12 Test Plans
o 1.13 Functional Specification Approval
 The fields marked in red need to be filled out by the functional teams
 All other fields will be filled by the technical teams
 The remaining sections will be completed at the beginning of the Realization phase
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............................................................................................................................. 3
1.6 Initial Development Approval..................................................................................................... 3
1.7 Final Development Approval...................................................................................................... 3
1.8 Assumptions................................................................................................................................ 3
1.9 Legacy Systems........................................................................................................................... 3
1.10 Business Requirements.............................................................................................................. 3
1.11 Interface / Conversion Requirements........................................................................................3
1.12 Report specification.................................................................................................................... 3
1.12.1 General Specifications............................................................................................................. 3
1.12.2 Data Fields............................................................................................................................... 3
1.12.3 Report Layout and/or Example................................................................................................. 3
1.13 Test Plans..................................................................................................................................... 3
1.14 Functional Specification Approval.............................................................................................3
2 Technical Specification........................................................................................................................... 3
2.1 Program Information................................................................................................................... 3
2.2 Program Structure....................................................................................................................... 3
2.3 SAP Script Forms........................................................................................................................ 3
2.4 Enhancements............................................................................................................................. 3
2.5 Modification.................................................................................................................................. 3
2.6 Custom Development.................................................................................................................. 3
2.7 Technical Specification Approval............................................................................................... 3
Page 2/26
1 FUNCTIONAL SPECIFICATION
1.1 REQUEST ADMINISTRATION
JUSTIFICATION SECTION:
Product/Module ECC SAP version: Date: 12/8/2021
Dev. Request ID/ IM Report ID (if a report): 148
Functional Team: Ops
Phase: Blueprint
Requested by: Production team Extension :
Functional Analyst (Owner): Production team Extension:
Technical Analyst: Extension :
1.2 CHANGE HISTORY
Change History (To track changes to specification after it has been approved)
Version Date Modified Brief Description of Change
# Modified By
01 2007/09/19 NEW Original specification
1.3 PRIORITY AND COMPLEXITY
Program ( ) Conversion ( ) Interface ( X ) ABAP Report ( ) User Exit ( ) Form

type: ( ) New Development – R/3 ( ) Legacy / Bolt-On ( ) BW Report
Priority: ( X ) Critical
( ) High
( ) Medium
( ) Low
Complexity ( ) Low ( ) Medium ( X ) High
1.4 ALTERNATIVE SOLUTIONS
Impact of not creating the ( ) legal requirements will not be fulfilled

program: ( X ) lack of information required for the business
( ) lose functionality compared to the old system
( ) others:
eg:
Are there any alternatives? ( ) Yes ( X ) No
Describe the alternative found:
Reason why this alternative was ( ) Performance problems ( ) Complexity
not acceptable ( ) Others
(Describe, if needed …____________________…)
1.5 EFFORT ESTIMATE
Technical Estimate Planning Estimate Revised Estimate
Page 3/26
Functional Spec Review / QC 2 days__ 2 days _________

Technical Design / QC Review ________ ______________
Technical Development ________ _______________
Technical Testing ________ _______________
Final QC Review / Production ________ _______________
Total Estimate ________ _______________
1.6 INITIAL DEVELOPMENT APPROVAL
Initial Development Approval:

Signature Date
Process/Workstream Approval OPS Team Lead Approval date
Application Dev./IM Lead Approval
PMO Approval(if necessary)
1.7 FINAL DEVELOPMENT APPROVAL
Final Development Approval: (upon successful completion of functional unit test)

Final Sign-off here indicates acceptance to transport development object(s) to QA system
Signature Date
Process/Workstream Approval OPS Team Lead Approval date
Application Dev./IM Lead Approval
PMO Approval(if necessary)
1.8 ASSUMPTIONS
Definitions, Acronyms, Abbreviations: Any term associated with this spec that may not be commonly used
Assumptions: List assumptions that will be used in the document
1.9 LEGACY SYSTEMS

List of Existing Legacy Systems SAP system of the legal entity
Involved in this Development Effort
Short description:
Page 4/26
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 (
1.10.2 Detailed Development Requirements Description:
Page 5/26
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:
From To
Required Material
Requiring Material
Material Controller
Period
Sum Period: Day

Week
Month
Period
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)
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)
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
2) Selection via semi-finished materials

a. Read table MDRS with the selected materials (MATNR), Requirement type
for each order.
b. For each production order (AUFNR) – MDRS-BDART = “AR” – read AFKO to get
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
for each order.
g. For each production order (AUFNR) – MDRS-BDART = “AR” – read AFKO to get
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)
Page 7/26
2nd Review RM BPD_M-080_070628_V10-Final_HHA.doc

REP_M-080-001_20070411_V02_HHA.xls
1.10.4 Control / Audit Processing Requirements:
1.10.5 General Processing Requirements

Processing Mode: ( ) Batch ( ) Online
Frequency: ( ) Annually ( ) Quarterly ( ) Monthly ( ) Weekly ( ) Daily
( ) Other (specify)___________________________________________
Expected Data Volume
Page 8/26
1.10.6 Authorization Requirements
Production planner - Plant - Production planner will only plan 'his' plant.
For Reports only:
User Group or User Role:___________________________________________________
1.10.7 Business Process Flow Diagram
1.10.8 Technical Flow Diagram/Example ( if applicable)
1.10.9 Selection Screen Requirements ( if applicable)
Page 9/26
1.11 INTERFACE / CONVERSION REQUIREMENTS

1.11.1 INTERFACE/CONVERSION SECTION:
Name of Interface or Conversion:

Type: ( ) Interface ( ) Conversion ( ) New Development
Functional Team:
Business Owner:
Mapping Attachment: ( ) No ( ) Yes -
Sample Data Attachment: ( ) No ( ) Yes -
1.11.2 Dependencies/Prerequisites (Translation Rules)
S No
Description
Dependency Type
(Object/Configuration/legacy/external systems)
Development Sequence
1.11.3 Are there any additional Training impacts?
None
Page 10/26
1.12 REPORT SPECIFICATION

1.12.1 General Specifications
Report Access / Format

Two ways in general exists to access EBS Reports:
Online Reporting:
For Online Reports the user get access to the report by using either a predefined
BW report via the BEx Analyzer or Web Analyzer tool or using the ERP/CRM created
ABAP report. Most of the reports are expected as Online Reports.
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.
Online Reporting: Requires a SAP online connection
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 Reporting: No SAP Connection available
Format required (Y/N) Amount of expected users for

Access via
*.xls *.pdf EBS Europe
Portal/Intranet
E-Mail
Printout Paper:
Page 11/26
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>
Frequency (What is the broadcast frequency?)

Real time Daily Monthly Quarterly Yearly Other
On demand
Timeliness of information:
Real time Daily Monthly Quarterly Yearly Other
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)
Report Properties Property Description

Report Type (i.e. Tabular, Bar Graph, Pie Tabular
Chart, combined)
Timeframe needed (e.g. current and 1 rolling month
prior year, 12 rolling month,..)
Color Coding / Thresholds needed (if When the quantity of semi-finished product is smaller then the
yes, which are those) corresponding planned / production order the order quantity that
passes the threshold should be marked in red.
1.12.2 Data Fields
1.12.2.1 Selection Criteria
(Report Prompts at run time, include a mock-up if possible)
Page 12/26
Mandatory (M) or
Prompt Description Characteristic Range (R) or Value (V) Variable
Optional (O)
Plant WERKS M V
MRP Controller DISPO O V
Material (requiring) BAUGR O R
Material (required) MATNR O R
Requirement date BDTER M R
Sum Period PER_DAY M V

PER_WEEK
PER_MONTH
PER_PERIOD
1.12.2.2 Key Figures
(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.)
Calculation
Se Colum Business Format Cell
BMC Measure Name / Column Unit or or
q n or Measure / Behaviour
Description Currency restriction Scale
Nu Row Catalogue Decimal e.g. Zero
(BMC) ID Type required?
m (C/R) Places Suppression
(Y/N)
1.12.2.3 Calculations / Formulas (Columns)
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.
Calculation Format /
Seq (C) or Required Calculation and Source Fields Calculation
Calculated Field Description Decimal Scale
Num Restriction (BMC ID) / Required Restriction Variable Places
(R)
Page 13/26
1.12.2.4
Page 14/26
1.12.2.5 Master Data / Characteristics
(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
Specific time Cell

Key &
scenario for Attribute Behaviour:
Description Filter on: Total SAP table
Seq relationships Navigati SAP Name within the source Display
Report Row (B), Key Only Specific Value (T) or and source
Nu between on (N) / system repeated
(Characteristic) Title (K), or or Variable Subtot field technical
m characteristics Display (Characteristic) Char.
Description Option al (S) name
(current or (D) Values
Only (D)
historical) (Y/N)
1 Semi-finished Product C B N T Material number MDRS- Y
MATNR
2 Batch number semi-finished product C K N Batch number MDRS-

CHARG
3 Sister Product C B N Material number MDRS- Y

BAUGR
4 Premix C K D -- Y
Page 15/26
Specific time Cell

Key &
Report Row (B), Key Only Specific Value (T) or and source
Only (D)
historical) (Y/N)
Column Definition
Specific time Cell

Key &
Report Column (B), Key Only Specific Value (T) or and source
Only (D)
historical) (Y/N)
1 MRP Controller C K D MRP Controller MARC- Y
DISPO
2 Requirement Date C K D Requirement Date MDRS- Y

BDTER
3 Order number C K D Order number MDRS- Y

AUFNR
Planned order number
MDRS-
PLNUM
4 Order quantity Semi C K D Target quantity AFKO- Y

GAMNG
Planned order quantity
PLAF-
GSMNG
Page 16/26
Specific time Cell

Key &
Report Column (B), Key Only Specific Value (T) or and source
Only (D)
historical) (Y/N)
5 Required quantity in Semi UoM C K D Requirement quantity MDRS- Y
BDMNG
6 Semi UoM C K D Base unit of measure AFKO-

GMEIN
PLAF-MEINS
MDRS-
MEINS
7 Order quantity Sister product C D Target quantity AFKO- Y

GAMNG
Planned order quantity
PLAF-
GSMNG
8 Sister UoM C D Base unit of measure AFKO- Y

GMEIN
PLAF-MEINS
1.12.2.6 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.
Page 17/26
Specific time scenario for

Characteristic relationships between Key & Description, Key Limit to: specific value or variable
Description characteristics (current or Only, or Description Only option
historical)
1.12.2.7 Totals / Sub totals / Exceptions / Cumulative / Non Cumulative
Seq Row Calculate Result as

Subtotal Total
Num Description
1 Semi-finished T Sum the required quantity in Semi UoM for
Product each semi-finished product
Page 18/26
1.12.3 Report Layout and/or Example
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 Required Order

number of Order quantity quantity
Semi-finished semi-finished Sister Pre- MRP Order quantity in Semi Semi Sister Sister
Product product product mix Material Description Contr. Date number Semi UoM UoM product UoM
63 3087TE012 NEOMAT GMS 001 10/01 1000203 480 kg
63 3087TE012 57 NEOMAT GMS BULK 003 10/02 1000226 48 kg 48 kg
63 3087TE012 59 NEOMAT GMS CAN 20 L 001 10/03 7842 80 kg 80 kg
63 6447TE003 NEOMAT GMS 001 10/05 7847 960 kg
Sum: 1440 1364 kg
904210 442TE005 * Horolith V 001 10/01 1000201 400 kg
904210 442TE005 207589 P3-HOROLITH V 24KG Can 001 10/01 1000224 48 kg 2 can
904210 442TE005 207590 P3-Horolith V, 250 kg drum 002 10/03 1000227 250 kg 250 kg
904210 442TE005 207589 P3-HOROLITH V 24KG Can 001 10/03 7840 72 kg 72 kg
904210 343TE023 * Horolith V 001 10/04 7845 800 kg
904210 343TE023 207599 P3-Horolith V, Bulk 001 10/05 7851 150 kg 150 kg
904210 343TE023 207590 P3-Horolith V, 250 kg drum 002 10/05 7912 500 kg 500 kg
904210 343TE023 207589 P3-HOROLITH V 24KG Can 001 10/06 7915 72 kg 72 kg
Sum: 1200 1092 kg
Example:
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-
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.
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.
Threshold:
We have a process order over 480 kg for the 10/01 of semi-finished 63. Against this quantity we have
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.
Page 19/26
1.13 TEST PLANS

Functional Test Plan: Document the criteria to be used for testing numerous cases with a description of
Each scenario, data to be used and positive/negative results
1.13.1 Unit Test Plan
1.13.2 Integration Test Plan (To be added in Realization Phase)
1.14 FUNCTIONAL SPECIFICATION APPROVAL
Functional Specification Approval:
Signature Date
Process/Workstream Approval
Technical Approval
2 TECHNICAL SPECIFICATION
2.1 PROGRAM INFORMATION

TECHNICAL SECTION:
2.1.1 Program Information
Program Name
What SAP
transaction(s) do the
interface/ conversion
involve?
Menu path for
transaction(s)
Report Transaction
Page 20/26
Select Options Field Name Default
Parameters Field Name Default
2.1.2 Program Flow
Page 21/26
2.1.3 Error Handling
File Type Name

Inbound
Intermediate
Outbound
Data Volume: 9999 records Date test data to be

available:
Only for Interfaces:
1. Type of interface
2. Direction of interface:
3. Frequency: ( ) Real-Time ( ) Batch
( ) Inbound ( ) Outbound ( ) Both
( ) Daily ( ) Weekly ( ) Monthly
( ) Other: _______________________
Only for Reports:
The report will be created via: ( ) Report Painter ( ) Report Writer ( ) ALV
( ) ABAP Program ( ) Info System ( ) SAPscript
( ) Other: _______________________ ( ) Smartform
2.2 PROGRAM STRUCTURE

Program Structure and processing (pseudo-code if required)
Data Mapping, Conversion and Validation:
Page 22/26
(Attach a excel spreadsheet with how to map data between different systems. Include conversion and
validation rules. The Excel mapping template is: TBD )
2.3 SAP SCRIPT FORMS
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)
Standard Text Added:
2.4 ENHANCEMENTS
Enhancements: (This section to be deleted if request does not belong to this classification)
Enhancement Project Name:
Name and type of SAP Exits/Objects that need to be enhanced:
2.5 MODIFICATION
Modification: (This section to be deleted if request does not belong to this classification)
Page 23/26
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)
2.6 CUSTOM DEVELOPMENT

Custom Development: (This section to be deleted if request does not belong to this classification)
Describe new tables, structures, domains, data elements, and changes to the existing data dictionary objects. For existing
tables and structures, all new fields are to be inserted at the end of the table. If a new data element or domain is used, it
should be defined separately in this part
2.6.1 Existing Tables and Structures
Table /Structure Data Element Domain Description

Field Name
2.6.2 New Tables and Structures

Table: Expected Size:
Table/Structure Data Element Domain Description Key Field
Field Name
2.6.3 New Domains

Domain Description Data Type/ Output Lower Check
Name Length Length Case Table
Page 24/26
2.6.4 New Data Elements

Data Element Description Domain Parameter Field
Name ID Labels
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
No. Name Push Button, Text Masks Values and on
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)
2.7 TECHNICAL SPECIFICATION APPROVAL
Technical Specification Approval:
Signature Date
Technical Approval
Page 25/26
Process/Workstream Approval
Page 26/26

Unctional AND Echnical Pecification

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Unctional AND Echnical Pecification

Загружено:

Авторское право:

Доступные форматы

FUNCTIONAL AND TECHNICAL SPECIFICATION

Prepared by: Production team Last Modification Date: 12/8/2021

PURPOSE OF DOCUMENT AND INSTRUCTIONS

1.1 REQUEST ADMINISTRATION

1.2 CHANGE HISTORY

1.3 PRIORITY AND COMPLEXITY

Program ( ) Conversion ( ) Interface ( X ) ABAP Report ( ) User Exit ( ) Form

1.4 ALTERNATIVE SOLUTIONS

Impact of not creating the ( ) legal requirements will not be fulfilled

1.5 EFFORT ESTIMATE

Technical Estimate Planning Estimate Revised Estimate

Functional Spec Review / QC 2 days__ 2 days _________

1.6 INITIAL DEVELOPMENT APPROVAL

Initial Development Approval:

1.7 FINAL DEVELOPMENT APPROVAL

Final Development Approval: (upon successful completion of functional unit test)

Assumptions: List assumptions that will be used in the document

1.9 LEGACY SYSTEMS

1.10 BUSINESS REQUIREMENTS

1.10.1 Business Driver (Purpose):

1.10.2 Detailed Development Requirements Description:

Sum Period: Day

2) Selection via semi-finished materials

2nd Review RM BPD_M-080_070628_V10-Final_HHA.doc

1.10.4 Control / Audit Processing Requirements:

1.10.5 General Processing Requirements

1.10.6 Authorization Requirements

For Reports only:

User Group or User Role:___________________________________________________

User Group or User Role:___________________________________________________

User Group or User Role:___________________________________________________

1.10.7 Business Process Flow Diagram

1.10.8 Technical Flow Diagram/Example ( if applicable)

1.10.9 Selection Screen Requirements ( if applicable)

1.11 INTERFACE / CONVERSION REQUIREMENTS

Name of Interface or Conversion:

1.11.2 Dependencies/Prerequisites (Translation Rules)

1.11.3 Are there any additional Training impacts?

1.12 REPORT SPECIFICATION

Report Access / Format

Online Reporting: Requires a SAP online connection

Offline Reporting: No SAP Connection available

Format required (Y/N) Amount of expected users for

Frequency (What is the broadcast frequency?)

Report Properties Property Description

1.12.2 Data Fields

1.12.2.1 Selection Criteria

(Report Prompts at run time, include a mock-up if possible)

MRP Controller DISPO O V

Material (requiring) BAUGR O R

Material (required) MATNR O R

Requirement date BDTER M R

Sum Period PER_DAY M V

1.12.2.2 Key Figures

1.12.2.3 Calculations / Formulas (Columns)

1.12.2.5 Master Data / Characteristics

Specific time Cell

2 Batch number semi-finished product C K N Batch number MDRS-

3 Sister Product C B N Material number MDRS- Y

Specific time Cell

Specific time Cell

2 Requirement Date C K D Requirement Date MDRS- Y

Functional Spec Review / QC 2 days 2 days _______