Search Results validate_customer

Overview

QP_MGD_EURO_CUSTOMER_MEDIATOR is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. The "QP" prefix places it within the Oracle Advanced Pricing (QP) module, and the name reflects its role as a migration mediator for converting customer and customer site records during the euro currency transition associated with the Economic and Monetary Union (EMU). The package header comment describes its purpose as the "Package Body for the Customer/Site Conversion." It is classified under ETRM as an OTHER API rather than a public, fully supported interface, which signals that it was designed for internal, upgrade-time conversion processing rather than general developer consumption.

The source header (QPXMCSTB.pls, version 120.0, dated 2005) shows the package was created in May 2000, the period immediately following the introduction of the euro, and was updated through 2002. Its business function is to migrate customer-related pricing setup so that a defined default euro price list is applied consistently to converted customers and their sites, optionally updating existing euro price lists where they already exist.

Key Procedures and Functions

ETRM documents three procedures for this package. The excerpt additionally reveals a fourth, private routine.

• CUSTOMER_CONVERSION (PUBLIC) — The main driver for converting an individual customer. According to the documented parameters, it accepts a customer identifier, a customer number, a default euro price list identifier, and a flag controlling whether an existing euro price list should be updated. It encapsulates the "Main Logic to Process the Customer Conversion" per the header comment.
• SITES_CONVERSION (PUBLIC) — Performs the equivalent conversion for customer sites (ship-to/bill-to locations) belonging to a customer, applying the euro price list assignment at the site level.
• ALL_CUSTOMER_CONVERSION (PUBLIC) — Added 07-May-2001 per the history block; drives conversion across the full customer population rather than a single record. This is the procedure most likely to be wrapped by a concurrent program.
• VALIDATE_CUSTOMER (PRIVATE) — Added 04-Jun-2001. Because it is private, it is not callable from outside the package body and is not included in the ETRM-documented procedure list. In the context of a user search for "validate_customer," this is the relevant routine: it performs pre-conversion or post-conversion validation of customer data, invoked internally by CUSTOMER_CONVERSION and ALL_CUSTOMER_CONVERSION rather than directly by external code.

Tables Accessed

The supplied ETRM metadata does not enumerate referenced APPS synonyms, so no definitive table list can be stated. Based on the package's documented purpose and the QP schema context, the package logically operates against Advanced Pricing and customer entities such as QP_PRICE_LISTS (for the default euro price list and existing list updates) and customer-related tables including HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL or their predecessors in the older customer model. The validate_customer routine would read the same customer records to confirm conversion eligibility while writing nothing. These table associations should be confirmed by querying DBA_DEPENDENCIES before any code is built against the package.

Usage Notes

The package carries a "noship" header tag, indicating it was not shipped publicly and forms part of the euro upgrade/conversion infrastructure rather than the supported API surface. It is most likely invoked by concurrent programs and upgrade scripts during the EMU transition, with ALL_CUSTOMER_CONVERSION serving as the batch entry point and CUSTOMER_CONVERSION and SITES_CONVERSION providing record-level processing. ETRM records zero packages referencing it, confirming its role as a terminal conversion utility. Because validate_customer is private, developers cannot call it directly; validation behavior is reachable only through the public procedures. In 12.1.1 and 12.2.2 environments, this package is effectively historical — retained for compatibility with converted data sets — and should not be treated as a supported extension point.