Search Results pa_autoalloc_rules_v

Overview

GL_AUTO_ALLOC_BATCH_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger. It presents the execution history of automatic allocation batches, exposing one consolidated row per allocation request and step. The view is built on top of GL_AUTO_ALLOC_BATCH_HISTORY, the base table that records each allocation run processed by the AutoAllocation engine, and enriches that history with descriptive names drawn from the underlying recurring batches, allocation batches, and PA allocation rules.

The view's role is primarily diagnostic and operational. It allows users and support personnel to trace which allocation method was applied to a given batch, which generated journal entry batch resulted from the run, the current status of the step, and the role (owner) under which the allocation was executed. The presence of the ALLOCATION_METHOD_CODE and its decoded ALLOCATION_METHOD meaning column makes the view a natural reference point for searches involving allocation_method, since the method code and its lookup meaning are both surfaced directly. In Oracle EBS 12.1.1 and 12.2.2 the object remains VALID and is exposed as an APPS-owned synonym for reporting.

Underlying Base Objects

The documented referenced base objects are GL_ALLOC_BATCHES (synonym), GL_AUTO_ALLOC_BATCH_HISTORY (synonym), GL_AUTO_ALLOC_VW_PKG (package), GL_LOOKUPS (view), GL_RECURRING_BATCHES (synonym), and PA_AUTOALLOC_RULES_V (view).

• GL_AUTO_ALLOC_BATCH_HISTORY (H) — the driving table, supplying request ID, step number, batch ID, batch type code, allocation method code, generated JE batch ID, status, and audit columns.
• GL_ALLOC_BATCHES (A) — outer-joined on BATCH_ID to provide the allocation batch name when the batch type is 'A'.
• GL_RECURRING_BATCHES (R) — outer-joined on BATCH_ID to provide the recurring batch name when the batch type is 'R'.
• PA_AUTOALLOC_RULES_V (P) — outer-joined on BATCH_ID to supply the PA allocation rule name when the batch type is 'P'.
• GL_LOOKUPS (L, L2) — joined twice: L on LOOKUP_TYPE 'ALLOCATION_METHOD_CODE' to decode the method code, and L2 on LOOKUP_TYPE 'AUTOALLOCATION' to decode the batch type code.
• GL_AUTO_ALLOC_VW_PKG — invoked via GET_OWNER_DSP to translate the owner value into a display-friendly role string, truncated to 240 characters.

Because the view aggregates with GROUP BY REQUEST_ID, STEP_NUMBER and applies MIN() to every non-grouped column, it collapses multiple underlying history rows that share a request and step into a single deterministic row.

Key Columns

• ROW_ID — MIN(ROWID) of the underlying history rows, providing a pseudo-key.
• REQUEST_ID — concurrent request that executed the allocation step.
• BATCH_ID — identifier of the allocation, recurring, or PA rule batch.
• BATCH_TYPE_CODE / ALLOCATION_BATCH_TYPE — the raw type code ('A', 'R', 'P') and its decoded lookup meaning.
• STEP_NUMBER — the allocation step sequence within the request.
• OWNER / ROLE — the owner identifier and its display translation from GET_OWNER_DSP.
• ALLOCATION_METHOD_CODE / ALLOCATION_METHOD — the allocation method code and the corresponding GL_LOOKUPS meaning, central to allocation_method queries.
• GENERATED_JE_BATCH_ID — journal entry batch produced by the allocation.
• PA_ALLOCATION_RUN_ID — associated Projects allocation run, where applicable.
• STATUS_CODE, COMPLETE_FLAG, ALL_HEADERS_REVERSED — execution state indicators.
• Creation and audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes auditing allocation runs by method, reconciling generated journal batches, and diagnosing incomplete or reversed allocations.

To list allocation history filtered by method:

• SELECT request_id, step_number, alloc_batch_name, ALLOCATION_METHOD, ALLOCATION_BATCH_TYPE, STATUS_CODE FROM gl_auto_alloc_batch_history_v WHERE ALLOCATION_METHOD_CODE = :method_code;

To trace the journal batch generated by a specific request:

• SELECT request_id, batch_id, generated_je_batch_id, complete_flag FROM gl_auto_alloc_batch_history_v WHERE request_id = :request_id ORDER BY step_number;

To identify incomplete steps across all roles:

• SELECT request_id, step_number, role, alloc_batch_name, status_code FROM gl_auto_alloc_batch_history_v WHERE complete_flag = 'N';

Because the view is read-only and aggregation-based, it is suited to reporting rather than transactional updates. All lookups for allocation method meanings originate from GL_LOOKUPS with LOOKUP_TYPE 'ALLOCATION_METHOD_CODE', and batch type meanings from 'AUTOALLOCATION', making the view self-describing for downstream reports and integrations.