New Table Fails FTP Cash Flow and Non-Cash Flow Table Classification (Doc ID 1292594.1)

Last updated on AUGUST 15, 2013

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.2 and later
Oracle Financial Services Funds Transfer Pricing - Version 5.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Checked for relevance on 15-Aug-2013.

Symptoms

In Oracle Financial Services Funds Transfer Pricing (FTP), you are trying to classify a new table as "TP Non-cash flow".  When the table fails the classification for TP Non-Cash Flow, you notice that the list of columns a table is required to have for this classification is different from the list of columns in the "TP Basic Requirements" Super Class.

Use the following query to review the list of columns required for TP Non-Cash Flow:

select * from REV_PROPERTY_COLUMNS
where table_property_cd in (select distinct table_property_cd
   from REV_TABLE_CLASS_PROPERTIES where table_classification_cd = 210);

(210 = TP Non-Cash Flow)

Four columns returned in the list do not exist in the TP Basic Requirements Super Class:

HISTORIC_OAS_ALT
HISTORIC_STATIC_SPREAD_ALT
CUR_STATIC_SPREAD_ALT
CUR_OAS_ALT

You expect the column requirements for classifying a table as TP Non-Cash Flow to match the columns listed in the TP Basic Requirements Super Class in the Erwin Data Model.

Note: These columns do exist in the TP Option Costing Requirements Super Class.

According to the Data Model Utilities Guide, you need the following Super-class entities for TP Non-Cash Flow:

BASIC_INSTRUMENT_REQ
LEAF_COLUMNS
MULTI_CUR_REQ
CASH_FLOW_EDIT_REQ
TP_BASIC_REQ

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