Results for “ar_cmgt_application_num_s”

20 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.OKL_CREDIT_MGNT_PVT package body is a private (PVT) PL/SQL implementation unit within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, documented through ETRM for releases 12.1.1 and 12.2.2. It encapsulates the internal business logic that governs credit management activities across the lease and finance contract lifecycle. Specifically, the package provides the procedural engine that submits credit requests to the Oracle Receivables credit management framework, evaluates the outcome of those requests, and compiles the resulting credit data for consumption by calling APIs. Because the package is classified as a private API, it is not intended for direct invocation by external integrators; instead it is consumed by the public credit request interface, OKL_CREDIT_REQUEST_PUB, and by related contract-processing packages such as OKL_CRQ_PVT, OKL_CS_LC_CONTRACT_PVT, and OKL_EXECUTE_FORMULA_PUB. The object holds VALID status in the APPS schema, confirming it compiles cleanly against the referenced dependencies.

Key Procedures and Functions

Three program units are documented for this package body:

  • SUBMIT_CREDIT_REQUEST — Initiates a credit request against a lease or finance contract. This routine assembles the required credit application context—customer account, contract header, and party role information—and forwards it to the Oracle Receivables credit management API for evaluation.
  • CREDIT_REQUEST_OUTCOME — Retrieves or processes the result returned by the credit management framework after a submitted request has been evaluated. It serves as the mechanism by which the lease application learns whether credit was approved, declined, or requires further review.
  • COMPILE_CREDIT_REQUEST — Gathers and consolidates the credit request data elements required as input to the submission or outcome process. It acts as the data-preparation layer that bridges lease contract attributes with the credit request data model.

No parameter signatures are documented in the available metadata; integrators should reference the deployed package specification for exact signatures.

Tables Accessed

The package reads and writes several base tables through APPS synonyms. OKL_CREDIT_REQUESTS is the primary transactional store for credit request records originating from lease contracts. OKL_K_HEADERS, OKC_K_HEADERS_B, and OKC_K_PARTY_ROLES_B supply contract header and party-role context, linking each credit request to the correct lease instrument and responsible party. HZ_CUST_ACCOUNTS provides the customer account identity used by the Receivables credit engine. The sequence AR_CMGT_APPLICATION_NUM_S—the term matched in the user's search—generates the unique application number assigned to each credit request submitted to AR_CMGT_CREDIT_REQUEST_API. DUAL is used for single-row PL/SQL evaluations.

Usage Notes

OKL_CREDIT_MGNT_PVT is invoked indirectly. The public wrapper OKL_CREDIT_REQUEST_PUB and the internal coordinator OKL_CRQ_PVT call into this body when a lease or finance contract requires a credit decision, typically triggered from the contract authoring or booking flow in the OKL forms or through concurrent credit-check processing. It also depends on shared infrastructure utilities including FND_API, FND_GLOBAL, OKC_API, OKL_API, and JTF_IH_PUB for error handling, environment context, and interaction history logging. The metadata records that the package is referenced by three other database objects, all internal to OKL, and that it is not referenced by any external object. Customizations should never call the private body directly; use OKL_CREDIT_REQUEST_PUB instead, and re-validate all private signatures after any Oracle patch or upgrade, since private APIs are not covered by Oracle's public API stability guarantee.