Search Results get_sub_line_number

Overview

OKS_IBINT_PUB is the public package body that supports Oracle Service Contracts integration with Oracle Installed Base (IB) and related order capture entities. Its central purpose is to synchronize service contract coverage with item instances, subscriptions, and contracts so that the installed base reflects the commercial agreements captured in order management and service contract modules. The package carries a 12.1.1 and 12.2.2-compatible header string and is registered under the APPS schema with a PUB (public) API classification, meaning its entry points are intended to be called from outside the package itself, including by other Oracle modules and by customer extensions.

The constants at the top of the body (G_LEVEL_UNEXPECTED, G_LEVEL_ERROR, G_LEVEL_EXCEPTION, G_LEVEL_EVENT, G_LEVEL_PROCEDURE, G_LEVEL_STATEMENT, and G_LEVEL_CURRENT) demonstrate that the package uses the FND_LOG diagnostic framework, with the module tag 'oks.plsql.oks_int_ibint_pub'. This enables DBAs and support engineers to trace execution granularly by runtime level. The header comment identifies a package version date of 2012/07/23.

Key Procedures and Functions

• IB_INTERFACE — The principal entry point that drives the installed base interface processing, coordinating the creation and update of item instances and their association with contracts.
• DELETE_BATCH — Removes a batch of interface records, typically used when a prior interface run must be backed out or a staging set is no longer required.
• CREATE_BATCH_RULES — Establishes the rule set that governs a batch interface invocation, defining which records qualify for processing.
• CREATE_K_COVERED_LEVELS_WEBADI — Creates the covered-level structures for a contract (K) via the WebADI interface, allowing desktop uploads of coverage hierarchies.
• CHECK_SUBSCR_INSTANCE — Validates a subscription instance, confirming that the subscription record is consistent before coverage is applied.
• POPULATE_CHILD_INSTANCES — Builds the child instance records beneath a parent instance so the installed base reflects the full component hierarchy.
• CHECK_CONTRACTS_IMPACTED — Determines whether one or more contracts are affected by a change, supporting deletion and update safeguards.
• GET_CONTRACTS — Retrieves the contracts associated with a given order line or instance, used to drive downstream coverage logic.
• CREATE_ITEM_INSTANCE — Creates a new CSI_ITEM_INSTANCES record for an item that is entering the installed base.
• VALIDATE_NEW_OWNER — Confirms that a proposed owner for an instance is valid and permissible before ownership is reassigned.

Note that the body also contains internal helpers such as CHECK_PARENT_CP_K, which verifies that a parent customer product exists for a given order line and service order line before coverage is extended.

Tables Accessed

• CSI_ITEM_INSTANCES, CSI_INSTANCE_STATUSES, CSI_COUNTER_ASSOCIATIONS, CSI_I_ORG_ASSIGNMENTS — The installed base tables that are read and written as instances are created, statused, counted, and assigned to organizations.
• OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_SYSTEM_PARAMETERS_ALL — Source order data used to identify the line and inventory item from which an instance originates, and to read order-management system parameters.
• OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_CLASS_OPERATIONS — Service contract structures that link contracts, contract lines, and items to the installed base coverage being generated.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL — Customer and account relationship data used when validating owners and locating the customer associated with an order.
• MTL_SYSTEM_ITEMS_TL, MTL_UNITS_OF_MEASURE_TL — Item and UOM translation views providing descriptive attributes for the created records.

Usage Notes

OKS_IBINT_PUB is referenced by sixteen other packages, making it a widely depended-upon integration API within the Service Contracts and Installed Base ecosystem. It is typically invoked from Service Contracts forms and concurrent programs that process installed base interfaces, from Enterprise Install Base workflows, and from order-to-service-contract integration paths. Custom code should call the documented public procedures rather than the private helpers, and should respect the FND_LOG module settings when debugging. Because the package manipulates CSI_ITEM_INSTANCES and OKC contract tables together, invocations should be treated transactionally, and the CHECK_CONTRACTS_IMPACTED and VALIDATE_NEW_OWNER routines should be exercised before destructive operations such as DELETE_BATCH.