5.22.2 Exception Messages

Below is a list of error messages generated during execution. They can be viewed in the ‘view log’ from UI or in FSI_MESSAGE_LOG table after filtering for the given batch_run_id. Appropriate messages are also logged on successful completion of railure of the utility, as the case may be.

Following error messages may be logged during execution:

• Exception 1: No records found in STG_BEHAVIOUR_PATTERN_NRP for <DATE>

  STG_* table has no records for the chosen execution date

• Exception 2: Error in Wrapper_bp_loader: <ENGINE_GENERATED_ERROR_MESSAGE>

  Execution of the utility failed due to some unexpected internal error

• Exception 3: Issue in look_up_tbl procedure: <ENGINE_GENERATED_ERROR_MESSAGE>

  Procedure to look-up values against matching tables failed; this is an internal error

• Exception 4: Issue in procedure: key_val_look_up: <ENGINE_GENERATED_ERROR_MESSAGE>

  Procedure to look-up key-value pairs against matching tables failed; this is an internal error

• Exception 5: ROW # <ROWNUM>: N_PATTERN_CD out of range.

  N_PATTERN_CD exceeded 99999

• Exception 6: ROW # <ROWNUM>: N_TENOR is not a valid number (must be >0).

  Self-explanatory

• Exception 7: ROW # <ROWNUM>: BEHAVIOUR TYPE DOES NOT MATCH VALID BEHAVIOUR TYPES

  Behaviour Pattern Type for a definition must be one of NM, NP or DR

• Exception 8: ROW # <ROWNUM>: TENOR UNIT DOES NOT MATCH VALID TENOR UNITS.

  Tenor Units must be one of D, M or Y

• Exception 9: ROW # <ROWNUM>: BEHAVIOUR SUB-TYPE EITHER DOES NOT EXIST OR IS INCORRECT FOR GIVEN BEHAVIOUR TYPE.

  Behaviour Sub-Type in a given pattern set must be as follows: <BEHAVIOUR TYPE>::[VALID SUB-TYPES] ::: NM[CR,VL], NP[SS,DF,L] & DR[SD,SR,UD,UR,U,S]

• Exception 10: ROW # <ROWNUM>: Warning: Replicating_Portfolio_Flag was NOT NULL but neither Y nor N; Will be replaced with N

  Self-explanatory

• Exception 11: ROW # <ROWNUM>: New pattern code but name is already in use for PATTERN_CD: <PATTERN_CD_NAME>. Please note names are NOT case sensitive.

  The pattern will be rejected as two pattern code definitions cannot have the same name

• Exception 12: ROW # <ROWNUM>: Warning: PATTERN_CODE already exists in FSI_BEHAVIOUR_PATTERN_MASTER with name: <NAME>. This name will be retained. Only the newer(date) of these two records will be kept.

  If a pattern code present in STG_* table already exists in the FSI_*_MASTER table, then the FSI_* table will be updated with the new definition but the name from FSI_*_MASTER will be retained if the date of execution for the batch is older than that for which the record already exists in the MASTER table.

• Exception 13: Error in Dq_validator: <ENGINE_GENERATED_MESSAGE>

  Function for validating STG_* table records failed; this is an internal error

• Exception 14: Definitions with negative N_PATTERN_PERCENTAGE. This PATTERN_CD will be ignored.

  Some pattern definitions the STG_* table had negative percentage values

• Exception 15: Pattern codes with N_PATTERN_PERCENTAGE violation found (>100). These will be ignored.

  Account percentage allocation across behaviour pattern types in a Pattern definitions in STG_* table must add to 100

• Exception 16: No violations of N_PATTERN_PERCENTAGE found for any pattern code & behaviour type combination.

  The definitions that remained after data quality checks had no anomalies in their pattern percentages

• Exception 17: Error in procedure percentage_chk: <ENGINE_GENERATED_MESSAGE>

  The percentage checker failed; this is an internal error

• Exception 18: Duplicate older Behaviour Pattern Definition in STG_TABLE. It will be ignored.

  The pattern definitions in STG_* table will be ignored if they are older than those in MASTER table

• Exception 19: Date comparison check passed; either no clashes found between STG_BEHAVIOUR_PATTERN_NRP records and FSI_BEHAVIOUR_PATTERN_MASTER records or all definitions in Stage Table were older.

  Self-explanatory

• Exception 20: Error in flg_older: <ENGINE_GENERATED_MESSAGE>

  Procedure for verification of date-clashes between new records in STG_* and those already present in FSI_* MASTER failed; this is an internal error

• Exception 21: Error During Merge Operation in FSI_BEHAVIOUR_PATTERN_MASTER: <ENGINE_GENERATED_MESSGE>

  Records could not be inserted into FSI_BEHAVIOUR_PATTERN_MASTER; this is either an internal error or a Primary Key violation

• Exception 22: Error During Merge Operation in FSI_BEHAVIOUR_PATTERN_DETAIL: <ENGINE_GENERATED_MESSGE>

  Records could not be inserted into FSI_BEHAVIOUR_PATTERN_DETAIL; this is either an internal error or a Foreign Key violation

• Exception 23: Could not clean-up old records for batch run id: <BATCH_RUN_ID>

  Previous error messages in FSI_MESSAGE_LOG for the same BATCH_RUN_ID as run could not be deleted; The execution may have still gone through