Projects/Deliver Invoice Status of documents/Functional Specification

Contents 1 Deliver and Invoice status 1.1 Overview 1.1.1 Scope 1.1.2 References 1.2 Design Considerations 1.2.1 Assumptions 1.2.2 Dependencies 1.2.3 Constraints 1.3 Functional Requirements 1.3.1 Business process definition 1.3.2 Functional requirements based on business processes 1.3.3 Functional requirements descriptions 1.3.4 Limitations 1.4 Non-Functional Requirements 1.5 Open Discussion Items 1.6 Closed Discussion Items

Deliver and Invoice status

Overview

• Having the deliver status and invoice status in Purchase/Sales order document allows the user to know whether the document is partially/fully delivered plus partially/fully invoiced in an easy and quick manner
• Having the invoice status in a goods receipt/goods shipment document allows the user to know whether the document is partially or fully invoiced in a very simple and quick manner

Two phases to develop this feature:

• Sales flow: That will include Sales Order, Goods shipment, Return from customer and return material receipt. This is planned for MP18
• Procurement flow: That will include Purchase Order, Return to Vendor, Return To Vendor Shipment and Goods Receipt. This is not planned in the short term

Scope

These new statuses will be present in the following documents:

• Purchase Order
• Return to Vendor
• Return To Vendor Shipment
• Goods Receipt
• Sales Order
• Return from customer
• Goods Shipment
• Return Material Receipt

The new statuses and values will be displayed as percent:

• Deliver status: 0%, 0-100% (Partial), and 100%
• Invoice status: 0%, 0-100% (Partial), and 100%

The statuses will be shown in the header of the document and won't be editable

• Deliver and Invoice status will be in Order document that is: Purchase Order, Return to vendor, Sales order and Return from Customer
• Invoice status will be in Goods receipt, Goods shipments, Return Material Receipt and Return To Vendor Shipment

References

Existing feature request for this functionality https://issues.openbravo.com/view.php?id=21160

Design Considerations

Assumptions

Dependencies

Constraints

Functional Requirements

Business process definition

1. Sales Order / Return from Customer and Purchase Order / Return to vendor (RTV)

• Ability to see Deliver status and Invoice status from the header
• Values could be 0-100%
• This values will be updated automatically and won't be editable
• In form view the status will be in the status bar while in the grid will be fields that could be filtered
• Rules:
  • IF accumulated delivered/invoiced qty of SO lines = 0 THEN status = No
  • IF accumulated delivered/invoiced qty of SO lines >0 AND < accumulated order qty THEN status = Partial
  • IF accumulated delivered/invoiced qty of SO lines >= accumulated order qty THEN status = Full
• The actions that can modify the status are:
  • When completing the order
  • When completing the corresponding goods shipment
  • When completing the corresponding sales invoice

2. Goods shipment/Return Material receipt and Goods receipt/Return to vendor shipment

• Ability to see Invoice status from the header
• Values could be 0-100%
• Rules:
  • IF accumulated invoiced qty = 0 THEN status = No
  • IF accumulated invoiced qty >0 and < delivered qty THEN status = Partial
  • IF accumulated invoiced qty >= delivered qty THEN status = Complete
• The actions that can modify the status are:
  • When completing the goods shipment
  • When completing the sales invoice

Functional requirements based on business processes

Functional requirements descriptions

Limitations

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items