Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0058191
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Distribution Ordersmajoralways2025-03-10 21:222025-03-26 19:19
ReporteraxelmercadoView Statuspublic 
Assigned ToAtulOpenbravo 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Statusopen
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket123712
OBNetwork customerOBPS
Regression introduced in release
Summary

0058191: Error in sequence number - DO

DescriptionOperation1 :
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 ReproduceIn 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 SolutionThe 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0177113)
hgbot (developer)
2025-03-21 13:21

Merge Request created: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/mods/org.openbravo.distributionorder/-/merge_requests/98 [^]
(0177167)
mtaal (viewer)
2025-03-24 10:50

fix is send for feedback/test
(0177252)
axelmercado (viewer)
2025-03-26 01:07

Sending feedback to Atul
(0177259)
mtaal (viewer)
2025-03-26 09:45

Hello,
We discussed internally.

The preference is what it is, it is not the default behavior and the current preference behavior is by design. If an additional new behavior is needed it is a feature request.

Afaics this is not a bug.

If the customer wants to use the preference then having different prefixes for different sequences could help here.

So we will reject this issue for the above reasons.
(0177295)
hgbot (developer)
2025-03-26 19:19

Merge request closed: https://gitlab.com/orisha-group/bu-commerce/openbravo/product/mods/org.openbravo.distributionorder/-/merge_requests/98 [^]

- 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


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker