OFSAA FTP Process Does Not Complete With Conditional Assumptions in the Transfer Pricing Rule (Doc ID 1384497.1)

Last updated on JANUARY 02, 2015

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version: 5.5 and later   [Release: 5 and later ]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) - Version 7.2
Oracle Financial Services Analytical Applications (OFSAA) - Version 5.x

Symptoms

On Oracle Financial Services Funds Transfer Pricing (FTP) 5.5 when attempting to generate a Transfer Rate using a conditional assumption on FSI_D_TERM_DEPOSITS.ADJUSTABLE_TYPE_CD = 250, the following error occurs running command line:

ERROR
[ofsa@OFSAA bin]$ ./ofstp OFSATEST_200315_EXEC_20111011_1 TP TASK1 20103103 200315 USER1
Warning: iso88951 does not exist.
Rem = 0Host IP--> 172.17.56.74
HostIP... 172.17.56.74
Port... 6500
ClsUSmsConnect::ClsUSmsConnect, Forming Login Info statement

| strBatchId : OFSATEST_200315_EXEC_20111011_1 | strComponentId : TP | Process ID : 200315 | User ID : USER1|
Connection to the following database was successful: testhpk
Running TP, Process ID: 200315
terminate called after throwing an instance of 'RWBoundsErr'
[ofsa@OFSAA bin]

There are no additional errors thrown in the FTP Debug log. The log ends abruptly after the following statement:

Module Logging OFS calculation module data: select
select a.rowid, a.ORG_UNIT_ID, a.GL_ACCOUNT_ID, a.COMMON_COA_ID,
a.PRODUCT_ID, a.SBU_ID, a.ALM_COA_ID, a.id_number,
a.identity_code, a.as_of_date, a.cur_net_rate, a.percent_sold,
a.cur_book_bal, a.matched_spread_c, a.transfer_rate,
a.accrual_basis_cd, a.amrt_term, a.amrt_term_mult,
a.amrt_type_cd, a.cur_par_bal, a.cur_tp_per_adb,
a.cur_gross_rate, a.cur_payment, a.deferred_cur_bal,
a.deferred_org_bal, a.interest_rate_cd, a.last_reprice_date,
a.margin, a.margin_gross, a.margin_t_rate, a.maturity_date,
a.neg_amrt_eq_date, a.neg_amrt_eq_freq, a.neg_amrt_eq_mult,
a.neg_amrt_limit, a.neg_amrt_amt, a.net_margin_cd,
a.next_payment_date, a.next_reprice_date, a.org_par_bal,
a.org_payment_amt, a.org_term, a.org_term_mult,
a.origination_date, a.issue_date, a.pmt_adjust_date,
a.pmt_chg_freq, a.pmt_chg_freq_mult, a.pmt_decr_cycle,
a.pmt_decr_life, a.pmt_freq, a.pmt_freq_mult, a.pmt_incr_cycle,
a.pmt_incr_life, a.prior_tp_per_adb, a.rate_cap_life,
a.rate_chg_min, a.rate_chg_rnd_cd, a.rate_chg_rnd_fac,
a.rate_decr_cycle, a.rate_floor_life, a.rate_incr_cycle,
a.rate_set_lag, a.rate_set_lag_mult, a.remain_no_pmts_c,
a.reprice_freq, a.reprice_freq_mult, a.teaser_end_date,
a.t_rate_int_rate_cd, a.last_payment_date, a.int_type,
a.adjustable_type_cd, a.lrd_balance, a.instrument_type_cd,
a.compound_basis_cd, a.iso_currency_cd, a.tp_average_life,
a.tp_duration, a.tp_effective_date, a.RESIDUAL_AMOUNT,
a.MATURITY_AMOUNT, a.AMORT_METH_PDFC_CD, a.EXPECTED_BAL,
a.EXPECTED_BAL_GROWTH_PCT, a.OFFSET_PERCENT, a.MINIMUM_BALANCE,
a.BEHAVIOUR_TYPE_CD, a.BEHAVIOUR_SUB_TYPE_CD,
a.DEVOLVEMENT_STATUS_CD
from FSI_D_TERM_DEPOSITS a
where a.ISO_CURRENCY_CD = :ISO_CURRENCY_CD
and a.PRODUCT_ID = :PRODUCT_ID
and as_of_date = to_date('03/ 31/ 2010', 'mm/ dd/ yyyy')

STEPS
The issue can be reproduced at will with the following steps:
1. create a tp rule with assumption defined at node level
2. define conditional assumptions for one of the leaves under that particular node
3. execute the tp rule

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms