Search Results cf_address3formula
Overview
RLM_RLMSCHRL_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by APPS and classified as OTHER in the ETRM repository. It is a report logic package generated for use with Oracle XML Publisher (BI Publisher) in release 12.1.1 and 12.2.2. The backport/trap identifiers in the package name, RLM_RLMSCHRL, tie it to the Return Material Authorization (RMA) and return-related scheduling functionality within the Logistics and Receiving Management modules. Specifically, the "SCHRL" suffix indicates it is the report-level package for a scheduling report, and the XMLP designation confirms that it produces the layout data and conditional formatting consumed by an XML Publisher template.
The header comment ($Header: RLMSCHRLS.pls 120.0 2008/01/25 ...) indicates a stable, low-revision codebase — version 120.0 with no site-level (noship) exceptions — meaning the package body is a shipped seed component rather than a customized object. It exposes a large set of global package variables that mirror the report's parameter form, together with formula functions used by the XML template to compute display values.
Key Procedures and Functions
The 42 documented program units fall into two groups: lifecycle hooks and column formulas.
- BEFOREREPORT and AFTERPFORM — standard XML Publisher report triggers. BEFOREREPORT runs when the report begins, initializing session state and resolving the concurrent request context. AFTERPFORM runs after the parameter form is submitted, primarily to build the dynamic P_WHERE_CLAUSE used to filter the schedule query.
- CF_*FORMULA functions — individual column formulas invoked from the XML layout to translate internal IDs into user-facing text. CF_CUSTOMER_NUMFORMULA resolves a customer number from CUSTOMER_ID; CF_SHIP_FROM_ORGFORMULA and CF_SHIP_FROM_ORG1FORMULA derive ship-from organization names from the ship-from org ID; CF_SHIP_TO_LOCFORMULA, CF_SHIP_TO_LOC1FORMULA, CF_BILL_TO_LOCFORMULA and CF_BILL_TO_LOC1FORMULA resolve ship-to and bill-to addresses; CF_ADDRESS1FORMULA, CF_ADDRESS2FORMULA and CF_ADDRESS3FORMULA return the three free-form address lines (the "cf_address2formula", i.e. address line 2, is the most commonly searched of these); CF_CUST_ITEM_NUMFORMULA and CF_CUST_ITEM_NUM1FORMULA return the customer item number; CF_INV_ITEM_CONC_SEGMENTFORMUL and CF_INV_CONC_SEGMENT1FORMULA return the inventory item concatenated segment; CF_SHIP_DEL_PATTERNFORMULA and CF_SHIP_DEL_PATTERN1FORMULA return the shipping delivery pattern code; CF_SCHEDULE_SOURCEFORMULA returns the schedule source description; and CF_TEST_INDICATORFORMULA returns a test/indicator flag.
Tables Accessed
The package queries eight APPS synonyms to populate the report. HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES and HZ_PARTIES supply the Trading Community Architecture (TCA) customer, account site and party data used by the customer, address and ship-to/bill-to formulas. MTL_CUSTOMER_ITEMS and MTL_SYSTEM_ITEMS_KFV provide customer item numbers and concatenated inventory item descriptions for the item formulas. RLM_INTERFACE_HEADERS_ALL and RLM_SCHEDULE_HEADERS_ALL are the core scheduling/receiving tables holding the header records reported. RLM_SHIP_DELIVERY_CODES supplies the shipping delivery pattern code for the delivery pattern formulas. Access is read-oriented, consistent with a report package.
Usage Notes
The package is invoked exclusively by the concurrent program that runs the associated Scheduling report, driven by the XML Publisher engine. It is not referenced by any documented dependent packages (0 referencing packages), so it should be treated as a leaf reporting object. The heavy use of VARCHAR2(32767) for the P_ package variables and separate CP_ variables indicates the standard Concurrent Programs parameter set rendered through the XML Publisher parameter form. Customizations should be limited to XML template changes; modifications to the package body would be overwritten by patching, so any field-level changes (for example, altering the format returned by CF_ADDRESS2FORMULA) are best implemented through a copied template rather than by editing this shipped package.