Results for “csp_ship_to_address_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSP_SHIP_TO_ADDRESS_PVT is an internal PL/SQL package in the APPS schema that supports Oracle E-Business Suite's Depot Repair, Service, and Field Service modules. Its principal business function is the creation, maintenance, and lifecycle management of ship-to addresses used on customer service orders, return material authorizations, requirement headers, and internal inventory location assignments. The package bridges the Oracle Receivables / Trading Community Architecture (HZ) customer model with the Oracle Inventory (INV) location model, ensuring that when a service transaction requires a ship-to address, a corresponding HZ location, site use, and inventory location exist and are properly linked.

Classified as a PVT (private) API, it is not intended for direct customer invocation. It is invoked internally by public service APIs and by the service module's table handlers, which drive address resolution during order and requirement processing.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents thirteen procedures and functions:

• SHIP_TO_ADDRESS_HANDLER — the primary entry point, coordinating the full ship-to processing flow.
• DO_CREATE_SHIP_TO_LOCATION — creates an HZ location record for a new ship-to address.
• DO_UPDATE_SHIP_TO_LOCATION — updates an existing ship-to location.
• DO_RS_CUST_RELATIONS — maintains the CSP_RS_CUST_RELATIONS record linking a service requirement to its customer relationship.
• DO_CREATE_SITE_USE — creates an HZ_CUST_SITE_USES record with the ship-to site use code.
• DO_UPDATE_SITE_USE — updates the corresponding site use.
• SITE_TO_INVLOC_LINKAGE — establishes the mapping between the HZ site use and the Oracle Inventory location.
• CALL_INTERNAL_HOOK — invokes configurable internal business logic hooks.
• CUST_INV_LOC_LINK — links customer data to the inventory location.
• RS_PRIMARY_SHIP_TO_ADDR — retrieves or sets the primary ship-to address for a requirement.
• RS_INACTIVATE_SHIP_TO — deactivates a ship-to address when it is no longer valid.
• COPY_HZ_CUST_SITE — copies HZ customer site information, supporting address reuse.

Tables Accessed

The package reads and writes a substantial set of base and interface tables via APPS synonyms:

• HZ_LOCATIONS, HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL — the location master and translated address data.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_S, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES, HZ_CUST_SITE_USES_ALL — the TCA customer, account site, and site-use model.
• HZ_CUSTOMER_PROFILES — customer-level profile options.
• CSP_RS_CUST_RELATIONS — service requirement-to-customer relationship records.
• CSP_REQUIREMENT_HEADERS — the service requirement header driving ship-to resolution.
• CSP_LOCATION_ID_S1 — sequence used to generate location identifiers.
• FND_TERRITORIES — territory/geography validation.
• AR_SYSTEM_PARAMETERS — Receivables setup values influencing address behavior.

Usage Notes

CSP_SHIP_TO_ADDRESS_PVT is invoked indirectly through ten dependent packages and table handlers, including CSF_ACCESS_PKG, CSL_CSP_LOCATIONS_ACC_PKG, CSM_HZ_LOCATION_PKG, CSM_MULTI_MOBQRY_PKG, CSM_WF_PKG, and the IUHK table-handler packages CSP_INV_LOC_ASSIGNMENTS_IUHK, CSP_REQUIREMENT_HEADERS_IUHK, CSP_REQUIREMENT_LINES_IUHK, and CSP_REQ_LINE_DETAILS_IUHK. Custom code should not call it directly; instead, customizations should use the public service APIs (such as the Depot Repair order or requirement APIs) that invoke this package. Because it performs committed database changes to TCA and Inventory records, it should only be called within the transaction context managed by its parent handler. Support and diagnostic engagements frequently query this object to understand how ship-to addresses are generated, updated, or inactivated during service order and RMA processing across both 12.1.1 and 12.2.2.