Search Results import_countrequest




Overview

The APPS.MTL_CCEOI_ACTION_PUB package is a public PL/SQL API within Oracle Inventory (INV) that provides online processing for Cycle Count Interface records. It allows users to validate and import records from the Cycle Count Open Interface table (MTL_CC_ENTRIES_INTERFACE) into the live cycle count tables that drive Oracle's cycle counting functionality. The package is declared with AUTHID CURRENT_USER and is classified as a public, active API in the ETRM repository, with the display name "Cycle Count Interface API." Its header identifies the source as INVPCCAS.pls, and the business entity it serves is INV_COUNT.

In Oracle EBS 12.1.1 and 12.2.2, cycle counting enables organizations to verify on-hand quantities for selected items on a scheduled basis and to reconcile system balances against physical counts. The interface mechanism exists so that count requests or count entries can be loaded in bulk — for example from external systems, spreadsheets, or barcode collection devices — rather than entered manually through the Cycle Counts form. MTL_CCEOI_ACTION_PUB is the programmatic entry point that moves those staged interface records into the operational cycle count structures.

Key Procedures and Functions

Two procedures are documented for this package:

  • IMPORT_COUNTREQUEST — The primary documented procedure for this package. It performs online processing of Cycle Count Interface records and imports qualifying records from the Cycle Count Open Interface table. The procedure processes only those interface rows whose process flag is set to ready for processing, and it validates all such rows before importing them. Its documented return parameters include an overall status flag, a message count, a message data buffer, an error code that indicates why a record was not imported, and an interface ID identifying the record processed. Its input parameters include the API version, a flag controlling initialization of the message list, a commit flag, a validation level that governs how thoroughly interface records are checked, and the interface record itself.
  • ACTS — A supporting procedure in the package. The available documentation does not describe its behavior in detail; it is listed as a second documented entry point alongside IMPORT_COUNTREQUEST.

Consistent with Oracle's public API conventions, IMPORT_COUNTREQUEST follows the standard x_return_status, x_msg_count, and x_msg_data error-handling pattern, supplemented here by x_errorcode and x_interface_id outputs that let the caller identify exactly which interface row failed and why.

Tables Accessed

The package references the following objects through APPS synonyms:

  • MTL_CC_ENTRIES_INTERFACE and MTL_CC_ENTRIES_INTERFACE_S1 — the Cycle Count Open Interface table and its sequence, which stage incoming count entries before validation and import.
  • MTL_CYCLE_COUNT_ENTRIES and MTL_CYCLE_COUNT_HEADERS — the operational cycle count entry and header tables into which validated records are imported.
  • MTL_MATERIAL_TRANSACTIONS_S — the transaction ID sequence, used when adjustments resulting from cycle counts are recorded as material transactions.
  • WMS_LICENSE_PLATE_NUMBERS — leveraged when license plate controlled (LPN) inventory is involved in the count import.
  • DUAL and PLITBLM — used respectively for single-row selections and for message-list handling.

In summary, the package reads staged records from the interface table and writes validated entries and headers into the cycle count operational tables, with supporting lookups for transaction sequencing and LPN validation.

Usage Notes

MTL_CCEOI_ACTION_PUB is typically invoked when cycle count interface data has been loaded and is awaiting import. This occurs through the Cycle Count Open Interface concurrent program and through the Cycle Counts form, where users may trigger online import of ready records. Because the package is a public API, it may also be called directly from custom PL/SQL, provided the caller correctly initializes the message list, sets an appropriate validation level, and manages commits using the p_commit flag. The ETRM metadata records that the package is referenced by two other packages, confirming its role as a shared service within the Inventory cycle count flow. Callers should always inspect x_return_status, x_errorcode, and the message buffer to determine whether individual interface records were imported or rejected.