Forms and Reports Functional Specification for Excess and Zero Demand Update

Forms and Reports Functional
Specification

Business Transformation Phase 2B Page 1 of 20
Forms & Reports Functional
Specification

Excess and Zero demand Update Program

VERSION: 1.0
LAST UPDATED: 07/12/2013

DOCUMENT CONTROL:

REVISION HISTORY:

Version # Date Modified Modified By Brief Description of Change
1.0 07/12/2013 xxxxxxxxxxx Existing program ZMTGEOUPDATE needs to be
copied and further modification such as PIM
code, additional z tables and etc

APPROVALS:

Specification

Author xxxxxxxxxxxxx Date Created: 06/15/2013
Functional Team
Lead
xxxxxxxxxxxxxxx Signature and
Date Approved:

Business Process
Owner
xxxxxxxxxxxxxxx Signature and
Date Approved:

Technical Team Lead xxxxxxxxxxxx Signature and
Date Approved:

Project Manager xxxxxxxxxxxxxxx Signature and
Date Approved:

Specification

TABLE OF CONTENTS:

I. INTRODUCTION _______________________________________________________ 4
A. Purpose of the document _________________________________________ 4
B. Request Overview _______________________________________________ 4
II. OVERVIEW ___________________________________________________________ 5
A. Business Driver _________________________________________________ 5
B. Key business requirements ________________________________________ 5
C. High level Process overview _______________________________________ 5
III. DETAILS _____________________________________________________________ 6
A. Detail Processing Logic ___________________________________________ 6
B. Selection Screen _______________________________________________ 10
C. Report/Form Layout ____________________________________________ 11
D. Paper Requirements ____________________________________________ 11
E. Print Requirement ______________________________________________ 11
F. Special characteristics _____________________________________________ 11
G. Exception Handling Rules ________________________________________ 11
H. Special Requirements ___________________________________________ 11
I. Dependencies ___________________________________________________ 11
J. Constraints _____________________________________________________ 11
K. Scheduling Requirements ________________________________________ 12
L. Test Specification ________________________________________________ 12
1. Functional Test Scenarios _______________________________________ 12
2. Test Data & Other Needs _______________________________________ 12
3. Test System & Environment _____________________________________ 12
M. Audit Requirements/Integrity Controls ______________________________ 13
N. Security/Authorization Requirements _______________________________ 13
I V. TECHNI CAL SECTI ON ________________________________________________ 13
A. Object Type: __________________________________________________ 13
B. All Z Objects Information _________________________________________ 14
C. Detail Technical Specification _____________________________________ 14
D. Open Item / Issues Log / Proposed Solutions (keep all history) ___________ 20

Specification

I. INTRODUCTION
A. Purpose of the document
To calculate Excess and Zero demand based on demand forecast and on hand inventory, with applicable
Time & Reserve percentage.

B. Request Overview

1. Scenario ID:
2. Scenario Title:
3. Process ID:
4. Process Title:
5. Development Spec ID:
6. Name of Enhancement:
7. Short Description:

8. Type: ABAP Report Form Query
Other_________________
9. Tools used ABAP Program Report Painter Report Writer
Information System ALV SAP Script
Smartform Other
10. Data latency: Batch On-demand
11. Frequency: Annually Quarterly Monthly Weekly
Daily Other
12. Requesting Team: ____________________
13. Systems Impacted: R/3 CRM APO EBP BW SEM
Other____________
14. Modules Impacted: FI CO SD MM PP QM BW SEM
Other____________
15. Complexity High Medium Low
16. Spec Created on: 05/30/2013
17. Date required by: 07/01/2013
18. Created by: __xxxxxxxxxx_______ Phone:
19. Functional Analyst: __ xxxxxxxxxx _______ Phone:
20. Technical Analyst: _____________________________ Phone:
21. Business Owner: __xxxxxxxxxxx_______ Phone:

Specification

