Search Results create_orig_sys_entity_mapp_1

Overview

The APPS.HZ_ORIG_SYSTEM_REF_PVT_JW package belongs to the Oracle E-Business Suite Trading Community Architecture (TCA) foundation layer. It is a public API wrapper generated by the Oracle Application Object Library (AOL) API generator and is owned by the APPS schema. Its primary business function is to expose a controlled, validated interface for creating, updating, and querying origin system reference relationships between entities in the TCA registry — for example, cross-referencing a party, party site, or location recorded in an external or legacy system with its corresponding Oracle TCA entity.

The suffix _JW identifies the package as a generated PL/SQL wrapper that delegates to the corresponding private package (HZ_ORIG_SYSTEM_REF_PVT) and to the underlying Entity Object layer. The package header declared in the ETRM documentation is dated 2006 (file ARHMOSJS.pls, version 120.5) and carries AUTHID CURRENT_USER semantics, meaning that privilege resolution occurs against the calling schema rather than the definer, which is significant when invoking these APIs from custom schemas.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions, all flagged as OTHER API classification. They follow a consistent create / update / get naming convention, with numeric suffixes that distinguish the generated variants for different entity types and mappings.

• CREATE_ORIG_SYS_ENTITY_MAPP_1 — Creates a new origin system entity mapping. Accepts p_init_msg_list and p_validation_level control parameters plus a sequence of positional p2_a0 … p2_a27 attributes, and returns the standard x_return_status, x_msg_count, and x_msg_data output parameters.
• UPDATE_ORIG_SYS_ENTITY_MAPP_2 — Updates an existing entity mapping. It adds an in out nocopy NUMBER parameter, p_object_version_number, to support optimistic record locking and version tracking, in addition to the same message and attribute parameters as the create variant.
• CREATE_ORIG_SYSTEM_REFERENC_3 — Creates a new origin system reference record.
• UPDATE_ORIG_SYSTEM_REFERENC_4 — Updates an existing origin system reference record.
• GET_ORIG_SYS_REFERENCE_REC_5 — Retrieves a single origin system reference record for a given key.
• CREATE_ORIG_SYSTEM_6 — Creates a new origin system definition.
• UPDATE_ORIG_SYSTEM_7 — Updates an existing origin system definition.

Tables Accessed

The documented metadata does not enumerate the underlying tables referenced via APPS synonyms. In practice, these APIs operate on the TCA origin system reference tables — principally HZ_ORIG_SYSTEMS, HZ_ORIG_SYS_REFERENCES, and the associated entity mapping structures — which store the mapping between a registered external system and the Oracle TCA objects it owns or references. No other packages are documented as referencing this package.

Usage Notes

Because the package is a generated private-layer wrapper, Oracle's standard guidance is to invoke the corresponding public TCA API rather than calling HZ_ORIG_SYSTEM_REF_PVT_JW directly. When direct invocation is required — typically for legacy data conversion, bulk integration loaders, or custom PL/SQL that must register origin system references — callers must initialize the message list, pass a valid validation level, handle the returned status and message stack, and supply the object version number on updates. Invocations are commonly wrapped inside concurrent programs or interface table processing routines during customer, supplier, or party migrations.