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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0049779
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Advanced Warehouse Operationsmajoralways2022-07-11 14:462022-08-02 14:18
ReporteravicenteView Statuspublic 
Assigned ToTriage Omni WMS 
PriorityhighResolutioninvalidFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned Tovmromanos
Regression introduced in release
Summary

0049779: Distribution Order API bug when close DOi after update "qtyIssued"

DescriptionWhen a DOi is closed through the API afte updating the "qtyIssued", the corresponding DOr is not closed, see the following video with audio https://drive.google.com/file/d/17sis3CcV4oKwLKkTkOGhyt4kBgzfdjU1/view [^]
Steps To Reproduce1. Create a DOi through the API.
2. Update the "qtyIssued" for the previously created DOi through the API.
3. Close the previously created DOi through the API.
BUG: The mirrow DOr is not closed --> AVI 20220713: it is NOT a BUT, see https://issues.openbravo.com/view.php?id=49779#c139270 [^]

4. Close the mirrow DOr through the API.
BUG: a new DOr and a new DOi are created instead to close the existing DOr. --> AVI 20220713: Now, a record is uniquely identifies using following 3 properties: 1. documentNo; 2. Organization; 3. isIssue.
In that case, It is not possible to close a DOr from the API if it has the same documentNo that the DOi (preference: Copy Document Number in Distribution Orders=Y) and received qty <> issued qty. It should be a way to do that.


See the following video with audio https://drive.google.com/file/d/17sis3CcV4oKwLKkTkOGhyt4kBgzfdjU1/view [^]
TagsFASH
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0049426 closedTriage Omni WMS Openbravo ERP Openbravo API to support Distribution Order 

-  Notes
(0139270)
prakashmurugesan88 (developer)
2022-07-12 15:52

Mirrow DOr will not be closed if there is pending received,

Following is the logic,
// order==receipt: always close the referenced order which is an issue
// order==issue: only close the receipt (referenced) order if all are received

https://gitlab.com/openbravo/product/mods/org.openbravo.distributionorder/-/blob/master/src/org/openbravo/distributionorder/erpCommon/utility/ProcessDistributionOrderUtil.java#L461 [^]
(0139815)
vmromanos (manager)
2022-08-02 14:18

I reviewed your video. I think it's working as expected:

1. The DOr is not closed automatically because there is something pending to be received (you sent 5 units but you didn't receive them yet). If everything sent in the DOi is already received, then the DOr would be automatically closed.
If you really want to close the DOr you need to manually close it (but not through the DOi close)...

2. And related to this, in the second part of the video (1:52) the system is creating a CLOSED DOr because there is no DOr in the EUR_Sandro_FR organization (so the process creates a new one). You did change the isIssue property [OK], but you missed to change the organization.

- Issue History
Date Modified Username Field Change
2022-07-11 14:46 avicente New Issue
2022-07-11 14:46 avicente Assigned To => Triage Omni WMS
2022-07-11 14:49 avicente Tag Attached: FASH
2022-07-11 14:49 avicente Relationship added related to 0049426
2022-07-12 15:52 prakashmurugesan88 Note Added: 0139270
2022-07-13 15:12 avicente Steps to Reproduce Updated View Revisions
2022-08-02 14:18 vmromanos Review Assigned To => vmromanos
2022-08-02 14:18 vmromanos Note Added: 0139815
2022-08-02 14:18 vmromanos Status new => closed
2022-08-02 14:18 vmromanos Resolution open => invalid
2022-09-06 17:18 caristu Category Advance Warehouse Operations => Advanced Warehouse Operations


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker