Search Results funded_value_ge_zero

Overview

APPS.PO_VAL_DISTRIBUTIONS is a validation package within the Oracle E-Business Suite Purchasing module. Its business purpose is to enforce the integrity and business rules governing purchase order distribution records, which represent the accounting and encumbrance detail lines attached to purchase order shipments. Each distribution carries a distribution number, quantity, monetary amount, encumbrance amount, budget account, and, in funded environments, a funded value. The package provides a centralized repository of validation logic used to confirm that these attributes are consistent, non-negative, unique where required, and properly related to executed and encumbered values before a purchase order or requisition distribution is committed to the database.

In the 12.1.1 and 12.2.2 releases, PO_VALIDATIONS acts as the orchestrating caller, invoking the individual check routines exposed by PO_VAL_DISTRIBUTIONS. The metadata confirms that PO_VAL_DISTRIBUTIONS is referenced by PO_VALIDATIONS and by itself, indicating internal reuse of its own routines. The package is classified as an OTHER API within ETRM and holds a VALID status in the APPS schema.

Key Procedures and Functions

The documented package exposes 26 procedures and functions, each encapsulating a discrete validation rule for distribution data:

• DIST_NUM_UNIQUE and DIST_NUM_GT_ZERO verify that a distribution number is unique within its context and greater than zero.
• QUANTITY_GT_ZERO and QUANTITY_GE_QUANTITY_EXEC ensure ordered quantities are positive and not less than quantities already executed.
• AMOUNT_GT_ZERO and AMOUNT_GE_AMOUNT_EXEC apply the equivalent monetary checks on distribution amounts.
• AMOUNT_TO_ENCUMBER_GE_ZERO enforces that the encumbrance amount is non-negative.
• AMOUNT_FUNDED_GE_EXC_AMOUNT and QTY_FUNDED_GE_EXC_QTY verify funded amounts and quantities meet or exceed executed values.
• FUNDED_VALUE_GE_ZERO, FUNDED_VAL_LE_TOT_ORDER_VAL, and FUNDED_VALUE_GT_BACKING_REQ validate funded value against zero, total order value, and backing requisition value.
• UNENCUM_AMT_LE_AMT_TO_ENCUM checks that unencumbered amounts do not exceed the amount to encumber.
• BUDGET_ACCOUNT_ID_NOT_NULL, GL_ENCUMBERED_DATE_NOT_NULL, and GL_ENC_DATE_NOT_NULL_OPEN enforce mandatory budget account and GL encumbrance date fields.
• OOP_ENTER_ALL_FIELDS and PJM_UNIT_NUMBER_EFFECTIVE handle outside-processing and project unit number checks.
• GMS_DATA_VALID and CHECK_FV_VALIDATIONS provide grants-management and funded-value validation coverage.

Tables Accessed

Validation draws on PO_DISTRIBUTIONS_ALL and PO_REQ_DISTRIBUTIONS_ALL for the distribution records under test, PO_DISTRIBUTIONS_INTERFACE and PO_LINES_INTERFACE for imported data, PO_LINE_TYPES for line type attributes, and FINANCIALS_SYSTEM_PARAMS_ALL for financials option settings. PO_SESSION_GT and PO_VALIDATION_RESULTS_GT serve as session-scoped and results-holding temporary structures, while DUAL and PLITBLM support utility operations.

Usage Notes

PO_VAL_DISTRIBUTIONS is not typically invoked directly by end users. It is called during purchase order, requisition, and interface processing when PO_VALIDATIONS performs row-level validation on distributions, and results are written to the validation results table for reporting back to forms or concurrent programs. Custom code extending purchasing validation should follow the same pattern, calling these documented routines rather than duplicating the logic.