Search Results check_duplicate_modifier_lines

Overview

QP_DELAYED_REQUESTS_UTIL is a PL/SQL utility package owned by the APPS schema within Oracle E-Business Suite Advanced Pricing (Oracle Pricing / ETRM). It provides a set of delayed-validation and maintenance routines used by the pricing engine and the pricing setup forms to enforce integrity across pricing list headers, list lines, price breaks, qualifiers, and modifier definitions. The package acts as a back-end helper invoked during list and modifier maintenance rather than as a standalone business API.

The naming convention "Delayed_Requests" reflects that several validation steps are deferred: instead of being executed at the moment an attribute is entered, they are processed after the setup operation completes, allowing batch or asynchronous validation of complex rules such as continuous price breaks, overlapping breaks, and mixed qualifier segment levels. The package is relevant to the "hvop_pricing_setup" search context because it governs the internal consistency of the pricing setup entities created through the Pricing Setup (QP) forms, including validation of price lists, qualifiers, pricing attributes, and modifier lines.

Key Procedures and Functions

• CHECK_FOR_DUPLICATE_QUALIFIERS — Detects duplicate qualifier rules for a given qualifier rule ID, preventing redundant qualifier definitions.
• VALIDATE_LINES_FOR_CHILD — Validates child list lines against a parent line and line type code.
• MAINTAIN_LIST_HEADER_PHASES — Maintains the phase records associated with a list header.
• CHECK_FOR_OVERLAPPING_BREAKS — Detects overlapping price break ranges for a list line.
• CHECK_CONTINUOUS_PRICE_BREAKS — Validates that price breaks form a continuous sequence without gaps.
• UPGRADE_PRICE_BREAKS — Converts non-continuous price breaks into the continuous model, using product attributes, list type, and active dates.
• CHECK_MULT_PRICE_BREAK_ATTRS — Validates multiple price break attributes against a parent list line.
• CHECK_MIXED_QUAL_SEG_LEVELS — Prevents mixing of qualifier segment levels within a qualifier rule.
• CHECK_MULTIPLE_PRL — Checks for conflicting or duplicate pricing list references on a list header.
• CHECK_DUPLICATE_MODIFIER_LINES — Detects duplicate modifier lines based on active dates, pricing attribute context, attribute, and value.
• CHECK_DUPLICATE_LIST_LINES — Detects duplicate list lines within pricing setup.

Additional documented routines include MAINTAIN_QUALIFIER_DEN_COLS, MAINTAIN_FACTOR_LIST_ATTRS, UPDATE_LIST_QUALIFICATION_IND, UPDATE_LIMITS_COLUMNS, UPDATE_LINE_QUALIFICATION_IND, UPDATE_CHILD_BREAK_LINES, UPDATE_PRICING_ATTR_PHASE, UPDATE_PRICING_PHASE, and UPDATE_MANUAL_MODIFIER_FLAG. These perform column maintenance and qualification indicator updates across the pricing setup tables.

Tables Accessed

• QP_LIST_HEADERS / QP_LIST_HEADERS_B — Parent pricing list and modifier definitions.
• QP_LIST_LINES — Individual list lines and price break lines.
• QP_LIST_HEADER_PHASES, QP_PRICING_PHASES, QP_PRICING_ATTRIBUTES — Phase and pricing attribute definitions used in validation and update routines.
• QP_QUALIFIERS — Qualifier rule data validated by the duplicate and mixed-segment checks.
• QP_LIMITS, QP_LIMIT_ATTRIBUTES — Limit definitions updated by UPDATE_LIMITS_COLUMNS.
• QP_CURRENCY_DETAILS, QP_ADV_MOD_PRODUCTS, QP_PRC_CONTEXTS_B, QP_PTE_SEGMENTS, QP_PTE_SOURCE_SYSTEMS, QP_RLTD_MODIFIERS — Supporting pricing setup entities referenced during validation and lookups.

Usage Notes

QP_DELAYED_REQUESTS_UTIL is invoked internally from the Oracle Pricing setup forms and from the pricing engine during list and modifier maintenance. It is referenced by one other package and is not intended as a public integration API. Customizations should avoid calling these procedures directly; instead, they should follow supported pricing APIs. The package is available in both Oracle EBS 12.1.1 and 12.2.2, with the 12.2.2 online patching (adop) model applying a dual-file system for its specification and body. Because the routines mutate setup data, they should be executed only within the standard pricing setup flow or under Oracle guidance.