Search Results gcs_gl_ji_groups_v

Overview

The GCS_GL_JI_GROUPS_V view is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the GCS – Financial Consolidation Hub product. Its documented description is "GL_INTERFACE source and group id information." The view exists to expose a consolidated, de-duplicated list of journal import groups together with the journal source and the set of books under which each group was created. In Oracle EBS 12.1.1 and 12.2.2, journal import processing is driven by the GL_INTERFACE and GL_INTERFACE_CONTROL tables, which use a GROUP_ID to bracket each set of interface lines and a REQUEST_ID to identify the concurrent request that loaded them.

The view plays a supporting role in integration and diagnostics rather than transactional accounting. It gives consolidation and reporting logic a single, uniform source for enumerating import groups, resolving each group back to a user-facing journal source name (USER_JE_SOURCE_NAME), and identifying the ledger. This is particularly relevant when users search on the term "user_je_source_name," which is one of the principal output columns of the view.

Underlying Base Objects

Although ETRM documents no referenced base objects for this view, the view definition itself references two dictionary tables:

• GL_INTERFACE – the journal import interface table that stores incoming journal lines and header attributes, including GROUP_ID, USER_JE_SOURCE_NAME, SET_OF_BOOKS_ID, and REQUEST_ID.
• GL_INTERFACE_CONTROL – the control table that tracks each interface load, including INTERFACE_TABLE_NAME, GROUP_ID, REQUEST_ID, and JE_SOURCE_NAME.
• GL_JE_SOURCES – the journal source definition table, joined to GL_INTERFACE_CONTROL to translate the internal JE_SOURCE_NAME into the user-visible USER_JE_SOURCE_NAME.

The view text is a UNION of two branches. The first selects directly from GL_INTERFACE where GROUP_ID is not null, returning a NULL INTERFACE_TABLE_NAME and the USER_JE_SOURCE_NAME stored on the interface rows. The second selects from GL_INTERFACE_CONTROL joined to GL_JE_SOURCES, filtering out groups whose interface table is GL_INTERFACE (via NVL to 'GL_INTERFACE'), and returns UPPER(INTERFACE_TABLE_NAME). The result sets are combined and ordered by the first column, GROUP_ID, producing a distinct list of group, source, ledger, and request combinations.

Key Columns

• GROUP_ID – the journal import grouping identifier that links interface lines and their control record; the view's ordering column.
• INTERFACE_TABLE_NAME – the alternate interface table (for example, a non-standard import table) when the group originates outside GL_INTERFACE; otherwise NULL.
• USER_JE_SOURCE_NAME – the user-facing journal source name, such as Payables or Manual, used to attribute imported journals.
• SET_OF_BOOKS_ID – the ledger identifier under which the group was loaded; in 12.2.2 this corresponds to the ledger defined in GL_LEDGERS.
• REQUEST_ID – the concurrent request that created the group, useful for tracing an import back to its submission.

Common Use Cases and Queries

The view is typically used to validate that journal imports were grouped and sourced correctly before or after running the Journal Import concurrent program. A common query enumerates all groups for a given source and ledger:

• SELECT group_id, user_je_source_name, set_of_books_id, request_id FROM apps.gcs_gl_ji_groups_v WHERE user_je_source_name = :source AND set_of_books_id = :sob;
• SELECT group_id, request_id, interface_table_name FROM apps.gcs_gl_ji_groups_v ORDER BY group_id;
• SELECT DISTINCT user_je_source_name FROM apps.gcs_gl_ji_groups_v;

Because the view de-duplicates by GROUP_ID and returns only groups present in the interface or control tables, it is an effective first-stop diagnostic when an import appears missing or mis-attributed to the wrong journal source.