Search Results p_yes

Overview

APPS.ENG_ENGRCNDR_XMLP_PKG is the generated PL/SQL package body that backs the Oracle E-Business Suite concurrent program for the Engineering Change Notice (ECN) report. In the 12.1.1 and 12.2.2 releases this package belongs to the Oracle Engineering (ENG) product family and is classified in ETRM as OTHER. Its role is to supply the data selection, lookup translation, revision resolution, and display-format logic required by the XML Publisher report template associated with the ECN listing. The package is instantiated by the Oracle Reports/XML Publisher runtime whenever the concurrent request executes; the BEFOREREPORT trigger initialises session-level variables and the numerous *_DISPFORMULA functions resolve conditional column output within the XML template.

The search term reported by the user, p_yes, corresponds to the package-level global variable assigned in BEFOREREPORT. It is populated from MFG_LOOKUPS by selecting the first four characters of the SYS_YES_NO lookup meaning for lookup code 1, and is subsequently used to set P_ADDITIONAL_CODE and P_ORDER_ENTRY_CODE based on the report parameters P_ADDITIONAL_DETAIL and P_ORDER_ENTRY_DETAIL. This mechanism allows the printed report to display localised Yes/No text rather than numeric flags.

Key Procedures and Functions

• BEFOREREPORT — Main initialisation trigger. Sets date-format conversions for P_FROM_DATE and P_TO_DATE, derives P_YES and P_NO from MFG_LOOKUPS, resolves the ECN status character, captures the concurrent request ID, and generates the report sequence from BOM_LISTS_S.NEXTVAL.
• AFTERREPORT — Post-processing trigger, typically used to release SRW initialisation resources.
• BEFOREPFORM / AFTERPFORM / BETWEENPAGE — Formatting triggers controlling page-level output and repeated header behaviour.
• GET_REV / LATEST_REV — Resolve the current or latest item revision for the change-notice line, reading MTL_ITEM_REVISIONS.
• LIMIT_CHANGE_NOTICES — Constrains the change-notice result set according to the entered selection criteria and organisation hierarchy.
• GET_NAME / GET_REQ_NAME / GET_ITEM_TYPE — Name resolution helpers returning party names, requester names, and inventory item type descriptions for the report body.
• OPTIONAL_DISPFORMULA, COSTED_DISPFORMULA, CHECK_ATP_DISPFORMULA, MUTUALLY_EXCLUSIVE_DISPFORMULA, REQUIRED_TO_SHIP_DISPFORMULA, REQUIRED_FOR_REVENUE_DISPFORMU, INCLUDE_ON_SHIP_DISPFORMULA, QUANTITY_RELATED_DISPFORMULA — Conditional display-format functions that translate the ECN attribute flags into the appropriate printed indicator for each column of the XML report.

Tables Accessed

• BOM_LISTS — Bill of material list headers referenced by the change-notice query.
• BOM_LISTS_S — Sequence source for the report's internal list identifier via NEXTVAL.
• MTL_ITEM_REVISIONS — Revision data for items affected by the ECN.
• MTL_PARAMETERS — Organisation parameters, used to resolve the master organisation and filter by organisation when P_ALL_ORGS is set.
• MFG_LOOKUPS — Lookup meanings for SYS_YES_NO and ECG_ECN_STATUS.
• HZ_PARTIES — Trading partner and requester name resolution.
• DUAL — Single-row selection for sequence initialisation.
• PLITBLM — Standard Oracle Reports temporary table used by the runtime for report processing.

Usage Notes

This package is invoked exclusively through its associated concurrent program and XML Publisher template. It is not referenced by any other package in the ETRM repository, confirming that the direct entry point is the registered concurrent executable. Customisations should not modify the package body directly; instead, the underlying report query or template should be copied and extended. Any custom code calling it must supply the mandatory report parameters P_FROM_DATE, P_TO_DATE, P_STATUS, P_ALL_ORGS, P_ADDITIONAL_DETAIL, and P_ORDER_ENTRY_DETAIL. Because the package sets P_CONC_REQUEST_ID from FND_GLOBAL.CONC_REQUEST_ID, it must always execute inside a valid concurrent request context.