My Oracle Support Banner

Troubleshooting Reverse Population Issues When Populating OFSA_DETAIL_LEAVES, OFSA_DETAIL_ORG_UNIT, and OFSA_DETAIL_OTHER_COA (Doc ID 1990889.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Purpose

This document describes how to fix setup related issues for the Reverse Population program, Batch_Member_Load, so the desired values are populated in OFSA_DETAIL_LEAVES, OFSA_DETAIL_OTHER_COA, and OFSA_DETAIL_ORG UNIT.

For example, the document covers the following:

Reverse Population moves dimension member data as follows for the seeded dimensions:

DIM_COMMON_COA_B, _TL, and _ATTR into OFSA_DETAIL_LEAVES
DIM_ORG_UNIT_B, _TL, and _ATTR into OFSA_DETAIL_ORG_UNIT
DIM_PRODUCTS_B, _TL, and _ATTR into OFSA_DETAIL_OTHER_COA where LEAF_NUM_ID = 4
DIM_GL_ACCOUNT_B, _TL, and _ATTR into OFSA_DETAIL_OTHER_COA where LEAF_NUM_ID = 2

Name and description values are transferred into OFSA_LEAF_DESC.

Note: Hierarchy data is also transferred into OFSA_IDT_ROLLUP.  However, this document does not cover the Hierarchy process.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 Known issue with Reverse Population in version 6.0.3
 Verifying Product ID values have a valid Common Chart of Account assigned
 Populating the O_ORG_ID column in DETAIL_ORG_UNIT
 How to Run the Reverse Population Program
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.