Search Results copy_attribute_to_rec

Overview

OE_OE_FORM_HEADER_PAYMENT is a PL/SQL package owned by the APPS schema that supports the Oracle Order Management (OM) Order Entry form. Its name follows the Oracle Forms library naming convention "OE_<FORM>_<BLOCK>", indicating that it back-ends the header payment block of the Order Organizer / Sales Orders window. In Oracle EBS 12.1.1 and 12.2.2, this package encapsulates the client-side field logic that Forms triggers would otherwise implement in PL/SQL libraries. It handles defaulting, attribute-level change events, row-level validation, locking, deletion, and copying of record attributes for the payment (payment terms / credit card authorization) block on the order header.

The package has no direct external API designation; ETRM classifies it as "OTHER", and it is referenced by zero other packages. It is a form-supporting utility rather than a public business API, and its execution is driven exclusively through the Sales Orders form runtime.

Key Procedures and Functions

The documented package exposes seven entry points, consistent with standard Oracle Forms block logic:

• DEFAULT_ATTRIBUTES — Populates default values for the payment block fields when a new header record is created, drawing on the order's payment terms and related header information.
• CHANGE_ATTRIBUTE — Responds to user-driven changes on a payment attribute, re-validating and propagating dependent field values.
• VALIDATE_AND_WRITE — Validates the payment block contents and writes them back to the underlying order structure, typically called before saving the header.
• DELETE_ROW — Removes a payment row from the form block, applying the appropriate delete semantics for the payment record.
• PROCESS_ENTITY — Executes the block-level processing logic that co-ordinates the other routines for the current entity (payment record) on the form.
• LOCK_ROW — Acquires an application-level lock on the payment row to prevent concurrent modification during an edit transaction.
• COPY_ATTRIBUTE_TO_REC — Copies a source attribute value into the current record, supporting record duplication and defaulting propagation within the block.

Tables Accessed

The only documented table referenced via APPS synonyms is PLITBLM. PLITBLM is a Forms/PL/SQL runtime structure rather than an Order Management transaction table; it holds the in-memory block and item values for the form session. This confirms that OE_OE_FORM_HEADER_PAYMENT does not persist data directly but operates on the form's block state. Publication of the payment information to persistent OM tables (such as the order header payment attributes) is delegated to the order entry public APIs, notably OE_ORDER_PUB, which the package references according to the dependency listing.

Usage Notes

This package is not intended for direct invocation from concurrent programs or custom PL/SQL. It is called indirectly by the Oracle Forms runtime as part of the Sales Orders (Order Entry) form's block and trigger execution. The dependency information shows a one-way dependency from the package to APPS.OE_ORDER_PUB and SYS.STANDARD, and no package depends on it, underscoring its status as a form-internal implementation detail.

Because the package name is an internal form unit, customizations should never call it directly. Extensions to payment-block behaviour should instead be implemented through the supported order entry APIs (OE_ORDER_PUB and related) or through form personalization and CUSTOM library hooks. In 12.2.2 the package retains the same APPS owner, VALID status, and seven-procedure structure, so this documentation applies equally to 12.1.1 and 12.2.2 instances.