What Updates Are Required for Alphanumeric Dimensions Accumulation Type Code and Billing Code
(Doc ID 2746255.1)
Last updated on APRIL 20, 2021
Applies to:Oracle Financial Services Profitability Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)
The Out of the box (OOTB) setup / installation sets all key dimensions with NUMBER for MEMBER_DATA_TYPE_CODE. In order to enable alphanumeric dimensions, have updated these key dimensions to VARCHAR2 to maintain current values. After completing this, a few questions came up:
Question 1. Confirm that simply updating rev_dimensions_b to MEMBER_DATA_TYPE_CODE=VARCHAR2 (and refreshing web cache) is all that is needed to allow alphas in the org_unit/product/etc_CODE field?
Question 2. Per the user guide, Billing Method was given as an example of a dimension that can have alphas in the "code" column MEMBER_DATA_TYPE_CODE. However, this dimension is currently defined as NUMBER. Is this correct or should it be updated it to VARCHAR2?
Question 3. ACCUM_TYPE_CD is not showing up in the UI and it seems REV_DIMENSIONS_B may be incorrect for this dimension.
- Accum Type is available in the dimension drop down and data is populated in fsi_accumulation_type_cd/mls but interface screen is empty
- In the rev_dim_b table, MEMBER_CODE_COLUMN has this in it: ROLLUP_SIGNAGE_DISPLAY_CD. Is that correct or should it be ACCUMULATION_TYPE_CD? (FYI - this is also how it looks in OFSAA version 6.x)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document