Search Results gl_set_of_books

Overview

IGC.IGC_CC_GROUPS is a transaction-table owned by the IGC schema within Oracle E-Business Suite, registered under the application design data as IGC.IGC_CC_GROUPS. It stores the definition of approval groups — logical collections of users who share a common level of approval authority. In the context of a user searching for "gl_set_of_books," this table matters because its primary business key is anchored to a Set of Books: every approval group is scoped to a single accounting book. The relationship between GL_SET_OF_BOOKS and IGC_CC_GROUPS is documented as an optional one-to-many association, meaning a given Set of Books may have zero, one, or many approval groups, each distinguished by a distinct CC_GROUP_ID.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, reflecting its transactional nature. It is not an interface or view object; it is a base table with twenty-five documented columns. The table carries standard "Who" audit columns and a descriptive flexfield segment block (CONTEXT plus ATTRIBUTE1 through ATTRIBUTE15), which is characteristic of a core application entity that supports extensibility. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, suggesting this object can be modeled as an independent hub rather than a link or satellite, though its SET_OF_BOOKS_ID foreign key conceptually ties it into the GL book dimension.

Key Information Stored

The table's most important columns fall into three groups: identifiers, descriptive attributes, and audit/flexfield columns.

• CC_GROUP_ID (NUMBER) — the surrogate primary key, defined by the CC_GROUP_PK constraint and backed by the unique index IGC_CC_GROUP_U1. This is the access group defining column and the primary join key to dependent objects.
• SET_OF_BOOKS_ID (NUMBER) — the accounting books defining column. This is the attribute that links an approval group to its owning Set of Books, and it participates in the composite business-key index IGC_CC_GROUPS_U2.
• CC_GROUP_NAME (VARCHAR2 30) — the human-readable access group name. Combined with SET_OF_BOOKS_ID, it forms the unique business key IGC_CC_GROUPS_U2, guaranteeing that no two groups within the same Set of Books share a name.
• CC_GROUP_DESC (VARCHAR2 150) — a free-text description of the approval group's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard Who columns. LAST_UPDATED_BY and CREATED_BY resolve to FND_USER.USER_ID, while LAST_UPDATE_LOGIN resolves to FND_LOGINS.LOGIN_ID.
• CONTEXT (VARCHAR2 30) and ATTRIBUTE1 through ATTRIBUTE15 (VARCHAR2 150 each) — the descriptive flexfield context and segment columns, allowing customers to extend the group definition without schema changes.

The distinction between the surrogate key (CC_GROUP_ID) and the business-key candidate (SET_OF_BOOKS_ID, CC_GROUP_NAME) is important: developers should join on CC_GROUP_ID, while business validation and uniqueness enforcement rely on the composite index.

Common Use Cases and Queries

The most frequent scenario is retrieving all approval groups belonging to a specific Set of Books, typically to populate a selection list or to drive approval-routing logic in purchasing or intercompany transactions. A representative query follows.

• List groups for a book: SELECT cc_group_id, cc_group_name, cc_group_desc FROM igc.igc_cc_groups WHERE set_of_books_id = :book_id ORDER BY cc_group_name;
• Resolve the book for a known group: SELECT set_of_books_id, cc_group_name FROM igc.igc_cc_groups WHERE cc_group_id = :group_id;
• Enforce business-key uniqueness during data migration by checking for duplicates on SET_OF_BOOKS_ID and CC_GROUP_NAME before insert.
• Report reference data across books, including flexfield usage, by selecting CONTEXT and populated ATTRIBUTEn columns.

Because the FK relationship to GL_SET_OF_BOOKS is optional, queries should not assume every Set of Books has groups; use an outer join when producing book-level inventories.

Related Objects

The following objects are significant in relation to IGC_CC_GROUPS based on the documented relationships.

• GL.GL_SETS_OF_BOOKS — the parent book definition, joined on gl_sets_of_books.set_of_books_id = igc_cc_groups.set_of_books_id. This is the optional one-to-many relationship documented for this table.
• FND_USER — referenced by CREATED_BY and LAST_UPDATED_BY for audit resolution; joins on fnd_user.user_id = igc_cc_groups.created_by (or last_updated_by).
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN; joins on fnd_logins.login_id = igc_cc_groups.last_update_login.
• IGC_CC_GROUP_PK — the primary-key constraint on CC_GROUP_ID, defining the row identity used by all dependent IGC approval tables.
• IGC_CC_GROUPS_U2 and IGC_CC_GROUP_U1 — the two unique indexes that enforce business and surrogate uniqueness respectively.

Dependent IGC approval-routing and intercompany control tables reference CC_GROUP_ID as a foreign key, though they are not enumerated in the provided metadata. Any IGC object that records a group identifier should be joined back to IGC_CC_GROUPS on CC_GROUP_ID to resolve the group name and its owning Set of Books.