Download - Bway Rdd Zcm26 Report v1.0
CR20110431 ZCM26 Functional Specification
Functional Specification - ReportScheduled Lines Overview - Purchasing
Document Reference: Bway RDD ZCM26 ReportVersion: 1.0
Document Status: Draft
Author: Peter Pope
Last Revision Date: 11-JUL-2011Date Created: 11-JUL-2011Date Printed: 11-JUL-2011
CR20110431 ZCM26 Functional Specification
Document Control
Business Area DTS MM/PP
GAP ID
FS Definition Form ID
SAP R/3 Version ECC 6.0
Global / Market
Approval and Distribution
Approved by Name Role Signature DateProcess Team Lead
Rick Seskauskas
Development team Lead
Peter Pope
Document History
Version Reason for change Date1.0 New 7/11/111.11.21.3
CR20110431 ZCM26 Functional Specification
Table of Contents
1. GENERAL INFORMATION.............................................................................................................52. BUSINESS NEEDS & REQUIREMENTS..........................................................................................73. ISSUES......................................................................................................................................74. SELECTION SCREEN DETAILS.....................................................................................................75. CURRENT FUNCTIONALITY..........................................................................................................86. DESIRED FUNCTIONALITY...........................................................................................................97. TECHNICAL DETAILS...................................................................................................................9
7.1.EXTRACT DATA RELATIONSHIP DIAGRAM.........................ERROR! BOOKMARK NOT DEFINED.8. STARTING CONDITIONS............................................................................................................199. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS................................................................1910. DATA MAPPING TABLES...........................................................................................................19
10.1. DESIRED REPORT DESIGN/LAYOUT:.................................................................................2010.2. REPORT EXAMPLE:.........................................................ERROR! BOOKMARK NOT DEFINED.
11. CUSTOM TABLES/STRUCTURE IN SAP......................................................................................2312. RECOVERY AND RESTART........................................................................................................2313. LANGUAGE OF TEXTS...............................................................................................................2314. CURRENCY AND UNITS OF MEASURE........................................................................................2315. ASSUMPTIONS..........................................................................................................................2416. ERROR HANDLING....................................................................................................................2417. TESTING SCENARIOS................................................................................................................24
CR20110431 ZCM26 Functional Specification
General Information
Area (SAP System components): MM Date: 7/11/11
Short description: ZCM26 Report
Requested by: Mike McClure Tel no: 630-203-4095
Author: Peter Pope Tel no: 708-799-2013
Program Transaction code: ZCM26
Task ID/Demand Number:
Project Name:
Priority: High/mandatory Medium/recommended
Low/optional
Complexity: High Medium Low
Volume of data: various DATE AVAILABLE FROM:
Mode: Online Background
Frequency: Daily Weekly Monthly Biweekly Others (Specify) : as needed
Technical information:
Report created using:
Characteristics required:
Report Painter Report Writer SAP Query ABAP program Info system R/3 BW Crystal Reports
Drilldown Buttons Sort ALV Grid ALV List Entry file Others: Call Transaction
General information:
Results if no Reports are created:
Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify):
DURATION OF DEVELOPMENT WORK
(IN MAN-DAYS):TBD
Is there an alternative in the standard system?
Yes No
Description of alternative:
Reasons why alternative is not acceptable:
Performance problems Complexity Others (Specify) :
CR20110431 ZCM26 Functional Specification
Business Needs & Requirements
Buyers need to be able to see the demand generated in SAP MRP separated from the Sales Forecast. Without this option there is considerable concern additional slow & obsolete inventory could be generated. In addition, the current MD04 view only shows one material at a time, which is an extremely slow process when reviewing MRP. The Buyer would have to drill down to gather all data for each individual item. The need is to get these details at a single glance.
Issues
none
Issue #
Issue owner
Date Raised
Issue Description Issue Resolution Resolved By & Date
Selection Screen Details
Name Table-Field / Check Box /
Radio Button – with group
Parameter (P) / Select-option
(S)
Comments (Range, Single/Multiple
selection, Patterns, Mandatory etc.)
Default Value
MATERIALMARA-MATNR
TABLE-FIELD SRANGE, MANDATORY
N/A
PLANTT001W-WERKS
TABLE-FIELD S RANGE, MANDATORY N/A
MRP CONTROLLERMARC-DISPO
TABLE-FIELD S RANGE N/A
MATERIAL GROUPSMARA-MATKL
TABLE-FIELD S RANGE N/A
VENDORLFA1-LIFNR
TABLE-FIELD SRANGE N/A
DATE RANGE TABLE-FIELD S RANGE, MANDATORY N/A
CR20110431 ZCM26 Functional Specification
Name Table-Field / Check Box /
Radio Button – with group
Parameter (P) / Select-option
(S)
Comments (Range, Single/Multiple
selection, Patterns, Mandatory etc.)
Default Value
PRODUCTION ORDER STATUS:
PRODUCTION ORDER ●PROD ORD LINK TO SALES ORD O
RADIO BUTTON P
Choose between all production orders
(Default), or only those linked to sales order
X for Production
Order
PLANNED ORDER STATUS:
PLANNED ORDER●PLANNED ORD LINKED TO SALES ORD O
RADIO BUTTON P
Choose between all planned orders
(Default), or only linked to sales order
X is default for Planned Order
DISPLAY QTY IN:
DEFAULT UOM ●BASE BOX OSHORT TONS O
RADIO BUTTON P
Choose between UOMs X is the Defaulted
UOM
Desired screen design (selection possibilities):
MATERIALPLANTVENDORMRP CONTROLLER INCLUDING PURCHASINGMATERIAL GROUPS INCLUDING PURCHASING
PRODUCTION ORDER STATUS: Choose between all production orders (Default), or only linked to sales orderPLANNED ORDER STATUS: Choose between all planned orders (Default), or only linked to sales order
DATE RANGE DETAIL, WEEKLY ROLL UP, MONTHLY ROLL UP SELECTION CRITERIAOPTION FOR BASE BOX OR SHORT TONS
Current Functionality
CR20110431 ZCM26 Functional Specification
Buyers currently see the demand generated in SAP MRP with the Sales Forecast, which causes considerable concern that additional slow & obsolete inventory could be generated. MD04 allows view of only a single material at a time, which causes delays when the need is for multiple materials at a time.
Desired Functionality
Buyers need to be able to see the demand generated in SAP MRP separated from the Sales Forecast. Without this option there is considerable concern additional slow & obsolete inventory could be generated. In addition, the current MD04 view only shows one material at a time, which is an extremely slow process when reviewing MRP. The Buyer would have to drill down to gather all data for each individual item.
A report ZCM25 was created for DTS already for the same reasons. PTP needs the same report copied (ZCM26), but having the report include MRP Controllers and create Purch Reqs vs. Planned Orders.
Technical Details
Need to provide Material, Plant and Date as mandatory fields.
Fields required are similar to those displayed in standard SAP transaction MD04, which displays data for a single material at a time and without a Date limitation. The desired functionality of ZCM26 is to display multiple materials at a time for a selected date range.
Call function module MD_STOCK_REQUIREMENTS_LIST_API to gather requirement data
Call function module MD_PEGGING_NODIALOG to gather the source of the requirements.
BAPI_REQUIREMENTS_GETDETAIL
BAPI_MATERIAL_STOCK_REQ_LIST
OVERVIEW1. First, get the requirements using:
MD_STOCK_REQUIREMENTS_LIST_API
*" IMPORTING*" VALUE(PLSCN) LIKE PLSC-PLSCN OPTIONAL*" VALUE(MATNR) LIKE MARC-MATNR*" VALUE(WERKS) LIKE MARC-WERKS*" VALUE(BERID) LIKE MDLV-BERID OPTIONAL*" VALUE(ERGBZ) LIKE T462-ERGBZ OPTIONAL*" VALUE(AFIBZ) LIKE T463-AFIBZ OPTIONAL
CR20110431 ZCM26 Functional Specification
*" VALUE(INPER) LIKE MDST-INPER OPTIONAL*" VALUE(DISPLAY_LIST_MDPSX) TYPE CHAR1 OPTIONAL*" VALUE(DISPLAY_LIST_MDEZX) TYPE CHAR1 OPTIONAL*" VALUE(DISPLAY_LIST_MDSUX) TYPE CHAR1 OPTIONAL*" VALUE(NOBUF) TYPE CHAR1 OPTIONAL*" VALUE(PLAUF) TYPE CM61X-PLAUF OPTIONAL*" EXPORTING*" VALUE(E_MT61D) TYPE MT61D*" VALUE(E_MDKP) TYPE MDKP*" VALUE(E_CM61M) TYPE CM61M*" VALUE(E_MDSTA) TYPE MDSTA*" VALUE(E_ERGBZ) TYPE SFILT-ERGBZ*" TABLES*" MDPSX STRUCTURE MDPS OPTIONAL*" MDEZX STRUCTURE MDEZ OPTIONAL*" MDSUX STRUCTURE MDSU OPTIONAL*" EXCEPTIONS*" MATERIAL_PLANT_NOT_FOUND*" PLANT_NOT_FOUND
Returns table data:
MDPS – Item in MRP Document
MDEZ – Individual Lines of MRP Elements
MDSU – Total Lines for MRP Elements
MRP Element Code List (MDEZ-DELKZ)
2. Next, get the source of the requirements using:
MD_PEGGING_NODIALOG sample
data: begin of mdrqx occurs 50. include structure mdrq.data: end of mdrqx. parameters: p_matnr type mara-matnr, p_werks type marc-werks, " Planning Plant p_aufnr type aufk-aufnr. data: werks type marc-werks.data: matnr type mara-matnr.data: delnr type mdps-del12. perform prod_order using P_matnr
CR20110431 ZCM26 Functional Specification
p_werks p_aufnr. ********************************************************************** PROD_ORDER*********************************************************************form prod_order using matnr werks aufnr. * edelkz = 'FE' -- Production Order* edelkz = 'PA' -- Planned Order call function 'MD_PEGGING_NODIALOG' exporting edelet = 0000 edelkz = 'FE' edelnr = aufnr edelps = 000001 ematnr = matnr ewerks = werks tables imdrqx = mdrqx exceptions error = 1 no_requirements_found = 2 order_not_found = 3 others = 4. loop at mdrqx where DELKZ = 'VC'. " VC is sales order write:/ mdrqx-DELKZ, mdrqx-matnr, mdrqx-planr+0(10), mdrqx-planr+10(6) . endloop.
LOGIC FLOW
Step 1Validate selection screen MATNR and WERKS
If MRP Controller selected, then search MARC to limit by DISPO for the MATNR and WERK.
Step 2
LOOP on selected MATNR and WERKS
CR20110431 ZCM26 Functional Specification
Call MD_STOCK_REQUIREMENTS_LIST_API
***********( CHECK FOR PERFORMANCE EFFICIENCIES )******************
Sending:
Selection screen MATNR
Selection screen WERKS
Returning:
Structure MDPSX
DAT02 Date (Delivery/Finish)
DELKZ MRP Element Code
MNG01 Qty
DELNR Order #
DEL12 MRP data
BAAR MRP data
DELPS Order Item
DELET Schedulingnumber
CR20110431 ZCM26 Functional Specification
MATKL Material Group
AUFNR Source Order
POSVR Source Order Item
KDAUF Sales Order
KDPOS Sales Order Item
EBELN PO Doc
EBELP PO Doc Item
MPNMT Material #
EKGRP Purchasing Group
Structure MDEZX
SORT0 Date (sort)
DAT01 Date (print)
DELKZ MRP Elem Code
DELB0 MRP Elem
EXTRA MRP Elem data
MNG01 Qty
PLUMI Sign (if + add, if – subtract)
MPNMT Material
WRK02 Plant
LIFNR Vendor
CR20110431 ZCM26 Functional Specification
Structure MDSUX
DELKZ MRP Elem Code
MNG01 PIR Qty
MNG02 Requirements Qty
MNG03 Receipts Qty
MDBES Minimum Stock Qty
Step 3First, SAVE “Stock-on-hand” where MDEZX-DELKZ = WB, and
“Safety-Stock” where MDEZX-DELKZ = SH
Step 4 Limit returned data by selection screen options:Limit returned MDEZX by DATE-RANGE from selection screen
Comparing MDEZX-SORT0
If VENDOR selected, then limit by MDEZX-LIFNR
If MRP GROUP selected, then limit by MDPSX-MATKL.
Step 5 “GET SOURCE OF REQUIREMENTS”
LOOP AT MDEZX
where PLUMI = “+”
Call MD_PEGGING_NODIALOG
CR20110431 ZCM26 Functional Specification
Sending:
EDELKZ From: MDEZX-DELKZ, MRP Element Code
EDELNR MDEZX-EXTRA, Order Number
EMATNR Selection screen Material Number
EWERKS Selection screen Plant
Returning:
EMDPSX
IMDRQX
DELNR
DELPS
DELET
DELKZ
MATNR
WERKS
DAT00
MNG01
MNG02
Fill ALV report line
LOOP BACK to GET next MRP Element
ENDLOOP on MDEZX (STEP 5)
CR20110431 ZCM26 Functional Specification
ENDLOOP on MATNR and WERKS (STEP 2)
Starting Conditions
Report is run per user request with transaction ZCM26. Probably should be run in background to prevent timeouts..
Security Requirements/ Authorization Detailsn/a
Data Mapping Tables
CR20110431 ZCM26 Functional Specification
Desired Report Design/Layout:
The report should be in the following sequence:PlantMaterialRequired date
The report is to show all DEMAND sources by Plant, Material and Required Date, along with its associated SUPPLY sources. For example, a Scheduling Agreement DEMAND might be SUPPLIED by a Planned Order, and a Sales Order DEMAND might be SUPPLIED by a Purchase Order. These associations would need to be displayed on the same line, as shown in the below format, and formatted as ALV for effective spreadsheet download.
Also, displayed below.
CR20110431 ZCM26 Functional Specification
REPORT EXAMPLEOutput DETAIL
PlantItem number
Item Descript
MRP Element
REQMTSOURCEMRP Element Ind. Desc.
REQMTSOURCEMRP Element Data Desc
On Hand Inventory
Expected Safety Stk
Firm Orders Placed
Demand QTY
Orders to be Placed/ Firmed
STO andPO #
Orders Due Date / Required Date
Demand Due Date / Required Date
Net available Inventory
Delivery /
Receiving
Plant
Customer
T001W-WERKS
kkkkMARA-MATNR
MARA-MAKTL
MDEZX-PLUMI = +, THENMDEZX-DELB0
IMDRQX-DELKZ, thenV457T-DELB1
IMDRQX-EXTRA
MDPSX-MNG01
MARC-EISBE
IF PLAF-AUFFX = X, thenMDPSX-MNG01
MDPSX-MNG01
PLAF-AUFFX = BLANK
MDEZX-EXTRA up to slash
MDPSX-UMDAT/UMDA2/DAT01
MDPSX-UMDAT/UMDA2/DAT01
MDPSX-MNG01 (minus) MARC-EISBE
MDEZX-MD4KD
Memphis
1016299
OA GAL TOP F 112 PLN
5000 8000 (3,000)
Pl Ord Production Order
0000708162/000040/0001
3000 6/7/2011
Pl Ord Safety Stock
Safety Stock 3000 6/8/2011
Pl Ord Production Order
0000708162/000040/0001
2000 6/10/2011
Con Rel Sales Order
0000707484/000040/0001
2000 6/11/2011 3140 NORTH PAK
Pl Ord Production Order
0000708162/000040/0001
1000 6/14/2011
Pch Ord Sales Order
0000706885/000020/0001
1000 6/15/2011
Pr Rq Rel Forecast Forecast 3000 7/5/2011 23450 IND. CAN Dep Req Forecast Forecast 3000 7/6/2011 3140
CR20110431 ZCM26 Functional Specification
Output
<Document #> <XXXXX> Functional Specification<Project
Logo>
Custom Tables/Structure in SAP
Table NameShort textSize categoryTable maintenance allowedData classBufferingTable maintenance generatorAuthorization GroupField Name
Data Element Domain Type Length Check Table-Field
Key Field
Foreign Key
Description
Comments
Recovery and Restart
Simply rerun job.
<Document #> <XXXXX> Functional Specification<Project
Logo>
Language of textsEnglish
Currency and Units of Measure
OPTION FOR BASE BOX OR SHORT TONS
Assumptions
Error Handling
Testing Scenarios
Normal Functionality - test cases that ensure the report functions as it should. ID Description1234Exception - special logic or exceptions (e.g. report shold exclude certain specific condition)
56Error Handling - functionality in case of errors (e.g. Error Message or Error Log )
<Document #> <XXXXX> Functional Specification<Project
Logo>
7
8