Search Results cust_address_1_ext




Overview
Explore in AI Chat

Overview

APPS.RLM_RLMSCHRL_XMLP_PKG is the packaged body behind the Oracle E-Business Suite Release Management (RLM) schedule report, an XML Publisher (BI Publisher) concurrent program output whose result set is populated through PL/SQL formula columns. In Oracle EBS 12.1.1 and 12.2.2, this package belongs to the Oracle Release Management application and is classified as an "OTHER" API, meaning it is not a published, supported integration interface but an internal component generated and maintained to support the report's data model. Its principal business purpose is to resolve and format descriptive display values for customer scheduling data—customer account numbers, ship-from organizations, ship-to and bill-to locations, customer item numbers, delivery patterns, and concatenated item segments—so that the printed or exported schedule report presents meaningful business identifiers rather than internal numeric primary keys.

The package is structured as a set of XML Publisher formula functions, each corresponding to a placeholder in the report layout, plus before-report and after-formula trigger routines that control invocation timing during report execution.

Key Procedures and Functions

The documented surface of the package exposes 42 procedures and functions. The core set includes the following.

Tables Accessed

The package reads through APPS synonyms. HZ_PARTIES and HZ_CUST_ACCOUNTS provide the trading partner and customer account linkage used to populate the customer number; HZ_CUST_ACCT_SITES supplies ship-to and bill-to location codes. MTL_CUSTOMER_ITEMS resolves customer item numbers, while MTL_SYSTEM_ITEMS_KFV provides the concatenated item description key flexfield values. RLM_INTERFACE_HEADERS_ALL and RLM_SCHEDULE_HEADERS_ALL are the Release Management interface and schedule header tables that drive the report's core data set, and RLM_SHIP_DELIVERY_CODES supplies ship delivery pattern codes.

Usage Notes

This package is invoked exclusively through the XML Publisher engine when the RLM schedule report concurrent program is run; it is not called directly by forms or custom code. Each formula function is executed once per report row or group as its layout placeholder is rendered. Because the functions are defined with a WHEN OTHERS handler that returns NULL on error, failures in lookup logic degrade gracefully to blank output rather than aborting the report. Customizations should avoid modifying this package body directly; extensions should be implemented in copied report definitions or custom packages to preserve supportability across 12.1.1 and 12.2.2 upgrades.