Search Results process_trx_request
Overview
OKL_AMORT_SCHED_REQ_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) Release 12.1.1 / 12.2.2 Leasing and Financing (OKL) module. It supports the Oracle Lease Management (OLM) amortization schedule feature by preparing and submitting transaction requests against lease contracts. In OLM, schedule generation and recalculation are not performed inline within the calling transaction; instead, they are queued as transaction requests that are later picked up and processed by the lease transaction engine. This package provides the private, non–external-API layer responsible for constructing those request records and driving their processing. The package body header (OKLRAMRB.pls, version 120.6, dated 2008) shows utility logic for populating the transaction request table, including cursor retrieval of the contract's currency code and organization identifier. Under the ETRM classification, the package is designated a PVT (private) API, meaning it is intended for internal use by the application and is not published for external integration.
Key Procedures and Functions
- PROCESS_TRX_REQUEST — The single documented procedure in the package. It accepts a transaction request associated with a lease contract's amortization schedule and carries out the processing logic required to move that request through the transaction request pipeline. In practical terms, it is the entry point invoked to submit the amortization schedule request for execution, coordinating the data already staged in the request table (for example, a request of type AMORITIZATION_SCHEDULE_CURRENT with status PROCESSED, as populated by the companion populate_trx_table procedure visible in the package body). Parameter details are not exposed in the ETRM metadata; only the procedure name and purpose are documented.
Tables Accessed
- OKC_K_HEADERS_B — The base contract header table. The package reads this table to retrieve the currency code and organization identifier for the contract identified by p_chr_id. These attributes are required to correctly stamp the amortization schedule request with the contract's financial and organizational context.
- OKL_TRX_REQUESTS — The transaction request staging table. The package inserts or manages the record that represents the amortization schedule request. Fields populated include request status code, request type code, comments, and the contract identifier (dnz_khr_id), consistent with the okl_trx_requests_pub.trqv_tbl_type structure used in the package body.
Usage Notes
Because OKL_AMORT_SCHED_REQ_PVT is classified as a private API and is referenced by zero other packages in the documented metadata, it is intended strictly for internal invocation within the Oracle Lease Management application. Typical call paths originate from OLM contract forms or from concurrent programs that regenerate or refresh amortization schedules for lease contracts. A caller first invokes the populate routine to stage the request data (deriving currency and org from OKC_K_HEADERS_B), then calls PROCESS_TRX_REQUEST to commit the request for downstream processing by the lease transaction engine. Customizations should not call this package directly; instead, supported public APIs such as OKL_TRX_REQUESTS_PUB or the standard lease schedule generation processes should be used, since private packages carry no guarantee of interface stability across patches or upgrades. Developers debugging amortization schedule failures in Release 12.1.1 or 12.2.2 may nonetheless trace this package to understand how request records are created and why a schedule request remained in a given status.
-
PACKAGE BODY: APPS.OKL_AMORT_SCHED_REQ_PVT
12.2.2
-
PACKAGE: APPS.OKL_AMORT_SCHED_REQ_PVT
12.1.1
-
PACKAGE BODY: APPS.OKL_AMORT_SCHED_REQ_PVT
12.1.1
-
PACKAGE: APPS.OKL_AMORT_SCHED_REQ_PVT
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKC_K_HEADERS_B
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKC_K_HEADERS_B
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKC_K_HEADERS_B
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS_PUB
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS_PUB
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKC_K_HEADERS_B
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_AMORT_SCHED_REQ_PVT
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_AMORT_SCHED_REQ_PVT
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_TRX_REQUESTS
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on STANDARD
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_API
12.1.1
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on STANDARD
12.2.2
-
APPS.OKL_AMORT_SCHED_REQ_PVT dependencies on OKL_API
12.2.2