Search Results pos_url_pkg




Overview
Explore in AI Chat

Overview

APPS.POS_URL_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under ETRM as OTHER (a supporting utility package rather than a public API). Its business function is to centralize the construction of iProcurement and Procurement self-service URLs within Oracle EBS 12.1.1 and 12.2.2. The package resolves internal and external application endpoints, builds login redirect URLs, and assembles destination page URLs complete with query parameters. It also derives context for menu functions based on whether the notification performer is a buyer or another role, returning a menu_function_parameter_rec that carries the appropriate home page and function identifiers (for example, POS_HT_SP_HP and POS_HT_SP_B_SUPP for buyers, versus ISP_HOMEPAGE_MENU and POS_HOME otherwise).

By isolating URL and navigation logic in a single package, Oracle ensures consistent link generation across notifications, workflow messages, and personalizations, so that users are routed to the correct page regardless of whether they access the system internally or externally. The header comment indicates the package has been stable since at least the 12.1.1 code line (POSURLB.pls 120.4.12010000.1, 2008/07/25).

Key Procedures and Functions

The ETRM metadata documents seven callable program units, each supporting a distinct navigation scenario:

  • GET_INTERNAL_URL — Returns the base URL for internal (within the corporate network) access, used as the foundation for buyer-facing links.
  • GET_EXTERNAL_URL — Returns the base URL for external access, typically used when the application is reached through a reverse proxy or DMZ configuration.
  • GET_INTERNAL_LOGIN_URL — Builds the login URL for users connecting internally, ensuring unauthenticated recipients of notifications are redirected to the correct sign-in page.
  • GET_EXTERNAL_LOGIN_URL — Builds the corresponding login URL for external users.
  • GET_BUYER_LOGIN_URL — Provides the buyer-specific login URL, distinguishing the procurement professional entry point from general self-service entry.
  • GET_DEST_PAGE_URL — Assembles the final destination page URL, appending menu-function context, function identifiers, and parameter name/value pairs into a query string.
  • GET_NTF_VENDOR_ID — Retrieves the vendor identifier associated with a notification, allowing supplier-facing links to be resolved correctly.

The package body additionally defines private helpers, such as get_menu_function_context, get_base_buyer_url, and get_page_url, which build the base OA.jsp endpoint and append parameters. The body's logic shows a trailing-slash check so that URLs are concatenated without producing double slashes.

Tables Accessed

The package reads from the following tables, accessed through APPS synonyms:

  • FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — Used to retrieve profile option settings that determine site-specific URL values and environment behavior at runtime.
  • WF_ITEM_ACTIVITY_STATUSES — Consulted to resolve workflow notification context, identifying the activity associated with a notification so that the correct page can be targeted.
  • WF_NOTIFICATIONS — Read to obtain notification attributes, including the performer and related vendor information.
  • OWA_PATTERN — An Oracle Web Agent utility used for pattern matching and string manipulation when parsing or constructing URL components.
  • PLITBLM — A PL/SQL table used for internal string handling operations.

Usage Notes

POS_URL_PKG is not intended for direct end-user invocation; it is a server-side utility invoked programmatically. It is referenced by 10 other packages within the APPS schema, which call its URL-building functions when generating links embedded in workflow notifications, iProcurement home page personalizations, and approval routing messages. Typical callers pass a destination function identifier and performer context, then receive a fully qualified URL suitable for inclusion in an e-mail or notification body.

Custom code extending Oracle Procurement should treat these functions as the supported mechanism for URL generation rather than hard-coding OA.jsp paths, because the internal versus external distinction and profile-driven base URLs are resolved centrally. In 12.1.1 and 12.2.2 deployments, administrators must ensure the relevant profile options for application URL are configured, since the package depends on them to return correct internal, external, and login endpoints. The package is read-only with respect to business data, making it safe to invoke from concurrent programs, forms personalizations, and OAF controllers without transactional side effects.