Search Results owner_dsp




Overview
Explore in AI Chat

Overview

GL_AUTO_ALLOC_BATCHES_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents allocation batch information used by the Automatic Allocations feature in General Ledger. The view exposes batch-level metadata for allocation sets, including batch identifiers, owner information, allocation method codes, descriptive flexfield (DFF) attributes, and lookup-driven type meanings. In addition to the raw columns inherited from the base table, the view derives two computed columns: NAME via GL_AUTO_ALLOC_VW_PKG.GET_BATCH_NAME, and OWNER_DSP via GL_AUTO_ALLOC_VW_PKG.GET_OWNER_DSP. This makes the view a reporting and integration convenience layer that resolves internally stored codes into user-facing display values.

Underlying Base Objects

The view is defined over three documented referenced objects:

  • GL_AUTO_ALLOC_BATCHES (accessed via synonym GLB) — the primary base object holding allocation batch records, including batch IDs, batch type codes, step numbers, owner, and DFF attributes.
  • GL_LOOKUPS (aliased LKP) — joined to the batch table on LOOKUP_TYPE = 'AUTOALLOCATION' and LOOKUP_CODE = BATCH_TYPE_CODE, yielding the TYPE column as the translated meaning of the batch type.
  • GL_AUTO_ALLOC_VW_PKG — the package supplying the GET_BATCH_NAME and GET_OWNER_DSP functions that generate the NAME and OWNER_DSP computed columns, respectively.

The view selects from GL_AUTO_ALLOC_BATCHES and GL_LOOKUPS, applying substring truncation (SUBSTR) to limit NAME to 150 characters and OWNER_DSP to 240 characters. All DFF attribute columns and descriptive columns from the base table are passed through unchanged.

Key Columns

Notable columns exposed by the view include:

  • ROW_ID — the ROWID of the underlying batch record, useful for row identification.
  • ALLOCATION_SET_ID, BATCH_ID, BATCH_TYPE_CODE — identifiers linking the batch to its allocation set and type.
  • STEP_NUMBER, ALLOCATION_METHOD_CODE — control the allocation processing sequence and method.
  • OWNER — the raw owner value stored on the batch record, from which OWNER_DSP is derived.
  • OWNER_DSP — the formatted display value for the owner, computed through GET_OWNER_DSP. This is the column most relevant to the user's search term "owner_dsp."
  • NAME — the formatted batch name derived from GET_BATCH_NAME.
  • TYPE — the descriptive meaning of the batch type code from GL_LOOKUPS.
  • ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — descriptive flexfield columns.
  • Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include verifying allocation batch definitions, reporting on batch ownership using the display form, and resolving batch type codes into readable descriptions. Because the view supplies both coded and display representations, it is suitable for custom reports, concurrent program inputs, and integration interfaces that require human-readable output without invoking package functions directly.

Example query listing allocation batches with resolved type and owner display:

  • SELECT BATCH_ID, NAME, TYPE, OWNER, OWNER_DSP, ALLOCATION_METHOD_CODE, STEP_NUMBER FROM GL_AUTO_ALLOC_BATCHES_V WHERE ALLOCATION_SET_ID = :p_allocation_set_id ORDER BY STEP_NUMBER;

Filtering specifically on the translated owner display, addressing the reported search term:

  • SELECT BATCH_ID, NAME, OWNER_DSP FROM GL_AUTO_ALLOC_BATCHES_V WHERE OWNER_DSP = :p_owner_display;