View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:Requisitions/Specifications

Contents

Requisitions Improvement - Functional Specifications

Overview

Purpose

The purpose of this project is to improve the functionality of Requisitions making easier the process to create purchase orders based on the Requisitions.

Scope

References

Design Considerations

Assumptions

Dependencies

  1. The MRP module generate requisitions, after the changes are done it has to be tested that there is no regression.

Constraints

  1. MRP Module can create Purchase Orders from Requisitions
    1. Assure that there is no regression in MRP module
    2. Assure that a Requisition Line can generate only a Purchase Order.

Glossary

Functional Requirements

User roles & profiles

The user roles affected by this functionality are:

Warehouse workers
Typically these users do not have a high level of professional education and might not be computer literate. They tend however to spend a number of years with the same employer and after hiring they go through a few days of training to learn the processes within the warehouse. These users, therefore, need to be able to learn how to use the product in a few hours. These users can create requisitions when the level of inventory for a product is low.
Purchase managers
Typically these users have a high level of professional education, are computer literate and receive training in the product and business process. These users perform purchase orders from the requisitions, they have to select the correspondent vendor taking into account the different variables that can take part in the decision: price, discounts, availability,...
Generic employee
These are users that work for the organization implementing Openbravo in a variety of roles and that are involved in a given business process on an occasional basis. Because of the infrequent nature of their involvement in the process, their primary concern is ease of use, defined as the ability to perform a new task without having to read any documentation. In the case of requisitions, employees request products and services that they need in their job using requisitions.

Business process definition

  1. The requisitions are created when some material needing is detected.
    1. They can be entered manually when the stock level is low or is expected a high demand in short time.
    2. They are also an output of the MRP for raw materials.
  2. The Purchase Manager reviews the new requisition and can create automatically a Purchase Order for it.
  3. The Purchase Manager can review all the requisitions lines and group them to create Purchase Orders.
  4. The user reviews the created Purchase Orders and complete them.

User stories

Story 1:

Story 2:

Story 3:

Story 4:

Story 5:

Functional requirements based on business processes

To achieve the desired functionalities are needed three windows and a new process:

  1. Requisitions: Based on existing window in MRP Management adapting to the new requirements. This window is used to enter new requisitions.
  2. Manage Requisitions: Based on the existing window in MRP Management adapting to the new requirements. This window is used to manage the completed requisitions, only the Purchase Manager should have access to it.
  3. Create Purchase Order from Requisitions: New manual window.
  4. Create Purchase Order: New button in Requisitions window.
Requisitions window
Num Requirement Importance Status
1.1 Ability to create new requisitions, minimum information is product, quantity and need by date Must have Completed
1.2 Ability to assign a requisition line to a preferred vendor Nice to have Completed
1.3 Block the requisition line when it has been completed Should have Completed
1.4 Ability to associate a requisition to a vendor and/or a price list Should have Completed
1.5 Ability to set a price for the product in the requisition line when no price list is selected in the header Nice to have Completed
Manage Requisitions window
Num Requirement Importance Status
2.1 Ability to manage the requisitions, close, reactivate,... Must have Completed
2.2 Ability to assign a requisition line to a preferred vendor Nice to have Completed
2.3 Ability to mark a requisition line when it has been ordered Should have Completed
2.4 Block the requisition line when the requisition has been completed Should have Completed
2.5 Ability to associate a requisition to a vendor and/or a price list Should have Completed
2.6 Ability to set a price for the product in the requisition line when no price list is selected in the header Nice to have Completed
2.7 Ability to associate existing purchase order lines to the requisition lines Should have Completed
2.8 Ability to lock requisition lines when are being used. The requisition is automatically locked in two cases.
  1. In the Requisition To Order manual window when is added to the bottom list to create the purchase order from it. The requisition is unlocked when is removed from the list.
  2. In the MRP Module, when a requisition is considered in a Purchase Plan Run it is locked. The requisition line is unlocked when the purchase orders are generated. It is also possible to unlock the requisition from the Requisition To Order window if the user is the lock owner.

The lock has these attributes:

  • Lock date: date when the requisition line is locked, locks of more that 3 days age are considered as not locked
  • Locked by: user responsible of the lock, only this user is able to unlock the requisition line.
  • Lock cause: Requisition To Order window or MRP module
  • Lock qty: quantity to order, used by the requisition to order window.
  • Lock price: price actual to use in the order, used by the requisition to order window.
Should have Completed
Create Purchase Orders from Requisition
Num Requirement Importance Status
3.1 Ability to select requisition lines to create purchase order Must have Completed
3.2 Ability to select the vendor of the created purchase order Must have Completed
3.3 Ability to set the date of the Purchase Order. Should have Completed
3.4 If no date is set it takes the sooner date of selected lines Nice to have Not included
3.5 Ability to filter the requisition lines by product and date Should have Completed
3.6 Requisition appear grouped by product and ordered by date Should have Not included (1)

Note (1): Not selected lines are ordered by need by date, product and attribute. Selected lines are grouped by vendor and price list.

Create Purchase Order process
Num Requirement Importance Status
4.1 When the requisition doesn't have a vendor defined it takes the current vendor defined in the product Must have Completed
4.2 The process creates a purchase order line for each requisition line Must have Completed
4.3 The process creates only a purchase order for each necessary vendor with several lines Should have Completed
4.4 Ability to select the date of the Purchase Orders Nice to have Completed
4.5 Ability to select the vendor of the Purchase Orders. If a requisition line has a product not sold by the vendor the current vendor of that product is used Nice to have Completed
4.6 Output message with created Purchase Order's Document Numbers Must have Completed

User Interface Mockups

Technical Requirements

  1. Create a new column in database to insert the button.
  2. Create a new procedure to create the purchase orders.

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items

Retrieved from "http://wiki.openbravo.com/wiki/Projects:Requisitions/Specifications"

This page has been accessed 6,105 times. This page was last modified on 8 June 2012, at 05:30. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.