Search Results insert_sales_credit
Overview
The APPS.OKC_SALES_CREDIT_PUB package is the public application programming interface for managing sales credit records within Oracle E-Business Suite's Contracts (OKC) module. In the ETRM (Enterprise Transaction and Reference Model) architecture, this package serves as the externally callable layer that exposes sales credit maintenance operations to forms, concurrent programs, and custom extensions. A sales credit record associates a contract or contract line with the salesperson or sales organization that receives revenue credit for the transaction, and this package governs the creation, modification, locking, deletion, and validation of those records.
The package is classified as PUB and owned by APPS, declaring AUTHID CURRENT_USER so that execution privileges resolve against the calling schema. It delegates its core processing to the private package OKC_Sales_credit_PVT, from which it borrows the scrv_rec_type (single record) and scrv_tbl_type (PL/SQL table) subtypes. This public/private split is the standard Oracle EBS pattern, ensuring that direct DML against the underlying tables is avoided and all business rules are centralized.
Key Procedures and Functions
The documented API surface exposes ten procedures and functions. Each procedure follows the Oracle EBS API convention of accepting p_api_version and p_init_msg_list, and returning x_return_status, x_msg_count, and x_msg_data for error handling. Where applicable, procedures accept and return both single-record and table-based overloads.
- INSERT_SALES_CREDIT — Creates one or more new sales credit records. The overload accepting a single
scrv_rec_typereturns the populated record; the overload accepting anscrv_tbl_typesupports bulk insertion of multiple records in a single call. - LOCK_SALES_CREDIT — Obtains a lock on existing sales credit records prior to update. It similarly provides single-record and table-based overloads to support both interactive and batch locking scenarios.
- UPDATE_SALES_CREDIT — Modifies existing sales credit records, again offering single-record and bulk table overloads, and returning the updated record(s).
- DELETE_SALES_CREDIT — Removes sales credit records that are no longer required, honoring the same API calling conventions.
- VALIDATE_SALES_CREDIT — Performs business-rule validation against the supplied record(s) without necessarily committing changes, permitting callers to verify data integrity before submitting an insert or update.
The consistent overload design allows callers to process large volumes — such as bulk contract imports — as efficiently as single interactive transactions.
Tables Accessed
Per the documented ETRM metadata, the package references the base table PLITBLM via APPS synonyms. Practical operation of the sales credit API additionally depends on the OKC sales credit base tables maintained through OKC_Sales_credit_PVT, which store the credit allocation records linking contracts and contract lines to salespersons and sales organizations. Callers should treat these underlying tables as private; all reads and writes should be performed through this public package so that validation logic, security, and audit behavior remain intact.
Usage Notes
OKC_SALES_CREDIT_PUB is typically invoked from Oracle Forms performing interactive sales credit maintenance, from concurrent programs that mass-generate or migrate contract sales credits, and from custom PL/SQL integrations that need to create or maintain credit assignments. The metadata records that the package is referenced by two other packages, indicating it participates in higher-level contract processing flows.
Callers should always pass a valid p_api_version, inspect x_return_status for OKC_API.G_RET_STS_SUCCESS or failure, and drain the message stack on error. For updates, the record should first be locked through LOCK_SALES_CREDIT to avoid lost-update conflicts. The package is available in both EBS 12.1.1 and 12.2.2, and its interface has remained stable across those releases.
-
APPS.OKS_SALES_CREDIT_PUB SQL Statements
12.2.2
-
APPS.OKC_SALES_CREDIT_PUB SQL Statements
12.2.2
-
APPS.OKC_SALES_CREDIT_PUB SQL Statements
12.1.1
-
APPS.OKS_SALES_CREDIT_PUB SQL Statements
12.1.1
-
PACKAGE: APPS.OKC_SALES_CREDIT_PUB
12.1.1
-
PACKAGE: APPS.OKC_SALES_CREDIT_PUB
12.2.2
-
PACKAGE: APPS.OKS_SALES_CREDIT_PUB
12.2.2
-
PACKAGE: APPS.OKS_SALES_CREDIT_PUB
12.1.1
-
PACKAGE BODY: APPS.OKC_SALES_CREDIT_PUB
12.2.2
-
PACKAGE BODY: APPS.OKS_SALES_CREDIT_PUB
12.2.2
-
APPS.AR_REVENUE_ADJUSTMENT_PVT SQL Statements
12.1.1
-
PACKAGE BODY: APPS.OKC_SALES_CREDIT_PUB
12.1.1
-
PACKAGE BODY: APPS.OKS_SALES_CREDIT_PUB
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT SQL Statements
12.2.2
-
PACKAGE: APPS.AR_REVENUE_ADJUSTMENT_PVT
12.2.2
-
PACKAGE: APPS.AR_REVENUE_ADJUSTMENT_PVT
12.1.1
-
PACKAGE BODY: APPS.AR_REVENUE_ADJUSTMENT_PVT
12.1.1
-
PACKAGE BODY: APPS.AR_REVENUE_ADJUSTMENT_PVT
12.2.2
-
APPS.OKS_SALES_CREDIT_PUB dependencies on OKC_API
12.1.1
-
APPS.OKC_SALES_CREDIT_PUB dependencies on OKC_API
12.2.2
-
APPS.OKS_SALES_CREDIT_PUB dependencies on OKC_API
12.2.2
-
APPS.OKC_SALES_CREDIT_PUB dependencies on OKC_API
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on AR_RAAPI_UTIL
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on AR_RAAPI_UTIL
12.2.2
-
APPS.OKS_SALES_CREDIT_PUB dependencies on OKC_API
12.1.1
-
APPS.OKS_SALES_CREDIT_PUB dependencies on OKC_API
12.2.2
-
APPS.OKC_SALES_CREDIT_PUB dependencies on OKC_API
12.1.1
-
APPS.OKC_SALES_CREDIT_PUB dependencies on OKC_API
12.2.2
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on FND_API
12.2.2
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on FND_API
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on ARP_UTIL
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on ARP_UTIL
12.2.2
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on AR_REVENUE_ADJUSTMENT_PVT
12.1.1
-
APPS.AR_REVENUE_ADJUSTMENT_PVT dependencies on AR_REVENUE_ADJUSTMENT_PVT
12.2.2