Search Results delete_charge_details

Overview

The APPS.CS_CHARGE_DETAILS_PUB package is the public integration interface for charge processing within Oracle Service (TeleService) in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the business logic that allows external and internal callers to create, update, delete, and copy charge detail records associated with service requests and their estimate lines. The package is registered in the Integration Repository under the display name "Service Request Charge Processing," carries a lifecycle status of "active," and is classified as a public (PUB) API with a compatibility rating of "S." Its business entity category is CS_SERVICE_CHARGE, and it is referenced by the Oracle Teleservice Implementation Guide Release 12.0 (Metalink note 390503.1). The package is documented in source as csxpests.pls, with a header revision of 120.13 dated 2008/01/11.

Key Procedures and Functions

The documented public interface comprises the following procedures, which together implement the charge lifecycle:

• CREATE_CHARGE_DETAILS — Inserts new charge detail records, accepting charge attributes through the Charges_Rec_Type record structure and persisting them as estimate or cost detail rows.
• UPDATE_CHARGE_DETAILS — Modifies existing charge detail records, allowing changes to quantities, billing flags, return dates, and related charge attributes.
• DELETE_CHARGE_DETAILS — Removes charge detail records from the service request, supporting correction of incorrectly captured charges.
• COPY_ESTIMATE — Duplicates an existing estimate, including its associated charge lines, to streamline creation of similar service estimates.
• BODY — The package body that encapsulates the private implementation logic and helper routines supporting the public procedures above.

The package relies on the Charges_Rec_Type record defined at lines 23–45 of the specification. This record carries fields such as estimate_detail_id, incident_id, charge_line_type, line_number, business_process_id, transaction_type_id, inventory_item_id_in, item_revision, billing_flag, txn_billing_type_id, unit_of_measure_code, quantity_required, return_reason_code, customer_product_id, serial_number, installed_cp_return_by_date, new_cp_return_by_date, sold_to_party_id, bill_to_party_id, bill_to_account_id, and bill_to_contact_id. Each numeric, character, and date attribute defaults to the corresponding FND_API.G_MISS_* sentinel, enabling callers to distinguish "no change" from explicit nulls during update operations.

Tables Accessed

The documented table accessed through APPS synonyms is CS_COST_DETAILS. This table stores the cost and charge detail rows associated with service request estimate lines. The package reads, inserts, updates, and deletes rows in this table as the corresponding public procedures are invoked. Charge detail records written by CREATE_CHARGE_DETAILS and maintained by UPDATE_CHARGE_DETAILS and DELETE_CHARGE_DETAILS are persisted here, and COPY_ESTIMATE uses the same table when duplicating estimate lines.

Usage Notes

This package is the supported public entry point for programmatic manipulation of service request charges. It is typically invoked from Oracle Service forms, from concurrent programs that process or migrate charge data, and from custom PL/SQL integrations that need to create or maintain charge details without direct DML against CS_COST_DETAILS. Because it is a public, compatibility-rated interface, customizations should call these procedures rather than manipulating the underlying tables directly, ensuring that validation, defaulting, and API-level consistency logic are applied. The Charges_Rec_Type record should be populated by callers, with unchanged attributes left at their FND_API.G_MISS_* defaults. Standard Oracle EBS API conventions—such as FND_API message handling and x_return_status conventions—apply when consuming this interface.