Results for “gl_intercompany_accts_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_INTERCOMPANY_ACCTS_V is a General Ledger view that exposes the intercompany account setup used by Oracle EBS to determine the balancing account for intercompany journal entries. The view presents the combination of journal source, journal category, and the debit/credit indicator (DR_CR_CODE) that together identify which intercompany account is applied when a journal is generated between balancing entities within a set of books. The ETRM metadata designates this object as "10SC ONLY" and records that it is not implemented in the documented database instance, meaning the definition is retained for reference but the underlying view was not created in the environment captured by that metadata.

The name of the view and the DR_CR_CODE column are directly relevant to the DR_CR lookup type, since the view resolves the debit/credit code against the GL_LOOKUPS table using LOOKUP_TYPE = 'DR_CR'. This makes the view useful in reporting and integration contexts where a caller must know, for a given source and category, whether a separate intercompany account is maintained for debits versus credits, and what description accompanies that code.

Underlying Base Objects

The view is defined over four base objects:

• GL_INTERCOMPANY_ACCOUNTS (aliased INT) — the primary table holding the intercompany account setup rows, keyed by journal source, journal category, and DR_CR_CODE, scoped to a SET_OF_BOOKS_ID.
• GL_JE_SOURCES (aliased SRC) — provides the user-defined journal source name, joined on JE_SOURCE_NAME.
• GL_JE_CATEGORIES (aliased CAT) — provides the user-defined journal category name, joined on JE_CATEGORY_NAME.
• GL_LOOKUPS (aliased LOOK, restricted to LOOKUP_TYPE = 'DR_CR') — provides the descriptive text for the debit/credit code.

The joins are all equality joins without an outer join, so a row is returned only when matching source, category, and DR_CR lookup entries exist. The ETRM metadata documents no additional referenced objects beyond these four.

Key Columns

• ROW_ID — the ROWID of the underlying GL_INTERCOMPANY_ACCOUNTS row, providing a unique handle for the setup record.
• JE_SOURCE_NAME — internal name of the journal source from GL_INTERCOMPANY_ACCOUNTS.
• USER_JE_SOURCE_NAME — the user-facing source name from GL_JE_SOURCES.
• JE_CATEGORY_NAME — internal name of the journal category.
• USER_JE_CATEGORY_NAME — the user-facing category name from GL_JE_CATEGORIES.
• DR_CR_CODE — the debit or credit indicator stored on the intercompany account setup; it is the code resolved against the DR_CR lookup type.
• SET_OF_BOOKS_ID — the ledger/set of books to which the intercompany account configuration applies.
• TYPE — the description text from GL_LOOKUPS for the DR_CR code, giving a readable label for the debit/credit classification.

Common Use Cases and Queries

The view is typically queried to audit or report intercompany account assignment by source and category, and to translate the internal DR_CR_CODE into a readable description. A representative query is:

• SELECT je_source_name, user_je_source_name, je_category_name, user_je_category_name, dr_cr_code, set_of_books_id, type FROM gl_intercompany_accts_v WHERE set_of_books_id = :p_sob ORDER BY user_je_source_name, user_je_category_name, dr_cr_code;

Because the definition resolves the DR_CR lookup inline, consumers do not need a separate join to GL_LOOKUPS to obtain the description. In integration scenarios, the view can be used to validate that a source/category combination has the required debit and credit intercompany accounts configured before journal import or intercompany processing is attempted. Note that in the documented 12.2.2 environment this view is not implemented; implementations relying on it should confirm object existence and licensing, since the metadata marks it as 10SC only.