Oracle® Communications Data Model Reference Release 11.3.2 E28440-05 |
|
|
PDF · Mobi · ePub |
This chapter describes the Oracle Communications Data Model utility scripts.
This chapter includes the following sections:
The Calendar population scripts consist of two one-time installation packages.
The Calendar population scripts include the following packages:
calendar_population_header.sql
calendar_population_body.sql
Running these packages does the following:
Prepares necessary changes for the OCDM_SYS schema.
Creates the Calendar_Population package that contains the following procedures:
RUN(in_setup_start_date, in_setup_no_years) is the main procedure to populate everything about calendar.
RBIW_Base_Time_Tables_ddl creates the base table needed to support multiple hierarchies: Business or Calendar.
RBIW_Populate_Time_Hier_Bsns(in_setup_start_date, in_setup_no_years) sets up the data in base table for the Business hierarchy as specified in setup or install section.
RBIW_Populate_Time_Hier_Clndr(in_setup_start_date, in_setup_no_years) sets up the data in base table for the Calendar hierarchy as specified in setup or install section.
RBIW_Time_hier_Star sets up the Time hierarchy reporting layer tables.
RBIW_Time_Views sets up the Time hierarchy reporting layer views, star and hybrid snowflake views.
RBIW_Populate_Time_Transform populates the Time transformation tables using the base Time tables or views created above. It populates transformation data for both hierarchies: Business and Calendar.
To populate calendar data:
Log in to OCDM_SYS user.
Execute the following SQL statement:
exec Calendar_Population.run(date,num_years);
where, date is the start date with which you want to populate calendar data. It is of type CHAR and should be input in the format 'YYYY-MM-DD' (for example,'2005-05-18'). num_years is the number of years to populate calendar data, which should be INTEGER.