Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0057028 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [POS2] POS | minor | always | 2024-11-06 22:21 | 2025-02-05 16:13 | |||||||
| Reporter | axelmercado | View Status | public | |||||||||
| Assigned To | mtaal | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | scheduled | 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 | |||||||||||
| Merge Request Status | ||||||||||||
| Review Assigned To | ||||||||||||
| OBNetwork customer | OBPS | |||||||||||
| Support ticket | 111068 | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0057028: The quantities of labels to be printed should be based on the last receipt of the OD and not on the quantity received so far. | |||||||||||
| Description | When you want to print labels from the import of a DO, the quantity that is set to print is the total received so far, which generates a problem when the reception is done in batches. For example: 50 units transferred to a store, to be delivered in 3 different deliveries 10+20+20 pcs. - 10 units, we can print the 10 units received. - Next 20 units. POS proposes us to print 30 labels, 10 of which we will have to discard as the product has been labeled in the first reception. - 20 last units, here we will have to discard 30 labels, the first 10 and the next 20. | |||||||||||
| Steps To Reproduce | This issue requires someone who knows both AWO and POS: 1- Generate an OD in which 50 units have been issued. 2- Receive the OD in partial form, it can be 10 units. 3- In POS, in the printing labels functionality, import the generated DO and verify that the amount of labels you propose to print is 10 (the amount received). Up to this point everything is OK. 4- Receive again the partial OD, it can be 20 units. 5- In POS, again in printing labels, import the DO and verify in this case that the proposed quantity to print is 30 (the total quantity received so far) although ideally it should propose 20 since probably the first 10 units have already been printed. This will prevent customers from printing more labels than desired, unless the user requests it and changes the quantity to be printed. | |||||||||||
| Tags | No tags attached. | |||||||||||
| 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 |
| 2024-11-06 22:21 | axelmercado | New Issue | |
| 2024-11-06 22:21 | axelmercado | Assigned To | => Retail |
| 2024-11-06 22:21 | axelmercado | OBNetwork customer | => OBPS |
| 2024-11-06 22:21 | axelmercado | Support ticket | => 111068 |
| 2024-11-06 22:21 | axelmercado | Triggers an Emergency Pack | => No |
| 2024-11-07 14:51 | migueldejuana | Status | new => scheduled |
| 2024-11-07 14:51 | migueldejuana | Assigned To | Retail => Rajesh_18 |
| 2024-11-11 15:57 | migueldejuana | Assigned To | Rajesh_18 => migueldejuana |
| 2024-11-11 16:09 | migueldejuana | Priority | high => normal |
| 2024-11-11 16:09 | migueldejuana | Type | defect => feature request |
| 2024-11-11 16:10 | migueldejuana | Relationship added | related to 0053247 |
| 2025-02-05 16:13 | migueldejuana | Assigned To | migueldejuana => mtaal |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |