Search Results set_approver




Overview

OKL_SO_CREDIT_APP_WF is an Oracle Lease Management (OKL) workflow integration package owned by APPS and defined with AUTHID CURRENT_USER. Its business purpose is to drive the credit approval business process for lease quotes and lease applications: it raises a credit approval event from a quote, creates the credit application records, builds the individual credit lines, resolves the requestor and approver, updates process status, and dispatches the associated workflow notification messages. In effect, it is the PL/SQL glue between the OKL quote/application tables and the Oracle Workflow engine (WF_EVENTS, OKL_WF_ITEM_S), and between OKL and Oracle Credit Management (AR_CMGT_CREDIT_REQUESTS, AR_CMGT_CF_RECOMMENDS).

The package header declares three global constants naming the credit checklist templates used in the process — G_CREDIT_CHKLST_TPL ('LACCLH'), G_CREDIT_CHKLST_TPL_RULE1 ('LACCLT') and G_CREDIT_CHKLST_TPL_RULE2 ('LACCLD') — and a record type l_chr_rec that carries the credit-relevant context: party, customer account and site identifiers, contract, credit KHR, currency, transaction and requested amounts, term, contact and operating unit. This record defines the data passed through the workflow activities.

Key Procedures and Functions

Nine documented entry points exist. The workflow callback procedures (CREATE_CREDIT_APP, CREATE_CREDIT_LINE, UPDATE_STATUS, SEND_MESSAGE, SET_REQUESTOR and SET_APPROVER) all follow the standard Oracle Workflow PL/SQL signature of itemtype, itemkey, actid, funcmode and resultout, which identifies them as activity functions invoked from a workflow definition rather than from a form.

  • CREATE_CREDIT_APP_EVENT — Raises the credit approval event for a quote, taking the quote and requestor identifiers and returning a return status.
  • CREATE_CREDIT_APP — Workflow activity that creates the credit application and its supporting records.
  • CREATE_CREDIT_LINE — Workflow activity that creates the individual credit line records associated with the application.
  • UPDATE_STATUS — Workflow activity that writes back the status of the credit approval process.
  • SEND_MESSAGE — Workflow activity that generates and sends the notification message for the process.
  • SET_REQUESTOR — Workflow activity that resolves and assigns the requestor for the credit application.
  • SET_APPROVER — Workflow activity that resolves and assigns the approver. This is the procedure matching the search term "set_approver"; it determines the approver identity (typically from FND_USER and the resource extensions) and makes it available to the workflow so that the approval notification is routed correctly.
  • CREDIT_APP_DETAILS — Retrieves credit application detail information for use by the process.
  • CREDIT_K_END_DATED — Handles end-dating of the credit K (contract) header records referenced by the credit application.

Tables Accessed

The package operates across three functional areas. Lease and quote data is read from OKL_LEASE_QUOTES_B, OKL_LEASE_APPLICATIONS_B, OKL_LEASE_APPS_ALL_B, OKL_CREDIT_REQUESTS, OKL_K_LINES and OKL_WF_ITEM_S. Contract structure is resolved through OKC_K_HEADERS_B, OKC_K_LINES_B and OKC_LINE_STYLES_B. Credit Management integration and routing use AR_CMGT_CREDIT_REQUESTS, AR_CMGT_CF_RECOMMENDS, JTF_RS_RESOURCE_EXTNS and FND_USER. Workflow event creation and diagnostics use WF_EVENTS and FND_LOG_MESSAGES.

Usage Notes

This package is not normally called directly. It is invoked by the OKL credit approval workflow as its activity functions; SET_APPROVER and SET_REQUESTOR run as attribute-setting activities, CREATE_CREDIT_APP and CREATE_CREDIT_LINE as record-creating activities, SEND_MESSAGE as the notification activity, and UPDATE_STATUS as the post-approval status writer. CREATE_CREDIT_APP_EVENT is the programmatic entry point used to launch the process from a quote, and is the only procedure in the package that a custom extension would typically call. Customizations should respect the AUTHID CURRENT_USER declaration and the fact that no other packaged APIs reference this package, so it may be modified without cascading compilation impact.