Search Results nls_yes

Overview

APPS.AR_ARXPAR_XMLP_PKG is the report-generation PL/SQL package body that supports the Oracle Receivables AutoCash Rules report (ARXPAR), an XML Publisher (BI Publisher) concurrent program in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package implements the standard Oracle Reports-to-XML Publisher integration hooks — BeforeReport and AfterReport — and a small set of formula columns and report placeholders consumed by the report template. The package participates in the AutoCash rules reporting flow within the Receivables application, translating stored lookup and concurrent program values into the localized strings and report metadata that appear on the printed or exported output. The body carries the header marker $Header: ARXPARB.pls 120.0 2007/12/27 13:58:13 abraghun noship $, indicating a shipped, non-customized object maintained by Oracle development. In the context of the original search term "nls_yes," the package contains a dedicated NLS_YESFORMULA function whose purpose is to resolve the YES/NO lookup meaning for the display language.

Key Procedures and Functions

• BEFOREREPORT — Executes at the start of the report run. It captures the concurrent request identifier from FND_GLOBAL and assigns it to the package variable P_CONC_REQUEST_ID, which is subsequently used to look up request, program, and report names. It returns TRUE to allow the report to continue.
• AFTERREPORT — Executes on completion of the report run and returns TRUE. It serves as the standard termination hook and contains no business logic in this version.
• REPORT_NAMEFORMULA — Derives the report name from the company name argument supplied by the report, stores it in RP_COMPANY_NAME, and queries FND_CONCURRENT_PROGRAMS_VL/FND_CONCURRENT_REQUESTS to resolve the user-facing concurrent program name (truncated to 80 bytes) into RP_REPORT_NAME. On NO_DATA_FOUND or missing data the default value 'AutoCash Rules' is returned.
• NLS_YESFORMULA — Returns the localized meaning of the lookup type 'YES/NO' with lookup code 'Y' from AR_LOOKUPS. This function supplies the translated positive-response text ("Yes") to the report layout. On NO_DATA_FOUND it returns a single space, preserving the template structure.
• NLS_NOFORMULA — The counterpart to NLS_YESFORMULA, returning the localized meaning for lookup code 'N'; on NO_DATA_FOUND it returns a single space.
• RP_COMPANY_NAME_P — Accessor function that exposes the stored RP_COMPANY_NAME placeholder to the report.
• RP_REPORT_NAME_P — Accessor function that returns RP_REPORT_NAME truncated at the first occurrence of ' (XML)', so the user sees the business report name without the XML Publisher suffix.

Tables Accessed

The package references two documented data sources. It queries FND_CONCURRENT_REQUESTS (through the APPS synonym) to resolve the concurrent request into the associated program and application identifiers, and it joins to FND_CONCURRENT_PROGRAMS_VL to obtain the user_concurrent_program_name. The two NLS formula functions read the AR_LOOKUPS view, filtering on lookup_type = 'YES/NO' and the relevant lookup_code, to retrieve the locale-specific lookup meaning. Both the YES and NO paths rely on this single lookup view, so an incomplete or inactive YES/NO lookup definition will drive the exception handler to return a blank placeholder.

Usage Notes

AR_ARXPAR_XMLP_PKG is invoked only in the context of the ARXPAR concurrent program — the AutoCash Rules report — rather than being called directly from Forms or custom code. During a report submission, the Oracle Reports runtime calls BeforeReport before the data model executes and AfterReport after the last section is processed; the formula columns NLS_YESFormula, NLS_NOFormula, and report_nameformula are evaluated by the report layout and placed on the output. The accessor functions (RP_COMPANY_NAME_p, RP_REPORT_NAME_p) are invoked as placeholders by the XML Publisher template to display the derived company and report names. Because the package is owned by APPS and shipped by Oracle under the "noship" flag, customers should not modify it; any localization requirement, including the Yes/No text driven by the "nls_yes" search, is resolved dynamically from AR_LOOKUPS at runtime, ensuring the report reflects the session language without code changes.