Search Results get_phone_email




Overview
Explore in AI Chat

Overview

IBE_ORDER_UTIL_PVT is a private PL/SQL package in the Oracle E-Business Suite iStore (IBE) module. It provides a collection of utility routines that support the iStore ordering flow, exposing helper logic used internally by other iStore packages rather than serving as a public integration API. The package is owned by APPS and classified as PVT (private), which indicates that it is intended for internal consumption within the IBE schema and is not formally published for customer extension. Its responsibilities cluster around three areas: computing recurring or subscription order totals, resolving price adjustments and model configuration actions for configured items, and retrieving primary contact information (phone and email) for an iStore party. The last documented routine, VALIDATE_LAST_UPDATE_DATE, supports optimistic concurrency checking on order records.

Key Procedures and Functions

  • GET_ORD_RECURRING_TOTALS — Returns the recurring charge breakdown for an order header, including periodicity code, description, and meaning as well as recurring subtotal, tax, charges, and total amounts. It follows the standard IBE/PL/SQL API convention of returning status, message count, and message data. It is used to display or persist recurring-billing figures on subscription-style orders.
  • GET_ADJUSTMENTS — Returns price adjustment detail for a header and/or line, exposing adjustment name, description, list line number, adjustment type code, arithmetic operator, price adjustment identifier, operand, unit discount amount, and the count of lines. Both the header and line parameters default to FND_API.G_MISS_NUM, allowing callers to scope the query to a header, a line, or both.
  • GET_MACD_ACTION_MODE — Returns action-mode information for a model or configuration change (MACD), including the top model line identifier and a flag indicating whether the line is subject to reconfiguration. This supports the configured-item flows in iStore.
  • GET_PHONE_EMAIL — A function that retrieves the primary phone and email for an iStore party. The documented comment distinguishes caller behavior by party type: for B2C, the caller passes the person_party_id of a PERSON-type party; for B2B, the caller passes the party_id of a PARTY_RELATIONSHIP. This function is the object most directly associated with the user's search for "get_phone_email".
  • VALIDATE_LAST_UPDATE_DATE — Verifies whether a supplied last_updated_date is older than the current stored value, providing the concurrency check used by iStore order utilities.

Tables Accessed

Documented references reach the following tables through APPS synonyms:

  • HZ_CONTACT_POINTS — the source of phone and email contact point data for GET_PHONE_EMAIL.
  • OE_ORDER_HEADERS_ALL — header-level order data used by the recurring totals, adjustments, and last-update-date routines.
  • OE_ORDER_LINES_ALL — line-level data supporting adjustment, model line, and configuration logic.
  • PLITBLM — used for the multi-row PL/SQL table handling associated with the array-typed out parameters.

Usage Notes

Because IBE_ORDER_UTIL_PVT is classified PVT, it is not intended as a supported extension point. It is typically invoked indirectly by other iStore packages during order submission, order review, and configuration display; the ETRM metadata records it as referenced by two other packages. The routines are also candidates for use from iStore JSP/UI layer code and from custom PL/SQL that needs the same recurring-total, adjustment, or contact-lookup logic. Custom code that calls the package must pass NOCOPY table types such as JTF_VARCHAR2_TABLE_300 and JTF_NUMBER_TABLE for the collection out parameters and must observe the standard X_return_status, X_msg_count, and X_msg_data error convention. The package header carries a header comment dated 2005, indicating stability across the 12.1.1 and 12.2.2 releases. For GET_PHONE_EMAIL specifically, callers must select the correct identifier by party type — person_party_id for B2C and the PARTY_RELATIONSHIP party_id for B2B — to obtain the primary phone and email values.