Search Results del_processed_recs




Overview
Explore in AI Chat

Overview

MTL_RELATED_ITEMS_PVT is the private implementation package for the Oracle EBS Inventory related-items feature. In Oracle Inventory, a related item is an association between two inventory items that carries planning semantics — for example, a substitute item, a substitute component, or a customer-specific item reference. The public API surface is defined by MTL_RELATED_ITEMS_PUB, and this companion package (declared in source file INVVRITS.pls, version 120.1.12020000.2) contains the procedural logic that performs the actual validation and persistence work.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema rather than the defining schema — an important consideration when it is invoked from concurrent programs or custom code that must have direct object privileges. The package defines the entity code G_Entity_Code := 'RelItem' and the base table name G_Table_Name := 'MTL_RELATED_ITEMS', which are used for error handling and messaging through the Error_Handler utility. A debug facility is controlled by the profile option INV_DEBUG_TRACE (user-facing name "INV: Debug Trace"), read into G_DEBUG.

Key Procedures and Functions

The package exposes four documented procedures:

  • PROCESS_REL_ITEM — The main API for a single related-item record. It processes CREATE, UPDATE, and DELETE operations on a related item together with its associated planning details: substitution sets and customer references. It accepts a related-item record plus planning-information and customer-reference collections and returns standard FND_API error outputs (return status, message count, and message list).
  • PROCESS_REL_ITEMS_ROWS — A concurrent-program entry point that pulls candidate rows from MTL_RELATED_ITEMS_INTERFACE and processes them. As documented in the header comment, this path does not support planning details, so substitution sets and customer references are not handled through interface loading.
  • DEL_PROCESSED_RECS — Deletes records that have already been processed. This is the procedure associated with the search term "del_processed_recs" and is typically used to purge successfully processed rows from the related-items interface or staging tables, keeping the interface clean for subsequent runs.
  • WRITE_DEBUG — A diagnostic helper that writes debug output when the INV_DEBUG_TRACE profile option is enabled, using Error_Handler.Write_Debug.

Tables Accessed

The package reads and writes MTL_RELATED_ITEMS (the base entity), MTL_RELATED_ITEMS_CUST_REF (customer references), and MTL_RELATED_ITEMS_INTERFACE plus its sequence MTL_RELATED_ITEMS_INTERFACE_S for inbound interface processing and purging. MTL_PARAMETERS supplies inventory organization defaults. Validation and reference lookups against Trading Community Architecture tables include HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_LOC_ASSIGNMENTS, HZ_PARTIES, and HZ_PARTY_SITES. FND_GRANTS, FND_OBJECTS, and FND_PRODUCT_INSTALLATIONS are queried for function-security and installation checks. All are accessed through APPS synonyms.

Usage Notes

This is a private package; callers should invoke the public MTL_RELATED_ITEMS_PUB API rather than MTL_RELATED_ITEMS_PVT directly. The private package is referenced by one other package within the EBS codebase, which is the expected pattern for a PUB/PVT pair. In practice, related-item maintenance is driven from the Inventory related-items form, which calls the public API and in turn delegates to PROCESS_REL_ITEM. Bulk loading is performed by the related-items interface concurrent program, which invokes PROCESS_REL_ITEMS_ROWS to consume MTL_RELATED_ITEMS_INTERFACE and DEL_PROCESSED_RECS to remove processed rows. Custom integrations should populate the interface and submit the standard concurrent program rather than calling these procedures directly, since direct calls bypass the supported error handling and validation sequencing. When troubleshooting, enable the INV: Debug Trace profile option to capture WRITE_DEBUG output.