Search Results dflt_hscredit_primary_srep

Overview

OE_HEADER_SCREDIT_UTIL is a server-side PL/SQL utility package in the Oracle Order Management module of Oracle E-Business Suite, owned by the APPS schema and classified as a utility (UTIL) API in the ETRM repository. Its name reflects its scope: order entry (OE), header-level sales credits (Scredit), and utility functions. The package encapsulates the business logic required to create, maintain, and validate sales credit assignments at the order header level within Oracle Order Management.

Sales credits identify the sales representatives who receive quota and compensation credit for an order, together with the percentage or amount of credit allocated to each. The package provides a programmatic layer between the Order Management forms and the underlying OE_SALES_CREDITS data model, including support for the multi-attribute descriptive flexfield context that is attached to header sales credit records. It is part of the broader Order Management PL/SQL API family and is intended for internal use by Oracle forms and concurrent processes rather than as a fully public, externally supported API.

Key Procedures and Functions

The ETRM metadata documents 22 procedures and functions within the package. The naming follows the standard Oracle Forms-generated table handler pattern:

• INSERT_ROW, UPDATE_ROW, DELETE_ROW — Perform the corresponding DML operations against the header sales credit record passed in the API record structure.
• QUERY_ROW, QUERY_ROWS, LOCK_ROW, LOCK_ROWS — Retrieve single or multiple sales credit records and obtain row-level locks for update processing.
• GET_VALUES, GET_IDS — Populate the API record with descriptive values or with the primary and foreign key identifiers for a sales credit row.
• COMPLETE_RECORD, CLEAR_DEPENDENT_ATTR, APPLY_ATTRIBUTE_CHANGES — Default missing columns, null out dependent attributes, and propagate changes across related fields so the record remains internally consistent.
• CONVERT_MISS_TO_NULL — Translate the Forms "missing" sentinel value into a true NULL before writing to the database.
• G_MISS_OE_AK_HSCREDIT_REC, API_REC_TO_ROWTYPE_REC, ROWTYPE_REC_TO_API_REC — Define the global missing record and convert between the API record type and the %ROWTYPE representation of the sales credit table.
• PRE_WRITE_PROCESS, CALCULATE — Perform pre-write validation and derive calculated values such as credit percentages or amounts.
• DFLT_HSCREDIT_PRIMARY_SREP — This is the routine directly associated with the search term dflt_hscredit_primary_srep. It defaults the primary sales representative on a header sales credit record, typically deriving the value from the order header's salesrep, the customer, or the calling form's context when no explicit representative has been supplied.
• GET_SALES_GROUP — Returns sales group information, consistent with the sales group constants declared in the package specification, a feature added under the change marker "SG".

Tables Accessed

The package operates against the following base tables through APPS synonyms:

• OE_ORDER_HEADERS_ALL — Supplies header context, including the header-level sales representative used as the default in DFLT_HSCREDIT_PRIMARY_SREP.
• OE_SALES_CREDITS — The primary table holding sales credit assignments; the insert, update, delete, and query routines act on this table.
• OE_SALES_CREDIT_HISTORY — Maintains the audit trail of changes to sales credit records.
• OE_SALES_CREDIT_TYPES — Validates the credit type (for example, quota or revenue) assigned to each credit line.
• PLITBLM — The standard Order Management PL/SQL table used for in-memory handling of multi-row collections and bulk processing.

Usage Notes

OE_HEADER_SCREDIT_UTIL is invoked primarily from the Order Management sales credit forms and from other Order Management packages — the ETRM metadata records it as referenced by 18 other packages, indicating it sits near the centre of the header sales credit processing chain. The naming convention of the routines (row handlers, record converters, and the G_MISS record) is characteristic of Oracle Forms 6i table-handler packages, so it is generally called during form-level insert, update, delete, and query events.

The header comment references file OEXUHSCS.pls and version 120.1, dated March 2006, with the "noship" designation, confirming that the package is a shipped but internally used component of Release 11i/12.x code lines. In EBS 12.1.1 and 12.2.2 the package exists in the same form, with the sales group extension noted by the "SG" change markers. Custom code should avoid calling the DML routines directly and instead use the supported Order Management public APIs; any direct use should be limited to read-only queries or to contexts where the caller replicates the record completion and defaulting logic that this package expects.