Search Results create_pricing_attribs




Overview
Explore in AI Chat

Overview

CSI_PRICING_ATTRIBS_PUB is a public PL/SQL API package in the Oracle E-Business Suite Applications (APPS) schema. It belongs to the Configure-to-Order (CTO) and Customer Sales Instance (CSI) product family and exposes the pricing attribute maintenance functions of the CSI data model to external callers. Pricing attributes in CSI constitute the descriptive characteristics of an item instance — the specific configuration choices, option selections, and descriptive flexfield values that differentiate one sold or shipped instance of a model from another. These attributes are consumed downstream by Oracle Pricing and Order Management to derive list price, adjustments, and modifiers for configured items.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking session rather than the package owner. Its procedures form the transactional half of the CSI pricing attribute API set, complementing the query procedures found in the data structure packages.

Key Procedures and Functions

  • GET_PRICING_ATTRIBS — Returns the pricing attributes associated with an item instance. It accepts a pricing attribute query record and an optional timestamp, and returns a pricing attributes table along with the standard API return status, message count, and message data out parameters.
  • CREATE_PRICING_ATTRIBS — Associates new pricing attributes with an item instance. It accepts a pricing attributes table (in/out) and a transaction record (in/out), and returns the standard API status and message out parameters.
  • UPDATE_PRICING_ATTRIBS — Updates existing pricing attributes for an item instance. This is the procedure most commonly referenced when users search for update_pricing_attribs, as it is the supported entry point for changing attribute values after the instance has been created.
  • EXPIRE_PRICING_ATTRIBS — Expires pricing attributes no longer in effect for an item instance, preserving historical records rather than physically deleting them.

All four procedures follow the Oracle EBS PL/SQL API convention of an p_api_version input, a p_commit flag defaulting to fnd_api.g_false, an p_init_msg_list flag, a p_validation_level defaulting to fnd_api.g_valid_level_full, and the standard x_return_status, x_msg_count, and x_msg_data outputs.

Tables Accessed

The documented ETRM metadata records references to DBMS_SQL and PLITBLM via APPS synonyms. DBMS_SQL indicates the package performs dynamic SQL execution, a pattern commonly used in CSI APIs to build attribute queries or updates against the CSI_ITEM_INSTANCES_PRICING_ATTRIBS or related pricing attribute staging tables at runtime. PLITBLM is the PL/SQL table (index-by table) built-in package used for collection manipulation, consistent with the use of the csi_datastructures_pub.pricing_attribs_tbl table type. Because the underlying DML is constructed dynamically, the concrete pricing attribute tables are not statically resolvable in the specification.

Usage Notes

CSI_PRICING_ATTRIBS_PUB is not intended for direct end-user invocation. It is called by Oracle Applications forms and concurrent programs within the CTO and CSI product suites, and by other PL/SQL packages — the ETRM metadata records four dependent packages. Custom code should always call these procedures rather than performing direct DML against the CSI pricing attribute tables, so that validation, message stacking, and the transaction record are handled consistently. Callers should pass a valid p_api_version, initialize the message list as required, and inspect x_return_status for fnd_api.g_ret_sts_success before committing, since the procedures default to no implicit commit. Any modifications must be performed within the standard API framework to preserve compatibility with Oracle Pricing and Order Management.