Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0046823 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Retail Modules] Order Preparation | minor | have not tried | 2021-05-25 10:29 | 2021-05-27 12:02 | |||||||
| Reporter | vmromanos | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0046823: Inconsistent task assignment in Order Preparation in Picking and Issuing tasks | |||||||||||
| Description | When you create a picking in the POS, the AWO task is assigned to the POS user. Once the picking is done, if you try to ISSUE the order in the POS, the issue AWO task is successfully created but the assigned user is null, so the flow can't continue from the POS. If the routing assignment is configured to Automatic confirmation, the issue task is assigned to the POS user (although it's not important as the task is confirmed already, so nothing to do with it). This behavior is not consistent at all. In case of manual confirmation the flow can't continue from the POS. | |||||||||||
| Steps To Reproduce | See http://wiki.openbravo.com/wiki/Modules:Order_Preparation [^] In AWO: Make sure the routing is set as Manual confirmation IN POS: Create a Sales Order to be prepared. Prepare it and generate the picking list. Assign it to the POS user. Confirm it. Issue the sales order. Verify the issue task has been properly created but the assigned user is null. There is no way to assign it to the POS user (as we can do with the Picking task), so the process can't continue from the POS. | |||||||||||
| Proposed Solution | Add a button "Assign" to be able to assign the issue tasks in case of manual confirmation. It it the similar scenario we already have for Picking tasks, but this time for the Issue Tasks Add a status "Issuing" (between Picked and Issued) to be active when there are issue tasks not confirmed yet. Add a button "Confirm All" to be able to confirm the issue tasks. It it the similar scenario we already have for Picking tasks, but this time for the Issue Tasks | |||||||||||
| Tags | DemoImprovementProgram | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2021-05-25 10:29 | vmromanos | New Issue | |
| 2021-05-25 10:29 | vmromanos | Assigned To | => Retail |
| 2021-05-25 10:29 | vmromanos | Triggers an Emergency Pack | => No |
| 2021-05-25 10:30 | vmromanos | Description Updated | View Revisions |
| 2021-05-25 12:51 | vmromanos | Proposed Solution updated | |
| 2021-05-25 12:52 | vmromanos | Type | defect => design defect |
| 2021-05-27 12:02 | xplacesc | Tag Attached: DemoImprovementProgram | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |