Difference between revisions of "MRP Supply and Demand Pegging"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Functional Requirements)
(Result of review by Mario Calderon, June 15th, 2013)
 
(3 intermediate revisions by the same user not shown)
Line 12: Line 12:
 
== Functional team  ==
 
== Functional team  ==
 
*Volunteers for analyzing:
 
*Volunteers for analyzing:
*Result of analysis:
+
** [[User:mar_cal_westf|Mario Calderon]] 19:00, 15 June 2013 (UTC) - Functional Review
 +
===Result of review by Mario Calderon, June 15th, 2013===
 +
*MRP Supply and Demand Pegging are actually two Windows in a Master/Detail manner.
 +
*MRP Demands View has two tabs
 +
**Demand Detail(Master, based on database view RV_PP_MRP_Demand)
 +
***Displays the demands according to the Production Master Plan
 +
**Supplies Detail (Detail, based on on database view RV_PP_MRP_Detail_Supply)
 +
***Displays the supplies '''for the demand''' according to the Production Master Plan
 +
*MRP Supplies View has two tabs
 +
**Supplies Detail(Master, based on database view RV_PP_MRP_Detail_Supply)
 +
***Displays the supplies according to the Production Master Plan
 +
**Demand Detail (Detail, based on on database view RV_PP_MRP_Demand)
 +
***Displays the demands '''for the supply''' according to the Production Master Plan
 +
*The Views differ in the order of the views (RV_PP_MRP_Supply and RV_PP_MRP_Demand from the standard Libero implementation).
 +
*Useful when analyzing supplies and demands
 +
**Supplies: '''shows which demands cause the supplies'''
 +
**Demands: '''shows which supplies cause the demands'''
 +
*The pegging is done during MRP: it documents the supply for the demand and viceversa
 +
*Desired feature: create a pegging while creating Manufacturing Orders at completing Sales Orders of the kind "Make to order"
 +
*'''Conclusion: accepted'''
 +
 
 
===User roles & profiles===
 
===User roles & profiles===
 
===Business process definition===
 
===Business process definition===
Line 23: Line 43:
 
== Development infrastructure  ==
 
== Development infrastructure  ==
 
== Technical Requirements ==
 
== Technical Requirements ==
 +
== Technical team  ==
 +
*Volunteers for analyzing:
 +
*Result of analysis:
 +
 
== Data Requirements ==
 
== Data Requirements ==
 
==Non-Functional Requirements==
 
==Non-Functional Requirements==
 
==Open Discussion Items==
 
==Open Discussion Items==
 
==Closed Discussion Items==
 
==Closed Discussion Items==

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 15th, 2013

  • MRP Supply and Demand Pegging are actually two Windows in a Master/Detail manner.
  • MRP Demands View has two tabs
    • Demand Detail(Master, based on database view RV_PP_MRP_Demand)
      • Displays the demands according to the Production Master Plan
    • Supplies Detail (Detail, based on on database view RV_PP_MRP_Detail_Supply)
      • Displays the supplies for the demand according to the Production Master Plan
  • MRP Supplies View has two tabs
    • Supplies Detail(Master, based on database view RV_PP_MRP_Detail_Supply)
      • Displays the supplies according to the Production Master Plan
    • Demand Detail (Detail, based on on database view RV_PP_MRP_Demand)
      • Displays the demands for the supply according to the Production Master Plan
  • The Views differ in the order of the views (RV_PP_MRP_Supply and RV_PP_MRP_Demand from the standard Libero implementation).
  • Useful when analyzing supplies and demands
    • Supplies: shows which demands cause the supplies
    • Demands: shows which supplies cause the demands
  • The pegging is done during MRP: it documents the supply for the demand and viceversa
  • Desired feature: create a pegging while creating Manufacturing Orders at completing Sales Orders of the kind "Make to order"
  • 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