Results for “okl_create_adj_pvt”

8 results




Overview
Explore in AI Chat

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

Overview

IEX_WRITEOFFOBJ_PUB is a public PL/SQL API in the Oracle EBS Applications (APPS) schema that governs the creation, approval, and rejection of writeoff objects within the iReceivables and Advanced Collections writeoff framework. The package is declared with AUTHID CURRENT_USER and serves as the orchestration layer that links a business writeoff request to the underlying Oracle Lease Management (OKL) and Oracle Receivables (AR) adjustment infrastructure. Its documented purpose is fourfold: to populate the OKL_TRX_ADJST_B and OKL_TXL_ADJSTS_LNS_B staging structures, to invoke the OKL_CREATE_ADJ_PVT wrapper for adjustment creation, to verify approval status before a writeoff is committed, and to update the IEX_WRITEOFF_OBJECTS record once the adjustment exists. The package is classified as a PUB API, meaning it is intended for supported external invocation from forms, concurrent programs, and custom extensions. Its source header dates to release 120.4 (2007), and the object remains documented in ETRM for both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes seven documented procedures and functions. The type definitions at the top of the specification establish the record structures passed between layers, including writeoff_rec_type (aliased to IEX_WRITEOFFS_PVT), writeoff_obj_rec_type, adjv_rec_type, and ajlv_rec_type.

  • CREATE_WRITEOFFS — The primary entry point. It accepts a writeoff object record, a writeoff type, an object identifier, and an invoice line identifier, and returns the generated adjustment identifier. It drives the population of the OKL adjustment staging tables and the call to the OKL adjustment creation wrapper.
  • APPROVE_WRITEOFFS — Confirms approval of a pending writeoff, allowing the adjustment flow to proceed upon a positive approval decision.
  • REJECT_WRITEOFFS — Records and processes the rejection of a writeoff request, preventing adjustment creation and updating the writeoff object status accordingly. This is the routine most frequently associated with the search term "reject_writeoffs."
  • INVOKE_WRITEOFF_WF — Invokes the Oracle Workflow process associated with the writeoff lifecycle, supporting the approval routing that APPROVE_WRITEOFFS and REJECT_WRITEOFFS subsequently act upon.
  • INIT_WRITEOFFOBJ_REC — Initializes the writeoff object record structure, populating default and miss-value attributes before a create or update operation.
  • GET_MESSAGES and GET_MESSAGES1 — Retrieve messages from the FND message stack so that calling forms can surface validation or processing errors to the user.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. IEX_WRITEOFFS and IEX_WRITEOFF_OBJECTS hold the writeoff header and object-level records that this API maintains. AR_ADJUSTMENTS, AR_PAYMENT_SCHEDULES, and AR_PAYMENT_SCHEDULES_ALL provide the Receivables adjustment and payment schedule context required to build the writeoff. Case integration relies on IEX_CASES_ALL_B and IEX_CASE_OBJECTS, tying the writeoff to a collections case. Resource and user attribution uses JTF_RS_RESOURCE_EXTNS and FND_USER. Contract linkage uses OKC_K_HEADERS_B and OKL_STRM_TYPE_B, while the Workflow parameter list is drawn from WF_PARAMETER_LIST_T. Message-stack access uses FND_NEW_MESSAGES and PLITBLM.

Usage Notes

IEX_WRITEOFFOBJ_PUB is typically invoked from the iReceivables and Advanced Collections writeoff forms, where the create, approve, and reject actions are user-driven. It may also be called from concurrent programs or custom PL/SQL that requires programmatic writeoff creation, provided the caller observes the standard FND_API messaging conventions (p_init_msg_list, p_commit, x_return_status, x_msg_count, x_msg_data). Because the package writes to OKL and AR adjustment structures, callers should ensure the relevant lease and Receivables data is committed before invocation. No other packages in the documented inventory reference this API, so it functions as a top-level service rather than an internal dependency.