II. OVERVIEW
A. Business Driver
Inventories are stated at the lower of cost (first-in, first-out method) or market. On a quarterly basis,
Xxxxxxxx Semiconductor assesses the realizable value of all inventories to determine whether
adjustments for impairment are required. Inventory that is obsolete or in excess of forecasted usage is
written down to its estimated realizable value based on assumptions about future demand and market
conditions.

B. Key business requirements
System should be able calculate Excess and Zero demand based on demand forecast and on hand
inventory, with applicable Time & Reserve percentage.
System should consider demand and inventory of Xxxxxxxx inventory only. As after Xxxxxxxx integration
with YYYYYY Corp SAP, inventory will be comingled with Xxxxxxxx and AGS inventory.

C. High level Process overview
E&Z process overview

Specification

III. DETAILS

A. Detail Processing Logic

Step A : Xxxxxxxx program ZMTGEOUPDATE which is in Xxxxxxxx system, needs to be copied and
modified to meet YYYYYY requirements.

Step B : Create table ZMEOPLANT and ZMEOPERIOD which are in xxxxxxxx system

Step C : Below is the additional logic to be added in Program ZMTGEOUPDATE for Xxxxxxxx
migration project :

STEP 1 : In selection parameter, additional field PIM code(Production/Inspection memo) to be added.
As after migration project, both Xxxxxxxx and AGS inventory will be in comingled status. Therefore E&Z
calc program needs to pick only Xxxxxxxx material for further processing including inventory in AGS
plants(defined in selection parameter)

STEP 2 : Based on PIM code(MARA-FERTH) value defined in selection parameter, go to table MARA with
material from internal table of MDKP records( MRP header records) and update PIM code value against
line item of MDKP internal database. If PIM code field in selection parameter is blank, then get all records
including update respective value found in MARA ie blank, xxxxxxxx PIM, AGS PIM and etc.

STEP 3 : Results of this program are updated in two table ZMEOPLANT and ZMEOPERIOD. Additional field
for PIM value need to be added to the exist table ZMEOPLANT and ZMEROPERIOD. When results are
updated in these two tables, PIM value also needs to be updated which has been stored in internal table
of MDKP. Create new field name ZMEOPLANT- FERTH and ZMEOPERIOD- FERTH in respective tables for
PIM

STEP 4 : Historical usage (ZMEOPLANT-USAGE12) date calc changes : Currently program uses
last 12 month consumption excluding current month in program is run using table mver. For SSG,
business needs to calc historical usage including current quarter in which program has run and previous
last 4 quarters .ie last 4 quarters plus current quarter consumption.

STEP 5 : Time stamp field update in Table ZMEOPLANT and ZMEOPERIOD : Currently table
ZMEOPLANT and ZMEOPERIOD doesnt have time stamp when records are inserted. As records from
these tables will be extracted into BI for E&Z reporting, therefore as a best practice its better have time
stamp. Below are two fields to be added for time stamp. 1) Time stamp of record insert, 2) Time stamp
of records changes.

STEP 6 : Tcode ZMTGEOUPDATE to be created for program ZMTGEOUPDATE

=====================================================

Below is the existing logic of E&Z calc program ZMTGEOUPDATE.
Note : Logic is read by me (functional analyst) which will give overview of the program logic but
may not provide compressive details or its accuracy.

Specification


Get Plant Data :
From the plant entered in Selection parameter, get plant details from T001W.
Also get company code details using plants from T001K
Get fiscal year xxxxxxxxt from company code table from T001
Save the fiscal year xxxxxxxxt for the primary plant
Keep above data in internal table t_zmeot001

