Base Views V_CUST_FUTURE_INV_POSITION and V_FUTURE_INV_POSITION With Customer Order Type Are Not Excluded (Doc ID 2033796.1)

Last updated on APRIL 10, 2017

Applies to:

Oracle Retail Merchandising System - Version 14.0.1 and later
Information in this document applies to any platform.

Symptoms

Base views V_CUST_FUTURE_INV_POSITION and V_FUTURE_INV_POSITION in Oracle Data Access Schema (DAS) are having issues where it is excluding the Purchase Orders but not Transfers, with type as 'Customer Order'.

Steps to Reproduce:

1. Create the DAS view  V_FUTURE_INV_POSITION in local schema. 

2. Gather its data and not it excludes records with PO type ='CO', but it includes the records with tsf_type='CO'. 

3. As per <Document 1599704.1> Oracle Retail Merchandising Data Access Schema (DAS) Developer’s Guide, Release 14.0 and 14.1,  the view V_AVAIL_INV_POSITION should include the back order quantity.

AVAIL_QTY: ITEM_LOC_SOH.STOCK_ON_HAND – [ITEM_LOC_SOH.TSF_RESERVED_QTY + ITEM_LOC_SOH.CUSTOMER_RES +, ITEM_LOC_SOH.CUSTOMER_BACKORDER + ITEM_LOC_SOH.NON_SELLABLE_QTY + ITEM_LOC_SOH.RTV_QTY]

But in the 0293_v_avail_inv_position.sql file, ITEM_LOC_SOH.CUSTOMER_BACKORDER is not included as below:

However it is available in the file 0242_v_avail_inv_position.sql

Changes

 

Cause

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