|
EAM-55260 Data Lake - R5STOCK deleted data not correctly reflecting on the compass |
|
|
Description |
|
|
When data is deleted from R5STOCK table for a specific part and the deletion is synchronized over to the data lake, the sto_part_org does not contain the part organization, but rather the part organization followed by the &% symbols and the store defined on sto_store column. When a simple query is run on the compass for R5STOCK and that part, it still shows the part data. *Steps to reproduce:* 1. Part has a store associated on the Parts | Stores tab, as well as stock value on Stock tab 2. Set stock quantity on Hand (STO_QTY) to 0 on the Parts | Stock tab 3. Deleted the Stock record 4. Delete the Store association via the Parts | Stores tab (this deletes the record from R5STOCK too) 5. New deletion record is recorded on r5datalakedelete (here dkd_keyfld2 is set to the part organization, followed by the &% symbols and the part store) 6. DKDL job runs and the deletion gets synchronized over to data lake *Expected results:* When running a select statement on R5STOCK for that part, no records should be returned. *Actual results:* When running a select statement on R5STOCK for that part, it still returns the stock record with 0 Q.ty on Hand, therefore not reflecting the actual status of the R5STOCK table in EAM, where no records exist on the DB for that Part-Store combination |
|
|
EAM-55272 Databridge: ProcessRequistion/SyncRequisition evt_object and evt_object_org are not pushed to the BOD when Req is approved |