Results for “csr_costs_pkg”

32 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CSR_COSTS_PKG is a stored PL/SQL package in the Oracle E-Business Suite Applications schema (APPS) whose status is documented as VALID. It belongs to the Customer Relationship Management / order capture family of objects and provides the programmatic maintenance layer for cost records associated with the CSR (Cost/Sales/Revenue) cost entity. In practical terms, the package supplies the insert, update, delete, lock, and translation routines that an Oracle Forms block, an OAF-based page, or a concurrent loader uses to persist cost definitions in a multilingual environment.

The object is classified in the ETRM repository with an API classification of OTHER, indicating that it is an internal maintenance package rather than a published, externally supported integration API. It is not referenced by any other package in the repository, so it functions as a leaf-level utility within the application's call stack rather than as a shared foundation component.

The package structure follows the standard Oracle EBS multi-language design pattern. It is delivered as a package specification plus a package body, and it manipulates a base table, a translation table, and a sequence through APPS synonyms. Its logical scope is therefore the lifecycle management of a single cost row, including the concurrent insertion or maintenance of the corresponding translated descriptions for each installed language.

Key Procedures and Functions

The documented interface exposes seven procedures:

  • INSERT_ROW — Creates a new cost record, including the non-translatable attributes stored in the base table and the language-specific description rows needed for the translated table.
  • LOCK_ROW — Implements the standard EBS locking idiom, issuing a SELECT ... FOR UPDATE against the target base row so that a forms session or concurrent process holds a consistent view before modification. It allows the calling layer to detect concurrent modification.
  • UPDATE_ROW — Applies changes to an existing cost record and manages the corresponding translated description rows, inserting new language entries or updating existing ones as appropriate.
  • DELETE_ROW — Removes the cost record and its dependent translation rows, following the EBS convention of a logical or physical delete consistent with the entity's referential rules.
  • ADD_LANGUAGE — Adds translation rows for a newly installed language, supporting the EBS procedure that populates _TL tables when a language is enabled in the instance.
  • TRANSLATE_ROW — Writes or refreshes the language-specific description for a row in the translation table, used when maintaining a single language's text independently.
  • LOAD_ROW — Provides the bulk or seed-data load path that inserts rows with explicit identifiers and audit columns, typically used by concurrent data loaders and install/upgrade scripts.

No parameter lists are documented in the available metadata; the procedures should be treated as internal and invoked only through the application's supported forms or loader paths.

Tables Accessed

  • CSR_COSTS_ALL_B — The base (non-translatable) table holding the core cost definition attributes. It is the target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
  • CSR_COSTS_ALL_TL — The translation table storing language-specific descriptions, maintained by INSERT_ROW, UPDATE_ROW, TRANSLATE_ROW, ADD_LANGUAGE, and DELETE_ROW.
  • CSR_COSTS_ALL_B_S1 — The sequence used to generate primary key values for new base rows, referenced during insert and load operations.
  • FND_LANGUAGES — The Oracle Application Object Library table of installed and enabled languages, consulted by ADD_LANGUAGE to determine which translation rows must exist.
  • DUAL — Used for single-row PL/SQL constructs, such as sequence retrieval or existence checks, and for utility calls.

Usage Notes

CSR_COSTS_PKG is an internal maintenance package. It is normally invoked from Oracle Forms or OAF pages that maintain cost definitions, from concurrent programs that load or migrate cost data, or from install and upgrade driver scripts executing ADD_LANGUAGE and LOAD_ROW. Because the API classification is OTHER and the package is referenced by no other package, custom code should not call it directly; supported integrations should target the owning application's documented interfaces. Where a customer requires programmatic maintenance, the package should be invoked only with the same audit and language context used by the forms layer, since INSERT_ROW, UPDATE_ROW, and LOAD_ROW depend on WHO columns and correct language codes. As with all APPS-schema packages in 12.1.1 and 12.2.2, the object resides in the APPS schema while the underlying tables are owned by the CSR product schema and exposed through synonyms.