Search Results get_contract_salesrep_email

Overview

OKS_CUSTOMER_ACCEPTANCE_PVT is a private PL/SQL package in the APPS schema that implements the customer acceptance and decline workflow for Oracle E-Business Suite service contracts. Within the ETRM (Enterprise Territory and Contracts) module, the package provides the programmatic engine behind the "Accept" and "Decline" actions presented to a customer who has been offered a contract or subscription. It resolves contract-related attributes such as amounts, tax, subtotals, vendor and customer identification, party and organization data, and sales representative e-mail addresses, then records the acceptance decision against the contract header. Because the object name carries the _PVT suffix, it is classified as a private API: it is not intended for direct external invocation and is instead called by public APIs, workflow activities, and views within the same product family.

The package deliberately separates read-only retrieval helpers from the two state-changing operations (ACCEPT_CONTRACT and DECLINE_CONTRACT), and it encapsulates e-mail delivery and payment-detail handling so that the acceptance flow can be driven end to end without exposing the underlying OKC and HZ tables to callers.

Key Procedures and Functions

The documented interface exposes twenty-four procedures and functions, grouped by purpose:

• Financial retrieval: GET_CONTRACT_AMOUNT, GET_CONTRACT_SUBTOTAL, and GET_CONTRACT_TAX return the monetary values presented to the customer for the contract under acceptance.
• Clause retrieval: GET_CONTRACT_ACCEPT_CLAUSE and GET_CONTRACT_DECLINE_CLAUSE return the acceptance and decline terms displayed to the customer, ensuring the correct contract clauses are surfaced for the decision.
• Party and entity resolution: GET_CONTRACT_VENDOR, GET_CONTRACT_CUSTOMER, GET_CONTRACT_PARTY, GET_CONTRACT_ORGANIZATION, GET_CONTRACT_CUST_ACCOUNT_ID, and GET_CONTRACT_SALESREP_EMAIL resolve the trading partners, customer account, operating organization, and sales representative contact used for correspondence.
• Notification helpers: GET_REQ_ASS_EMAIL_SUBJECT and DURATION_UNIT_AND_PERIOD build the e-mail subject line and duration phrasing used in acceptance notifications.
• Payment detail handling: GET_CREDIT_CARD_DTLS, GET_CREDIT_CARD_CVV2, and GET_CONTRACT_CURRENCY_TIP retrieve masked credit-card data, the CVV2 value, and the currency-specific input tip. UPDATE_PAYMENT_DETAILS persists changes to stored payment information.
• State transition: ACCEPT_CONTRACT and DECLINE_CONTRACT record the customer's decision on the contract, and SEND_EMAIL dispatches the resulting confirmation or notification message.

All procedures follow Oracle Application Object Library conventions, returning status through the FND_API-compatible interface and standard exception handling.

Tables Accessed

The package reads and writes through APPS synonyms against the following documented tables:

• Contracts core: OKC_K_HEADERS_ALL_B and OKC_K_PARTY_ROLES_B supply the contract header and the party roles used to identify the customer and vendor; OKC_CONTACTS provides the contact records for correspondence.
• Customer and party data: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and HZ_PARTY_SITES resolve customer accounts, sites, site uses, parties, and party sites.
• Organization and resources: HR_ALL_ORGANIZATION_UNITS supplies operating unit information; JTF_RS_SALESREPS and JTF_RS_RESOURCE_EXTNS provide the sales representative and associated resource details, including e-mail addresses.
• Foundation: FND_CURRENCIES_TL and FND_NEW_MESSAGES support currency display tips and notification messaging; FND_USER identifies the acting user context.

Usage Notes

OKS_CUSTOMER_ACCEPTANCE_PVT is environment-internal. The ETRM metadata shows it is referenced by OKS_CONTRACT_UPD_DTLS_V, OKS_WF_K_PROCESS_PVT, and two further packages, confirming that inbound calls arrive from the contract update details view, the contract workflow process package, and related private APIs rather than from customer-facing code. In practice, acceptance is triggered when a customer responds to a contract offer through the customer acceptance user interface or an integrated workflow; the workflow activity calls the private package, which in turn records the decision and emits notification e-mail. Customizations should not call OKS_CUSTOMER_ACCEPTANCE_PVT directly; instead, extend the supported public APIs or workflow activities that wrap it. Because it is a private package, its signature may change between releases, so any bespoke reference must be revalidated during upgrades to 12.1.1 and 12.2.2.