Search Results delete_dimension_assign_pre

Overview

CN_MULTI_RATE_SCHEDULES_CUHK is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Telecommunication industry module (CN). It provides the programmatic API for creating, maintaining, and deleting multi-rate commission schedules and their associated rate dimensions, dimension assignments, and tiers. The package encapsulates the business logic needed to assemble a rate schedule from a named schedule, a commission unit code (AMOUNT or PERCENT), and a table of dimension assignments, then to generate the corresponding tier structure for each assignment. This ensures that commission plans defined in Oracle Incentive Compensation (or comparable CN rate scheduling functionality) are constructed consistently and transactionally, rather than through direct data manipulation against the underlying base tables.

Key Procedures and Functions

The package follows the standard EBS pre/post concurrency pattern. Each logical operation is exposed as a pair: a _PRE procedure that validates inputs and prepares the operation, and a _POST procedure that commits the changes. The documented interface exposes 26 procedures and functions, including the following:

• CREATE_SCHEDULE_PRE / CREATE_SCHEDULE_POST — Create a rate schedule from a name, a commission unit code, and a table of rate dimension assignments. On creation, the schedule is assigned its dimensions and the appropriate set of tiers is generated.
• UPDATE_SCHEDULE_PRE / UPDATE_SCHEDULE_POST — Modify an existing rate schedule. The schedule is identified by its original name; a new name, commission unit code, and dimension assignment table may be supplied. If the assignment table is empty or omitted, only the name and commission unit code are updated and tiers are left unaffected.
• DELETE_SCHEDULE_PRE / DELETE_SCHEDULE_POST — Remove a rate schedule and its dependent structures.
• CREATE_DIMENSION_ASSIGN_PRE / CREATE_DIMENSION_ASSIGN_POST — Add a new rate dimension assignment to a schedule.
• UPDATE_DIMENSION_ASSIGN_PRE / UPDATE_DIMENSION_ASSIGN_POST — Amend an existing dimension assignment. The assignment table is rebuilt according to the revised set of dimension assignments.
• DELETE_DIMENSION_ASSIGN_PRE / DELETE_DIMENSION_ASSIGN_POST — Remove a dimension assignment; this is the procedure family a user reaches when searching for "delete_dimension_assign_post".
• UPDATE_RATE_PRE / UPDATE_RATE_POST — Adjust commission rate values, using the tier structure originally created with null commission amounts.
• CREATE_DIMENSION_PRE / CREATE_DIMENSION_POST, UPDATE_DIMENSION_PRE / UPDATE_DIMENSION_POST, DELETE_DIMENSION_PRE / DELETE_DIMENSION_POST — Maintain the rate dimension definitions referenced by dimension assignments.

The procedures use a common error-reporting convention: an x_return_status out parameter, an x_msg_count, and an x_msg_data value that carry the outcome of the call to the caller.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• CN_RATE_SCHEDULES — The master rate schedule record, holding the schedule name and commission unit code.
• CN_RATE_SCH_DIMS — The association between a rate schedule and its assigned rate dimensions.
• CN_RATE_DIMENSIONS — The definition of each selectable rate dimension.
• CN_RATE_TIERS — The tier definitions generated for a schedule's dimension assignments.
• CN_RATE_DIM_TIERS — The link between rate dimensions and their tiers.

The dimension assignment table passed to the create and update APIs corresponds to the CN_MULTI_RATE_SCHEDULES_PUB.dim_assign_tbl_type record structure, which the package maps onto CN_RATE_SCH_DIMS and the tier tables.

Usage Notes

CN_MULTI_RATE_SCHEDULES_CUHK is typically invoked from Oracle Forms or from custom PL/SQL code where a rate schedule must be maintained as a unit of work. Because the operations are split into PRE and POST procedures, callers must invoke the POST procedure after a successful PRE call to persist changes; the PRE procedure alone validates and prepares but does not finalize. The package is referenced by one other package, confirming it is an integration point for higher-level commission setup logic. When tiers are first created their commission amounts are null and must be populated through UPDATE_RATE_PRE / UPDATE_RATE_POST or the Update_Tier API. Any custom deployment should preserve the standard error-handling contract and avoid direct DML against the underlying CN_RATE_* tables, so that the tier and dimension-assignment integrity maintained by this package is not bypassed.