Search Results rp_item_flex2_p
Overview
APPS.ONT_OEXIODIS_XMLP_PKG is the PL/SQL backing package for an Oracle Order Management XML Publisher (BI Publisher) concurrent report. The package naming convention — ONT for the Order Management schema, OEXIODIS for the report short name, and the _XMLP_PKG suffix — identifies it as an auto-generated shell package created at report registration time. Its principal responsibilities are to declare the report's bind parameters, format display values through formula functions, and supply the before/after report logic and lexical reference (LP_) values that the XML data template uses to construct the SQL executed against the Order Management tables.
In the context of Oracle EBS 12.1.1 and 12.2.2, the package is not a public application programming interface. It is an internal code unit owned by APPS and classified as OTHER. The search term rp_item_flex2_p corresponds to one of the formula functions within this package that governs how item flexfield information is rendered on the report output.
Key Procedures and Functions
The documented procedures and functions fall into three groups.
- Report lifecycle: BEFOREREPORT and AFTERPFORM perform initialization and bind-variable setup before the data template executes. AFTERREPORT runs post-processing and report cleanup. AFTERPFORM executes after the parameter form is submitted, allowing the package to derive internal values from user selections.
- Reference and label helpers: C_BUILD_LBLFORMULA, CF_SO_HOLDFORMULA, CF_PO_ITEM_DISPLAYFORMULA, and CF_ORDER_BYFORMULA build the dynamic label and formula text consumed by the XML template. P_CUSTOMER_NUMBER_LOWVALIDTRIG provides validation logic for the low customer number parameter.
- Report parameter accessors: RP_REPORT_NAME_P, RP_COMPANY_NAME_P, RP_SUB_TITLE_P, RP_ORDER_RANGE_P, RP_REQUISITION_RANGE_P, RP_ORDER_DATE_RANGE_P, RP_ITEM_DISPLAY_METHOD_P, RP_OPEN_ORDER_ONLY_P, RP_ORDER_BY_P, RP_ITEM_FLEX2_P, RP_ITEM_FLEX_ALL_SEG_P, and RP_ITEM_RANGE_P return formatted parameter strings for display in the report header and body.
RP_ITEM_FLEX2_P specifically returns the display text associated with the second item flexfield segment selection supplied by the user. RP_ITEM_FLEX_ALL_SEG_P returns the concatenated representation of all item flexfield segments, and RP_ITEM_DISPLAY_METHOD_P returns the chosen item display mode. Together these functions drive the flexible item identification presentation on the report.
Tables Accessed
The package reads from the following APPS-synonymed tables:
- FND_CONCURRENT_REQUESTS — used to resolve the concurrent request context, including the request ID bound to P_CONC_REQUEST_ID.
- OE_ORDER_HOLDS_ALL — supplies hold information referenced by CF_SO_HOLDFORMULA for sales order hold display.
- OE_TRANSACTION_TYPES_TL — provides translated order transaction type names for order type and category labels (LP_ORDER_TYPE, LP_ORDER_CATEGORY).
- MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS, MTL_CROSS_REFERENCES, MTL_CROSS_REFERENCE_TYPES — support customer item and cross-reference resolution, which the item flexfield display logic and item range filters rely on.
These tables indicate the report focuses on order-line detail with item cross-reference and flexfield enrichment.
Usage Notes
ONT_OEXIODIS_XMLP_PKG is invoked exclusively by the Oracle XML Publisher concurrent program with which it is registered. Users do not call it directly. It is not referenced by any other PL/SQL package, confirming its role as a report-specific artifact. The parameter variables declared in the package specification (P_ORDER_NUM_LOW, P_ITEM_FLEX_CODE, P_ITEM_STRUCTURE_NUM, P_SOB_ID, and similar) map to the concurrent program's parameter form, while the LP_ variables hold lexical substitution values embedded into the report's SQL query. Customization should be avoided; interface changes should be handled through the underlying report definition or by creating a copy of the concurrent program rather than modifying the seeded package. In 12.2.2 the object remains an internal APPS-owned unit with no public API classification, so it should be treated as read-only from an integration standpoint.