Search Results concurrent




Overview
Explore in AI Chat

Overview

The concurrent program OKL_AM_VEND_RES_SHR_RPT is an Oracle Leasing and Finance Management (OKL) report owned by the OKL product family within Oracle E-Business Suite. It is presented to end users under the user-facing name OKL Report - Vendor Residual Share Report. As its name implies, the program produces a report of vendor residual sharing activity that has already been performed, allowing leasing operations and finance personnel to review, reconcile, and audit residual participations passed between the lessor and its vendor or third-party partners.

Residual sharing is a common commercial arrangement in equipment leasing, where an originating vendor retains a portion of the end-of-term residual value of a leased asset. The report gives visibility into those distributions after the underlying transactions have been processed, rather than calculating or posting them. It is therefore a reporting and enquiry object, not a transaction-generating one. The program is delivered enabled and is available to any OKL implementation without additional configuration, subject to the standard security and responsibility setup that governs concurrent program access.

Execution Details

The documented execution metadata for this program is as follows:

  • Product: OKL - Leasing and Finance Management
  • User Name: OKL Report - Vendor Residual Share Report
  • Description: Report for Vendor Residual Sharing which has been done
  • Enabled: Yes
  • Execution Method: Java Concurrent Program
  • Argument Method: Standard
  • Executable: OKLXMLWRAPPER
  • Executable User Name: OKLXMLWRAPPER
  • Execution Filename: JCP4OKLXmlPublisherWrapper

The use of the OKLXMLWRAPPER executable with the Java class JCP4OKLXmlPublisherWrapper indicates that this report is implemented on top of the Oracle XML Publisher (BI Publisher) framework. The wrapper class invokes the underlying data definition and layout template registered in the XML Publisher repository for the Vendor Residual Share Report, then returns the generated output to the concurrent manager. This is the standard pattern across many OKL print and report programs in releases 12.1.1 and 12.2.2, and it allows the report layout to be modified through RTF or XSL-FO templates without changing the executable definition.

How to Run

Users submit the program from the Standard Request Submission (SRS) window — Requests > Run in the navigator — by selecting OKL Report - Vendor Residual Share Report from the list of values. Access is controlled by the request group assigned to the responsibility, so the program will only appear for responsibilities whose request groups include it.

Because the Argument Method is Standard, the parameters are defined on the concurrent program itself rather than supplied through a custom argument mechanism. Typical OKL reporting parameters for this type of program include a ledger or operating unit, a date range restricting the residual sharing activity to be reported, and vendor or contract identifiers used to narrow the output. The exact parameter list is defined in the concurrent program definition and should be reviewed in the System Administrator responsibility under Concurrent > Program for the specific instance. Output can be directed to the standard report destination, and because the run-time engine is XML Publisher, the layout can also be previewed or regenerated from the XML Publisher Administrator responsibility if the template requires adjustment.

Related Objects

The program belongs to the OKL concurrent program family that shares the OKLXMLWRAPPER executable, including other XML Publisher-based OKL reports such as the various OKL Report series programs for contracts, residuals, and accounting. Related functional objects typically include the OKL vendor residual sharing entities and the underlying leasing contract tables (OKL_* base tables) from which the report extracts data, as well as the associated XML Publisher data definition and layout that are registered under the OKL application. Administrators diagnosing issues with the report generally check the concurrent request log, the XML Publisher template registration, and the data returned by the OKL residual sharing tables, in that order.