Search Results get_all_parents

Overview

OZF_QP_QUAL_PVT is a private PL/SQL package in the Oracle E-Business Suite APPS schema that serves as the internal engine for resolving market segment and qualifier information used by Oracle Trade Management (OZF) and Oracle Advanced Pricing (QP). Its stated purpose is to retrieve Market Segment qualifiers — the attributes by which customers, buying groups, and territories are matched against pricing and offer qualifiers. The package is declared AUTHID CURRENT_USER, and the last shipped header revision (120.8, dated 16-Oct-2011) reflects its maintenance lifecycle across several Trade Management enhancements, including SSD-IDSM accrual changes (10216374/9447673) and backdating adjustment functionality for supplier ship and debit offers (ER10157845). Because it is classified as a private (PVT) API, it is not part of the supported public interface; it is invoked internally by other Trade Management packages and is referenced by two additional packages in the current release.

Key Procedures and Functions

The documented interface exposes fifteen procedures and functions. The most significant are summarized below; parameter signatures are intentionally omitted.

• get_all_parents — Performs a recursive traversal to identify all parent parties for a given party, populating a multirecord attribute-mapping structure. It is the entry point most commonly sought by developers resolving hierarchical customer relationships.
• get_buying_groups — Returns all buying groups to which a customer belongs, expressed as a multirecord collection suitable for qualifier evaluation.
• get_lists — Returns all Advanced Pricing lists associated with a customer.
• get_segments — Retrieves the market segments applicable to a customer.
• get_distributor_acct_id, get_distributor_lists, get_distributor_segments, get_distributor_territories — Distributor-oriented counterparts that resolve the account identifier, list memberships, segments, and territory assignments for distributor parties.
• find_tm_territories and find_sa_territories — Locate Territory Manager and Sales Application territories, respectively, for a qualifying entity.
• get_sales_method, get_item_cost, and get_additional_qualifiers — Supply supplementary qualification attributes, including sales method, item cost, and any residual qualifiers not covered by the dedicated lookups.

Tables Accessed

The package operates against several core EBS tables through APPS synonyms. Customer and party data is drawn from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_RELATIONSHIPS, and HZ_CUSTOMER_PROFILES; the recursive parent logic in get_all_parents depends principally on HZ_RELATIONSHIPS. Market segment and list memberships are read from AMS_PARTY_MARKET_SEGMENTS and AMS_LIST_ENTRIES. Territory resolution uses JTF_TERR, JTF_TERR_ALL, and the qualifier-type usage tables JTF_TERR_QTYPE_USGS and JTF_TERR_QTYPE_USGS_ALL. Item cost qualification reads MTL_SYSTEM_ITEMS, while order-context qualifiers such as sold-to organization are sourced from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. The package is predominantly read-only, materializing qualifier values into PL/SQL collections rather than persisting them.

Usage Notes

OZF_QP_QUAL_PVT is invoked at runtime by Trade Management and Advanced Pricing processing whenever qualifier resolution is required — for example, during offer and promotion qualification, pricing list determination, and territory-based eligibility checks. It is typically called from other PL/SQL packages rather than directly from forms or concurrent programs, and it is documented as being referenced by two other packages in release 12.2.2. Because it is a private API with an AUTHID CURRENT_USER declaration, customizations should avoid direct calls; defects and enhancements should instead be raised through Oracle Support. Developers investigating party hierarchies in the Trade Management schema frequently arrive at this package via the get_all_parents procedure, which remains the canonical internal implementation of recursive parent resolution for qualifier purposes. Behavior is identical in 12.1.1 and 12.2.2 as delivered code, though the two releases differ in underlying AD/TXK technology stack and file system layout.