Difference between revisions of "MRP Browse for demand and supplies"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Result of review by Mario Calderon, June 14th, 2013)
(Result of review by Mario Calderon, June 14th, 2013)
 
Line 23: Line 23:
 
**If MRP Browse for supplies, the MRP Supplies Pegging view is opened (http://www.adempiere.com/MRP_Supply_and_Demand_Pegging), enabling to know how this supplied is satisfied.
 
**If MRP Browse for supplies, the MRP Supplies Pegging view is opened (http://www.adempiere.com/MRP_Supply_and_Demand_Pegging), enabling to know how this supplied is satisfied.
 
*Useful for Libero
 
*Useful for Libero
 +
*'''Conclusion: accepted'''
  
 
===User roles & profiles===
 
===User roles & profiles===

Latest revision as of 05:49, 17 June 2013

Status

Contributors

Overview

Purpose

References

Design Considerations

Assumptions

Dependencies

Constraints

Glossary

Functional Requirements

Functional team

  • Volunteers for analyzing:

Result of review by Mario Calderon, June 14th, 2013

  • MRP Browser for demand and supplies are actually two Smart Browsers.
  • The Smart Browsers differ in the views (RV_PP_MRP_Supply and RV_PP_MRP_Demand from the standard Libero implementation).
  • Parameters: fields of Manufacturing Order, like Document number, Business Partner, Warehouse, Date promised (as range), Project, etc.
  • Result of search are Manufacturing Orders, Purchase Orders, etc. from the Production Master plan for that match the filtering parameters.
  • Smart Browsers help analyzing better the Product Master Plan, enabling the user to filter and also to differentiate between entries in the Product Master Plan for supply and entries for demand.
  • Navigation into search results possible
  • Useful for Libero
  • Conclusion: accepted

User roles & profiles

Business process definition

User stories

Functional requirements based on business processes

User Interface Mockups

Acceptance criteria

QA and test cases

Development infrastructure

Technical Requirements

Technical team

  • Volunteers for analyzing:
  • Result of analysis:

Data Requirements

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items