Search Results update_estimate_details

Overview

CS_CHARGE_CREATE_ORDER_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) TeleService / Service (CS) module, owned by the APPS schema. The _PVT suffix indicates that it is a private API intended for internal use by the owning module rather than a published, externally callable interface. Its business purpose is to manage the creation and submission of service orders arising from incidents and charge transactions, and to manage the estimate detail records that support billing-related service activity. The package was designed so that service incident processing can generate an order against the appropriate customer, account, and party context, capturing information such as the originating submit source and submit-from system.

The package header carries a legacy version string dated 2004 and its procedures were copied forward from the csxchors.pls source file at version 115.8, confirming this object's lineage in the older CS service-order processing stack. It operates with AUTHID CURRENT_USER, and therefore executes with the privileges of the invoking schema.

Key Procedures and Functions

The ETRM metadata documents two procedures, matching the user's search term in the second of them:

• SUBMIT_ORDER — The public procedure in this package, described as an API for submitting an order. It is intended for use by the owning module only. It accepts inputs identifying the incident, party, and account, along with a booking flag, submit source, and submit-from-system attributes, and returns the standard EBS API return status, message count, and message data outputs. The account identifier was changed to an optional parameter per bug fix 2447927.
• UPDATE_ESTIMATE_DETAILS — A procedure copied from csxchors.pls version 115.8. It operates against an estimate detail record identified by estimate detail ID and an order header context, and was extended for the 11.5.10 release with additional parameters covering a submit error message and the submit-from system. This procedure is the target of the user's "update_estimate_details" search and handles the maintenance of estimate detail rows that underpin service order and billing processing.

Tables Accessed

The documented table references, reached through APPS synonyms, fall into several logical groups:

• Estimates and billing: CS_ESTIMATE_DETAILS, CS_BILLING_TYPE_CATEGORIES, CS_TXN_BILLING_TYPES, CS_TXN_BILLING_OETXN_ALL, and CS_TRANSACTION_TYPES_B support estimate and transaction billing classification.
• Installed base and party data: CSI_ITEM_INSTANCES, CSI_INSTALL_PARAMETERS, CSI_I_PARTIES, CSI_II_RELATIONSHIPS, CSI_IB_TXN_TYPES, and CSI_TXN_TYPES identify the customer's installed assets and related transaction types.
• Customer/contact: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, and CS_HZ_SR_CONTACT_POINTS supply account and contact context.
• Service incidents: CS_INCIDENTS_ALL_B provides the source incident record driving order creation.

Usage Notes

Because CS_CHARGE_CREATE_ORDER_PVT is classified as a private API, it is normally invoked by other CS module code rather than directly by customers. The metadata records that it is referenced by one other package, consistent with its role as an internal dependency. In practice it is reached through TeleService forms and service-order processing logic when a charge or estimate requires order generation, or by concurrent processing that drives incident-to-order creation. Custom integrators should avoid calling this private package directly and instead use the published CS APIs for order submission and estimate handling, since the private interface and its parameter signatures may change between patch levels and releases.