Search Results z2intergroup_transfer




Overview
Explore in AI Chat

Overview

APPS.XTR_XTRLTIGI_XMLP_PKG is the generated PL/SQL package body that supports the Oracle E-Business Suite Treasury (ETRM) XML Publisher concurrent program XTRLTIGI. The suffix "XMLP_PKG" identifies it as a report-level package produced by the Oracle Reports-to-XML Publisher bridge, where report triggers and user parameters are re-implemented as PL/SQL functions inside a single package. Its business purpose is to render the "Letter of Interest / Group Interest" treasury report, which consolidates bank balances, interest costs, and intergroup transfer positions for a given company, party, and accounting period range, and presents them in a formatted letter addressed to a specified attention line.

The package is a presentation-layer artifact rather than a business-logic engine. It retrieves localized label text, validates entry parameters, and coordinates page-level formatting before and after the report data model is executed. In EBS 12.1.1 and 12.2.2 the source header records version 120.1 dated 2007/12/28, confirming the object predates the 12.2 online patching model and is shipped as a nonshipped (noship) custom or one-off component managed under the APPS schema.

Key Procedures and Functions

The documented package exposes six procedures and functions, each mapping to an Oracle Reports trigger of the same intent:

  • BEFOREREPORT — Executes once before the report data model runs. It calls CEP_STANDARD.GET_WINDOW_SESSION_TITLE to populate the company name header, then loads localized UI labels by querying XTR_SYS_LANGUAGES_VL for MODULE_NAME = 'XTRLTIGI' and assigning each ITEM_NAME (Z1PARAMETERS, Z1PERIOD_FROM, Z1PERIOD_TO, Z1COMPANY, Z1PARTY_CODE, Z2PAGE, Z2ATTENTION, Z2BANK_BALANCES, Z2FOR, Z2INTEREST_COSTS, Z2INTERGROUP_TRANSFER, Z2INTERGROUP_TRANSFERS, Z2IS, Z2REGARDS, Z2TOTAL_INTEREST_TO) to a report-level global. This is the routine that raises the XTR_LOOKUP_ERR message when the session title lookup fails.
  • AFTERPFORM — Runs after the parameter form is submitted, performing post-parameter housekeeping such as resolving or defaulting derived report values.
  • BEFOREPFORM — Runs before the parameter form is displayed, used to seed or pre-populate parameter fields.
  • AFTERREPORT — Runs once after all report output has been generated, used for cleanup and teardown of report-level state.
  • BETWEENPAGE — Fires between logical pages of output, controlling page-break behavior and resetting page-scoped counters or headers.
  • P_COMPANYVALIDTRIGGER — A validation trigger for the company parameter, confirming that the entered company value is acceptable before the report is submitted.

Tables Accessed

Two tables are referenced through APPS synonyms. XTR_SYS_LANGUAGES_VL is read in BEFOREREPORT to obtain the translated label text for every prompt and heading on the letter, filtered by MODULE_NAME 'XTRLTIGI'. FND_NEW_MESSAGES is referenced via the FND_NEW_MESSAGES.MESSAGE_TEXT anchored datatype used to declare L_MESSAGE, and is the underlying store consulted by FND_MESSAGE.SET_NAME and FND_MESSAGE.GET when the XTR_LOOKUP_ERR message is retrieved. FND_CONCURRENT_REQUESTS is accessed to resolve concurrent request context, consistent with standard XML Publisher report package behavior.

Usage Notes

This package is never called directly by application code. It is invoked exclusively by the XML Publisher runtime when the XTRLTIGI concurrent program is submitted, either from the Treasury responsibility menu or programmatically through the concurrent manager. The XTR_LOOKUP_ERR reference that users commonly search for originates in the BEFOREREPORT exception handler: if CEP_STANDARD.GET_WINDOW_SESSION_TITLE fails, the package sets message name XTR_LOOKUP_ERR, retrieves its text into L_MESSAGE, and raises application error -20101. Because the raised error passes NULL as the message argument, end users see the generic lookup failure rather than a detailed cause, so diagnosis typically requires enabling the P_DISPLAY_DEBUG parameter and reviewing the concurrent request log. Referenced by zero other packages, it has no inbound dependency within the ETRM schema and can be patched independently during upgrades.