MRP Browse for demand and supplies
From ADempiere
Revision as of 05:49, 17 June 2013 by Mar cal westf (Talk) (→Result of review by Mario Calderon, June 14th, 2013)
This Wiki is read-only for reference purposes to avoid broken links.
Contents
- 1 Status
- 2 Contributors
- 3 Overview
- 4 Purpose
- 5 References
- 6 Design Considerations
- 7 Glossary
- 8 Functional Requirements
- 9 Functional team
- 10 Acceptance criteria
- 11 QA and test cases
- 12 Development infrastructure
- 13 Technical Requirements
- 14 Technical team
- 15 Data Requirements
- 16 Non-Functional Requirements
- 17 Open Discussion Items
- 18 Closed Discussion Items
Status
Contributors
Overview
Purpose
References
Design Considerations
Assumptions
Dependencies
Constraints
Glossary
Functional Requirements
Functional team
- Volunteers for analyzing:
- Mario Calderon 14:00, 14 June 2013 (UTC) - Functional Review
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
- If MRP Browse for demand, the MRP Demand Pegging view is opened (http://www.adempiere.com/MRP_Supply_and_Demand_Pegging), enabling to know where this demand comes from.
- 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
- 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: