Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0022673 | Openbravo ERP | 09. Financial management | public | 2012-12-26 20:15 | 2013-01-25 09:53 |
| Reporter | dmiguelez | ||||
| Assigned To | dmiguelez | ||||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | OS | 20 | OS Version | Community Appliance | |
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | Sandrahuguet | ||||
| OBNetwork customer | No | ||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0022673: Business Partner Blocking | ||||
| Description | Add the possibility to block a Business Partner. | ||||
| Steps To Reproduce | Functional Specs: On the Customer and Vendor Tabs of the Business Partner, a check is going to be created called Business Partner Block. When a document is block to a particular Business Partner, this document will not be able to be completed. Other actions such as create a new one, or void or reactivate will be possible. By checking it, a new section will be shown with the possible blocking options, filled by the following default values. Customer - Order: Blocked. - Goods Shipment: Blocked. - Invoice: Blocked. - Payment: Not blocked. Vendor - Order: Blocked. - Goods Receipt: Not blocked. - Invoice: Blocked. - Payment: Blocked. This are the reasons why the default values are the previous ones. - Order By default Order is blocked for both Customer and Vendor. It makes sense that if a client blocks a Business Partner, the client should not be able to complete an Order, since this document is the one that starts the basic business flow. Therefore by default, an Order will never be completed for a blocked Business Partner. - Goods Shipment / Receipt By default Goods Shipment is blocked for a Customer, but not for a Vendor. When blocking a Customer, it is reasonable to think that the client does not want to send any Shipment to him, since the client may doubt if the Customer is going to pay for it. But not for a Vendor. The reason is that, if there were Orders already created pending to be receipt, the Warehouse manager should have the possibility to register in the system the receipt when it happens. The actions to perform afterwards (Invoicing and Payment) may be blocked, but this way it is possible to register the reception of a Goods Receipt in the system and decide what to do with it later. - Invoice By default the Invoice is blocked for both the Customer and the Vendor. Since the Invoice is a contractual document and have further implications because of it (Taxes for example), this document is blocked disabling the option to "sign a contract" with a Blocked Business Partner. - Payment By default the Payment is blocked for the Vendor, but not for the Customer. The reason for it is based on the cash flow. It should not possible to make a Payment to a blocked Vendor, but it should be possible to receive a Payment from a Customer. The system will allow incoming payments but would block outgoing ones. Also, when Payments are blocked, execution of Payments is also blocked, meaning that if there is a Payment in Awaiting Execution status, it would not be possible to execute it. Additional Notes. Transactions and Reconciliations are never blocked. Therefore a Payment against a GL/Item is always possible to make. G/L Journal entries are also never blocked, since blocking of Posing is out of scope for this project. | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-12-26 20:15 | dmiguelez | New Issue | |||
| 2012-12-26 20:15 | dmiguelez | Assigned To | => dmiguelez | ||
| 2012-12-26 20:15 | dmiguelez | Modules | => Core | ||
| 2012-12-26 20:15 | dmiguelez | OBNetwork customer | => No | ||
| 2012-12-26 20:15 | dmiguelez | Triggers an Emergency Pack | => No | ||
| 2013-01-10 16:36 | hgbot | Checkin | |||
| 2013-01-10 16:36 | hgbot | Note Added: 0055465 | |||
| 2013-01-10 16:36 | hgbot | Status | new => resolved | ||
| 2013-01-10 16:36 | hgbot | Resolution | open => fixed | ||
| 2013-01-10 16:36 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/50e8582535d5ca442814d271983d50ade6763a40 [^] | ||
| 2013-01-11 08:27 | Sandrahuguet | Review Assigned To | => Sandrahuguet | ||
| 2013-01-11 08:27 | Sandrahuguet | Note Added: 0055477 | |||
| 2013-01-11 08:27 | Sandrahuguet | Status | resolved => closed | ||
| 2013-01-11 12:24 | hgbot | Checkin | |||
| 2013-01-11 12:24 | hgbot | Note Added: 0055479 | |||
| 2013-01-14 18:59 | hudsonbot | Checkin | |||
| 2013-01-14 18:59 | hudsonbot | Note Added: 0055510 | |||
| 2013-01-25 09:53 | xplacesc | Note Added: 0055836 | |||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||