Search Results okl_mla_create_update_pub_w




Overview
Explore in AI Chat

Overview

OKL_MLA_CREATE_UPDATE_PUB_W is an Oracle Applications (APPS) PL/SQL package body within the Oracle Lease and Finance Management (OKL) module. It belongs to the ETRM (Enterprise Transaction Resource Model) family of APIs and functions as the public "W" (wrapper) layer for the OKL_MLA_CREATE_UPDATE_PUB package. In Oracle EBS 12.1.1 and 12.2.2, "MLA" refers to the Multi-Ledger Architecture / accounting integration layer used by leasing contracts. The package's business purpose is to expose the deal creation, update, and party creation logic of the leasing module to external or internal callers through a stable, published interface. The "W" suffix convention in EBS indicates that this package translates between the public API data structures (record types and PL/SQL tables) and the core OKL_MLA_CREATE_UPDATE_PUB implementation, performing parameter massaging and Rosetta (field-mapping) table copy operations before delegating to the underlying API.

The package body is documented in ETRM 12.2.2 as VALID with an API classification of OTHER, owned by APPS, and it is not referenced by any other database object, confirming its role as a top-level entry point rather than an internal helper.

Key Procedures and Functions

The package exposes nine documented procedures. The core business operations are:

  • CREATE_DEAL — Creates a new lease/loan deal in the OKL data model, initiating the contract record that underpins the MLA transaction.
  • UPDATE_DEAL — Modifies an existing deal, allowing changes to contract attributes after initial creation.
  • CREATE_PARTY — Creates party (customer/lessee/vendor) information associated with the leasing transaction.
  • ROSETTA_TABLE_COPY_IN_P7 / P9 / P11 — Inbound Rosetta table copy routines. These map "Rosetta" (translation/mapping) tables into the PL/SQL table structures consumed by the core API for the corresponding parameter groups (P7, P9, P11).
  • ROSETTA_TABLE_COPY_OUT_P7 / P9 / P11 — Outbound counterparts that copy result data from the core structures back into Rosetta tables for the same parameter groups.

The numbered P7, P9, and P11 suffixes correspond to distinct parameter groupings or record segments, indicating the wrapper is organized around multiple logical parameter sets. No parameter lists are documented, so the exact signatures are intentionally not reproduced here.

Tables Accessed

The only documented table referenced through APPS synonyms is PLITBLM, which is the Oracle PL/SQL "table of index-by tables" support table used for nested-table handling. Its presence confirms the package relies heavily on PL/SQL collection types. The package also depends on the JTF collection types JTF_DATE_TABLE, JTF_NUMBER_TABLE, and the JTF_VARCHAR2_TABLE_100/200/300/500/2000 types, which are the standard EBS mechanisms for passing date, number, and character collections into APIs. The actual deal and party persistence is performed downstream by OKL_MLA_CREATE_UPDATE_PUB and OKL_API, so the base OKL deal, party, and accounting tables are written indirectly rather than directly by this wrapper.

Usage Notes

OKL_MLA_CREATE_UPDATE_PUB_W is typically invoked programmatically — from custom PL/SQL, from concurrent program logic, or from OKL forms that need to create or update deals and parties through a supported public entry point. Because it depends on FND_API and OKL_API, it should be called within the standard FND global initialization context (initializing the FND message/API stack and committing or rolling back around the call). Since the package is not referenced by any database object, callers must reference it explicitly by its APPS synonym. The Rosetta copy procedures are normally invoked internally by CREATE_DEAL and UPDATE_DEAL to marshal collections; direct external invocation is uncommon and should be avoided. As with all OKL public APIs, error handling is expected to follow the FND_API convention of returning a return status and message stack rather than raising unhandled exceptions.