Search Results purge_charges

Overview

CS_CHARGE_DETAILS_PVT is a private (PVT) PL/SQL package in the APPS schema that serves as the core implementation layer for the Service Charges functionality within Oracle E-Business Suite's TeleService and Service Billing modules. It maintains the atomic records that represent individual billable charges associated with a service request, repair order, or debrief line — encompassing labor, parts, expenses, and miscellaneous fee lines that ultimately flow into the service billing engine. The package encapsulates the low-level insert, update, and delete logic for charge detail records, and it also provides utility functions to copy estimate lines into actual charges, resolve contract associations, and purge stale or invalid charge and validation data.

As a private package, CS_CHARGE_DETAILS_PVT is not intended to be called directly by external consumers. It is wrapped by the public API CS_CHARGE_DETAILS_PUB, which exposes a stable, versioned interface to forms, concurrent programs, and custom extensions while delegating the actual data manipulation to this private package. The dependency metadata confirms a bidirectional relationship: CS_CHARGE_DETAILS_PVT references CS_CHARGE_DETAILS_PUB, and CS_CHARGE_DETAILS_PUB in turn references CS_CHARGE_DETAILS_PVT.

Key Procedures and Functions

The documented API surface comprises seven procedures and functions:

• CREATE_CHARGE_DETAILS — Inserts new charge detail records, establishing the billable line items that will be processed by the service billing engine.
• UPDATE_CHARGE_DETAILS — Modifies existing charge detail records to reflect changes in quantity, price, or other charge attributes.
• DELETE_CHARGE_DETAILS — Removes charge detail records that are no longer applicable.
• COPY_ESTIMATE — Copies estimate detail lines into actual charge detail records, supporting the transition from quoting/estimation to billing.
• GET_CONTRACT — Retrieves the service contract associated with a given charge context, used to determine billing terms and pricing coverage.
• PURGE_CHG_VALIDATIONS — Removes obsolete charge validation records.
• PURGE_CHARGES — Deletes charge records that are no longer required, typically as part of housekeeping or rollback operations.

Parameter lists are intentionally not reproduced here; consult the package specification for exact signatures.

Tables Accessed

The package reads and writes across a broad set of Service and Install Base tables referenced through APPS synonyms:

• Charge and debrief data: CS_ESTIMATE_DETAILS, CSF_DEBRIEF_LINES, CS_BILLING_TYPE_CATEGORIES, and CSP_AVAILABLE_PARTS_TEMP support charge creation, estimate copying, and billing classification.
• Service transactions: CSD_PRODUCT_TRANSACTIONS and CSD_REPAIRS link charges to product transactions and repair orders.
• Install Base: CSI_ITEM_INSTANCES, CSI_IB_TXN_TYPES, CSI_II_RELATIONSHIPS, CSI_I_PARTIES, CSI_TXN_TYPES, CSI_SOURCE_IB_TYPES, and CSI_INSTALL_PARAMETERS provide the installed-asset context and transaction-type validation needed to determine what is billable under a contract.
• Business processes: CS_BUSINESS_PROCESSES and CS_BUS_PROCESS_TXNS tie charge activity to configured service business processes.

Usage Notes

CS_CHARGE_DETAILS_PVT is invoked indirectly through CS_CHARGE_DETAILS_PUB by Service Request and Service Billing forms, and is also called by CS_SERVICE_BILLING_ENGINE_PVT during billing extraction and by CS_SR_DELETE_UTIL during service request deletion and cleanup. Custom code should never call the PVT package directly; use the public API layer instead. The purge routines are typically invoked during period-end housekeeping or when rollback of charge processing is required. Because the package interacts with FND_API and FND_GLOBAL, callers benefit from standard EBS error handling and session context (organization, user) consistent with the FND framework.