Results for “inventory_adjustment_account”

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

Overview

MTL_CYCLE_COUNT_HEADERS_ALL_V is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module. It exposes the controlling header records for cycle count activities, presenting the definition, approval rules, scheduling parameters, tolerance thresholds, and serial/container handling options configured for each cycle count header within an organization. The ETRM metadata annotates this object with the description "10SC ONLY," indicating that it is a restricted or specialized variant associated with the 10SC (ten-schema / restricted configuration) deliverable rather than a general-purpose global view. Despite that restriction, the columns it projects are drawn directly from cycle count header setup data used by the standard Inventory cycle counting process.

The view applies a row-level filter that excludes disabled cycle count headers. Specifically, it returns only rows where TRUNC(NVL(DISABLE_DATE, SYSDATE+1)) > TRUNC(SYSDATE), meaning a header is visible only if it has no disable date or its disable date falls after the current date. This makes the view particularly suitable for reporting on currently active cycle count definitions, since logically deleted or expired headers are suppressed.

Underlying Base Objects

The view is defined over a single documented base object: MTL_CYCLE_COUNT_HEADERS, referenced through a SYNONYM in the APPS schema. All columns projected by the view originate from this table; the view is essentially a filtered and lightly transformed projection rather than a join across multiple entities. The one noteworthy transformation is the SERIAL_COUNT_OPTION column, which is returned as NVL(SERIAL_COUNT_OPTION, 1), defaulting to a value of 1 when the underlying column is null. Because the underlying table MTL_CYCLE_COUNT_HEADERS is organization-specific (keyed in part by ORGANIZATION_ID), the view functions as an "ALL" style view exposing header definitions across organizations, filtered by the active-disable-date predicate.

Key Columns

• CYCLE_COUNT_HEADER_ID — Primary identifier for the cycle count header.
• ORGANIZATION_ID — Inventory organization to which the header belongs.
• CYCLE_COUNT_HEADER_NAME — User-defined name of the cycle count definition.
• INVENTORY_ADJUSTMENT_ACCOUNT — The general ledger account used to post inventory adjustments generated by counts under this header. This is the column most relevant to the "inventory_adjustment_account" search term.
• ORIENTATION_CODE — Indicates whether the count is oriented by item or by location.
• ABC_ASSIGNMENT_GROUP_ID — Links the header to an ABC assignment group for count frequency.
• APPROVAL_OPTION_CODE and tolerance columns (APPROVAL_TOLERANCE_POSITIVE, APPROVAL_TOLERANCE_NEGATIVE, COST_TOLERANCE_POSITIVE, COST_TOLERANCE_NEGATIVE, HIT_MISS_TOLERANCE_POSITIVE, HIT_MISS_TOLERANCE_NEGATIVE) — Govern approval and variance thresholds.
• Scheduling columns (AUTOSCHEDULE_ENABLED_FLAG, SCHEDULE_INTERVAL_TIME, HEADER_LAST_SCHEDULE_DATE, HEADER_NEXT_SCHEDULE_DATE) — Define automated count scheduling behavior.
• Serial and container columns (SERIAL_COUNT_OPTION, SERIAL_DETAIL_OPTION, SERIAL_ADJUSTMENT_OPTION, SERIAL_DISCREPANCY_OPTION, CONTAINER_ENABLED_FLAG, CONTAINER_ADJUSTMENT_OPTION) — Control handling of serialized and containerized items.
• DISABLE_DATE — Drives the view's active-row filter.
• Attribute1–15 and WHO columns — Standard descriptive flexfield and audit fields.

Common Use Cases and Queries

The view is typically queried to report active cycle count header definitions and, in particular, to determine the inventory adjustment account assigned to each active header. A representative query is:

SELECT cycle_count_header_id,
       organization_id,
       cycle_count_header_name,
       inventory_adjustment_account
FROM   apps.mtl_cycle_count_headers_all_v
WHERE  organization_id = :org_id;

Because the view already filters out disabled headers, additional DISABLE_DATE predicates are unnecessary for active-header reporting. The "10SC ONLY" designation warrants caution: this view should not be assumed to exist or behave identically in every environment and is best validated against the target instance before being embedded in custom reports or integrations.