Search Results oe_payments
Overview
OE_PAYMENTS is a transactional table in the ONT (Order Management) schema of Oracle E-Business Suite, holding commitment payment information captured against order headers and lines. It supports payment-related processing for order management transactions, including credit card authorizations, receipt method details, and commitment amounts applied or interfaced to downstream financial systems. The table exists in both Release 12.1.1 and 12.2.2 with a documented physical schema of 53 columns in 12.2.2.
From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is standalone. This suggests OE_PAYMENTS behaves primarily as an independent entity rather than a dependent link or satellite, though its foreign keys to AR_RECEIPT_METHODS and IBY_FNDCPT_TX_EXTENSIONS indicate enrichment relationships that a formal model might treat as reference or lookup links.
Key Information Stored
The surrogate primary key is PAYMENT_TRX_ID. A unique index, OE_PAYMENTS_U1, defines the business-key candidate as the combination of HEADER_ID, LINE_ID, and PAYMENT_NUMBER, establishing payment uniqueness within an order line context.
The most significant columns include:
- HEADER_ID and LINE_ID — the order header and line to which the payment applies.
- PAYMENT_NUMBER — the sequential identifier for a payment within the order line.
- PAYMENT_AMOUNT and PREPAID_AMOUNT — the monetary value of the payment and prepaid portion.
- COMMITMENT_APPLIED_AMOUNT and COMMITMENT_INTERFACED_AMOUNT — amounts applied and passed to financials.
- PAYMENT_TYPE_CODE and PAYMENT_LEVEL_CODE — classification of payment and the level at which it applies.
- CREDIT_CARD_CODE, CREDIT_CARD_NUMBER, CREDIT_CARD_HOLDER_NAME, CREDIT_CARD_EXPIRATION_DATE, CREDIT_CARD_APPROVAL_CODE, and CREDIT_CARD_APPROVAL_DATE — credit card authorization details.
- RECEIPT_METHOD_ID — foreign key to AR_RECEIPT_METHODS indicating the payment instrument.
- TRXN_EXTENSION_ID — foreign key to IBY_FNDCPT_TX_EXTENSIONS for payment transaction extension data.
Common Use Cases and Queries
Typical reporting scenarios include reconciling order commitment payments, auditing credit card authorizations, and tracking amounts interfaced to receivables. A representative query retrieves all payments for a given order:
- SELECT p.PAYMENT_NUMBER, p.PAYMENT_AMOUNT, p.PAYMENT_TYPE_CODE, p.RECEIPT_METHOD_ID FROM OE_PAYMENTS p WHERE p.HEADER_ID = :header_id;
- Join to AR_RECEIPT_METHODS on RECEIPT_METHOD_ID to resolve the receipt method name for payment method reporting.
- Aggregate COMMITMENT_APPLIED_AMOUNT and COMMITMENT_INTERFACED_AMOUNT by HEADER_ID to validate interfacing completeness.
- Filter on DEFER_PAYMENT_PROCESSING_FLAG and INVOICED_FLAG to isolate payments pending invoicing.
Related Objects
The following objects are most significant in relation to OE_PAYMENTS:
- AR_RECEIPT_METHODS — referenced via RECEIPT_METHOD_ID; defines the receipt method used for the payment.
- IBY_FNDCPT_TX_EXTENSIONS — referenced via TRXN_EXTENSION_ID; supplies payment transaction extension attributes.
- OE_ORDER_HEADERS_ALL — parent order header identified by HEADER_ID.
- OE_ORDER_LINES_ALL — parent order line identified by LINE_ID.
- OE_PAYMENTS_U1 — unique index enforcing the HEADER_ID, LINE_ID, PAYMENT_NUMBER business key.
-
Table: OE_PAYMENTS
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PAYMENTS, object_name:OE_PAYMENTS, status:VALID, product: ONT - Order Management , description: It holds the commitment payment information. , implementation_dba_data: ONT.OE_PAYMENTS ,
-
Table: OE_PAYMENTS
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PAYMENTS, object_name:OE_PAYMENTS, status:VALID, product: ONT - Order Management , description: It holds the commitment payment information. , implementation_dba_data: ONT.OE_PAYMENTS ,
-
APPS.OE_PREPAYMENT_PVT SQL Statements
12.2.2
-
APPS.OE_COMMITMENT_PVT SQL Statements
12.1.1
-
APPS.OE_COMMITMENT_PVT SQL Statements
12.2.2
-
APPS.OE_PREPAYMENT_PVT SQL Statements
12.1.1
-
APPS.OE_VALIDATE_HEADER_PAYMENT SQL Statements
12.2.2
-
APPS.OE_VALIDATE_HEADER_PAYMENT SQL Statements
12.1.1
-
APPS.OE_PREPAYMENT_UTIL SQL Statements
12.1.1
-
APPS.OE_DEFAULT_HEADER_PAYMENT SQL Statements
12.1.1
-
APPS.OE_PREPAYMENT_UTIL SQL Statements
12.2.2
-
APPS.OE_DEFAULT_HEADER_PAYMENT SQL Statements
12.2.2
-
APPS.OE_PAYMENTS_UTIL SQL Statements
12.2.2
-
APPS.OE_DEFAULT_LINE_PAYMENT SQL Statements
12.1.1
-
APPS.OE_PAYMENTS_UTIL SQL Statements
12.1.1
-
APPS.OE_VALIDATE_LINE_PAYMENT SQL Statements
12.1.1
-
APPS.OE_VALIDATE_LINE_PAYMENT SQL Statements
12.2.2
-
APPS.OE_CREDIT_PUB SQL Statements
12.2.2
-
APPS.OE_DEFAULT_LINE_PAYMENT SQL Statements
12.2.2
-
APPS.OE_PAYMENT_DATA_MIGRATION_UTIL SQL Statements
12.2.2
-
APPS.OE_PAYMENT_DATA_MIGRATION_UTIL SQL Statements
12.1.1
-
APPS.OE_CREDIT_PUB SQL Statements
12.1.1
-
APPS.OE_HEADER_PAYMENT_UTIL SQL Statements
12.1.1
-
PACKAGE BODY: APPS.OE_PAYMENT_DATA_MIGRATION_UTIL
12.2.2
-
PACKAGE BODY: APPS.OE_PAYMENT_DATA_MIGRATION_UTIL
12.1.1
-
APPS.OE_LINE_PAYMENT_UTIL SQL Statements
12.2.2
-
APPS.OE_LINE_PAYMENT_UTIL SQL Statements
12.1.1
-
APPS.OE_HEADER_PAYMENT_UTIL SQL Statements
12.2.2
-
VIEW: APPS.OE_AK_HEADER_PAYMENTS_V
12.1.1
-
VIEW: ONT.OE_PAYMENTS#
12.2.2
owner:ONT, object_type:VIEW, object_name:OE_PAYMENTS#, status:VALID,
-
VIEW: APPS.OE_AK_HEADER_PAYMENTS_V
12.2.2
-
VIEW: APPS.OE_AK_LINE_PAYMENTS_V
12.1.1
-
VIEW: APPS.OE_AK_LINE_PAYMENTS_V
12.2.2
-
SYNONYM: APPS.OE_PAYMENTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OE_PAYMENTS, status:VALID,
-
SYNONYM: APPS.OE_PAYMENTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OE_PAYMENTS, status:VALID,
-
VIEW: ONT.OE_PAYMENTS#
12.2.2
-
Table: OE_PAYMENTS_IFACE_ALL
12.1.1
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PAYMENTS_IFACE_ALL, object_name:OE_PAYMENTS_IFACE_ALL, status:VALID, product: ONT - Order Management , description: This table is used to store Payments data to be imported into OE_PAYMENTS table. This table will be used by Order Import Program. , implementation_dba_data: ONT.OE_PAYMENTS_IFACE_ALL ,
-
Table: OE_PAYMENTS_IFACE_ALL
12.2.2
owner:ONT, object_type:TABLE, fnd_design_data:ONT.OE_PAYMENTS_IFACE_ALL, object_name:OE_PAYMENTS_IFACE_ALL, status:VALID, product: ONT - Order Management , description: This table is used to store Payments data to be imported into OE_PAYMENTS table. This table will be used by Order Import Program. , implementation_dba_data: ONT.OE_PAYMENTS_IFACE_ALL ,
-
VIEW: APPS.AR_IDEP_ACTIONS_NOT_TAKEN
12.1.1
-
APPS.OE_VERIFY_PAYMENT_PUB SQL Statements
12.2.2
-
APPS.OE_PAYMENT_TRXN_UTIL SQL Statements
12.2.2
-
VIEW: APPS.AR_IDEP_ACTIONS_NOT_TAKEN
12.2.2
-
PACKAGE BODY: APPS.OE_INF_POPULATE_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:OE_INF_POPULATE_PUB, status:VALID,
-
PACKAGE BODY: APPS.OE_DEFAULT_HEADER_PAYMENT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:OE_DEFAULT_HEADER_PAYMENT, status:VALID,
-
PACKAGE BODY: APPS.OE_DEFAULT_LINE_PAYMENT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OE_DEFAULT_LINE_PAYMENT, status:VALID,
-
PACKAGE BODY: APPS.AR_RAXCBR_XMLP_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AR_RAXCBR_XMLP_PKG, status:VALID,
-
PACKAGE BODY: APPS.OE_INF_POPULATE_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OE_INF_POPULATE_PUB, status:VALID,
-
PACKAGE BODY: APPS.OE_VALIDATE_HEADER_PAYMENT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OE_VALIDATE_HEADER_PAYMENT, status:VALID,
-
PACKAGE BODY: APPS.OE_DEFAULT_HEADER_PAYMENT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:OE_DEFAULT_HEADER_PAYMENT, status:VALID,
-
PACKAGE BODY: APPS.OE_DEFAULT_LINE_PAYMENT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:OE_DEFAULT_LINE_PAYMENT, status:VALID,