Results for “cycle_count_header_name”

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

Overview

The APPS.MTL_CYCLE_COUNT_HEADERS_V view exposes cycle count header definitions maintained in Oracle Inventory (INV). It presents one row per cycle count header, combining the stored header attributes from the base cycle count header table with decoded lookup meanings for several coded columns. The view is documented as 10SC ONLY in the ETRM reference for Oracle EBS 12.1.1 and 12.2.2, indicating that its supported use is scoped to that specific configuration rather than to all Inventory implementations.

For reporting and integration purposes, the view provides a denormalized, human-readable projection of cycle count header setup. Instead of requiring the caller to join to FND lookups for every coded value, the view resolves meanings such as orientation, schedule interval, approval option, and the serial-related options at the row level. This makes it convenient for operational reports, extract programs, and integrations that need to read cycle count scheduling and approval configuration without replicating lookup decoding logic.

Underlying Base Objects

The documented base objects referenced by the view are:

• MFG_LOOKUPS (VIEW) — the lookup source used to decode coded header columns into descriptive meanings.
• MTL_ABC_ASSIGNMENT_GROUPS (SYNONYM) — the ABC assignment group source that supplies the assignment group name.
• MTL_CYCLE_COUNT_HEADERS (SYNONYM) — the primary cycle count header table that supplies the header identifiers and configuration columns.

In the view definition, the header table appears aliased as CC, the ABC assignment group source as ABC, and lookups as MFG, MFG2, MFG3, MFG4, MFG5, MFG6, MFG7, and MFG8 depending on the column being decoded. The ROWID of the header row is exposed as ROW_ID. Because the view is defined over these base objects, it inherits their organization-level security and transactional context; queries against it reflect only the cycle count headers visible through the underlying Inventory data.

Key Columns

• CYCLE_COUNT_HEADER_ID, ORGANIZATION_ID, CYCLE_COUNT_HEADER_NAME — identity and ownership of the cycle count header.
• APPROVAL_OPTION_CODE and APPROVAL_OPTION — the approval option code stored on the header, with its decoded lookup meaning. This pair is directly relevant to requests searching on the term "approval_option".
• APPROVAL_TOLERANCE_POSITIVE, APPROVAL_TOLERANCE_NEGATIVE, COST_TOLERANCE_POSITIVE, COST_TOLERANCE_NEGATIVE — tolerances governing count approval.
• HIT_MISS_TOLERANCE_POSITIVE, HIT_MISS_TOLERANCE_NEGATIVE — hit/miss accuracy thresholds.
• ABC_ASSIGNMENT_GROUP_ID and ABC_ASSIGNMENT_GROUP — the ABC assignment group linked to the header.
• ORIENTATION_CODE and ORIENTATION, SCHEDULE_INTERVAL_TIME and SCHEDULE_INTERVAL — decoded scheduling attributes.
• AUTOSCHEDULE_ENABLED_FLAG, ZERO_COUNT_FLAG, AUTOMATIC_RECOUNT_FLAG, MAXIMUM_AUTO_RECOUNTS, HEADER_LAST_SCHEDULE_DATE, HEADER_NEXT_SCHEDULE_DATE, DISABLE_DATE — scheduling and control behavior.
• SERIAL_COUNT_OPTION, SERIAL_DETAIL_OPTION, SERIAL_ADJUSTMENT_OPTION, SERIAL_DISCREPANCY_OPTION with their respective meanings — serialized item count behavior.
• CONTAINER_ENABLED_FLAG, CONTAINER_ADJUSTMENT_OPTION, CONTAINER_DISCREPANCY_OPTION — container-related count handling.
• ONHAND_VISIBLE_FLAG, DAYS_UNTIL_LATE, UNSCHEDULED_COUNT_ENTRY, CYCLE_COUNT_CALENDAR, CALENDAR_EXCEPTION_SET — operational visibility and calendar configuration.
• STANDARD WHO COLUMNS AND DESCRIPTIVE FLEXFIELDS — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, plus ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical scenarios include listing all cycle count headers in an organization with their approval and tolerance configuration, verifying decoded values for a specific approval option, and extracting cycle count setup for auditing or migration. Because the view exposes both the code and the meaning, it is well suited to reports and interfaces that must present readable values.

SELECT cycle_count_header_id,
       cycle_count_header_name,
       organization_id,
       abc_assignment_group,
       approval_option_code,
       approval_option,
       autoschedule_enabled_flag,
       schedule_interval_time
  FROM apps.mtl_cycle_count_headers_v
 WHERE organization_id = :org_id;

SELECT cycle_count_header_id,
       cycle_count_header_name,
       approval_option,
       approval_tolerance_positive,
       approval_tolerance_negative,
       cost_tolerance_positive,
       cost_tolerance_negative
  FROM apps.mtl_cycle_count_headers_v
 WHERE approval_option_code = :approval_option_code
   AND organization_id = :org_id;

As with all APPS views, queries should qualify the APPS schema and apply organization and security predicates appropriate to the calling responsibility. Implementations should confirm the documented 10SC ONLY scope before relying on the view in other configurations.