Results for “count_uom”

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

Overview

MTL_CC_ENTRIES_INTERFACE is an Inventory (INV) module interface table that serves as the staging area for cycle count entry data flowing into Oracle E-Business Suite. Cycle counting is the process of periodically counting on-hand inventory for selected items and reconciling those counts against system quantities. Rather than posting count results directly into the transaction tables, Oracle EBS routes them through this interface, allowing validation, error handling, and controlled processing before the records are converted into cycle count entries and inventory adjustments.

The table belongs to the INV schema and contains 139 documented columns in ETRM 12.2.2. Its primary key is defined by the unique index MTL_CC_ENTRIES_INTERFACE_U1, implemented on the surrogate identifier CC_ENTRY_INTERFACE_ID. In Data Vault modeling terms, the foreign-key structure suggests a satellite-leaning classification: the table carries descriptive, evolving attributes (count quantities, flags, account segments) tied to recurring cycle count processes, though its staging role also gives it link-like characteristics that connect items, locations, counts, and accounts.

Key Information Stored

The following columns represent the most functionally significant attributes of the table:

• CC_ENTRY_INTERFACE_ID – Surrogate primary key (MTL_CC_ENTRIES_INTERFACE_U1) uniquely identifying each staged interface row.
• CC_ENTRY_INTERFACE_GROUP_ID – Groups related interface rows for batch processing.
• ORGANIZATION_ID – Warehouse or inventory organization in which the count was performed.
• CYCLE_COUNT_HEADER_ID / CYCLE_COUNT_HEADER_NAME – Links the entry to the owning cycle count header (count name).
• CYCLE_COUNT_ENTRY_ID – Reference to the corresponding cycle count entry record.
• INVENTORY_ITEM_ID, ITEM_SEGMENT1–20, REVISION – Item identification, including concatenated segment values and revision.
• SUBINVENTORY, LOCATOR_ID, LOCATOR_SEGMENT1–20 – Physical stocking location and concatenated locator segments.
• LOT_NUMBER, SERIAL_NUMBER – Lot and serial control information for controlled items.
• COUNT_QUANTITY, PRIMARY_UOM_QUANTITY, COUNT_UOM – Quantity observed and system quantity in the primary unit of measure.
• ADJUSTMENT_ACCOUNT_ID, ACCOUNT_SEGMENT1–30 – Accounting flexfield for the adjustment generated by the count discrepancy.
• COUNT_DATE, EMPLOYEE_ID, EMPLOYEE_FULL_NAME – Date of count and the counter responsible.
• PROCESS_FLAG, VALID_FLAG, ERROR_FLAG, STATUS_FLAG, DELETE_FLAG, LOCK_FLAG – Control flags governing validation and processing status.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID – Concurrent program context that created or processed the row.
• SECONDARY_COUNT_QUANTITY, SECONDARY_UNIT_OF_MEASURE – Secondary UOM quantities for dual-unit items.
• PARENT_LPN_ID, OUTERMOST_LPN_ID, COST_GROUP_ID – LPN and cost group attribution for logistics and costing.

Common Use Cases and Queries

Because this is an interface table, the dominant use cases involve monitoring, debugging, and reporting on the flow of cycle count data before and after processing. Typical queries include:

• Identifying rows that failed validation: SELECT cc_entry_interface_id, inventory_item_id, error_flag FROM mtl_cc_entries_interface WHERE error_flag = 'Y';
• Checking pending rows for a specific organization before running the cycle count entry processor: WHERE organization_id = :org AND process_flag = 'N';
• Reporting count versus system variance for a given cycle count header, joining COUNT_QUANTITY and PRIMARY_UOM_QUANTITY to highlight discrepancies.
• Auditing which concurrent request processed a batch: WHERE request_id = :request_id;
• Reviewing rows joined to MTL_CC_INTERFACE_ERRORS to trace the root cause of a rejection.

Operational troubleshooting commonly centers on PROCESS_FLAG, ERROR_FLAG, and STATUS_FLAG states, since a row that never advances past these flags is frequently the source of stuck cycle count processing.

Related Objects

The table participates in a relatively rich foreign-key network, which identifies the most important related objects:

• MTL_CYCLE_COUNT_HEADERS – joined via CYCLE_COUNT_HEADER_ID; the owning count definition.
• MTL_CYCLE_COUNT_ENTRIES – joined via CYCLE_COUNT_ENTRY_ID; the entry-level detail record.
• MTL_CC_INTERFACE_ERRORS – references this table through CC_ENTRY_INTERFACE_ID; captures validation error messages.
• MTL_SYSTEM_ITEMS_B – joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item definition.
• MTL_ITEM_LOCATIONS – joined via LOCATOR_ID to resolve the storage location.
• MTL_SECONDARY_INVENTORIES – joined via SUBINVENTORY and ORGANIZATION_ID.
• MTL_LOT_NUMBERS / MTL_ITEM_REVISIONS_B – control-attribute validation for lot and revision.
• GL_CODE_COMBINATIONS – joined via ADJUSTMENT_ACCOUNT_ID for the adjustment account.
• CST_COST_GROUPS – joined via COST_GROUP_ID for cost group attribution.
• MTL_PARAMETERS – organization context via ORGANIZATION_ID.

Cycle count entries are ultimately processed by the Cycle Count Entry and Adjustment concurrent programs, which read from this interface, validate against the master item, subinventory, and locator tables above, and then post the resulting entries and inventory adjustments.