Get dates from various selections for (1) avg monthly MRP requirements and (2)
month range for consumption history :
(1) avg monthly MRP requirements - Current date (when program is run) to next 3 months
i.e., next 4 months.
(2) fiscal month range for consumption history - The month range is a 12 month period
ending with last fiscal month. (previous 12 months)
(3) Dates of 4 period buckets : Based on Start date of first E&O period field from selection
parameter, 4 period buckets are determined. Period 1 bucket, from first date of current
month(based on start date of first E&O period field) to next 12 months( 12 months
period picked from no. of months period field of table ZMEOPARMS) . Then period 2
bucket, from first day of 13 month to next 10 months(picked from table ZMEOPARMS)
and then period 3 bucket, from first of 23 months to next 14 months (picked from table
ZMEOPARMS based on period nbr)
Based on fiscal year xxxxxxxxt of primary plant(t_zmeot001) from step Get plant Data,
periods are calculated.

Get MRP Document headers :
1. If planning Scenario is blank in selection parameter then get MD (Type of MRP list) from
MDKP. i.e., if LTP is not run for demand forecasting. But if planning scenario is entered in
selection parameter then get data LP (Type of MRP list) from MDKP. Below data needs
to be collected for all LP or MD records :
Material Number MATNR, Plant(PLWRK), Planning Scenario of Long-Term
Planning(PLSCN), MRP date(DSDAT), Number of material requirements planning
table(DTNUM), Base Unit of Measure(MEINS), Safety Stock(EISBE), Aggregated MRP
list(CFLAG), MRP Type(DISMM), Message identification(MSGID), Message Type(MSGAR),
Message number(MSGNR),

2. Get all non-planning materials ( ND materials)
Based on material, plant in selection parameter and ND MRP type (MARC-dismm)
, records are pulled from material master data(MARC).
ND records collected are added into step 1 LTP run records ( MDKP records). If records
already exist then records is updated with MRP type ND, else record is added to MDKP records.
process_material_local
Get material and plant details :
Based on material and plant in MDKP, get additional fields from Material master, such Profit
center, MRP Controller (Materials Planner), Procurement Type, Special procurement type.
Standard cost update to MDKP records If plant is 0930, then get standard cost of material from
MBEW. Other plant, get Standard cost of material from material ledger tables ( ckmlhd/ ckmlcr).

Specification


