1. Implementation Guide
  2. Integration with Merchandising
  3. Using RDE for Calendar Setup (Gen 2 Architecture)

Using RDE for Calendar Setup (Gen 2 Architecture)

RDE can be used to integrate the calendar from Merchandising for initial setup of a new RAP environment; however there are several manual steps you must take to perform this activity. You have the option of following the steps below, or you can perform the file-based calendar load as defined in Calendar and Partition Setup. Whichever option you choose, the calendar must be set up before you can load any other data from Merchandising.

  1. The out-of-box Merchandising calendar does not conform to the preferred RAP calendar structure. The RAP calendar must start from Day 1 of a fiscal year, and the Merchandising calendar does not (if no changes were made to it after provisioning). You must use the Calendar Maintenance functions of Merchandising to edit the business calendar, adding or deleting periods such that the first fiscal period defined is period 1 of the fiscal year, and the first date for that period is day 1 of that fiscal year. Refer to the Configure Calendar section of the Merchandising Implementation Guide for details.. For example, if your fiscal calendar starts in February 2020, then the first record in the CALENDAR table must be for this same month. YEAR_454 will be 2020 and MONTH_454 will be 2.

  2. Configure C_ODI_PARAM for your START_DT and END_DT. START_DT must be set in one of these ways:

    1. The first day of a fiscal year in the calendar (that is, the same date as the FIRST_DAY value for the first fiscal period of an FY).

    2. Some date earlier than anything in the CALENDAR table. If your first CALENDAR period is February 2020, then START_DT can be set to 20190101. The only reason to do this is if you want the Gregorian calendar to have additional Gregorian years available for any downstream use.

  3. Configure the jobs in the AIF DATA schedule for loading the data. You will need the RDE job RDE_EXTRACT_DIM_P12_MCALPERIODSDE_JOB to extract the data, which is part of the RDE_EXTRACT_DIM_INITIAL_ADHOC process. Configure the CALENDAR_LOAD_ADHOC process to load this data and perform initial environment setup activities. You must disable the following jobs:

    • COPY_SI_CALENDAR_JOB

    • STG_SI_CALENDAR_JOB

    • SI_W_MCAL_PERIODS_DS_JOB

  4. Run RDE_EXTRACT_DIM_P12_MCALPERIODSDE_JOB to extract the data from Merchandising and verify that the table W_MCAL_PERIOD_DS contains the full calendar information by querying it from APEX.

  5. Run the modified CALENDAR_LOAD_ADHOC process and all later steps starting with step 4 in the Calendar and Partition Setup.

  6. If you have any failure on the DIM_CALENDAR_VALIDATOR_JOB, it means your Merchandising calendar may need more changes to align with the RAP data requirements. Modify the data in the source and start over, being sure to use C_LOAD_DATES_CLEANUP_ADHOC to clear any failure statuses from the database before restarting.

If the validator job rule CAL_R2 continues to happen after updating the Merchandising calendar, but you know that your first calendar year is not meeting the requirements and want to bypass the error for now, then you would need to update the table C_DIM_RULE_LIST from the Control & Tactical Center. Change the error type for this rule to W so that it only throws a warning in the batch program instead of failing. For example, if your Merchandising calendar starts in 2010 and you are not going to load any data until 2020 in RAP, then having an invalid first year of the calendar is not going to block you from other data load activities.