Results for “payment_type_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OE_HEADER_PAYMENT_CL_DEP_ATTR is a dependent attribute package within the Oracle Order Management (OM) module of Oracle E-Business Suite. Its role is to manage and derive dependent attribute values for header-level payment information captured in the Order Management payment workflow. The package name incorporates the "_CL_DEP_ATTR" suffix commonly used in Oracle EBS to denote a class of dependent attribute routines that populate or validate a record's dependent fields based on the selection of a controlling (parent) value. In this case, the controlling structure is the header payment record, represented by the view OE_AK_HEADER_PAYMENTS_V, which exposes payment-related descriptive flexfield attributes.

The package is declared with AUTHID CURRENT_USER and was first shipped under the file header OEXNHPMS.pls (version 115.1, dated 2003/10/20). It is classified as an OTHER API in the ETRM documentation, indicating it is an internal supporting package rather than a public, callable business API. It is referenced by one other package, confirming its role as a utility dependency consumed by higher-level payment processing logic.

Key Procedures and Functions

All six documented procedures operate on a single IN OUT NOCOPY parameter typed against the OE_AK_HEADER_PAYMENTS_V rowtype. NOCOPY passes the record by reference for performance, and the IN OUT mode indicates these routines mutate the record in place, filling dependent attributes. Each procedure corresponds to a specific payment attribute:

• PAYMENT_LEVEL_CODE — Derives or sets the payment level code on the header payment record.
• PAYMENT_TYPE_CODE — Populates the payment type code dependent on the selected payment context.
• PAYMENT_TRX — Handles payment transaction-related attribute values on the header record.
• RECEIPT_METHOD — Resolves the receipt method associated with the payment.
• PAYMENT_COLLECTION_EVENT — Determines the payment collection event attribute.
• CHECK_NUMBER — Sets or validates the check number attribute for the payment.

Each procedure follows the same signature pattern, ensuring a consistent calling convention across all dependent attributes.

Tables Accessed

The ETRM metadata excerpt does not enumerate specific base tables accessed through APPS synonyms. The primary data structure referenced is the view OE_AK_HEADER_PAYMENTS_V, which serves as both the record type source and the working structure for these procedures. This view is part of the AK (Application Kit) descriptive flexfield infrastructure and exposes header payment fields that customer-specific and business-specific dependent attributes are computed against. Any underlying base table reads would be performed through this view rather than directly.

Usage Notes

OE_HEADER_PAYMENT_CL_DEP_ATTR is an internal dependent-attribute package. In Oracle EBS, such packages are typically invoked by the descriptive flexfield runtime or by the AK attribute framework when a controlling segment changes, at which point dependent attributes must be recalculated. Practically, this occurs when an order is entered or modified in the Order Management forms, particularly at the payment step of the order header. The procedures accept the header payment record, mutate the appropriate attribute, and return control to the caller.

Because the package is not a public API, custom code should not call it directly; instead, developers extending Oracle Order Management payment functionality should work through the supported headers and line APIs. The presence of AUTHID CURRENT_USER means it executes with the privileges of the invoking session, so it must be granted appropriately. Given its 2003 origin and 115.1 version, the package is stable and tied to the core order header payment processing flow in both 12.1.1 and 12.2.2.