For the MDKP records where MRP type is not ND( normal planning materials)
Based on Aggregated MRP list (mdkp-cflag) get MRP line items from mdtb
If Availability indicator (MDTB- vrfkz) is flagged, then process below
If Receipt/issue indicator((mdtb-plumi) = -( which means requirement), and
Receipt/requirements date(mdtb-dat00)falls between current date to Avg monthly MRP date ie
with 4 months, then keep in zmeoplant-avreq12 internal table.
Else ie other records are processed below
Based on MRP element (mdtb-delkz), records are selected into various category-
When 'WB'. "Plant stock = zmeoplant-onhnd
WHEN 'LB'. "Storage location stock= zmeoplant-onhnd
WHEN 'KB'. "Sales order stock = zmeoplant-onhnd
WHEN 'LK'. "Sub contract stock = zmeoplant-onhndlk
WHEN 'QM'. "QM stock = zmeoplant-onhndqm
WHEN 'BE'. "Purchase Order
Then with this PO go to EKPO to find out if Purchasing Document Type(ekko-
bsart) is 'ZG'("STOCK TRANSPORT PO ) or PO vendor ekko-lifnr is(from selection
parameter)"Internal vendor range = zmeoplant-onordipo
All other PO = zmeoplant-onordepo

WHEN 'BA'. "Purchase Requisition = zmeoplant-onordprq
WHEN 'FE'. "Production Order (SWO)= zmeoplant-onordswo
Get CO order balance ( using aufk and FM K_BALANCE_GET)

WHEN 'PA' "Planned Order
OR 'SA'. "Simulated Planned Order= zmeoplant-onordplo

WHEN 'SB' "(reduction of reqts)
OR 'SM'. "Simulated Reqts (reduction of reqts)
Then put qty in zmeoplant-avreq12(4 months avg MRP req)

Other MRP elements(unexpected MRP elements), show in separate message tab

If necessary, get the demand forecast and include it as additional requirements. This
only applies to materials with MRP type PE when using LTP data.

If MRP Type(mdkp-dismm ) is PE, then obtain these forecast based on selection
material & plant from ( FM MPOP_SINGLE_READ) and keep records in zmeoplant-
avreq12(4months avg MRP req)

Subtract and vendor consignment stock from the on-hand Obtain vendor consignment
stock from MARD and deduction from on hand inventory
zmeoplant-onhnd = zmeoplant-onhnd - consign_qty

Blocked stock to be added to On-hand inventory Get blocked stock for the plant when
in selection parameter and add to on hand inventory

* Compute the total on-hand
zmeoplant-totonhnd = zmeoplant-onhnd
+ zmeoplant-onhndkb
+ zmeoplant-onhndlk

Specification

+ zmeoplant-onhndqm
+ zmeoplant-onordipo
+ block_qty.

* Convert the sum of next 4 months MRP reqts to a 12 month basis
zmeoplant-avreq12 = zmeoplant-avreq12 * 3.

For the MDKP records where MRP type are ND( normal planning materials)
get_mrp_documents_nd

Inventory is obtained for material where planning is not done as material master has MRP status
of ND. So for these materials, inventory and requirements are obtained from Stock requirement
list.

Using FM 'MD_STOCK_REQUIREMENTS_LIST_API', records are extracted.

Based on Aggregated MRP list (mdkp-cflag) get MRP line items from mdtb
If Availability indicator (MDTB- vrfkz) is flagged, then process below
If Receipt/issue indicator((mdtb-plumi) = -( which means requirement), and
Receipt/requirements date(mdtb-dat00)falls between current date to Avg monthly MRP date ie
with 4 months, then keep in zmeoplant-avreq12 internal table.
Else ie other records are processed below
Based on MRP element (mdtb-delkz), records are selected into various categories-
When 'WB'. "Plant stock = zmeoplant-onhnd
WHEN 'LB'. "Storage location stock= zmeoplant-onhnd
WHEN 'KB'. "Sales order stock = zmeoplant-onhnd
WHEN 'LK'. "Sub contract stock = zmeoplant-onhndlk
WHEN 'QM'. "QM stock = zmeoplant-onhndqm
WHEN 'BE'. "Purchase Order
Then with this PO go to EKPO to find out if Purchasing Document Type(ekko-
bsart) is 'ZG'("STOCK TRANSPORT PO ) or PO vendor ekko-lifnr is(from selection
parameter)"Internal vendor range = zmeoplant-onordipo
All other PO = zmeoplant-onordepo

WHEN 'BA'. "Purchase Requisition = zmeoplant-onordprq
WHEN 'FE'. "Production Order (SWO)= zmeoplant-onordswo
Get CO order balance ( using aufk and FM K_BALANCE_GET)

WHEN 'PA' "Planned Order
OR 'SA'. "Simulated Planned Order= zmeoplant-onordplo

WHEN 'SB' "(reduction of reqts)
OR 'SM'. "Simulated Reqts (reduction of reqts)
Then put qty in zmeoplant-avreq12(4 months avg MRP req)

Other MRP elements(unexpected MRP elements), show in separate message tab

If necessary, get the demand forecast and include it as additional requirements. This
only applies to materials with MRP type PE when using LTP data.

Specification


If MRP Type(mdkp-dismm ) is PE, then obtain these forecast based on selection
material & plant from ( FM MPOP_SINGLE_READ) and keep records in zmeoplant-
avreq12(4months avg MRP req)

Subtract and vendor consignment stock from the on-hand Obtain vendor consignment
stock from MARD and deduction from on hand inventory
zmeoplant-onhnd = zmeoplant-onhnd - consign_qty

Blocked stock to be added to On-hand inventory Get blocked stock for the plant when
in selection parameter and add to on hand inventory

* Compute the total on-hand
zmeoplant-totonhnd = zmeoplant-onhnd
+ zmeoplant-onhndkb
+ zmeoplant-onhndlk
+ zmeoplant-onhndqm
+ zmeoplant-onordipo
+ block_qty.

* Convert the sum of next 4 months MRP reqts to a 12 month basis
zmeoplant-avreq12 = zmeoplant-avreq12 * 3.

Table ZMEOPARMS setup Time & Reserve % :

Table ZMEOPARMS where user maintain time and reserve % for calculation of reserve amount on excess
inventory.

B. Selection Screen
<Describe the selection screen if used. Specify the fields for the selection and what checks need to be
done after the user has entered his or her criteria.>

Program ZMTGEOUPDATE selection screen :

Screen
Label
Referenced
Field
Range of Value Attributes,
Default Values
Validations
/ Checks
Comments/
Selection
Criteria (select
options,
parameters,
radio buttons,
checkboxes)
PIM MARA-FERTH Y N

Specification

C. Report/Form Layout
Additional fields to be updated in table ZMEOPLANT and ZMEOPERIOD :
1) Add PIM field(FERTH) to table ZMEOPLANT and ZMEOPERIOD and update values of PIM to the
field. Please create with field name ZMEOPLANT- FERTH and ZMEOPERIOD- FERTH
2) Time stamp of record insert
3) Time stamp of record changes

