Search Results update_errors

Overview

The APPS.CS_CHARGE_CREATE_ORDER_PVT package body is a private Oracle EBS Service (CS) module responsible for generating order-capture transactions and estimate records from charge lines associated with service incidents and item instances. It supports the Service Charges / billing integration flows in Release 12.1.1 and 12.2.2 by translating chargeable activity on a service request into an order-ready structure and by persisting estimate details that later feed billing and invoicing.

The package builds on the CS Charging model, which drives revenue recognition for services rendered on installed assets. The header identifies the module as private (_PVT), indicating that its procedures are invoked internally by other CS packages — the metadata confirms a single referencing package in the dependency chain. The body declares global error-handling constants (G_MAXERRPARMLEN, G_MAXERRLEN, g_oraerrmsg) and private helper procedures, including get_who_info, which retrieves the FND_GLOBAL login and user identifiers, and Get_acct_from_party_site, which resolves a valid customer account and account site from a party site using the HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL tables.

Key Procedures and Functions

Two public procedures are documented for this package.

• SUBMIT_ORDER — Assembles and submits the order-capture payload derived from charged service activity. It orchestrates the creation of order transaction records by resolving the owning customer account, billing type, transaction type, and item instance context, then routes the result to the order-capture interface. This procedure is the principal entry point for converting charge lines into order-ready structures.
• UPDATE_ESTIMATE_DETAILS — Persists or refreshes estimate line details associated with a charge or service transaction. The procedure writes to CS_ESTIMATE_DETAILS so downstream billing processes can retrieve accurate estimates. Because the user search term was "update_errors," this procedure is the primary location where update-error conditions are raised or logged; failures here typically surface as database or validation errors propagated from the estimate-detail write.

Private helpers such as Get_acct_from_party_site are not exposed directly but are called by the public procedures to resolve account data. Parameter lists are not documented here and should not be assumed.

Tables Accessed

The package reads and writes through APPS synonyms. Key tables include:

• CS_ESTIMATE_DETAILS — persistence of estimate lines updated by UPDATE_ESTIMATE_DETAILS.
• CS_TXN_BILLING_OETXN_ALL, CS_TXN_BILLING_TYPES, and CS_BILLING_TYPE_CATEGORIES — determine how charge transactions are mapped to order-capture billing structures.
• CS_INCIDENTS_ALL_B, CS_TRANSACTION_TYPES_B, and CS_HZ_SR_CONTACT_POINTS — supply incident, transaction-type, and contact context.
• CSI_ITEM_INSTANCES, CSI_IB_TXN_TYPES, CSI_II_RELATIONSHIPS, CSI_INSTALL_PARAMETERS, CSI_I_PARTIES, and CSI_TXN_TYPES — provide installed-base and transaction-type metadata required to validate the charge.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCOUNTS_ALL — resolve the sold-to customer account used during order submission.

Usage Notes

This private package is invoked from other CS PL/SQL modules rather than directly from forms or concurrent programs. It is typically triggered when a user creates, updates, or charges against a service request, at which point the calling package delegates order submission and estimate-detail maintenance to CS_CHARGE_CREATE_ORDER_PVT. Customizations should not call this package directly; instead, they should use the supported public APIs that wrap it. When troubleshooting "update_errors" returned during charging, checking the write to CS_ESTIMATE_DETAILS and the account-resolution logic in Get_acct_from_party_site is the recommended first step.