Search Results notify_salesrep

Overview

OKS_EXTWAR_UTIL_PUB is a public PL/SQL package in the APPS schema that provides utility services for the Oracle Service (OKS) extended warranty module within Oracle E-Business Suite 12.1.1 and 12.2.2. Extended warranties are sold as service contracts that entitle a customer to coverage, repair, or replacement of a product over a defined period. The package supplies the supporting logic that service and warranty flows require: resolving party, resource, and salesperson identifiers; retrieving warranty header information; staging warranty data; managing contacts associated with a warranty contract; applying status code translation; and producing notifications and log messages to administrators and sales personnel.

The package is classified as a PUB interface, meaning it is intended to be called by other application code rather than treated as a private implementation detail. It declares a War_tbl subtype derived from OKS_EXTWAR_UTIL_PVT and exposes several global constants and message tokens inherited from OKC_API, the Contracts foundation layer. This inheritance confirms that OKS_EXTWAR_UTIL_PUB operates within the Oracle Contracts messaging and error-handling framework, including standard tokens for required values, invalid values, column name substitution, and unexpected errors.

Key Procedures and Functions

The documented interface comprises 23 procedures and functions. Grouped by purpose:

• Warranty data retrieval: GET_WARRANTY_INFO returns warranty detail, and UPDATE_HDR_AMOUNT adjusts the header amount on a warranty contract.
• Resource and party resolution: GET_OKS_RESOURCE, GET_PARTY_ID, GET_SALESREP_ID, GET_RESOURCE_NAME, and GET_PARTY_NAME resolve internal identifiers and display names from resource, party, and salesperson data.
• Contact management: CREATE_CONTACT, DELETE_CONTACT, and REASSIGNCONTACT maintain the contact records attached to a warranty contract.
• Status and code handling: DEF_STS_CODE defines or derives a status code value, and GET_STE_CODE returns the associated STE code. These are the routines most relevant to the search term "def_sts_code," where DEF_STS_CODE supplies the default or derived status code used when processing warranty records.
• Messaging and notification: SET_MSG, GET_FND_MESSAGE, NOTIFY, LOG_MESSAGES, and the targeted notification routines NOTIFY_SETUP_ADMIN, NOTIFY_TERRITORY_ADMIN, NOTIFY_CONTRACT_ADMIN, and NOTIFY_SALESREP deliver alerts through Oracle Workflow/Notification mailers to the appropriate audience.

The package also declares a global exception, G_EXCEPTION_HALT_VALIDATION, used to abort validation processing when a fatal condition is detected.

Tables Accessed

The package reads and writes through APPS synonyms across several EBS schemas:

• Contracts tables: OKC_K_HEADERS_B, OKC_K_LINES_B, and OKC_K_PARTY_ROLES_B supply the warranty contract header, line, and party role records; OKC_CONTACTS stores contact data; OKC_STATUSES_B provides status code definitions consumed by DEF_STS_CODE and GET_STE_CODE.
• Party and location tables: HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS resolve customer and site information for contract parties and contacts.
• Resource and user tables: JTF_RS_RESOURCE_EXTNS, JTF_RS_RESOURCE_EXTNS_TL, and JTF_RS_SALESREPS identify service resources and sales representatives; OKS_JTF_RES_TEMP is a temporary staging table for resource data.
• HR tables: HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS_ALL provide organizational unit and internal location context.
• FND_USER is used to identify application users for notification and audit purposes.

Usage Notes

OKS_EXTWAR_UTIL_PUB is typically invoked indirectly. Oracle Service forms and extended warranty setup flows call it to populate resource and party fields, validate contacts, and apply status codes; concurrent programs and workflow notification activities call the NOTIFY and LOG_MESSAGES routines. The package is referenced by two other packages, so customizations or extensions in that dependency chain should account for its public signature. When extending or troubleshooting status behavior, DEF_STS_CODE is the appropriate entry point; callers should set the standard OKC_API message tokens before invoking messaging procedures so that errors are surfaced consistently through the EBS message dictionary.