Search Results okl_in_tpp_pvt

Overview

OKL_IN_TPP_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle Lease and Finance Management (OKL) application within Oracle E-Business Suite. The "PVT" classification indicates that this is an internal, private-scope package, intended for use by other members of the OKL_IN module rather than as a public API surface. Its role is tied to the "IN" (Installment / Interface) functional area of the ETRM/OKL product family.

Based on the package name and the two documented procedures, the package appears to deal with Third Party Payment (TPP) processing — specifically the resolution and handling of agency and agent addresses associated with lease contract parties. In lease finance scenarios, payments are frequently routed through an agency or an agent acting on behalf of a lessor or lessee, and correct address resolution from the TCA (Trading Community Architecture) model is essential for remittance, billing, and correspondence. The private designation confirms that OKL_IN_TPP_PVT is a helper package; it exposes its logic only to sibling packages within the OKL installation and is not documented as a supported entry point for external or customer-written code.

The package's status is recorded as VALID, and it resides in the APPS schema alongside the rest of the OKL application objects. Per the ETRM metadata it references APPS.OKL_API and the SYS STANDARD package, and it is referenced by a same-named public package, OKL_IN_TPP_PVT suggesting the private body supplies implementation used indirectly through higher-level callers.

Key Procedures and Functions

The ETRM metadata documents exactly two procedures on this package:

• AGENCY_ADDRESS — resolves or returns the address associated with an agency involved in the third party payment flow. In the lease model, an agency is a party that facilitates payment handling on behalf of contractual parties; this procedure encapsulates the lookup logic for that agency's address data.
• AGENT_ADDRESS — resolves or returns the address associated with an agent acting in the third party payment chain. This is logically parallel to AGENCY_ADDRESS but targets the agent party rather than the agency entity.

No parameter lists are documented in the ETRM resource, and none should be assumed. What can be stated with confidence is that both procedures exist and that their purpose is address retrieval/resolution within the TPP (Third Party Payment) processing path. Because the package is classified private, these procedures are not intended as a supported integration API; they are implementation helpers consumed within the OKL_IN package family.

Tables Accessed

The documented table references are exposed through APPS synonyms and are:

• HZ_PARTIES — the TCA Registry table holding party records. The package reads this to identify the agency or agent party associated with the lease transaction and to obtain party-level attributes needed for address resolution.
• HZ_PARTY_SITES — the TCA table linking parties to sites (locations). Used to obtain the site assignments that underpin the actual address returned by AGENCY_ADDRESS and AGENT_ADDRESS.

These two tables reflect a standard TCA address resolution pattern: locate the party in HZ_PARTIES, then resolve its location associations in HZ_PARTY_SITES. The package also depends on APPS.OKL_API, the core lease public API package, indicating it participates in the broader OKL contract and party processing model. No writes are documented, but given the "get address" semantics, read operations are most likely, with any state changes handled by the calling layer.

Usage Notes

OKL_IN_TPP_PVT is not designed for direct invocation by customers or by concurrent programs. Its private classification and its dependency chain — referencing OKL_API and being referenced by a same-named public wrapper — indicate that it is invoked indirectly by the public OKL_IN_TPP package, which in turn is called from standard lease processing, such as contract creation, third party payment setup, and remittance processing.

When lease contracts involve an agency or agent for payment routing, standard OKL flows will reach this package to populate the address information on documents, notifications, and payment instructions. Custom code should not call OKL_IN_TPP_PVT directly: the supported route is the corresponding public API or the standard forms and concurrent programs that already delegate to it. Any extension or troubleshooting at this level should focus on ensuring the HZ_PARTIES and HZ_PARTY_SITES records for the relevant agency or agent are accurate, valid, and properly dated, since this package depends entirely on that TCA data to produce a correct address.