Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC)

MOSC Banner

PBCS: how to include a source column as an FDMEE drill-through attribute when length >20

edited Oct 19, 2015 10:57PM in Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC) 2 commentsAnswered ✓

I am loading a source file into Planning via FDMEE (PBCS). The file has transaction level detail which is aggregated by FDMEE before being exported to Planning. The goal is to drill back from a balance in Smart View to the FDMEE Drill Through Details page to see the transactions that contributed to the balance.

The source file contains several transaction-specific columns which I would like to include in the Drill Through Details display. An example is Journal Description. However, if I try to include this field an Attribute in the Import Format, FDMEE fails because the relevant column in TDATASEG_T has a width of 20 characters (whereas Journal Description may be much longer than that).

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center