Results for “x_org_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.INVIDIT2 is an internal Oracle E-Business Suite PL/SQL package that supports the creation and maintenance of inventory item records in a multi-organization environment. It is classified as an "OTHER" API, meaning it is not a public, supported interface but rather an internal helper package invoked by higher-level item import and item definition processes. The package header declares AUTHID CURRENT_USER, so it executes with the privileges of the calling user rather than the package owner.
The core purpose of INVIDIT2 is to perform the discrete insert operations required when a new item is loaded into the item master and propagated to one or more inventory organizations. The package accepts an X_event indicator and the key identifiers X_item_id, X_org_id, and X_master_org_id to determine context. This is the identifier most commonly associated with the package by implementers searching on "x_item_id," since nearly every procedure is parameterized on that value.
Key Procedures and Functions
- TABLE_INSERTS — The primary driver procedure. It orchestrates insertion of an item's attribute set, including inventory, purchasing, internal order, MRP planning, serviceable product, costing, engineering, and customer order flags, along with EAM item type, contract item type, unit of measure attributes, catalog group, and lifecycle/phase references.
- INSERT_PENDING_STATUS — Records a pending status row for an item in a given organization, optionally tied to a lifecycle and current phase.
- INSERT_REVISION — Creates an item revision record for the specified item and organization, capturing the updating user and login context.
- INSERT_CATEGORIES — Assigns category information to the item within the organization and master organization context.
- INSERT_COSTING_CATEGORY — Establishes the costing category association for the item.
- INSERT_COST_ROW — Inserts a cost row for the item, typically the initial cost record in the costing tables.
- INSERT_COST_DETAILS — Populates cost detail components associated with the item's cost record.
- INSERT_UOM_CONVERSION — Creates unit of measure conversion definitions for the item.
- DELETE_CATEGORIES — Removes category assignments, supporting re-processing or correction scenarios.
- MATCH_CATALOG_DESCR_ELEMENTS — Matches catalog descriptive elements to the item, supporting catalog and descriptive element value population.
- INSERT_DEFAULT_SUBINVENTORIES — Creates default subinventory defaults for item transaction, receiving, and shipping, corresponding to the move order, receiving, and shipping subinventory parameters introduced in later releases.
Tables Accessed
The package reads and writes a tightly scoped set of item-related tables. MTL_SYSTEM_ITEMS_B and MTL_ITEM_ATTRIBUTES hold the core item definition and attribute values. MTL_ITEM_CATEGORIES, MTL_CATEGORY_SETS_B, and MTL_DEFAULT_CATEGORY_SETS support category assignment. Revision data is stored in MTL_ITEM_REVISIONS_B, MTL_ITEM_REVISIONS_B_S, and MTL_ITEM_REVISIONS_TL. Pending status rows go to MTL_PENDING_ITEM_STATUS. Cost information is written to CST_ITEM_COSTS. Descriptive element and value data flow through MTL_DESCRIPTIVE_ELEMENTS and MTL_DESCR_ELEMENT_VALUES. Organization context is validated against MTL_PARAMETERS and HR_ORGANIZATION_INFORMATION, and FND_LANGUAGES supplies language information for translated columns.
Usage Notes
INVIDIT2 is an internal package and should not be called directly from custom code without careful validation. It is referenced by four other packages, which are the supported entry points for item creation. Typical invocation occurs through the item import concurrent program, the item definition forms, and the public item APIs that internally delegate to packages such as this one. The X_event parameter conventionally follows Oracle's 'INSERT', 'UPDATE', or 'DELETE' convention to signal the operation being performed. Because the package inserts rather than updates, it is generally called once per new item-organization combination. Implementers should treat the procedure signatures as version-specific; Oracle may change them between releases, so customizations that reference INVIDIT2 directly carry upgrade risk.
-
PACKAGE: APPS.INVIDIT2 12.1.1
-
PACKAGE BODY: APPS.INVIDIT2 12.2.2
-
PACKAGE: APPS.INVIDIT2 12.2.2
-
PACKAGE BODY: APPS.INVIDIT2 12.1.1
-
APPS.INVIDIT2 SQL Statements 12.2.2
-
APPS.INVIDIT2 SQL Statements 12.1.1
-
PACKAGE: APPS.ENG_BOM_PKG 12.2.2
-
PACKAGE: APPS.WIP_COMMON 12.2.2