Search Results get_modifier

Overview

OKS_MASS_UPDATE_PVT is a private PL/SQL package in the APPS schema that provides the core implementation logic for the Oracle Service (OKS) mass update feature in Oracle E-Business Suite 12.1.1 and 12.2.2. The package supports the bulk modification of service contracts and their associated lines, enabling users to apply attribute changes across large sets of contracts in a single operation rather than editing each record individually. Its classification as a PVT (private) package indicates that it is not intended for direct invocation by external applications; instead, it is called by the public API layer, specifically OKS_IBINT_PUB, which exposes mass update functionality to Oracle Integration and related contract interfaces. The package also contains internal forward references to itself, consistent with the recursive processing that mass update operations frequently require when traversing contract hierarchies and service lines.

The package depends on the standard Oracle Application Object Library APIs FND_API and FND_LOG for error handling and debug logging, and on OKC_API for core contract operations. This dependency pattern confirms that OKS_MASS_UPDATE_PVT operates within the standard EBS API framework rather than as a standalone utility.

Key Procedures and Functions

The documented interface exposes sixteen procedures and functions that cover validation, lookup, and update processing:

• UPDATE_CONTRACTS — the principal procedure that performs the mass update of contract records and their lines.
• VALIDATE_ACCOUNT_ID — verifies that a customer account identifier supplied for the update is valid.
• CHECK_RELATION — evaluates relationship conditions between contract or party records during the update.
• GET_ADDRESS and SITE_ADDRESS — retrieve address information, typically for site-level or party-level resolution.
• GET_STE_CODE, GET_STATUS, GET_STATUS_CODE, and GET_LINE_STATUS — return status and state code values used to filter or set contract and line attributes.
• GET_END_DATE — obtains the end date applicable to a contract or line during updates.
• GET_SEQ_NO, GET_LINE_NUMBER, and GET_TOPLINE_NUMBER — resolve sequence and line numbering, including top-level line identification for hierarchical line structures.
• GET_MODIFIER and NEGOTIATED_AMOUNT — return pricing-related values used in the update of contract terms.
• CREATE_TRANSACTION_SOURCE — establishes the transaction source context required when mass update changes generate downstream transactional records.

These routines collectively handle the validation, lookup, and attribute resolution needed before and during a mass update.

Tables Accessed

The package reads and writes several categories of tables through APPS synonyms. Customer and party data is accessed via HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_ORG_CONTACTS, supporting account validation and address resolution. Service and contract configuration data comes from OKS_BATCH_RULES, OKS_BILLING_PROFILES_B, and OKS_K_DEFAULTS. Installed base and counter data is drawn from CSI_ITEM_INSTANCES and CSI_COUNTER_ASSOCIATIONS. Additional references include CSI_MASS_EDIT_ENTRIES_TL for mass edit entry descriptions, CS_CTR_ASSOCIATIONS, CS_INCIDENTS_ALL_B, and FND_ATTACHED_DOCUMENTS for service request and attachment context. Together these tables supply the customer, contract, installed base, and reference information required to validate and apply mass updates.

Usage Notes

OKS_MASS_UPDATE_PVT is not intended for direct calls from custom code. It is invoked by OKS_IBINT_PUB, the public integration API, which in turn is typically driven from the Service Contracts mass update user interface or from concurrent processing that applies bulk changes to selected contracts. Developers extending mass update behavior should call the public API rather than this private package. Because the package writes to contract and line records, it should be invoked within a controlled transaction with appropriate error handling; the use of FND_API and FND_LOG allows callers to retrieve standardized error messages and enable debug logging when diagnosing mass update failures. As a PVT package, its signature may change between patch levels, so customizations should be validated after upgrades to 12.1.1 or 12.2.2.