Search Results get_billto_phone

Overview

OKS_AUTO_REMINDER is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a valid, OTHER-type API within the Service Contracts (OKS) module. Its principal business function is to support the automated reminder and notification process for service contracts, particularly around contract renewal, expiration, and status changes. The package provides the backend logic that evaluates service contract conditions, resolves recipient and contact information, and assembles the data required for outbound notifications. It is a supporting package in the OKS notification framework rather than a public transactional API, and it is tightly integrated with the Service Contracts workflow and mail subsystems. Because it is referenced by OKS_MAIL, OKS_K_ACTIONS_PVT, and OKS_WF_K_PROCESS_PVT, it operates as a shared utility layer invoked during contract lifecycle events and reminder processing.

Key Procedures and Functions

The package exposes twenty-five documented procedures and functions. Several provide contract state management, including UPDATE_CONTRACT_STATUS and UPDATE_RENEWAL_STATUS, which set the relevant status flags on contract records during reminder and renewal processing. VALIDATE_AUTOREMINDER_K validates the contract or contract line against auto-reminder rules. A group of getter functions retrieves contextual and organizational data: GET_ORG_CONTEXT, GET_ORG_ID, GET_PARTY_ID, and GET_QTOPARTY_ID resolve operating unit and party identifiers, while GET_DURATION and GET_TIME_STATS return timing metrics used to determine reminder intervals. Recipient resolution is handled by GET_BILLTO_CONTACT, GET_BILLTO_EMAIL, GET_BILLTO_FAX, GET_BILLTO_PHONE, and GET_QTO_EMAIL, which retrieve bill-to and quote-to contact details for notification delivery. Additional getters supply contract and product attributes: GET_LICENSE_LEVEL, GET_NO_OF_USERS, GET_PRICING_TYPE, GET_PRODUCT_NAME, and GET_SERVICE_NAME. CREATE_USER supports creation or resolution of the notification user context. Together these units supply the data that OKS_MAIL and the workflow process use to build and dispatch reminders.

Tables Accessed

The package reads and writes through APPS synonyms across several EBS schemas. Service Contracts data is drawn from OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, and OKC_CONTACTS, providing contract headers, lines, items, party roles, and contact records. Customer and product information comes from CS_CUSTOMER_PRODUCTS_ALL, which links installed base products to contracts. Trading partner and contact data is sourced from HZ_PARTIES, HZ_CUST_ACCOUNT_ROLES, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS, supporting party identity and communication endpoint resolution. Resource extension data is obtained from JTF_RS_RESOURCE_EXTNS, and security and user context from FND_USER, FND_RESPONSIBILITY, and FND_SECURITY_GROUPS. These tables collectively supply the contract, customer, contact, resource, and responsibility attributes needed to determine reminder recipients and content.

Usage Notes

OKS_AUTO_REMINDER is not typically invoked directly by end users. It is called programmatically by other Service Contracts components, specifically OKS_K_ACTIONS_PVT, OKS_MAIL, and OKS_WF_K_PROCESS_PVT, which drive contract actions, email generation, and workflow-based reminder processing. It may be executed indirectly through concurrent programs or workflow background processes that evaluate contract auto-reminder rules and generate notifications for renewals or expirations. In Oracle EBS 12.1.1 and 12.2.2 the package remains valid, and its dependency on OKC_API indicates reliance on the core Contracts API for certain operations. Customizations should avoid direct modification; instead, custom code should call the package's documented functions or hook into the OKS workflow and mail framework. Because it is a supporting utility with no documented public API signature, developers integrating with it should verify behavior against the specific EBS release and patch level in use.