Openbravo Issue Tracking System - Retail Modules
{
"messageId": "MessageId0144",
"channel": "External",
"posTerminal": "Magento",
"data": [
{
"currency": "EUR",
"payment": 135,
"step": "create",
"grossAmount": 135,
"netAmount": 111.57,
"documentStatus": "NC",
"businessPartner": "WVG/C0002",
"completeTicket": true,
"organization": "B5DE96143D6642228E3B9DEC69886A47",
"documentType": "91133D5715FA429C875334DB798D57A1",
"transactionDocument": "91133D5715FA429C875334DB798D57A1",
"warehouse" : "0B3E1D8D0FCB44FB81EA1A3FF158B086",
"lines": [
{
"product": "WVG/L0014",
"qty": 1,
"grossAmount": 135,
"netAmount": 111.57,
"taxAmount": 23.43,
"taxLines": {
"Entregas IVA 21%": {
"rate": 21,
"netAmount": 111.57,
"taxAmount": 23.43
}
}
},
],
"taxes": {
"Entregas IVA 21%": {
"rate": 21,
"grossAmount": 135,
"netAmount": 111.57,
"taxAmount": 23.43
}
}
}
]
}
We have registered a sale in "Magento" posTerminal, and we want to load a ticket in Posets Store with the Posets Store Warehouse, but linked to the Magento posTerminal. This is a common scenario when working with e-commerce and OMS, where the sale happens in an e-commerce solution and the order will be delivered by a different organization within the cross store.
If we try to load this JSON with the External Order Loader, it will fail with the following error:
"Value 0B3E1D8D0FCB44FB81EA1A3FF158B086 does not resolve to an instance of Warehouse"
Note that 0B3E1D8D0FCB44FB81EA1A3FF158B086 is the Posets Warehouse Id.
However, if we try to manually enter the ticket in the ERP it will work fine.
The problem is when the external order loader tries to find the warehouse [ExternalOrderLoader.resolve()]. In that moment it automatically adds a filter by the organization's natural tree to search for the warehouse from the provided ID. This looks OK, but the organization is taken from the posTerminal one (in our case Magento), so it fails because Posets is a Magento's sibling.
An error "Value 0B3E1D8D0FCB44FB81EA1A3FF158B086 does not resolve to an instance of Warehouse" is returned
1. If an organization is passed as part of the json file, use this organization to filter by its natural tree when resolving a json property.
2. Take the posTerminal organization and search for the related cross store organization. If defined, take it as the one for the filter.
I attached a proposed solution for the second option
crossStore_ExternalOrderLoader.diff (1,073) 2021-04-29 17:31https://issues.openbravo.com/file_download.php?file_id=15606&type=bug