Results for “gl_auto_alloc_bat_hist_det_v”

20 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_AUTO_ALLOC_BAT_HIST_DET_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined in the General Ledger (GL) product. It presents the execution history of Automatic Allocation batch programs together with the user-facing concurrent program name resolved from the application's multilingual concurrent program definitions. The view is essentially an enriched projection of GL_AUTO_ALLOC_BAT_HIST_DET, adding a translated PROGRAM_NAME column derived from FND_CONCURRENT_PROGRAMS_TL and FND_CONCURRENT_PROGRAMS. It is used in reporting and diagnostic contexts where the raw program name code stored against an allocation run must be rendered as a readable, language-specific concurrent program name. Because the view joins to the FND concurrent manager tables rather than storing redundant text, it always reflects the currently installed and translated program definitions.

Underlying Base Objects

The view is defined over three referenced base objects, all exposed through APPS synonyms:

  • GL_AUTO_ALLOC_BAT_HIST_DET — the primary fact table holding one row per allocation execution step, aliased D in the view text.
  • FND_CONCURRENT_PROGRAMS (CP) — the base concurrent program definition table, supplying the application-to-program mapping.
  • FND_CONCURRENT_PROGRAMS_TL (CPT) — the translated concurrent program name table, supplying USER_CONCURRENT_PROGRAM_NAME.

The join is restricted in three ways: CP.APPLICATION_ID must be in (101, 275), which covers the General Ledger application and the related application identifier under which allocation programs are registered; CP.CONCURRENT_PROGRAM_NAME must equal D.PROGRAM_NAME_CODE; and CPT is joined to CP on both APPLICATION_ID and CONCURRENT_PROGRAM_ID. Language filtering uses USERENV('LANG') so that each session sees the program name in its own language. All standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are carried through from the detail table, along with the rowid as ROW_ID for row-level addressing.

Key Columns

  • ROW_ID — the ROWID of the underlying GL_AUTO_ALLOC_BAT_HIST_DET row; useful for locating or updating the base record.
  • REQUEST_ID — the concurrent request identifier for the allocation execution; supports joining to FND_CONCURRENT_REQUESTS and FND_CONC_REQ_OUTPUTS for output and log retrieval.
  • PARENT_REQUEST_ID — the parent request when the allocation is executed as part of a request set or batch hierarchy.
  • STEP_NUMBER — the sequence of the step within a multi-step allocation batch.
  • PROGRAM_NAME_CODE — the internal concurrent program short name as stored in the detail table; the join key to FND_CONCURRENT_PROGRAMS.
  • STATUS_CODE — the completion status of the step, typically aligned to concurrent request phase/status values.
  • RUN_MODE — indicates how the allocation batch was executed (for example, validation or execution mode).
  • PROGRAM_NAME — the translated USER_CONCURRENT_PROGRAM_NAME from FND_CONCURRENT_PROGRAMS_TL, resolving the code into the language of the querying session.

Common Use Cases and Queries

Typical usage includes monitoring the outcome of automatic allocation runs, auditing which allocation programs ran and in what order, and producing user-facing reports where the program name must appear translated. The view is also convenient when diagnosing a run by correlating the allocation step with its concurrent request log.

List recent allocation steps with readable program names:

  • SELECT request_id, parent_request_id, step_number, program_name, status_code, run_mode, creation_date FROM apps.gl_auto_alloc_bat_hist_det_v ORDER BY creation_date DESC;

Filter a specific allocation request and join to the concurrent request for phase and status detail:

  • SELECT v.request_id, v.step_number, v.program_name, v.status_code, r.phase_code, r.status_code req_status FROM apps.gl_auto_alloc_bat_hist_det_v v, fnd_concurrent_requests r WHERE v.request_id = r.request_id AND v.request_id = :request_id;

Where the translated name is required, the session language drives the PROGRAM_NAME value automatically; to compare against a specific language, query FND_CONCURRENT_PROGRAMS_TL directly with an explicit LANGUAGE predicate. As with all APPS views, querying through the synonym respects the standard MO security and grants of the APPS schema.