Datastage FMS J_Flattener_ESourceSummerSetID and tree's effective date (Doc ID 1901008.1)

Last updated on MARCH 16, 2016

Applies to:

PeopleSoft Enterprise EPM Financials Warehouse - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.

Goal

Customer noticed that a small handful of accounts were not populating in the table H_ACCOUNT. Upon investigation, discovered that the accounts were created after tree's effective date. The tree that was imported in to EPM has a date of 7.1.2010, but the accounts have an effective date of 7.1.2012. The hierarchy process is looking for accounts that have an effective date that occurred on or before the effective date of the tree.

Customer think that he process would operate in the opposite manner, pulling in accounts with an effective date on or after 7.1.2010. Customer initially going to copy forward the tree with a 7.1.2012 effective date, but the business office opted to insert effective dated rows of 1.1.1901 on the account setup (which does resolve the issue). Customer wanted to check on the reasoning and what the recommended best practice is?
 

Solution

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