Search Results get_accounting_rule_duration

Overview

OE_DEFAULT_PVT is a private PL/SQL package in the APPS schema that supplies defaulting logic for Oracle Order Management in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows the EBS convention of a _PVT package, indicating that the package is intended for internal use by Oracle's own forms, APIs, and concurrent programs rather than as a public extension point. The package resolves and returns default values for order header and order line attributes—customer locations, receipt methods, tax attributes, credit card details, and accounting rule durations—so that the Order Management forms and Order Capture workflows can populate fields consistently whenever a new order or line is entered.

The dependency metadata shows OE_DEFAULT_PVT referencing only SYS.STANDARD, meaning the package relies on standard PL/SQL constructs and the underlying tables it queries directly. It is referenced by 22 other database objects, including the OE_OE_FORM_HEADER family of form-handler packages and a large set of ONT_D* defaulting rule packages (credit card number, expiration date, holder name, receipt method, sold-to and deliver-to attributes, tax code, tax exemption and accounting rule duration). This pattern confirms that OE_DEFAULT_PVT functions as a low-level utility layer invoked by the Order Management defaulting framework.

Key Procedures and Functions

The documented metadata lists 14 procedures and functions, all of which are getter-style routines that retrieve a defaulted value for a given order context:

• GET_TAX_EXEMPT_NUMBER – returns the tax exemption number applicable to the customer for the order.
• GET_TAX_EXEMPT_REASON – returns the reason associated with a customer tax exemption.
• GET_TAX_EXEMPTION_DETAILS – retrieves the combined exemption information used to default the tax exemption fields.
• GET_TAX_CODE – returns the default tax code for the order or line.
• GET_CREDIT_CARD_NUMBER – returns the defaulted credit card number for payment processing.
• GET_CC_EXPIRATION_DATE – returns the defaulted credit card expiration date.
• GET_CC_HOLDER_NAME – returns the defaulted credit card holder name.
• GET_RECEIPT_METHOD – returns the default receipt method for the order's payment context.
• GET_SOB_CURRENCY_CODE – returns the currency code associated with the set of books.
• GET_PRIMARY_CUSTOMER_LOCATION – returns the primary customer location used as a default.
• GET_PRIMARY_DELIVER_TO – returns the primary deliver-to location for the order.
• GET_ACCOUNTING_RULE_DURATION – returns the duration of the accounting rule used to default revenue scheduling.
• GET_COMMITMENT_FROM_AGREEMENT – returns the commitment reference derived from an agreement.
• GET_LATEST_ACCEPTABLE_DATE – returns the latest acceptable date default for the order or line.

Tables Accessed

OE_DEFAULT_PVT reads from several core Order Management and Receivables tables (accessed through APPS synonyms) to derive its default values:

• OE_ORDER_HEADERS / OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL – source of existing order header and line attributes used to derive defaults.
• OE_PAYMENT_TYPES_ALL – supplies receipt method and payment type defaults.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNTS_ALL, HZ_CUST_ACCT_RELATE, HZ_CUST_ACCT_SITES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES – the Trading Community Architecture tables used to resolve customer accounts, locations, and site uses for sold-to, ship-to, and deliver-to defaults.
• RA_CUSTOMER_TRX_ALL, RA_CUST_TRX_TYPES, RA_RULES – Receivables tables used for accounting rule duration and transaction type derived defaults.

Usage Notes

Because OE_DEFAULT_PVT is a _PVT package, Oracle does not document it as a supported public API, and direct invocation from custom code is not recommended; Oracle may change its signature without notice. In practice it is invoked indirectly whenever an order is created or modified through the Order Management forms (via the OE_OE_FORM_HEADER, OE_OE_FORM_HEADER_PAYMENT, and OE_OE_FORM_LINE_PAYMENT handlers) and through the Order Capture defaulting rule packages (the ONT_D* family), which call these getters to populate credit card, tax, location, and accounting rule attributes. Developers diagnosing defaulting behavior should treat OE_DEFAULT_PVT as the final implementation layer behind the seeded defaulting rules, and should perform any supported extension through the standard Order Management defaulting setup or public APIs rather than by calling this package directly.