Search Results oks_integration_util_pub




Overview

OKS_INTEGRATION_UTIL_PUB is a public PL/SQL utility package in the Oracle EBS Service Contracts (OKS) module. It supports the integration of Service Contracts data with external and dependent subsystems, particularly the order capture and JTF (JavaScript Topology Framework) layers. The package provides shared routines for building order detail records, converting and resolving date values, deriving ranges, and logging diagnostics. Its header ($Header: OKSRIUTS.pls 120.0) confirms it is an established component of the Service Contracts integration layer rather than a new or transitional object, and it remains valid across EBS 12.1.1 and 12.2.2.

The package operates under the OKS application with API classification PUB, meaning its procedures are intended for invocation by other Oracle code, concurrent programs, or justified custom extensions. It declares standard OKC_API message constants (for required-value, invalid-value, and token substitution errors) and a global G_EXCEPTION_HALT_VALIDATION exception, indicating its role in validation-driven integration flows. Global constants such as G_RULE_GROUP_CODE := 'SVC_K' and the family of JTF entity names (OKX_ORDERHEAD, OKX_ORDERLINE, OKX_SERVICE, OKX_WARRANTY, OKX_PARTY, OKX_OPERUNIT, OKX_PCONTACT) tie the package directly to Service Contracts rule groups and order/warranty integration identifiers.

Key Procedures and Functions

The package exposes six documented procedures and functions:

  • CREATE_K_ORDER_DETAILS — Populates Service Contracts order detail records (OKS_K_ORDER_DETAILS), assembling the detail rows required for integration of contract or rule information with order-capture structures.
  • GET_DATES — Retrieves effective date information relevant to the package's integration processing, typically used to determine the applicable start and end dates for rules or order details.
  • CONVERT_DATES — Converts date values between representations or calendars used by the Service Contracts and target integration layers.
  • DEBUG_LOG — Writes diagnostic output for troubleshooting integration executions.
  • UPGRADE_RULE_DATES — Upgrades or migrates rule date values, ensuring existing rule records carry forward valid effective dates during data upgrade or maintenance operations. This is the procedure most directly associated with the user search term.
  • GENERATE_RANGES — Produces date or numeric range sets used to drive rule and order-detail processing.

Tables Accessed

The package references the following objects through APPS synonyms:

  • OKC_RULES_B and OKC_RULE_GROUPS_B — the base rule and rule-group tables for Service Contracts; read and updated in rule date processing.
  • OKS_K_ORDER_DETAILS — the order detail staging table populated by CREATE_K_ORDER_DETAILS.
  • DBMS_JOB, DBMS_LOCK, USER_JOBS — used for scheduling and serializing batch or concurrent processing.
  • PLITBLM — the PL/SQL table utility for in-memory collections.
  • UTL_FILE — used to write debug log output.
  • V$INSTANCE, V$PARAMETER — read for session/database context and diagnostics.

Usage Notes

OKS_INTEGRATION_UTIL_PUB is not typically invoked directly from a form. It is called by other Service Contracts packages — the metadata records that two packages reference it — and by concurrent programs or custom code that perform rule date upgrades, generate ranges, or create order detail records during integration or upgrade activities. The presence of DBMS_JOB, DBMS_LOCK, and USER_JOBS indicates that some invocations are batch or scheduled rather than interactive. Because it is a PUB package, Oracle supports its documented interfaces for customer extension; however, its global exception and constants should be respected so that error handling and token substitution remain consistent with OKC_API conventions. The UPGRADE_RULE_DATES procedure is the appropriate entry point when rule effective dates must be migrated or corrected, and DEBUG_LOG or UTL_FILE output should be reviewed when diagnosing failures in that flow.