0046846: Order Confirmation should take into account first OMS Run ID if available

Description

The Order Confirmation process is able to exclude any warehouse that previously discarded a sales order. This feature is working out of the box.

Let's imagine this flow:
1. I call the OMS excluding some warehouse
2. I enter a ticket linked to the previous OMS Run ID
3. The ticket is rejected by the shop

At this point, the system should be smart enough to understand that the ticket was created through a OMS Run execution (because it's linked in the C_Order.EM_OBOMS_Run_ID column), read the included/excluded warehouses and propagate this information to the next oms run call.
However, right now it only excludes the warehouse that has just rejected the sales order.

Steps To Reproduce

Call the OMS engine passing a excluded warehouse.
Create a sales order with the proposal and link it to the OMS Run ID.
Reject this order.
Verify the new oms run executed to create the order is considering the initially excluded warehouse.

Proposed Solution

In case the C_Order.EM_OBOMS_Run_ID column is informed in the very first ticket, consider it like we do it for the rest of the flow.

Issue History
Date Modified	Username	Field	Change
2021-05-26 14:08	vmromanos	New Issue
2021-05-26 14:08	vmromanos	Assigned To	=> Triage Finance
2021-05-27 12:03	xplacesc	Tag Attached: DemoImprovementProgram

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
There are no notes attached to this issue.