No Product master table fields in ECC update program as discussed with business. Since
these reporting values will be available in E&Z BI report
D. Paper Requirements
NA

E. Print Requirement
<Identify the print requirement if any. Type of layout, type of printer, etc.>

F. Special characteristics
< Sorting, grouping, where total or subtotals should occur, if any, drilldown, etc.>

G. Exception Handling Rules
<Specify instructions to be followed when errors occur, or any processing outside the normal process
flow.>

H. Special Requirements
<Provide any special requirements related to this development effort such as language translations,
configurability or personalization allowed, etc.>

I. Dependencies
<List any dependencies to other technical objects or configuration objects>

J. Constraints
As program will be run not just for plants of Xxxxxxxx but also AGS related plant. Therefore, special
consideration is required on performance improvement of the program

Specification

K. Scheduling Requirements
Program will be run during off-peak hours and in background mode immediately after LTP run program is
finished. Process is to run on the last Saturday of the 1st month of the quarter. Program will run only
once in quarter

L. Test Specification
<This portion of the document is used to plan the unit testing. It includes items such as defining the test
participants, the test environment, the schedule, and scope of the testing event.>

Will be part of Xxxxxxxx migration project time line
1. Functional Test Scenarios
<Document test scenarios to test all of the functional requirements. Include a test scenario for each
different business scenario that may occur.>

ID
Test Scenario Expected Results Comments
1
Validation of PIM material :
Pick a material having PIM
code in material master of
xxxxxxxx plart.
Xxxxxxxx plart showing up
in the table ZMEOPLANT
and ZMEOPERIOD

2
Validation of standard cost Check if standard cost is
picked from master plant
entered in selection
paratemer

3
Validate On hand qty
figures displayed in E&Z
report
Check the values of on
hand qty figures of E&Z
report with MB5B report
for a particular material

2. Test Data & Other Needs
<If any, specify test data set-up & refresh needs, volume of data, timeliness of data, etc.>

Demand forecast data needs to be uploaded and LTP run should be executed successfully.

3. Test System & Environment
<Identify test system and client.>

Test System:
Client:

Specification

M. Audit Requirements/Integrity Controls
<Specify the controls that are required to ensure that the data has been processed correctly.>

N. Security/Authorization Requirements
<Provide any special authorization checking or data security provisions required.>

Program ZMTGEOUPDATE is very critical and important step of E&Z process from quarter
close prosperity to post E&Z reserve. And program ZMTGEOUPDATE updates two Z tables,
from which results are analysied. Therefore Program ZMTGEOUPDATE will be accessable to
run by only few business user.

E&Z program will be included in planner roles.

1. Tcode ZMTGEOUPDATE : access to run program and update in Table
ZMEOPERIOD and ZMEOPLANT. Specific role of E&Z process need to be
created and access provided to few business user. As currently available in
Xxxxxxxx system
2. Table ZMEOPERIOD and ZMEOPLANT : Read access for these table to
user as currently available in xxxxxxxx system.

