Search Results approval_status_code

Overview

IGC_CBC_JE_BATCHES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGC (Contract Commitment) product family. It consolidates posted journal entry batches together with their period information, batch type, budgetary control status, and header-level attributes into a single queryable structure. The view is documented as VALID and is intended for both reporting and integration consumption, allowing downstream processes to query committed budgetary journal batches without directly joining the underlying transaction, period, and lookup tables manually.

A distinguishing characteristic of the view is that it is a filtered, presentation-ready projection. The WHERE clause restricts output to batches whose approval status code equals 'A' and whose batch status equals 'P' (posted), limiting results to finalized transactions. It also derives descriptive display columns—SHOW_BATCH_STATUS, SHOW_ACTUAL_FLAG, and SHOW_BC_STATUS—by joining to GL_LOOKUPS, which makes the view particularly useful when a user needs to visualize the budgetary control status in human-readable form. This last point directly addresses searches such as "show_bc_status," since the view exposes a decoded budgetary control status column rather than a stored code.

Underlying Base Objects

The view is defined over five documented base objects:

• IGC_CBC_JE_BATCHES (SYNONYM) — the primary source supplying batch header attributes such as CBC_JE_BATCH_ID, batch name, batch status, approval status, effective date, running totals, and descriptive flexfield attributes.
• IGC_CBC_JE_LINES (SYNONYM) — joined on CBC_JE_BATCH_ID and used primarily to obtain the JE source name and the minimum line number per batch.
• GL_PERIOD_STATUSES (SYNONYM) — joined by set of books, application (101 = General Ledger), and effective date falling between the period start and end dates, providing PERIOD_NAME, PERIOD_YEAR, and PERIOD_NUM. Adjustment periods are excluded via the ADJUSTMENT_PERIOD_FLAG predicate.
• GL_LOOKUPS (VIEW) — referenced twice: once as L2 against lookup type 'JE_BATCH_BC_STATUS' to decode budgetary control status, and once as L3 against lookup type 'BATCH_TYPE' to decode the actual flag.
• GL_LEDGERS (SYNONYM) — documented as a referenced base object, supporting the set of books and ledger context of the returned batches.

The line-level join is constrained by a correlated subquery so that only the minimum CBC_JE_LINE_NUM for each batch is returned, preventing row multiplication when multiple lines exist.

Key Columns

The view exposes a broad set of columns. The most significant include:

• CBC_JE_BATCH_ID and CBC_JE_LINE_NUM — the batch and representative line identifiers.
• BATCH_STATUS — the raw batch status code; the derived SHOW_BATCH_STATUS column displays the literal 'POSTED'.
• ACTUAL_FLAG and SHOW_ACTUAL_FLAG — the stored batch type flag and its decoded description from GL_LOOKUPS.
• BUDGETARY_CONTROL_STATUS and SHOW_BC_STATUS — the stored code and the decoded meaning, the latter joined from lookup type 'JE_BATCH_BC_STATUS'. This is the column relevant to "show_bc_status" searches.
• SET_OF_BOOKS_ID, CC_HEADER_ID, APPROVAL_STATUS_CODE — ledger, commitment header, and approval context.
• EFFECTIVE_DATE, PERIOD_NAME, START_DATE, END_DATE, PERIOD_YEAR, PERIOD_NUM — period and date context.
• RUNNING_TOTAL_DR and RUNNING_TOTAL_CR — cumulative debit and credit amounts for the batch.
• USER_JE_SOURCE_NAME — the journal source name obtained from the line record.

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) and ATTRIBUTE1 through ATTRIBUTE10 are also surfaced for traceability and descriptive flexfield use.

Common Use Cases and Queries

Typical uses include reconciling posted commitment batches against GL periods, reporting budgetary control status in a readable format, and feeding integration processes that require only finalized, approved batches. A representative query for budgetary control status reporting is:

SELECT cbc_je_batch_id, name, period_name, show_bc_status, running_total_dr, running_total_cred FROM apps.igc_cbc_je_batches_v WHERE set_of_books_id = :p_sob_id AND period_name = :p_period;

Because the view already enforces approval and posted status filters, callers should not expect draft or unapproved batches to appear. To inspect all budgetary control states, a query filtered on SHOW_BC_STATUS may be used. When integrating, restrict columns to those required and always scope by SET_OF_BOOKS_ID and period to control result volume.