B.12 Adding a Custom Run Purpose

To add a new custom run purpose, follow these steps to add an entry in the Lookup and Process Purpose Map tables:

  1. Add an entry in the FSI_LRM_LOOKUP_TL table.
  2. Execute the following SQL query in the atomic schema by replacing the placeholders PURPOSE_ID and PURPOSE_DESCRIPTION.

    insert into FSI_LRM_LOOKUP_TL (LOOKUP_CD, LANG_CODE, CATEGORY_ID, LOOKUP_DESCRIPTION) values ('##PURPOSE_ID##', 'en_US', '10', '##PURPOSE_DESCRIPTION##') /

    Where,

    PURPOSE_ID value is any value greater than 50. PURPOSE_DESCRIPTION is a description of the new purpose.

  3. Add an entry in the FSI_LRM_PROCESS_PURPOSE_MAP table.
  4. Add the task entries for the ##PURPOSE_ID## added in step 1, in the Process Purpose map table for both Contractual and BAU Runs. This gives the pre and post Tasks in the Run.
  5. To enable the NSFR option for any of the custom run purposes, enter the respective Run purpose code as comma separated values against the component code NSFR_ENABLED in the SETUP_MASTER table. This code enables the NSFR option in the Run Management screen for the mentioned purposes.

    select * from setup_master where v_component_code like 'NSFR_ENABLED'

  6. In the fsi_lrm_process_purpose_map table, update the F_FCAST_ENABLED column with the appropriate values, for all the runs. The available values are 1 or 2, where:
    • 1 is Yes, which indicates that forecasting is enabled.
    • 2 is No, which indicates that forecasting is not enabled.