My Oracle Support Banner

OBIA 11g: An Unposted Journal Can Be Deleted in EBS But OBIA Does Not Have The Logic To Delete These Journals in Data Warehouse (Doc ID 2180011.1)

Last updated on FEBRUARY 23, 2021

Applies to:

Business Intelligence Applications Consumer - Version and later
Information in this document applies to any platform.


SILOS_SIL_GLOTHERFACT has a Soft delete preprocess step that is using W_GL_OTHER_F_PE to identify deleted records but there is no code to populate W_GL_OTHER_F_PE table

Please confirm how should W_GL_OTHER_F_PE table get populated?

Issue: An un-posted journal can be deleted in EBS but OBIA does not have the logic to delete these journals in warehouse.

Example: Lets say a user creates a journal for account 1234, Ledger ABC and JAN-16 period for $100.
                 This is un-posted but gets picked up by OBIA incremental load and gets loaded in W_GL_OTHER_F with un-posted status.
                 Next day, user deletes this journal in EBS and creates another journal for the same combination for $200.
                 When this journal gets loaded in OBIA, if I run a report aggregated at account 1234, Ledger ABC and JAN-16 level,
                 OBIA will show $300 but EBS will show $200 as 1st journal was deleted in EBS but it did not get deleted in OBIA.


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

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