Search Results entry_code_meaning

Overview

The IGC_CBC_BA_RANGES_FCL_V view is a public API-layer database object owned by the APPS schema within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the IGC – Contract Commitment product family, a module historically associated with the Grants and Contract Accounting functionality used for budgetary control and funds reservation on awards, contracts, and projects. The view is registered in EBS with a status of VALID, meaning its compiled definition resolves successfully against the current data dictionary and is available for querying by forms, concurrent programs, and integration interfaces.

The view provides a denormalized, reporting-friendly representation of budget assignment ranges that govern the funds check level applied during commitment and encumbrance processing. Funds check level determines whether Oracle performs a hard (absolute) or advisory funds check, or no check at all, when expenditures or commitments are entered against a funding source. The assignment ranges define which combinations of accounting flexfield segments and currency codes map to a given check level, budget entity, and entry code. By exposing both the raw codes and their decoded meanings, the view supports auditing, reconciliation, and the construction of validation reports without requiring joins to the underlying base tables.

Underlying Base Objects

According to the documented ETRM metadata, the view text is constructed with a SELECT DISTINCT over a base assignment-range object aliased as RA, joined to two lookup references to the GL meaning table (aliased GL1 and GL2). The documented base object list records only DUAL (SYNONYM), which reflects the seeded lookup and dual-table references present in the query; the primary source of the assignment range data is a budget assignment range base table within the IGC/APPS schema. Because the view text carries numerous common columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, ATTRIBUTE1 through ATTRIBUTE9, and the ROWID alias ROW_ID, the base object is an EBS-standard transactional table that supports concurrent-processing and audit conventions.

The join to the GL meaning table supplies two decoded values: GL1.MEANING as ENTRY_CODE_MEANING and GL2.MEANING as SBC_FUNDS_CHECK_MEANING. This design allows the view to present both the stored code and its human-readable description in a single result set, which is the primary reporting convenience it offers over the base table.

Key Columns

• BUDGET_ENTITY_ID – Identifies the budget entity to which the assignment range belongs.
• SET_OF_BOOKS_ID and CURRENCY_CODE – Establish the ledger and currency context for the range.
• ENTRY_CODE and ENTRY_CODE_MEANING – The entry classification code and its decoded description from GL lookups. This pair is the object of the user's search term.
• RANGE_ID, SEQUENCE_NUMBER, and STATUS – Identify the specific range row, its evaluation order, and its active/inactive state.
• FUNDS_CHECK_LEVEL_CODE and SBC_FUNDS_CHECK_MEANING – The stored funds check level code and its decoded meaning (e.g., absolute, advisory, none).
• AUTOMATIC_ENCUMBRANCE_FLAG – Indicates whether automatic encumbrance is enabled for the range.
• SEGMENT1_LOW through SEGMENT30_LOW and the corresponding _HIGH columns – Define the low and high boundaries of each accounting flexfield segment, enabling range-based matching across up to thirty segments.
• AMOUNT_TYPE and BOUNDARY_CODE – Specify the amount basis and inclusion/exclusion boundary semantics of the range.
• FUNDING_BUDGET_VERSION_ID and FUNDING_BUDGET_NAME – Link the range to a specific funding budget version and its name.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE9 – Descriptive flexfield context and attribute columns for extensibility.
• Standard audit and concurrency columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ROW_ID, and the concurrent manager identifiers PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.

Common Use Cases and Queries

Typical use cases include reviewing and troubleshooting funds check configuration, validating that assignment ranges cover the intended accounting flexfield combinations, and reconciling funds check levels against budget definitions. A common query returning the core decoded attributes is shown below:

SELECT budget_entity_id,
       set_of_books_id,
       currency_code,
       entry_code,
       entry_code_meaning,
       range_id,
       status,
       funds_check_level_code,
       sbc_funds_check_meaning,
       funding_budget_name
FROM   apps.igc_cbc_ba_ranges_fcl_v
WHERE  status = 'A'
ORDER  BY budget_entity_id, sequence_number;

To investigate a specific entry code as sought in the original search:

SELECT budget_entity_id,
       range_id,
       entry_code,
       entry_code_meaning,
       funds_check_level_code,
       sbc_funds_check_meaning,
       segment1_low, segment1_high,
       segment2_low, segment2_high
FROM   apps.igc_cbc_ba_ranges_fcl_v
WHERE  entry_code = :entry_code
  AND  set_of_books_id = :ledger_id;

Because the view exposes both low and high segment boundaries across all thirty flexfield segments, integration and reporting solutions can reconstruct range-based matching logic in SQL, feeding exception reports that highlight overlapping or uncovered ranges. Access should be granted through the standard APPS synonyms and responsibility-based permissions, and queries should be limited to the ledger and budget entity scope required to maintain acceptable performance on large EBS installations.