Search Results csm_servicep_wrapper_pkg




Overview
Explore in AI Chat

Overview

CSM_SERVICEP_WRAPPER_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its role is that of a wrapper or orchestration layer within the Service (CSM) module — the prefix "SERVICEP" and the suffix "WRAPPER" indicate that it encapsulates a set of lower-level service-related operations behind a single, stable interface. The package is documented as VALID in both 12.1.1 and 12.2.2 environments and is classified under the generic API classification OTHER, meaning that Oracle does not publish it as a supported public interface. It nevertheless sits at the centre of a small dependency chain: it references a limited set of ASG and application tables through APPS synonyms, and it is referenced by one other package. The procedures exposed by the package deal with the propagation of client-side (including HTML5) configuration changes, the population and deletion of access records, conflict detection and resolution, and a schema verification routine. Together these responsibilities suggest the package supports the synchronisation of access and responsibility data between an external or client-side cache and the EBS database.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions in the package. Their purposes are as follows.

  • APPLY_CLIENT_CHANGES — Applies changes originating from the client tier to the database, writing the accumulated client-side modifications into the relevant service and access tables.
  • POPULATE_ACCESS_RECORDS — Builds or refreshes the access record set, typically by materialising rows derived from user, responsibility, and deferred transaction information.
  • DELETE_ACCESS_RECORDS — Removes access records, providing the inverse operation to POPULATE_ACCESS_RECORDS and used when access must be revoked or reset.
  • CHECK_OLITE_SCHEMA — Validates the schema expected by the OLite (Oracle Lite / mobile) client, confirming that the database objects required for synchronisation are present and compatible.
  • DETECT_CONFLICT — Identifies conflicts that arise when client-supplied changes disagree with the current database state, returning or recording the conflicting entries for resolution.
  • CONFLICT_RESOLUTION_METHOD — Determines or applies the resolution strategy for conflicts detected by DETECT_CONFLICT, allowing the caller to reconcile divergent data.
  • APPLY_HTML5_CHANGES — The HTML5 counterpart of APPLY_CLIENT_CHANGES, applying changes generated by the HTML5 user interface rather than the earlier client technology.

No parameter lists are published in the available metadata, and callers should obtain signatures from the package specification in the database before invoking any of these units.

Tables Accessed

The documented table references are made through APPS synonyms and comprise the following.

  • ASG_DEFERRED_TRANINFO — Holds deferred transaction information, used to stage changes that must be applied later, consistent with the conflict detection and resolution flow.
  • ASG_USER — The user definition table, consulted when populating and validating access records.
  • ASG_USER_PUB_RESPS — Associates users with public responsibilities; central to determining which access records a user should hold.
  • ALL_SYNONYMS — Queried for metadata purposes, most likely by CHECK_OLITE_SCHEMA to verify that the required synonyms exist.
  • PLITBLM — A PL/SQL internal table used for bulk processing, supporting set-based population and deletion of access records.

The package also references SYS.STANDARD, the standard PL/SQL package, confirming it uses only core language constructs in addition to the tables above.

Usage Notes

CSM_SERVICEP_WRAPPER_PKG is not an Oracle-published public API and is therefore not intended for direct invocation by customer code. In practice it is called by forms, by the Service module's client synchronisation logic, or by concurrent programs that flush changes collected in a client or mobile environment into the EBS database. The dependency list shows the package is referenced by one other package, indicating that direct calls are normally made from that higher-level program unit rather than from the user interface. Because the package participates in conflict detection and resolution, it is invoked during synchronisation cycles rather than during ordinary transactional processing.

Customisations that call this package should treat it as an internal implementation detail: its interface may change between releases, its behaviour is tied to the ASG synonym set, and it should be exercised only within the synchronisation context for which it was designed. Developers who require this functionality should investigate whether a supported public API exists for the same business operation before depending on CSM_SERVICEP_WRAPPER_PKG.