0054974: Task and Reception list duplicated caused by delta SAME flow in SMCP

Description

The SMCP client has been presenting a problem of duplicated task and receptions lists for some time. When a task contains the confirmed quantity less than the expected/issued quantity, a duplicate task is created as if the "Delta Same" button was selected in AWO, when the client does not contain such functionality.

We believe this is due to the following part of the code where the deltaResponse = OBAWO_Constants.DELTA_SAME:

  private String getDeltaResponse(final OBAWOTask task) {
    String deltaResponse = null;
    if (task.getDeltaResponse() != null) {
      deltaResponse = task.getDeltaResponse();
    } else {
      if (StringUtils.equals(OBAWO_Constants.DELTA_DIFFERENT,
          task.getInventoryTransactionType().getDeltaResponse())) {
        deltaResponse = OBAWO_Constants.DELTA_DIFFERENT;
      } else {
        deltaResponse = OBAWO_Constants.DELTA_SAME;
      }
      task.setDeltaResponse(deltaResponse);
    }
    return deltaResponse;
  }

Steps To Reproduce

At AWO:
1- Select a DO that is available to receive.
2- Confirm some tasks completely and others partially or with quantity 0.
3- After having processed all the tasks of the DO, verify that the tasks received partially or with quantity 0, a new task has been created.
4- Check in BO the previous DO and verify that the tasks and the reception list are duplicated.

Tags

No tags attached.

Attached Files

image.png [^] (15,442 bytes) 2024-03-18 18:45

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0162265) aferraz (manager) 2024-03-18 12:00	Moved to feedback because we don't have enough information to reproduce the problem.

(0162308) axelmercado (developer) 2024-03-18 18:45	As can be seen in the attached image, duplicate tasks come with the delta response = SAME field. The SMCP client does not have the SAME button flow, the user cannot set it. The only part of the code where this value is set is the one mentioned in the description, which details the behavior of the tasks received partially or with a value of 0. The random reproducibility has been given because it is not an easy problem to reproduce, sometimes it happens and sometimes it doesn't, but the flow of steps to follow is the basic one: You have a DO to receive, you proceed to receive them and some tasks are received partially, nothing else (this in the client environment).

Issue History
Date Modified	Username	Field	Change
2024-03-15 23:57	axelmercado	New Issue
2024-03-15 23:57	axelmercado	Assigned To	=> Triage Omni WMS
2024-03-18 09:24	mtaal	Assigned To	Triage Omni WMS => ludmila_ursu
2024-03-18 11:28	aferraz	Status	new => feedback
2024-03-18 12:00	aferraz	Note Added: 0162265
2024-03-18 18:45	axelmercado	File Added: image.png
2024-03-18 18:45	axelmercado	Note Added: 0162308
2024-03-18 18:45	axelmercado	Status	feedback => new
2024-04-22 11:40	mtaal	Status	new => feedback