Hard-coded Dates In DWA_ARPU_BASE_CUST_TYP
Last updated on NOVEMBER 02, 2016
Applies to:Oracle Communications Data Model - Version 11.3.1 and later
Information in this document applies to any platform.
You are deploying a project with OCDM version 18.104.22.168.
You are having some doubts regarding the materialized view DWA_ARPU_BASE_CUST_TYP and the way its constructed.
Looking into its code, we have found the following line:
And DWR_PROD_SBRP.PROD_SBRP_STRT_DT BETWEEN to_date(20130101,'yyyymmdd') and to_date(20130201,'yyyymmdd') -- TEMPORARY --l_start_date and l_end_date
This seems to be a date hard-coded into this SQL code.
How can we change this for our project requirements? Is this an error? Is this expected? Do you have any specification for this line? What types of dates ranges should this clause include?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms