Mapper in Conditional Assumption Fails to Select Hierarchy Nodes to Assign Transfer Rates (Doc ID 2525954.1)

Last updated on MAY 03, 2023

Applies to:

Symptoms

In Oracle Financial Services Funds Transfer Pricing (FTP) 6.1.1.1, when attempting to process a Transfer Pricing Rule containing a Conditional Assumption that uses a hierarchy mapper, it does not work.  The mapper fails to filter for the node values to assign the Transfer Rates.

If you run the SQL query from the ofstp.xxxxxxx.log referencing FSI_COND_ASSUMPTION and REV_HIERARCHY_FILTER, the query returns the wrong value for HIERARCHY_SYS_ID.  For example:

select FSI_M_TRANSFER_PRICE_RULE.transfer_price_sys_id,
     FSI_M_TRANSFER_PRICE_RULE.product_id,
     FSI_M_TRANSFER_PRICE_RULE.ccy_cd,
     FSI_COND_ASSUMPTION.cond_sys_id, FSI_COND_ASSUMPTION.sequence,
     FSI_COND_ASSUMPTION.range, FSI_COND_ASSUMPTION.filter_sys_id,
     REV_HIERARCHY_FILTER.HIERARCHY_SYS_ID
from FSI_M_TRANSFER_PRICE_RULE, FSI_COND_ASSUMPTION,
     REV_HIERARCHY_FILTER
where FSI_COND_ASSUMPTION.filter_sys_id =
     REV_HIERARCHY_FILTER.Sys_Id_Num
and FSI_COND_ASSUMPTION.cond_sys_id =
     FSI_M_TRANSFER_PRICE_RULE.cond_sys_id
and FSI_COND_ASSUMPTION.sequence =
     FSI_M_TRANSFER_PRICE_RULE.cond_sequence
and FSI_M_TRANSFER_PRICE_RULE.transfer_price_sys_id = 123456
order by FSI_COND_ASSUMPTION.sequence, FSI_COND_ASSUMPTION.range

The query returns the wrong HIERARCHY_SYS_ID value which is stored in REV_HIERARCHY_FILTER.  The mapper is pointing to the wrong Hierarchy.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.