My Oracle Support Banner

Hard-coded Dates In DWA_ARPU_BASE_CUST_TYP (Doc ID 2189410.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle Communications Data Model - Version 11.3.1 and later
Information in this document applies to any platform.




NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.


You are deploying a project with OCDM version

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:

where 1=1
  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?




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.