Results for “check_source”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.OKL_AM_SERVICE_K_INT_WF package is an Oracle Lease and Finance Management (OLFM/OKL) integration component belonging to the ETRM (Enterprise Transaction and Resource Management) suite. It serves as a workflow-oriented bridge between the asset management module and the Oracle Workflow / Service Contracts (OKC) infrastructure. Its primary business function is to detect, evaluate and publish workflow events relating to the servicing of leased assets — including asset returns, disposition, termination, and de-linking activities. The package validates the appropriate source context for a workflow event, assembles notification payloads for the various business scenarios, and raises integration events into the Workflow event queue. It is classified as a supporting API (classification OTHER) rather than a formal public API, and is chiefly invoked by other OKL business processes rather than directly by end users.
Key Procedures and Functions
The documented interface exposes ten procedures/functions, which fall into four functional groups.
- GET_ASSETS_SCHEDULE — Retrieves the schedule of assets associated with a given contract or service context, providing the input data used by the remaining notification routines.
- RAISE_SERVICE_K_INT_EVENT — The central integration routine; constructs and raises the service-related workflow event into the Workflow event system based on the caller's business context.
- CHECK_SOURCE — Validates the origin or calling context of a request, ensuring only legitimate sources trigger downstream event generation.
- POPULATE_ATTRIBUTES — Populates the attribute collection (an OKC/FND-style attribute map) used to carry context values into notification messages.
- POP_RETURN_NOTI_DTLS — Assembles the notification details for asset return scenarios.
- POP_DISPOSE_NOTI_DTLS — Assembles notification details for asset disposition scenarios.
- POP_TERM_NOTI_DTLS — Assembles notification details for contract/asset termination scenarios.
- POP_DELINK_NOTI_DTLS — Builds the payload for successful de-link notifications.
- POP_DELINK_ERR_NOTI_DTLS — Builds the payload for de-link error notifications.
Tables Accessed
The package reads and writes a mixture of OKL, OKC and inventory tables (through APPS synonyms). Contract structure is sourced from OKC_K_HEADERS_B, OKC_K_LINES_B/OKC_K_LINES_TL, OKC_K_ITEMS, OKC_K_REL_OBJS, OKC_LINE_STYLES_B and OKC_STATUSES_B, which supply the contract, line and status context for each event. Asset instances are drawn from CSI_ITEM_INSTANCES, while MTL_SYSTEM_ITEMS supplies master item definitions. Asset return data is obtained from OKL_ASSET_RETURNS_B, and quote-line data from OKL_TXL_QUOTE_LINES_B. Workflow integration relies on OKL_WF_ITEM_S and WF_EVENTS to publish events, with FND_NEW_MESSAGES and FND_USER providing message text and recipient information.
Usage Notes
This package is not designed for direct end-user invocation. It is typically called from OLFM business flows (for example, the asset return, termination and disposition processes), from the OKL_AM_LEASE_LOAN_TRMNT_PVT package, or from its own internal routines (it is referenced by itself). Custom developments that need to raise a service-related lease workflow event should call RAISE_SERVICE_K_INT_EVENT after populating context through the appropriate notification routines. Because WORKFLOW and OKC_API/OKL_API are dependencies, callers should initialise the standard API application context (FND_GLOBAL / MO_GLOBAL) and commit appropriately. Form-based or concurrent-program integrations that trigger these events should ensure the Workflow background engine processes are running so generated events are consumed as expected.