Mis-match in Expressions Between T2T 'STAGE' XML and 'Source Mapping' XML in ALM 8.0.4 (Doc ID 2276334.1)

Last updated on JUNE 16, 2017

Applies to:

Oracle Financial Services Asset Liability Management - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Asset Liability Management (ALM) 8.0.4, for the seeded Data Mapping T2Ts, you see a mis-match in an Expression for CUR_PAR_BAL between the "STAGE" xml file and the "Source Mapping" xml file.

In /<ftpshare>/<infodom>/erwin/Sources/<Source>, in T2T_INVESTMENTS.mapping.xml, the Expression for CUR_PAR_BAL uses n_eop_bal:

<MAP>
  <SOURCE TABLENAME="EXPRESSION" TYPE="FIELD">
     <COLUMN FIELDORDER="7" ID="CUR_PAR_BAL">
       <LENGTH>0</LENGTH>
       <DATATYPE>Number</DATATYPE>
       <PRECISION/>
       <SCALE/>
       <NULLIF/>
       <DEFAULTIF/>
       <STARTPOSITION>1</STARTPOSITION>
       <EXPRESSION>STG_INVESTMENTS.n_eop_bal</EXPRESSION>
     </COLUMN>
   </SOURCE>

However, in /<ftpshare>/STAGE/<Source>, in T2T_INVESTMENTS.xml, the Expression for CUR_PAR_BAL uses n_eop_bal_lcy:

<COLUMN ID="CUR_PAR_BAL">
   <DATATYPE>Number</DATATYPE>
   <LENGTH>0</LENGTH>
   <PRECISION/>
   <SCALE/>
   <MANDATORY/>
   <FIELDFORMAT/>
   <NULLIF/>
   <DEFAULTIF>Number(14,2)</DEFAULTIF>
   <FIELDORDER>7</FIELDORDER>
   <STARTPOSITION/>
   <EXPRESSION>STG_INVESTMENTS.n_eop_bal_lcy</EXPRESSION>
</COLUMN>


There is also an issue for PMT_FREQ in T2T_MM_CONTRACTS:

In /<ftpshare>/STAGE/<Source>, PMT_FREQ uses an expression that existed in 8.0.2:

<EXPRESSION>case when stg_mm_contracts.N_COUPON_FREQUENCY=-1 then NULL when
stg_mm_contracts.N_COUPON_FREQUENCY=0 then NULL when
stg_mm_contracts.N_COUPON_FREQUENCY=1 then 1 when
stg_mm_contracts.N_COUPON_FREQUENCY=2 then 6 when
stg_mm_contracts.N_COUPON_FREQUENCY=3

However, in /<ftpshare>/<infodom>/erwin/Sources/<Source>, the entry for PMT_FREQ no longer uses an Expression.  Instead, PMT_FREQ is directly mapped to "n_int_payment_frequency".

You expect both files to be in sync and contain the same Expressions.

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