Search Results create_cost_details

Overview

APPS.CS_COST_DETAILS_PUB is a public PL/SQL package in Oracle E-Business Suite that exposes the cost detail maintenance API for the Service (CS) module, specifically the TeleService / field service costing and incident charge line functionality. The package provides a supported, programmatic interface for creating, updating, and deleting cost records associated with service incidents and estimate details. It is classified as a public (PUB) API, meaning Oracle intends it for external invocation by forms, concurrent programs, and custom integration code rather than as an internal-only utility.

The header comment ($Header: csxpcsts.pls 120.1 2008/01/18 ... noship $) indicates the file ships with the EBS codebase and follows standard API conventions. The package defines a single composite record type, COST_REC_TYPE, which carries the full attribute set of a cost detail row: identifiers such as cost_id, incident_id, and estimate_Detail_id; classification fields such as charge_line_type, transaction_type_id, and txn_billing_type_id; inventory and quantity fields (inventory_item_id, quantity, unit_of_measure_code, org_id, inventory_org_id); monetary fields (currency_code, extended_cost); a source_id/source_code pair for origin tracking; transaction_date; and the standard attribute1 through attribute15 DFF columns. Every element defaults to the corresponding FND_API.G_MISS_* sentinel value, enabling the standard EBS "miss" semantics in which only explicitly populated fields are considered by the API. A global record variable, G_MISS_COST_REC, is also declared.

Key Procedures and Functions

The ETRM metadata documents four procedures:

• CREATE_COST_DETAILS — Inserts a new cost detail record. It accepts the cost record structure (and related control parameters) to persist a cost line against a service incident or estimate detail.
• UPDATE_COST_DETAILS — Modifies an existing cost detail record, using the FND_API.G_MISS_* convention so that only fields supplied by the caller are changed.
• DELETE_COST_DETAILS — Removes a cost detail record. This is the routine surfaced by the search term delete_cost_details; it is the supported way to programmatically purge a cost record rather than issuing a direct DML statement against the underlying table.
• LOG_COST_REC_PARAMETERS — A diagnostic/logging helper that writes the contents of a cost record parameter to the EBS debug log, used for troubleshooting API calls.

Parameter lists are not enumerated in the available metadata; only procedure names and purposes are documented here.

Tables Accessed

The ETRM excerpt does not list the underlying tables explicitly, though the package operates over the CS cost details entity (the base cost table underlying the Service cost detail UI), referenced through APPS synonyms. The API reads and writes cost detail rows keyed by cost_id and joined to incident_id, estimate_detail_id, inventory, and organization context columns.

Usage Notes

CS_COST_DETAILS_PUB is referenced by four other packages, confirming it is a shared service-layer API. It is typically invoked from the Service/TeleService cost entry forms and from custom concurrent programs or PL/SQL integrations that manage incident costing. Because it is a PUB API, callers should use it in preference to direct inserts, updates, or deletes on the cost tables, ensuring validation, DFF handling, and consistent FND_API error/return conventions.