Results for “mtl_cycle_count_headers_val_v”

14 results




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

Overview

MTL_CYCLE_COUNT_HEADERS_VAL_V is an Oracle E-Business Suite view owned by the APPS schema within the Inventory (INV) product module. ETRM documentation designates the object with the description "10SC ONLY," indicating that this view is restricted in scope and typically associated with a specific localization or product configuration rather than the general Inventory feature set. The view is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments.

Functionally, the view exposes the physical cycle count header definition, presented as a validation-oriented projection of the base header data. Cycle count headers in Oracle Inventory define the rules by which cycle counts are scheduled, approved, and reconciled for a given organization. The CYCLE_COUNT_HEADER_NAME column, which surfaces the user-assigned name of each cycle count definition, is the most commonly referenced attribute and is the term by which users search for this object. The view's role is to provide a consumable, read-only interface for reporting, validation (LOV) queries, and integration logic that must reference cycle count header setup without directly accessing the base table.

Underlying Base Objects

The view is defined over a single documented base object: the synonym MTL_CYCLE_COUNT_HEADERS. This synonym resolves to the underlying APPS.MTL_CYCLE_COUNT_HEADERS table, the master table storing cycle count header records for every inventory organization. Because the view is a simple projection rather than a join, each row in the view corresponds one-to-one with a row in the base table.

The view text confirms this relationship with a direct SELECT list from MTL_CYCLE_COUNT_HEADERS, applying only a single transformation: NVL(SERIAL_COUNT_OPTION, 1) is substituted for the raw SERIAL_COUNT_OPTION column. All other columns are passed through without modification. No WHERE clause, aggregation, or join is present, so no filtering or denormalization occurs at the view layer. As a result, row-level security and multi-org access to the underlying table govern visibility through the view unchanged.

Key Columns

The view exposes the full header attribute set. The principal columns include:

Common Use Cases and Queries

Because the view is a direct projection of the header table, it is most often used for LOV lookups, reports, and validation logic that need the cycle count header name and its associated control settings. A typical lookup query follows:

  • SELECT cycle_count_header_id, cycle_count_header_name, organization_id, description FROM apps.mtl_cycle_count_headers_val_v WHERE organization_id = :p_org ORDER BY cycle_count_header_name;

A second common pattern retrieves scheduling and tolerance behavior for a specific header:

  • SELECT cycle_count_header_name, autoschedule_enabled_flag, schedule_interval_time, header_next_schedule_date, approval_option_code FROM apps.mtl_cycle_count_headers_val_v WHERE cycle_count_header_id = :p_header_id;

Integration and interface programs frequently validate that a supplied cycle count header name exists for an organization before proceeding with scheduling or count entry. Because the view carries no additional WHERE clause, callers must always constrain by ORGANIZATION_ID (and, where appropriate, DISABLE_DATE IS NULL) to avoid returning headers across unrelated inventory organizations.