Openbravo Issue Tracking System - Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0058191 | Modules | Distribution Orders | public | 2025-03-10 21:22 | 2025-03-26 19:19 |
Reporter | axelmercado | ||||
Assigned To | AtulOpenbravo | ||||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | open | ||||
Regression date | |||||
Regression introduced by commit | |||||
Regression level | |||||
Review Assigned To | |||||
Support ticket | 123712 | ||||
OBNetwork customer | OBPS | ||||
Regression introduced in release | |||||
Summary | 0058191: Error in sequence number - DO | ||||
Description | Operation1 : When we make the distributation order operations starting by the DOI to generate the DOR. The Documents No are created this way : DOI Doc No= DOR DOC No= T1000292 Operation2 : If we want to do the opposite, starting by the DOR to generate the DOI. The Documents No are created this way: DOR Doc N= DOI DOC NO= T1000111 < Operation 1 which is not correct. - Document NO of the 2nd Operation should be continued (1st Operation + 1). Doc No 2nd Operation have to be # than the 1st Operation and it doesn’t have to be repeated. | ||||
Steps To Reproduce | In Livebuilds: 1- Create a DO Issue and verify the numbering with which it is created. 2- Process the DO (“Book” button) and verify that the corresponding DO Receipt has been created (it should contain the same document No.). 3- Go to the DO Receipt window and create a new order, verify that the document No. is not the next to the previous one that has been created automatically. 4- Check the sequences of both document types in the “Document Sequence” window and verify that they are different. | ||||
Proposed Solution | The DO numbering should be synchronized for both DO Issue and DO Receipt, regardless of where it was created and whether or not the document has been processed. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2025-03-10 21:22 | axelmercado | New Issue | |||
2025-03-10 21:22 | axelmercado | Assigned To | => Triage Omni WMS | ||
2025-03-10 21:22 | axelmercado | Support ticket | => 123712 | ||
2025-03-10 21:22 | axelmercado | OBNetwork customer | => OBPS | ||
2025-03-17 13:55 | egoitz | Severity | minor => major | ||
2025-03-17 18:53 | mtaal | Assigned To | Triage Omni WMS => AtulOpenbravo | ||
2025-03-21 13:21 | hgbot | Merge Request Status | => open | ||
2025-03-21 13:21 | hgbot | Note Added: 0177113 | |||
2025-03-24 10:50 | mtaal | Note Added: 0177167 | |||
2025-03-24 10:50 | mtaal | Status | new => feedback | ||
2025-03-26 01:07 | axelmercado | Note Added: 0177252 | |||
2025-03-26 09:45 | mtaal | Note Added: 0177259 | |||
2025-03-26 09:45 | mtaal | Status | feedback => closed | ||
2025-03-26 09:45 | mtaal | Resolution | open => no change required | ||
2025-03-26 19:19 | hgbot | Note Added: 0177295 |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|