Search Results jtf_varchar2_table_2000

Overview

The APPS.JTF_TERR_JSP_REPORTS_W package is a PL/SQL wrapper (denoted by the _W suffix) that supports the JSP-based reporting infrastructure of Oracle Territory Manager (JTF — the Java/HTML foundation shared by CRM modules such as Sales, Service, and TeleSales). It is defined with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the definer, which is typical for public integration surfaces that must respect row-level security and territory access rules.

The package acts as an internal bridging layer. Its role is to receive multi-value parameters submitted from a web (JSP) or form-based reporting page, convert them into strongly typed PL/SQL collections used by the territory reporting engine, and then expose the engine's tabular result set back out as flat collections that the JSP layer can render. In effect, it is the procedural glue between the browser-driven report request and the set-based territory report query logic held in the companion body jtf_terr_jsp_reports.

Key Procedures and Functions

ETRM documents exactly three callable units:

• ROSETTA_TABLE_COPY_IN_P1 — A "Rosetta stone" transformer that copies inbound flat string arrays into the package's internal composite report table type (jtf_terr_jsp_reports.report_out_tbl_type). The 20 input parameters (a0 through a19) are each typed as JTF_VARCHAR2_TABLE_2000, the standard Oracle EBS 2000-byte CLOB-less VARCHAR2 collection. This procedure converts the "many rows of scalar strings" shape produced by the JSP request into the record-oriented structure the report engine consumes.
• ROSETTA_TABLE_COPY_OUT_P1 — The inverse operation. It reads the internal report_out_tbl_type and unpacks it into 20 OUT NOCOPY JTF_VARCHAR2_TABLE_2000 parameters. NOCOPY is significant: it passes collection results by reference, avoiding the memory and CPU cost of copying large 2000-character arrays on each call, which matters for large territory reports.
• REPORT_CONTROL — The driving entry point. It accepts a report identifier (p_report) alongside up to four additional VARCHAR2 parameters (p_param1–p_param4) that select and filter the report to execute. This is the procedure typically invoked to trigger a specific JSP territory report.

Tables Accessed

The only table documented through APPS synonyms is PLITBLM, an Oracle Application Object Library table used for storing message and language-translation data. Its presence indicates that REPORT_CONTROL and the surrounding report engine retrieve user-facing labels, column headings, and error messages dynamically so that territory reports can be rendered in the session language rather than with hard-coded English text. Actual territory data is obtained indirectly through the parent jtf_terr_jsp_reports package rather than through direct references recorded in this wrapper.

Usage Notes

Because the package is marked as a wrapper and is not referenced by any other documented package, it is not a general-purpose public API. It is invoked internally by JSP pages or OAF/JTT components of the Territory Manager HTML interface, and potentially by concurrent programs that render territory reports. The JTF_VARCHAR2_TABLE_2000 type that dominates the signature — and which the user searched for — is the defining characteristic of this code: it is Oracle's standard EBS collection for passing arbitrarily long lists of strings between Java, JSP, and PL/SQL layers across the 12.1.1 and 12.2.2 releases. Developers extending territory reports should call these procedures only through the supported reporting UI or the parent package, and should not alter the wrapper signatures, since the JSP caller expects the fixed 20-array (a0–a19) contract.