Search Results create_cii_for_subscription

Overview

OKS_AUTH_UTIL_PUB is a public PL/SQL package in the APPS schema that provides the authorization utility application programming interface for Oracle Service Contracts (OKS) and Oracle Enterprise Trading Management (ETRM) in Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates a broad range of service-layer operations that support subscription management, service counter handling, customer and contact creation, and instance or item configuration. As a public (PUB) package, it is intended to be callable from external code, forms, concurrent programs, and other public APIs, in contrast to the underlying private implementation package OKS_AUTH_UTIL_PVT, to which it delegates much of its logic.

The package sits within the authorization and entitlement layer of ETRM, bridging the OKS (Service Contracts) data model with the OKC (Contracts Core) tables and customer-facing entities in Oracle Trading Community Architecture (TCA). Its procedures and functions serve to retrieve, validate, and persist data required to authorize, sell, and manage service and subscription offerings, including the creation and maintenance of counters that measure consumption against a contract or subscription entitlement.

Key Procedures and Functions

The documented interface exposes a variety of procedures and functions that fall into several functional categories:

• Selection retrieval: GETSELECTIONS_PROD and GETSELECTIONS_OTHER return selection data, distinguishing product-related selections from other selection types, typically used to populate or validate configuration choices.
• Copy utilities: COPYSERVICE and COPY_PARAMETER duplicate service definitions and their associated parameters, supporting clone and template scenarios.
• Counter handling: CHK_COUNTER and CHK_EVENT validate counter and event conditions, forming part of the usage metering and entitlement enforcement logic.
• Party and contact management: CONTACT_POINT resolves contact points; CREATE_PERSON, UPDATE_PERSON, CREATE_ORG_CONTACT, and UPDATE_ORG_CONTACT insert and maintain person and organization contact records in TCA.
• Party site management: CREATE_PARTY_SITE and UPDATE_PARTY_SITE create and update party sites associated with a customer or prospect.
• Trading Community roles and accounts: CREATE_CUST_ACCOUNT_ROLE, UPDATE_CUST_ACCOUNT_ROLE, and CREATE_CUST_ACCT_SITE establish customer account roles and account sites.
• CII and subscription utilities: CREATE_CII_FOR_SUBSCRIPTION and DELETE_CII_FOR_SUBSCRIPTION manage customer interaction or instance information tied to a subscription record.
• Status and code resolution: DEF_STS_CODE and GET_STE_CODE derive default status codes and service/event codes used during authorization processing.

Tables Accessed

The package reads from and writes to several key base and interface tables through APPS synonyms. Contract header and line data are accessed through OKC_K_HEADERS_B and OKC_K_LINES_B, with the view OKC_K_LINES_V used for line-level reads. Service counter functionality relies on CSI_COUNTERS_B, CSI_COUNTER_ASSOCIATIONS, CSI_COUNTER_TEMPLATE_B, and CS_CSI_COUNTER_GROUPS. Subscription and pricing data flow through OKS_SUBSCR_HEADER_B, OKC_CONDITION_HEADERS_B, OKC_PRICE_ADJUSTMENTS, and QP_LIST_HEADERS_B. Item references are resolved via MTL_SYSTEM_ITEMS_KFV, and PLITBLM supports list and value-set operations.

Usage Notes

OKS_AUTH_UTIL_PUB is typically invoked from the Service Contracts forms and related concurrent programs, as well as from custom extensions that need to programmatically authorize, meter, or replicate service and subscription data. It is also referenced by OKS_SUBSCRIPTION_PVT and by the package itself, indicating both internal orchestration and external consumption. Boundaries between the public and private packages should be respected: direct calls should target OKS_AUTH_UTIL_PUB, not OKS_AUTH_UTIL_PVT. Because the package performs DML across TCA and contract tables, callers should wrap invocations in appropriate transaction control and error handling consistent with FND_API, OKC_API, and OKS_QP_INT_PVT dependencies.