Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0050600Retail ModulesRetail APIpublic2022-10-20 14:512023-07-11 10:23
Reporterazzeddine_meftoh 
Assigned Tomtaal 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerGold
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0050600: Multiple event OBDOAPI_UpdateDOQuantities for one DO reception confirmed in AWO
Descriptionwhen confirming the reception of a DO in AWO the event OBDOAPI_UpdateDOQuantities is triggered for each line.
we should send only one event when confirming the reception.
Steps To Reproducewhen confirming the reception of a DO in AWO the event OBDOAPI_UpdateDOQuantities is triggered for each line.
we should send only one event when confirming the reception.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of design defect 0052774 closed Triage Omni WMS [RM-7065] API event" Update Distribution Order quantities through goods movement" is sending the DO as many times as #lines 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-10-20 14:51azzeddine_meftohNew Issue
2022-10-20 14:51azzeddine_meftohAssigned To => Triage Platform Conn
2022-10-20 14:51azzeddine_meftohTriggers an Emergency Pack => No
2022-10-20 14:53azzeddine_meftohNote Added: 0142356
2022-10-20 15:05vmromanosAssigned ToTriage Platform Conn => AtulOpenbravo
2022-10-20 15:06vmromanosOBNetwork customer => Gold
2022-11-22 11:49vmromanosAssigned ToAtulOpenbravo => vmromanos
2022-11-22 11:49vmromanosStatusnew => acknowledged
2022-11-22 14:39vmromanosNote Added: 0144010
2022-11-22 14:39vmromanosTypedefect => design defect
2023-06-26 12:07mtaalRelationship addedhas duplicate 0052774
2023-07-11 10:22mtaalAssigned Tovmromanos => mtaal
2023-07-11 10:22mtaalStatusacknowledged => scheduled
2023-07-11 10:23mtaalRelationship replacedduplicate of 0052774
2023-07-11 10:23mtaalNote Added: 0152311
2023-07-11 10:23mtaalStatusscheduled => closed
2023-07-11 10:23mtaalResolutionopen => duplicate

Notes
(0142356)
azzeddine_meftoh   
2022-10-20 14:53   
for info we get as many event as lines present in the DO
(0144010)
vmromanos   
2022-11-22 14:39   
Design defect:

Each time we confirm a distribution order reception we are individually confirming each of the tasks associated to the lines.

Each task confirmation updates the DO's quantities, so an OBDOAPI_UpdateDOQuantities event is triggered for each task/line.

When the transaction ends, the events are added to the queue to be launched afterwards (in an asynchronous way). In the moment that they are launched, the system generates the Distribution Order JSON with the information found in the Database at this moment, so the user is receiving the same json information as many times as tasks where confirmed behind the scenes.


If you don't want to have this behavior, you can subscribe instead to the OBDOAPI_UpdateDOStatus which is sent just one time when the DO is closed.
(0152311)
mtaal   
2023-07-11 10:23   
The observed behavior is as expected, a new event is introduced to allow DO header level events. See duplicate issue.