CR20110431

ZCM26 Functional Specification

Functional Specification - Report Scheduled Lines Overview - Purchasing

Document Reference: Version: Document Status:

Bway RDD ZCM26 Report 1.0

Draft

Author:

Peter Pope

Last Revision Date: Date Created: Date Printed:

11-JUL-2011 11-JUL-2011 11-JUL-2011

CR20110431

ZCM26 Functional Specification

Document Control
Business Area GAP ID FS Definition Form ID SAP R/3 Version Global / Market ECC 6.0

DTS MM/PP

Approval and Distribution

Approved by Process Team Lead Development team Lead Name Rick Seskauskas Peter Pope Role Signature Date

Document History
Version 1.0 1.1 1.2 1.3 Reason for change New Date 7/11/11

CR20110431

ZCM26 Functional Specification

Table of Contents
1. 2. 3. 4. 5. 6. 7. GENERAL INFORMATION .......................................................................................................... 4 BUSINESS NEEDS & REQUIREMENTS ........................................................................................ 5 ISSUES ................................................................................................................................... 5 SELECTION SCREEN DETAILS .................................................................................................. 5 CURRENT FUNCTIONALITY ....................................................................................................... 6 DESIRED FUNCTIONALITY ........................................................................................................ 7 TECHNICAL DETAILS ................................................................................................................ 7 7.1.EXTRACT DATA RELATIONSHIP DIAGRAM ....................... ERROR! BOOKMARK NOT DEFINED. 8. STARTING CONDITIONS ......................................................................................................... 14 9. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS ............................................................. 14 10. DATA MAPPING TABLES......................................................................................................... 14 10.1. DESIRED REPORT DESIGN/LAYOUT: .............................................................................. 15 10.2. REPORT EXAMPLE: ....................................................... ERROR! BOOKMARK NOT DEFINED. 11. CUSTOM TABLES/STRUCTURE IN SAP .................................................................................... 18 12. RECOVERY AND RESTART ..................................................................................................... 18 13. LANGUAGE OF TEXTS ............................................................................................................ 19 14. CURRENCY AND UNITS OF MEASURE ...................................................................................... 19 15. ASSUMPTIONS ...................................................................................................................... 19 16. ERROR HANDLING ................................................................................................................. 19 17. TESTING SCENARIOS............................................................................................................. 19

CR20110431

ZCM26 Functional Specification

General Information
Area (SAP System components): Short description: Requested by: Author: Program Transaction code: Task ID/Demand Number: Project Name: Priority: Complexity: Volume of data: Mode: Frequency: Technical information: Report created using: High/mandatory Medium/recommended Low/optional High Medium various DATE AVAILABLE FROM: Online Background Daily Weekly Monthly Others (Specify) : as needed Report Painter ABAP program R/3 Report Writer Info system BW MM ZCM26 Report Mike McClure Peter Pope ZCM26 Date: Tel no: Tel no: 7/11/11 630-203-4095 708-799-2013

Low

Biweekly

SAP Query Crystal Reports

Characteristics required:

General information: Results if no Reports are created:

DURATION OF DEVELOPMENT WORK

Drilldown Buttons Sort ALV Grid ALV List Entry file Others: Call Transaction Legal requirements not fulfilled Lack of essential business information Lack of functions compared to legacy system Others (Specify): TBD Yes No

(IN MAN-DAYS):

Is there an alternative in the standard system? Description of alternative: Reasons why alternative is not acceptable:

Performance problems Others (Specify) :

Complexity

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 TABLE-FIELD TABLE-FIELD TABLE-FIELD TABLE-FIELD TABLE-FIELD TABLE-FIELD Parameter (P) / Select-option (S) S S S S S S Comments (Range, Single/Multiple selection, Patterns, Mandatory etc.) RANGE, MANDATORY RANGE, MANDATORY RANGE RANGE RANGE RANGE, MANDATORY Default Value

MATERIAL MARA-MATNR
PLANT T001W-WERKS MRP CONTROLLER MARC-DISPO MATERIAL GROUPS MARA-MATKL

N/A N/A N/A N/A N/A N/A

VENDOR LFA1-LIFNR
DATE RANGE

CR20110431

ZCM26 Functional Specification

Name

Table-Field / Check Box / Radio Button with group

Parameter (P) / Select-option (S)

PRODUCTION ORDER STATUS: PRODUCTION ORDER PROD ORD LINK TO SALES ORD O PLANNED ORDER STATUS: PLANNED ORDER PLANNED ORD LINKED TO SALES ORD O DISPLAY QTY IN: DEFAULT UOM BASE BOX O SHORT TONS O RADIO BUTTON P

Comments (Range, Single/Multiple selection, Patterns, Mandatory etc.) Choose between all production orders (Default), or only those linked to sales order

Default Value

X for Production Order

RADIO BUTTON

Choose between all planned orders (Default), or only linked to sales order

X is default for Planned Order

Choose between UOMs RADIO BUTTON P

X is the Defaulted UOM

Desired screen design (selection possibilities):

MATERIAL PLANT VENDOR MRP CONTROLLER INCLUDING PURCHASING MATERIAL GROUPS INCLUDING PURCHASING PRODUCTION ORDER STATUS: Choose between all production orders
(Default), or only linked to sales order PLANNED ORDER STATUS: Choose between all planned orders (Default), or only linked to sales order

DATE RANGE DETAIL, WEEKLY ROLL UP, MONTHLY ROLL UP SELECTION CRITERIA OPTION 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

OVERVIEW
1. First, get the requirements using:
MD_STOCK_REQUIREMENTS_LIST_API
*" *" *" *" *" *" *" *" IMPORTING VALUE(PLSCN) VALUE(MATNR) VALUE(WERKS) VALUE(BERID) VALUE(ERGBZ) VALUE(AFIBZ) VALUE(INPER) LIKE LIKE LIKE LIKE LIKE LIKE LIKE PLSC-PLSCN MARC-MATNR MARC-WERKS MDLV-BERID T462-ERGBZ T463-AFIBZ MDST-INPER OPTIONAL

OPTIONAL OPTIONAL OPTIONAL OPTIONAL

CR20110431

ZCM26 Functional Specification

*" *" *" *" *" *" *" *" *" *" *" *" *" *" *" *" *" *"

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 p_werks

CR20110431

ZCM26 Functional Specification

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 1
Validate 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 DELKZ MNG01 DELNR DEL12 BAAR DELPS DELET Date (Delivery/Finish) MRP Element Code Qty Order # MRP data MRP data Order Item Schedulingnumber

CR20110431

ZCM26 Functional Specification

MATKL AUFNR POSVR KDAUF KDPOS EBELN EBELP MPNMT EKGRP

Material Group Source Order Source Order Item Sales Order Sales Order Item PO Doc PO Doc Item Material # Purchasing Group

Structure MDEZX SORT0 DAT01 DELKZ DELB0 EXTRA MNG01 PLUMI MPNMT WRK02 LIFNR Date (sort) Date (print) MRP Elem Code MRP Elem MRP Elem data Qty Sign (if + add, if subtract) Material Plant Vendor

CR20110431

ZCM26 Functional Specification

Structure MDSUX DELKZ MNG01 MNG02 MNG03 MDBES MRP Elem Code PIR Qty Requirements Qty Receipts Qty Minimum Stock Qty

Step 3
First, 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 EDELNR EMATNR EWERKS From: MDEZX-DELKZ, MRP Element Code MDEZX-EXTRA, Order Number Selection screen Material Number 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 Details

n/a

Data Mapping Tables

CR20110431

ZCM26 Functional Specification

Desired Report Design/Layout:

The report should be in the following sequence: Plant Material Required 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 EXAMPLE
Output DETAIL REQMT SOURCE MRP Element Ind. Desc. IMDRQXDELKZ, then V457TDELB1 REQMT SOURCE MRP Element Data Desc Orders to be Placed / Firmed Orders Due Date / Required Date Demand Due Date / Required Date Deliver y/ Receivi ng Plant

Plant

Item number

Item Descript

MRP Element MDEZXPLUMI = +, THEN MDEZXDELB0

On Hand Inventory

Expected Safety Stk

Firm Orders Placed IF PLAFAUFFX = X, then MDPSXMNG01

Demand QTY

STO and PO #

Net available Inventory MDPSXMNG01 (minus) MARCEISBE (3,000)

Custom

MDEZ

T001WWERKS Memphis

kkkk MARAMATNR 1016299

MARAMAKTL OA GAL TOP F 112 PLN

IMDRQXEXTRA

MDPSXMNG01 5000

MARCEISBE 8000

MDPSXMNG01

PLAFAUFFX = BLANK

MDEZX -EXTRA up to slash

MDPSXUMDAT/ UMDA2/ DAT01

MDPSXUMDAT/ UMDA2/ DAT01

Pl Ord

Production Order Safety Stock Production Order Sales Order Production Order Sales Order Forecast Forecast

0000708162/ 000040/0001 Safety Stock 0000708162/ 000040/0001 0000707484/ 000040/0001 0000708162/ 000040/0001 0000706885/ 000020/0001 Forecast Forecast

3000

6/7/2011

Pl Ord Pl Ord

3000 2000 6/10/2011

6/8/2011

Con Rel

2000

6/11/2011

3140

NORTH

Pl Ord

1000

6/14/2011

Pch Ord

1000

6/15/2011

Pr Rq Rel Dep Req

3000 3000

7/5/2011 7/6/2011

23450 3140

IND. CA

CR20110431

ZCM26 Functional Specification

Output

<Document #>

<XXXXX> Functional Specification

<Project Logo>

Custom Tables/Structure in SAP

Table Name Short text Size category Table maintenance allowed Data class Buffering Table maintenance generator Authorization Group Field Data Element Domain Type Name

Length Check TableField

Key Field

Foreign Key

Description

Comments

Recovery and Restart

Simply rerun job.

<Document #>

<XXXXX> Functional Specification

<Project Logo>

Language of texts
English

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 Description 1 2 3 4 Exception - special logic or exceptions (e.g. report shold exclude certain specific condition) 5 6 Error Handling - functionality in case of errors (e.g. Error Message or Error Log )

<Document #>

<XXXXX> Functional Specification

<Project Logo>