IV. TECHNICAL SECTION

A. Object Type:
Report (X ) Interface ( ) Conversion ( ) Enhancement ( ) Workflow ( )
Form ( ) WebDynpro ( ) Other ( ) Specify: _____________

Specification


B. All Z Objects Information
Object Type Report
Object Name ZAFGR177
Object Description Excess and Obsolete Update
Development
Class
ZAFG
Transaction Code ZAFGR177
Message Class ZZ
Other Relevant
Information
NA

C. Detail Technical Specification
Requirement:

There was a requirement to copy the Xxxxxxxx report ZMTGEOUPDATE into xxxx following the xxxx
standards and do the fine tuning.

Solution:

The Solution can be done with the functionality established in Xxxxxxxx System and create a new report
ZAFGR177 in xxxx system .

Details Logic Implemented:

Selection screen for user input
--------------------------------
Primary plant(for master data) ( p_plwrk)
Plants in E&O (s_werks)
E&O run ID (p_runid )
Start date of first E&O period (p_mrpdat)
Parameter set (p_parms )
Material (s_matnr)
Internal vendor list (s_lifnr)
PIM Code (s_pmcode)
Planning Scenario (p_plscn)

Other Parameters for user action
--------------------------------------
Delete data(for RUN ID) (P_RERUN)
Include-PE & ND type materials (P_PEFST)
No database updates (P_TEST)

Specification


option for No. of records to be insert in to table in one sort (Default 5,000)
------------------------------------------------------------
Nbr of DB inserts per commit (P_COMIT)

Details logic
--------------
-> if p_rerun = checked ('X') AND p_test Not checked.

deleting the existing records from below two Z-tables

ZAM0238
ZAM0239

If records deleted or not deleted based on that below message will display.

ZAM0239 RECORDS DELETED
ZAM0239 NO RECORDS TO DELETE
ZAM0238 RECORDS DELETED
ZAM0238 NO RECORDS TO DELETE

-> Then getting the plant related master data for the selected plants based on selection screen (s_werks)
value.
- Get the plant names and valuation areas from the plant master from T001W table by passing
werks IN s_werks
AND bwkey NE space.
- Get the company codes from the valuation area table T001K table by passing
bwkey = T001W-bwkey
- gathering plant name,valuation area,company code ,fiscal year xxxxxxxxt and currency
into an internal table (it_zmeot001) selecting from table t001w,t001k and t001.

--> Then Saving the fiscal year xxxxxxxxt for the primary plant which will be used in getting the fiscal
month of the MRP/LTP run date.

-> Setup dates used for various selections

1st setup--Getting the E&O parameters from ZAF0156 table and capturing in an internal table.

Then getting the fiscal month of the MRP/LTP run date by passing the fiscal year
xxxxxxxxt and MRP/LTP run date.
and getting the previous fiscal month by passing fiscal month and year of MRP/LTP run
date.

-- Then setting the begin and end date to the end of the previous period as (lastenddate =
'18991231').
-- Then based on no. of periods in ZAF0156 internal table getting the next fiscal month.
-- Finally getting the end date of the period and updating the enddate in ZAF0156 internal table .
2nd setup-- Setup date range for determining avg monthly MRP requirements for next 4 months.
3rs setup-- Setup fiscal month range for consumption history for previous 12 months + current quarter ie.
for 15 months.

-> Get the MRP doc headers for the selected plants (MDKP)
-- If Planning scenario (p_plscn) is not entered in selection screen then
getting the MRP List headers for the selected plants/LTP from MDKP table passing by

Specification

plwrk IN s_werks (plant entered from selection screen)
AND sobsl <> 'PB' (Special procurement type)
AND matnr IN s_matnr(Material entered from Selection screen)
AND dtart = 'MD'. (Type of MRP list)
Else
getting the MRP List headers for the selected plants/LTP from MDKP table passing by
plwrk IN s_werks
AND sobsl <> 'PB'
AND matnr IN s_matnr
AND dtart = 'LP'
AND plscn = p_plscn.(Planning scenario entered from sel.screen)

