Search Results generate_pm_schedules

Overview

The APPS.OKS_IMPORT_POST_INSERT package is a component of the Oracle Service Contracts (OKS) module within Oracle E-Business Suite, released under versions 12.1.1 and 12.2.2. Its business function is to perform the post-insert processing phase of the Service Contracts Import process. When service contracts are loaded into the application from external sources or staged interface tables, the raw header, line, covered level, and usage counter records must be inserted first before downstream contractual artifacts can be derived. This package supplies the single entry point that executes those dependent routines after the initial insert completes.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the package owner, a design pattern that respects the invoker's security context during import. The source header identifies its creation by Mihira Karra and dates the file revision to September 2007, consistent with the ETRM 12.2.2 documented metadata that classifies it as API classification OTHER.

Key Procedures and Functions

The package exposes exactly one documented public procedure: IMPORT_POST_INSERT. ETRM metadata records no parameters for this procedure; it is invoked without an explicit argument list and coordinates the following post-insert routines, as enumerated in the package's own comment block:

• Generate_billing_schedules — derives billing schedules for the newly inserted contract lines.
• Generate_PM_schedules — generates preventive maintenance (PM) schedules tied to the imported contract coverage. This is the routine most commonly associated with the search term "generate_pm_schedules."
• Create_JTF_notes — creates notes in the JTF (Interaction / Notes) framework for the imported contracts.
• Instantiate_srvc_ctr_events — instantiates service contract events that drive subsequent business processing.
• Rollup_amounts — calculates and rolls up monetary amounts across contract headers and lines.

There are no additional documented functions or overloads in the ETRM 12.2.2 metadata; the procedure is the sole published interface.

Tables Accessed

The package reads and writes a mixture of base Service Contracts tables, interface/staging tables, and reference tables, referenced through APPS synonyms:

• Base contract tables: OKC_K_HEADERS_ALL_B, OKC_K_LINES_B, OKS_K_LINES_B, OKS_STREAM_LEVELS_B, and OKS_LEVEL_ELEMENTS hold the definitive header, line, stream level, and level element records that post-insert processing manipulates.
• Reference tables: OKC_TIME_CODE_UNITS_B and OKC_TIME_CODE_UNITS_TL supply the time-code unit definitions used when generating billing and PM schedules.
• Staging and interface tables: OKS_COVERED_LEVELS_INTERFACE, OKS_INT_COVERED_LEVEL_STG_TEMP, OKS_INT_HEADER_STG_TEMP, OKS_INT_LINE_STG_TEMP, OKS_INT_USAGE_COUNTER_STG_TEMP, and OKS_NOTES_INTERFACE carry the incoming import data through the temporary staging area prior to conversion into permanent contract records.
• Utility objects: DUAL for singleton SELECTs and PLITBLM, the standard PL/SQL integer table type used for array processing within the package.

Usage Notes

This package is not intended for direct end-user invocation. It is called programmatically at the conclusion of the Service Contracts Import flow, typically from Service Contracts Import concurrent programs or from the importing framework after rows have been inserted into the OKS interface and staging temp tables. Custom integration code that loads contracts through the OKS import interface should invoke OKS_IMPORT_POST_INSERT.IMPORT_POST_INSERT once all insert activity is committed, so that billing schedules, PM schedules, JTF notes, service contract events, and amount rollups are generated consistently.

ETRM metadata shows the package is referenced by one other package, confirming it operates as a subordinate step rather than a top-level entry point. Because the procedure takes no parameters, it relies on session context and the state of the interface tables at invocation time. Callers must ensure the relevant interface and staging temp tables are populated and that the preceding insert phase has completed; otherwise the schedule generation and rollup routines operate on incomplete data. Standard Oracle support practice applies: the package resides in the APPS schema and should be referenced with the APPS synonym rather than qualified directly against a custom schema.