| Openbravo Issue Tracking System - Openbravo ERP | 
| View Issue Details | 
| 
 | 
| ID | Project | Category | View Status | Date Submitted | Last Update | 
| 0020128 | Openbravo ERP | 08. Project and service management | public | 2012-03-27 17:43 | 2012-05-18 09:17 | 
| 
 | 
| Reporter | extra |  | 
| Assigned To | mirurita |  | 
| Priority | normal | Severity | minor | Reproducibility | always | 
| Status | new | Resolution | open |  | 
| Platform |  | OS | 5 | OS Version |  | 
| Product Version | 3.0MP7.3 |  | 
| Target Version |  | Fixed in Version |  |  | 
| Merge Request Status |  | 
| Review Assigned To |  | 
| 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 | 0020128: Create Sales Order From Expenses generates a Warehouse Order | 
| Description | When a user wants to create a sales order from billable expenses entered by employees, the sales order which is generated is a Warehouse Order. It should be an option for the user to select which order type to use.
 | 
| Steps To Reproduce | Enter an expense sheet with billable lines and process it. Navigate to Create Sales Order From Expenses and run the process.
 Check that generated order are Warehouse Orders.
 | 
| Proposed Solution | Either give the user an option to select the order type in the Create Sales Order From Expenses window; Or make the order type configurable somewhere in the application (a preference?);
 Or any other idea so that the generation of the warehouse order is not hard-coded.
 | 
| Additional Information |  | 
| Tags | No tags attached. | 
| Relationships |  | 
| Attached Files |  | 
| 
 | 
| Issue History | 
| Date Modified | Username | Field | Change | 
| 2012-03-27 17:43 | extra | New Issue |  | 
| 2012-03-27 17:43 | extra | Assigned To | => vmromanos | 
| 2012-03-27 17:43 | extra | Modules | => Core | 
| 2012-03-27 17:54 | vmromanos | OBNetwork customer | => No | 
| 2012-03-27 17:54 | vmromanos | Type | design defect => feature request | 
| 2012-03-27 18:04 | extra | Note Added: 0046790 |  | 
| 2012-05-10 12:12 | gorka_gil | Assigned To | vmromanos => mirurita | 
| 2012-05-18 09:15 | extra | Note Added: 0048755 |  | 
| 2012-05-18 09:17 | extra | Note Added: 0048756 |  | 
	| Notes | 
	| 
 | 
	| 
		
			| (0046790) |  
			| extra |  
			| 2012-03-27 18:04 |  | 
		
			| Don't know why the type has been changed and basically it does not matter. However from my point of view when a logic is hard-coded in a system which is supposed to be highly customizable, highly modular, and so on, that's a design defect. |  | 
	| 
 | 
	| 
		
			| (0048755) |  
			| extra |  
			| 2012-05-18 09:15 |  | 
		
			| We have delivered the module Type of Sales Order Expenses which is a solution for this issue. |  | 
	| 
 | 
	| 
		
			| (0048756) |  
			| extra |  
			| 2012-05-18 09:17 |  | 
		
			| This type of sales order expenses module re-uses the Expense checkbox available in document type. If a user ticks this checkbox for the document type Standard Order, all sales order for expenses will be created having the transaction document = Standard Order.
 The user can tick the expense flag for the type of sales order which is more consistent with its way of work.
 |  |