FTP Rates Are Not Assigned Correctly When a Lower Level Node Has a Definition Which Should Override a Higher Level Definition (Doc ID 2761338.1)

Last updated on NOVEMBER 02, 2022

Applies to:

Symptoms

On FTP 8.0.7.4, Transfer pricing rates are not being assigned correctly when a lower level node has a rule definition which is expected to override the upper level definition in the product hierarchy.

Transfer Pricing Rule Example:

Liabilities 4617 > Transfer Pricing Method Definition Assigns 30 Day rate
  Other Liabilities 3850 > Transfer Pricing Method Definition Assigns 5 Year rate
      Savings Leaf 1468 > No Definition
    
  *** The process is ignoring the lower level node “Other Liabilities” definition and pricing with the upper level node ‘Liabilities” definition.

The issue can be traced the issue back to the FSI_PROCESS_NODE_MAP table entries which are incorrectly mapping to the upper level node when it should be mapped to the lower level node.
This issue is not consistent, since some lower level definitions are recognized and mapped properly while others are not.

FSI_PROCESS_NODE_MAP Entries:

NODE_MAP_ID PROD_ID CURRENCY TP_NODE
559 1468 USD 4617
==> Shows higher parent node 4617.

Expect:
NODE_MAP_ID PROD_ID CURRENCY TP_NODE
559 1468 USD 3850
 
EXPECTED BEHAVIOR
Expect the Transfer Pricing rule to use the rate assignment / definition from the node level closest to the leaf.  Any TP method definition which is at a higher parent node should not be used.

Cause

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