Results for “count_type_code”

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

Overview

MTL_REPLENISH_LINES_VIEW is a dictionary view owned by the APPS schema in Oracle E-Business Suite, defined within the INV (Inventory) product family. Its ETRM record carries the annotation "- Retrofitted," indicating that the object was carried forward into Release 12.1.1 and 12.2.2 from an earlier code line with minimal structural change. The view is declared VALID and serves as a denormalized reporting layer over the replenishment line table, exposing replenishment line rows enriched with item master attributes and lookup-driven error descriptions. Rather than presenting raw transactional columns alone, it joins replenishment data to item definitions and to the MTL_REPLENISHMENT_ERROR lookup, giving report authors, concurrent program logic, and integration extract routines a single relational source for replenishment diagnostics. Because it is a view and not a table, it consumes no storage, inherits the privileges granted on APPS objects, and reflects the current committed state of the underlying base objects at query time.

Underlying Base Objects

The ETRM metadata documents four referenced base objects: MFG_LOOKUPS (VIEW), MTL_ITEM_LOCATIONS (SYNONYM), MTL_REPLENISH_LINES (SYNONYM), and MTL_SYSTEM_ITEMS (SYNONYM). The view text confirms this composition through an inner join between MTL_REPLENISH_LINES and MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID and ORGANIZATION_ID, plus an outer join to MFG_LOOKUPS on LOOKUP_TYPE = 'MTL_REPLENISHMENT_ERROR' and LOOKUP_CODE = ERROR_FLAG. The MTL_REPLENISH_LINES and MTL_SYSTEM_ITEMS synonyms resolve to the base replenishment and item tables in the INV and INV/EGO schemas respectively; MFG_LOOKUPS is itself a view exposing seeded lookup values. MTL_ITEM_LOCATIONS participates in the locator-qualified branch of the UNION ALL, where the LOCATOR_ID IS NULL predicate separates lines with no locator context from those resolved to a specific locator.

Key Columns

• REPLENISHMENT_LINE_ID / REPLENISHMENT_HEADER_ID — primary identifiers linking each line to its parent replenishment header.
• ERROR_FLAG — the critical diagnostic column, holding the lookup code that describes why a replenishment line failed validation or processing; it drives the outer join to MFG_LOOKUPS.
• MEANING — the translated description of ERROR_FLAG obtained from MFG_LOOKUPS, allowing reports to display human-readable error text rather than codes.
• SEGMENT1, DESCRIPTION — item number and description sourced from MTL_SYSTEM_ITEMS.
• COUNT_TYPE_CODE, COUNT_QUANTITY, COUNT_UOM_CODE, SUPPLY_QUANTITY, REORDER_QUANTITY — stock count and replenishment quantity metrics.
• SOURCE_TYPE, SOURCE_ORGANIZATION_ID, SOURCE_SUBINVENTORY — the sourcing origin for the replenishment demand.
• EXPENSE_ACCOUNT, ENCUMBRANCE_ACCOUNT, REFERENCE, TASK_ID, LOCATOR_ID — accounting, project, and locator context.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the submission that generated the row.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the ROWID pseudo-column.

Common Use Cases and Queries

The most frequent use of this view is error diagnosis: identifying replenishment lines that failed processing and explaining why. Because ERROR_FLAG is the searched term, queries typically filter on it or join MEANING for reporting.

• List all errored replenishment lines for an organization: SELECT REPLENISHMENT_LINE_ID, SEGMENT1, DESCRIPTION, ERROR_FLAG, MEANING FROM APPS.MTL_REPLENISH_LINES_VIEW WHERE ORGANIZATION_ID = :org AND ERROR_FLAG IS NOT NULL;
• Error distribution report: SELECT ERROR_FLAG, MEANING, COUNT(*) FROM APPS.MTL_REPLENISH_LINES_VIEW GROUP BY ERROR_FLAG, MEANING ORDER BY 3 DESC;
• Locator-aware retrieval: the view's UNION ALL structure means LOCATOR_ID-specific rows surface alongside the LOCATOR_ID IS NULL branch, so filtering on LOCATOR_ID returns both the unlocated and located replenishment entries.
• Integration extracts: downstream systems commonly select REPLENISHMENT_LINE_ID, INVENTORY_ITEM_ID, COUNT_QUANTITY, and ERROR_FLAG to reconcile replenishment activity between EBS and external planning tools.
• Concurrent program troubleshooting: filtering by REQUEST_ID or PROGRAM_ID isolates the rows produced by a specific replenishment run, and the PENDING/processed status is inferred from the presence or absence of ERROR_FLAG.

When developing reports, note that the outer join to MFG_LOOKUPS is mandatory for obtaining MEANING; lines with a NULL ERROR_FLAG are successfully processed and will return a NULL MEANING. All queries should be schema-qualified with APPS and, where run by non-APPS users, issued through a synonym or a grant on the view.