Results for “post_update_ship_location”

10 results




Overview
Explore in AI Chat

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

Overview

CSL_CSP_LOCATIONS_ACC_PKG is an APPS-owned PL/SQL package within the Oracle E-Business Suite environment, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API type. Its name — combining the CSL (Customer Support/Service Logistics) prefix, the CSP module designator, and "locations_acc" — indicates that it manages the intersection of shipping locations and customer account information used by Oracle's field service and service logistics flows. It operates on the receiving/accounting boundary of location data, keeping CSP-side records synchronized with the master customer and location data held in the Trading Community Architecture (TCA) tables. In both EBS 12.1.1 and 12.2.2, the package is documented as VALID, meaning it has compiled successfully and is an active, callable component of the APPS schema. It is a dependency of CSL_USER_PKG, which suggests it functions as a lower-level utility invoked by higher-level service logistics processing rather than as a top-level entry point.

Key Procedures and Functions

The package exposes nine documented program units. They fall into two functional groups: replication logic and table-level DML event handlers.

  • REPLICATE_RECORD — propagates a location/account record, presumably copying data between the CSP-related staging or association tables and the underlying TCA location structures.
  • PRE_INSERT_SHIP_LOCATION — executes validation or defaulting logic immediately before a ship-location record is inserted.
  • POST_INSERT_SHIP_LOCATION — performs follow-up processing after the insert, such as populating related association rows.
  • PRE_UPDATE_SHIP_LOCATION — validates or captures state before an existing ship-location record is modified.
  • POST_UPDATE_SHIP_LOCATION — carries out dependent updates and synchronization after the change.
  • PRE_DELETE_SHIP_LOCATION — performs referential or business-rule checks before removal of a ship-location record.
  • POST_DELETE_SHIP_LOCATION — cleans up related records following deletion.
  • DELETE_ALL_ACC_RECORDS — bulk-removes all account-related location records, typically used for reprocessing or reset scenarios.
  • INSERT_ALL_ACC_RECORDS — bulk-creates the account-related location records, complementing the delete routine.

Tables Accessed

The package references six tables through APPS synonyms, all central to location and customer account data:

  • CSP_RS_CUST_RELATIONS — the CSP customer-relationship table that links service customers to their account context.
  • HZ_CUST_ACCT_SITES_ALL — customer account sites, defining the physical addresses associated with an account.
  • HZ_CUST_SITE_USES_ALL — site-use assignments, determining the business purpose (e.g., ship-to, bill-to) of each site.
  • HZ_LOCATIONS — the TCA address master table holding normalized location/address data.
  • HZ_PARTY_SITES — the association between parties and their sites, bridging party and location records.
  • PO_LOCATION_ASSOCIATIONS_ALL — purchasing location associations, relating locations to operating units or inventory organizations.

Collectively, these tables indicate that the package maintains the linkage between CSP shipment locations and TCA-maintained customer account/site data.

Usage Notes

Given its pre/post DML handler naming and its citation as a dependency of CSL_USER_PKG, the package is most likely invoked indirectly — either by database triggers on the ship-location tables, by CSL_USER_PKG during user or customer setup, or by concurrent programs that perform bulk location replication. The paired DELETE_ALL_ACC_RECORDS and INSERT_ALL_ACC_RECORDS routines strongly suggest a refresh/reconciliation concurrent program that rebuilds account records wholesale. Customizations should treat the package as a dependency-bearing component: direct invocation is possible from custom PL/SQL, but changes to its behavior risk affecting CSL_USER_PKG and any trigger-based callers. In 12.1.1 and 12.2.2 the TCA tables underlying it share the same structure, so the package's logic remains portable across both releases.