Search Results populate_data

Overview

WSH_ITM_ITEM_SYNC is an Oracle EBS shipping-execution package owned by the APPS schema and classified under the ETRM registry as an "OTHER" API. Its declared purpose is to synchronize item master data across organizations within the Oracle Inventory and Warehouse Management (WSH) domain. In EBS releases 12.1.1 and 12.2.2, organizations are modeled as separate inventory entities, and the same item definition frequently must exist in multiple organizations before it can be received, transferred, or shipped. This package provides a mechanism to propagate item records from a source organization to a target organization, using a concurrent-program entry point that accepts a defined set of filtering parameters.

The package is declared AUTHID CURRENT_USER, meaning that when invoked it executes with the privileges of the calling user rather than the definer's privileges. This is significant in EBS because the package relies on APPS synonyms for the underlying tables; callers must therefore have the appropriate grants and organization access to read source data and insert target data.

Key Procedures and Functions

ETRM documents exactly one procedure for this package: POPULATE_DATA.

• POPULATE_DATA — The single public procedure and the object most relevant to a search on "populate_data." It follows the standard concurrent-program signature convention: two OUT parameters, errbuf (VARCHAR2) and retcode (NUMBER), followed by a set of IN parameters that control the synchronization scope. These IN parameters supply a from/to organization code pair, a from/to item range, a user item type filter, and two numeric windows expressed in days — one for records created and one for records updated. Together they allow a targeted batch: only items matching the specified organizations, item value range, item type, and creation/update age are processed. The procedure returns status through errbuf and retcode, which the concurrent manager interprets to report success, warning, or error. No further procedures or functions are documented in the package specification excerpt.

Tables Accessed

The package references the following objects through APPS synonyms:

• WSH_ITM_ITEMS and WSH_ITM_ITEMS_S — the primary item staging/interface tables. The base table holds the item rows being populated or synchronized; the _S table is the corresponding translation or shadow table used in a multi-lingual (MLS) or supplementary context. These are the principal read/write targets of POPULATE_DATA.
• WSH_ITM_REQUEST_CONTROL and WSH_ITM_REQUEST_CONTROL_S — control and status tables that track the progress of an item-synchronization request, including parameter state and completion status, with _S serving the translations side.
• FND_LANGUAGES — the installed-language reference table, read to determine which language rows must be inserted or synchronized in the MLS companion tables.
• DBMS_SQL and PLITBLM — the Oracle-supplied dynamic SQL package and the PL/SQL integer-indexed table type used for constructing run-time queries and bulk processing. These support the parameterized, range-driven nature of POPULATE_DATA.
• DUAL — the standard single-row pseudo-table, used for lightweight validation or expression evaluation.

Usage Notes

Because POPULATE_DATA carries the (errbuf, retcode) signature, it is designed to be registered as a Concurrent Program executable and submitted from the EBS Concurrent Programs form, typically with a PL/SQL stored-procedure executable referencing APPS.WSH_ITM_ITEM_SYNC.POPULATE_DATA. The organization codes, item ranges, item type, and created/updated day windows map naturally to concurrent program parameters, enabling schedulers and administrators to run incremental synchronization jobs (for example, only items created or updated in the last N days).

The header note $Header: WSHITISS.pls 120.0.12010000.2 2009/03/19 ... ship $ indicates the specification was shipped and stable across the 12.1.1 and 12.2.2 code lines, which matters because 12.2.x introduces online patching and a different editioning/AD_ZD model even though this file name is unchanged. ETRM records zero packages referencing WSH_ITM_ITEM_SYNC, so it is not a dependent internal utility; it is an entry-point package invoked directly by concurrent processing or custom code. Custom callers should honor the organization-access security and item-type validation enforced by the underlying tables, and should inspect retcode/errbuf and WSH_ITM_REQUEST_CONTROL status rather than assuming silent success.