Search Results cf_inv_conc_segment1formula

Overview

RLM_RLMSCHRL_XMLP_PKG is an Oracle EBS PL/SQL package owned by APPS and classified as OTHER. It is the generated runtime support package for the Oracle Release Management (RLM) concurrent program report "RLMSCHRL" — the Schedule/Release Report XML Publisher (BI Publisher) layout package. In EBS 12.1.1 and 12.2.2, XML Publisher report packages follow a standard pattern: the report's SQL query supplies bind parameters and a WHERE clause, then the report triggers call functions in the package to format derived columns and to produce the parameter display block on the report header. This package exists almost exclusively to serve that reporting contract.

Its parameter attributes (P_CUSTOMER, P_SCHEDULE_TYPE, P_SCHEDULE_NUM, P_SHIP_FROM, P_SHIP_TO, P_HORIZON_START_DATE, P_TP_FROM/TO, P_PROCESS_DATE_FROM/TO, P_ORG_ID, P_CONC_REQUEST_ID, and others) map directly to the report's concurrent program parameters. The CP_… variables populate the "parameter display" section of the report, while P_WHERE_CLAUSE carries the dynamically constructed filter predicate built from those parameters.

Key Procedures and Functions

The 42 documented units fall into two groups. The first is EBS boilerplate required by every XML Publisher report package:

• BEFOREREPORT — initializes package-level variables and default values before the report query executes, a standard entry point for the report's Before Report trigger.
• AFTERPFORM — runs after the parameter form; includes validation logic for date-range parameters (issue date, process date, horizon dates), which must satisfy ordering constraints.

The second group consists of the CF_…FORMULA column functions, which are called from the report's SELECT statement to derive reported values that are not stored directly in the base tables:

• CF_CUSTOMER_NUMFORMULA — returns the customer number for a given customer identifier.
• CF_SHIP_FROM_ORGFORMULA, CF_SHIP_FROM_ORG1FORMULA — resolve the ship-from organization name/code depending on the schedule source and the org identifier or customer-specific override.
• CF_SHIP_TO_LOCFORMULA, CF_SHIP_TO_LOC1FORMULA, CF_BILL_TO_LOCFORMULA, CF_BILL_TO_LOC1FORMULA — derive formatted ship-to and bill-to location descriptions from address identifiers.
• CF_ADDRESS1FORMULA, CF_ADDRESS2FORMULA, CF_ADDRESS3FORMULA — return the address lines of the ship-to party site.
• CF_CUST_ITEM_NUMFORMULA, CF_CUST_ITEM_NUM1FORMULA — return the customer's item number from the customer item cross-reference.
• CF_INV_ITEM_CONC_SEGMENTFORMUL and CF_INV_CONC_SEGMENT1FORMULA — return the inventory item's concatenated segments (which the user's search term "cf_inv_conc_segment1formula" points to), i.e. the formatted item key flexfield value. The name is truncated to Oracle's 30-character identifier limit, which is why the object appears in two variants.
• CF_SHIP_DEL_PATTERNFORMULA, CF_SHIP_DEL_PATTERN1FORMULA — translate the ship delivery code into its description.
• CF_SCHEDULE_SOURCEFORMULA, CF_TEST_INDICATORFORMULA — supply the schedule source description and the report's test/blank indicator respectively.

Tables Accessed

All table access is through APPS synonyms. RLM_SCHEDULE_HEADERS_ALL and RLM_INTERFACE_HEADERS_ALL supply the scheduling and interface header rows that are the report's subject. RLM_SHIP_DELIVERY_CODES backs CF_SHIP_DEL_PATTERNFORMULA. HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, and HZ_PARTIES provide the TCA customer, party, and site data used by the customer, ship-to, bill-to, and address functions. MTL_CUSTOMER_ITEMS supplies the customer item cross-reference used by CF_CUST_ITEM_NUMFORMULA, and MTL_SYSTEM_ITEMS_KFV supplies the concatenated item segment description used by CF_INV_ITEM_CONC_SEGMENTFORMULA. Lookups are read-only; the package writes no data.

Usage Notes

This package is not intended for direct invocation. It is called by the Oracle Reports/XML Publisher runtime when the restricted concurrent program RLMSCHRL is submitted, either from the Release Management responsibility or by any request set invoking that report. In practice, the CF_ functions are referenced by name inside the report's data model queries, so a query containing "CF_INV_CONC_SEGMENT1FORMULA" will fail to compile against a database where the APPS synonym or package does not exist or is invalid. Because it is generated code and has no dependents (referenced by 0 other packages), it should not be extended or modified directly; customizations belong on the underlying views or in the report template. Migration or patching activity should ensure the package is compiled valid after TCA or RLM table changes, since invalid TCA objects will cascade failures into the report.