PURGECOMPLETEDUIN BATCH Does Not Purge Data Older Than 365 Days
Last updated on MAY 11, 2016
Applies to:Oracle Retail Store Inventory Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
Why PURGECOMPLETEDUIN BATCH not Purged data older than 365 days when status is 6 and 8?
As per PurgeCompletedUINDetail batch UIN’s in status 6(Remove from Inventory)and 8(Missing) considered as completed UIN’s hence they must be deleted but they were not. As per STOCK COUNT package , stock count is scheduled for these UIN’s with same status, hence causes the UIN’s to present in child tables due to which batch not delete from parent table. This batch considering these status while scheduling stock count.
So batch considered these as completed UIN's but in Stock Count package it is defined as open UIN's, Hence stock count is scheduled for these UIN'S although they are not even present in stores.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms