Search Results get_object_details
Overview
OKS_CODE_HOOK is a client extension package body owned by APPS within the Oracle E-Business Suite Service Contracts (OKS) module. Its business function is to expose a set of predefined hook points that allow implementers and partners to inject custom business logic into standard Service Contracts processing without modifying Oracle-supplied code. The package is classified as OTHER in the ETRM repository, reflecting its role as a customizable extension layer rather than a transactional API. Each procedure follows a conventional hook contract: it returns a status indicator through an OUT parameter (typically 1 when the hook has been used, 0 when standard behavior should prevail, and -1 when an error occurs) together with one or more output values that override the default processing result. This design allows the calling Service Contracts programs to remain upgrade-safe while accommodating customer-specific rules.
Key Procedures and Functions
The documented procedures and functions (12 total) cover several functional areas of Service Contracts:
- TAX_TRX_DATE — Determines the transaction date used for tax calculation on a contract header or line, returning a hook status and a date.
- BILLING_INTERFACE_ST_DATE — A client extension that lets users apply an alternative approach when running the Service Contracts main billing program, returning a hook status, a billing interface start date, and a parallel processing hint.
- CALC_HEADER_AMT — Provides a hook for overriding or supplementing contract header amount calculation.
- CUSTOM_FUNCTION — A generic extension point allowing customer-defined logic to be invoked from standard processing.
- DATE_ASMBLR_FN — A function used in date assembly logic, typically for constructing effective dates during contract processing.
- CUSTOM_DA_PRC — A custom procedure for date-related processing within the contracts flow.
- GET_CUSTOM_STATUS — Retrieves a customer-defined status value for use by Service Contracts logic.
- UPDATE_MERGE_ACCOUNT — Handles account updates resulting from a merge operation.
- UPDATE_PARTY_MERGE — Handles party merge processing, propagating merged party information to contracts data.
- GET_CONTRACT_SOURCE_DETAILS — Returns details about the source of a contract, such as the originating order or document.
- GET_SUBS_QTY — Retrieves the subscription quantity associated with a contract line or service.
- GET_SUBS_UOM — Retrieves the unit of measure for a subscription quantity.
Tables Accessed
The package operates against standard Service Contracts and Order Management tables accessed through APPS synonyms:
- OKC_K_HEADERS_B and OKC_K_LINES_B — Contract header and line base tables, used to resolve contract context such as header and line identifiers and start dates.
- OKC_CLASS_OPERATIONS, OKC_OPERATION_INSTANCES, and OKC_OPERATION_LINES — Contract class and operation tables, supporting status and operation-related logic used by the status and merge hooks.
- OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — Order Management header and line tables, used by GET_CONTRACT_SOURCE_DETAILS to trace contract source information back to originating orders.
Usage Notes
OKS_CODE_HOOK is not invoked directly by end users. It is called by standard Service Contracts programs — most notably the billing program referenced by BILLING_INTERFACE_ST_DATE and tax calculation routines referenced by TAX_TRX_DATE — at designated hook points. Implementers customize the package body to add site-specific logic, and the value returned in the hook status parameter controls whether the custom logic replaces or supplements standard behavior. The package is referenced by eight other packages, indicating broad integration across the Service Contracts code base. Because customizations reside in this hook package, upgrades can proceed without reapplying changes to Oracle-owned objects. When searching for "get_object_details," note that no procedure of that name is documented in this package; equivalent metadata retrieval for contract objects is handled by GET_CONTRACT_SOURCE_DETAILS and related functions.
-
PACKAGE BODY: APPS.OKS_CODE_HOOK
12.2.2
-
PACKAGE BODY: APPS.AMS_APPROVAL_SUBMIT_PVT
12.2.2
-
PACKAGE BODY: APPS.AMS_APPROVAL_SUBMIT_PVT
12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL_EXT
12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL_EXT
12.2.2
-
PACKAGE BODY: APPS.JTF_TASK_UTL_EXT
12.1.1
-
PACKAGE BODY: APPS.JTF_TASK_UTL_EXT
12.2.2
-
PACKAGE BODY: APPS.ASO_APR_WF_PVT
12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL
12.1.1
-
PACKAGE: APPS.JTF_TASK_UTL
12.2.2
-
PACKAGE: APPS.OKL_AM_UTIL_PVT
12.1.1
-
PACKAGE BODY: APPS.ASO_APR_WF_PVT
12.2.2
-
PACKAGE: APPS.OKL_AM_UTIL_PVT
12.2.2
-
APPS.OKS_CODE_HOOK dependencies on OKC_K_REL_OBJS_V
12.2.2
-
APPS.ASO_APR_WF_PVT dependencies on ASO_QUOTE_HEADERS_ALL
12.2.2
-
APPS.OKL_AM_UTIL_PVT dependencies on OKL_TRX_MSGS
12.2.2
-
APPS.OKL_AM_UTIL_PVT dependencies on OKL_TRX_MSGS
12.1.1
-
APPS.ASO_APR_WF_PVT dependencies on ASO_QUOTE_HEADERS_ALL
12.1.1
-
PACKAGE BODY: APPS.AMS_ACTMETRICS_ENGINE_PVT
12.1.1
-
PACKAGE BODY: APPS.AMS_ACTMETRICS_ENGINE_PVT
12.2.2
-
APPS.ASO_APR_WF_PVT dependencies on ASO_APR_OBJ_APPROVALS
12.2.2
-
APPS.ASO_APR_WF_PVT dependencies on ASO_APR_OBJ_APPROVALS
12.1.1
-
PACKAGE BODY: APPS.OKL_AM_UTIL_PVT
12.2.2
-
PACKAGE BODY: APPS.OKL_AM_UTIL_PVT
12.1.1
-
APPS.AMS_APPROVAL_SUBMIT_PVT dependencies on FND_API
12.2.2
-
APPS.AMS_APPROVAL_SUBMIT_PVT dependencies on FND_API
12.1.1
-
APPS.JTF_TASK_UTL_EXT dependencies on FND_API
12.1.1
-
APPS.JTF_TASK_UTL_EXT dependencies on FND_API
12.2.2
-
PACKAGE BODY: APPS.JTF_TASK_UTL
12.2.2
-
PACKAGE BODY: APPS.JTF_TASK_UTL
12.1.1
-
APPS.JTF_TASK_UTL dependencies on FND_MSG_PUB
12.1.1
-
APPS.JTF_TASK_UTL dependencies on FND_MSG_PUB
12.2.2
-
APPS.OKL_AM_UTIL_PVT dependencies on OKL_API
12.2.2
-
APPS.OKL_AM_UTIL_PVT dependencies on OKL_API
12.1.1