-- next getting all ND materials from MARC table and updating MDKP table (if blank material is in
selection, then all material in that plant is considered) and updating MDKP table.
-- Then mapping the records from MDKP table to the MARC table based on plant and material
combination and MRP type = 'ND'.
if ND type record exists then updating the MDKP records as per ND type
Else
modifying the MDKP table based on MRP type of MARC record.

-> Then looping all records of MDKP table at every new matnr filling the ZAM0239 table.
-- converitng any MRP error messages to the job log as success messages
-- capturing plant and material data and filling ZAM0238 table as following.
- validating the MARC records based on material and plant combination of MDKP record.
- validating it_zmeot001 (Plant, Valuation Area, and Company Code table for E&O )
based on plant of MDKP record.
- Then if valuation area = 4030
getting material valuation data from MBEW table and filling ZAM0238-unitcost
field of ZAM0238 table
else
getting Material Ledger: Header Record and Material Ledger: Period Totals
Records Values
filling ZAM0238-unitcost and ZAM0238-unitcost_32 fields of ZAM0238 table.
- Then checking MRP type = 'ND' or not
if it is 'ND' getting MRP records from MDTB and MDTC table based on DTNUM
(Number of material requirements planning table) and filling the ZAM0238 table fields by some
calculations and validations switched based on MRP Element(mdtb-delkz). Below MRP Element are
being checked and done some calculations.
'WB','LB','KB','LK','QM','BA','PA' OR 'SA'--For these type calculation done by
adding Quantity
received or quantity required with respective field of ZAM0238 table.

'BE'--(Purchase Order) checking in EKKO table and filling the records.

'FE'--(Production Order (shop work order)) getting the CO order balances and
capturing in a table.

'SB' or 'SM'-( reduction of reqts) validating ZAF0156 table by passing
Receipt/Requirements date and skipping any requests after the last period
if not record exist else filling ZAM0239 table.
Others--(Unexpected MRP Element)
capturing the error and success message into an internal table.

If necessary, get the demand forecast and include it as additional

Specification

requirements. This only applies to materials with MRP type PE when
using LTP data and only if the p_pefst option is selected on the
selection screen.

Then Subtracting the vendor consignment stock from the on-hand
(consignment stock is getting from MARD table by passing material and plant)

Then computing the total on-hand value and Converting the sum of next 4
months MRP reqts to a 15 month basis.
- IF MRP type NE 'ND'.Then gertting MRP records by using a standard RFC
'MD_STOCK_REQUIREMENTS_LIST_API' and processing as above to fill the ZAM0238 table and
ZAM0239 table .

- Then getting open blanket purchase orders from EKPO table and filling ZAM0238 table.
- Then setting negative qtys to zero in ZAM0238 records.
- If there are any sources of supply, get last 12 months + current quarter consumption
from MVER table and filling the ZAM0238 table.
- Then At End of material selection in the each row of loop computing reserve by period
prorating reserve quantity to plants prorating reserve value to periods.

- Then if p_test check box is not checked inserting the values finally to ZAM0238
database table and ZAM0239 database table.
- Those Material which have unexpected MRP elements the logs will be created for those
and displayed in output screen.

Test cases:

Input :-

Specification


Output-:

Specification


Updating in the Z-table (ZAM0238)

Specification

Updating in the Z-table(ZAM0239)

D. Open Item / Issues Log / Proposed Solutions (keep all history)

Assigned
To
<Name>
Date
Opened
Due
Date
Status Description Resolution

Forms and Reports Functional Specification for Excess and Zero Demand Update

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Forms and Reports Functional Specification for Excess and Zero Demand Update

Caricato da

Copyright:

Formati disponibili

Forms and Reports Functional

Potrebbero piacerti anche