Search Results validate_hsc_total_for_bk




Overview
Explore in AI Chat

Overview

APPS.OE_VALIDATE_HEADER_SCREDIT is a server-side PL/SQL validation package within the Oracle Order Management (OM) module of Oracle E-Business Suite. Its header comment dates from release 11i (OEXLHSCS.pls, version 120.0) and it remains present in 12.1.1 and 12.2.2 as an internal, non-public API. The package's business purpose is to validate sales credit data assigned at the order header level, most notably the quota percentage totals distributed across sales credit lines. Sales credits apportion revenue and quota credit among salespersons associated with an order, and Oracle enforces that the quota percentages entered against a header sum correctly before the record can be committed. The package name confirms this scope: "Header_Scredit" refers specifically to header-level sales credit, while the SCREDIT suffix and the procedures within address quota and sales credit validation. A package-level constant, G_Create_Auto_Sales_Credit, defaults to 'Y', indicating behaviour relating to automatic creation of sales credit records during validation. The package is classified as OTHER in ETRM rather than as a public or private API, which signals that it is intended for internal invocation by the Order Management runtime and validation framework, not for direct external calls.

Key Procedures and Functions

  • VALIDATE_HSC_QUOTA_TOTAL — The procedure most directly relevant to the search term "validate_hsc_quota_total." It accepts a header identifier and returns a status, validating that quota percent totals for the sales credits attached to that order header are consistent and permissible. This is the primary entry point for header sales credit quota validation.
  • ENTITY — Performs entity-level validation for a header sales credit record, accepting a Header_Scredit_Rec_Type record from OE_Order_PUB and an optional "old" record for comparison, together with a return status. It applies entity-level rules before persistence.
  • ATTRIBUTES — Performs attribute-level validation on the same Header_Scredit_Rec_Type record. According to the source comment, this procedure was changed to pass the record as IN OUT NOCOPY to fix bug 3006018, and it likewise accepts the prior record for change detection.
  • ENTITY_DELETE — Validates a header sales credit record in the context of a deletion, ensuring that removal does not violate business rules such as quota consistency or mandatory sales credit configurations.
  • VALIDATE_HSC_TOTAL_FOR_BK — A variant validation of header sales credit totals, evidently intended for a background or supplementary validation path. The suffix "BK" indicates a secondary validation routine rather than the primary entry point.

Tables Accessed

The package reads and validates against two documented tables, accessed through APPS synonyms. OE_SALES_CREDITS stores the sales credit records themselves, including the quota percentages and associated salesperson assignments; the package reads these rows when checking that totals reconcile. OE_SALES_CREDIT_TYPES defines the valid sales credit types and their behaviour, and is referenced to confirm that the sales credit entries under validation carry legitimate types. Both tables are core Order Management entities, and the package's role is to enforce cross-row and cross-type consistency on the data they hold rather than to own or populate them.

Usage Notes

APPS.OE_VALIDATE_HEADER_SCREDIT is an internal validation package, not a documented public API. It is referenced by four other packages, indicating that it is invoked by the broader Order Management sales credit validation flow, typically when an order header with sales credits is saved or booked. In the standard application it is triggered indirectly through the Order Management forms and the sales credit validation logic in OE_Order_PUB, and it may also be reached from concurrent or batch processing that creates or books orders. Because the package manipulates header sales credit records, direct custom calls should be avoided; developers needing similar validation should route through the supported public APIs in OE_Order_PUB instead. Customizations that modify this package risk being overwritten during patching and are unsupported. The presence of the same package in both 12.1.1 and 12.2.2 confirms behavioural continuity across those releases.