Search Results get_party_site_id

Overview

CSD_OM_INTERFACE_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as an internal integration bridge between Oracle Depot Repair (CSD) and the Order Management (OM) and Trading Community Architecture (TCA) model. The package header is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the definer, which is consistent with its role as a supporting routine invoked from within the Depot Repair application stack.

The documented source lineage ($Header: csdvomts.pls 115.3 2004/02/17) shows that the package was originally created as part of Depot Repair order-management interfaces and has been carried forward into the current EBS releases without structural change. Because it is classified as a PVT package, it is not part of the public, supported integration API surface; Oracle documents its behavior primarily for internal dependency reference and upgrade impact analysis.

Key Procedures and Functions

The ETRM metadata for release 12.2.2 documents two procedures in the package:

• PROCESS_RMA — Processes return material authorization activity originating from Depot Repair into Order Management. Its signature includes the standard concurrent-program out parameters errbuf and retcode, together with an inventory organization identifier and a subinventory name, indicating that the procedure is designed to be callable from a concurrent program or a host PL/SQL block. It is the operational entry point that moves repair-related RMA data into the OM flow.
• GET_PARTY_SITE_ID — the procedure associated with the searched term get_party_site_id. It resolves a TCA party site use identifier from a site use type and a customer site use identifier. Its parameters accept a site use type value, an existing customer site use identifier, and return both the corresponding party site use identifier and a status indicator. The routine is a lookup/conversion helper: given the OM-style cust_site_use_id, it returns the equivalent party_site_use_id used in the HZ (Trading Community) data model.

Tables Accessed

The documented table references are extensive and fall into four functional groups, all accessed through APPS synonyms:

• Depot Repair tables: CSD_REPAIRS, CSI_ITEM_INSTANCES, CS_ESTIMATE_DETAILS, CS_INCIDENTS_ALL_B, CS_INCIDENT_STATUSES — these supply the repair order, item instance, estimate, and service incident context that PROCESS_RMA consumes.
• Organization: HR_ALL_ORGANIZATION_UNITS — used to validate and resolve the inventory organization passed into PROCESS_RMA.
• TCA / Customer model: HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_CONTACT_POINTS — this group underpins GET_PARTY_SITE_ID, which navigates from the customer-side site use records (HZ_CUST_SITE_USES_ALL) to the party-side site use records (HZ_PARTY_SITE_USES).

No tables outside this documented list are referenced by the package.

Usage Notes

CSD_OM_INTERFACE_PVT is referenced by zero other packages according to the ETRM dependency data, which confirms that it is a leaf-level internal component rather than a shared library. In practice it is invoked from Depot Repair forms and concurrent programs — most notably RMA processing flows that must reconcile customer site use identifiers against the TCA party site use model — and from custom extensions that need to convert between cust_site_use_id and party_site_use_id values.

Because the package is classified PVT and is not part of the public API inventory, custom code should treat it as subject to change without notice. Oracle does not guarantee backward compatibility for its signatures across patches or upgrades. When developing new integrations, the supported public APIs (for example, the HZ and CS public packages) should be used in preference to direct calls into CSD_OM_INTERFACE_PVT. Where a call is unavoidable — typically when replicating standard Depot Repair behavior — the package should be invoked under the APPS schema or with equivalent privileges, with the returned x_return_status value checked before proceeding.