Results for “ece_ap_payment”
40 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ECE_AP_PAYMENT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the E-Commerce Execution (ECE) product family, which provides the trading-partner and document-exchange infrastructure used by Oracle iPayment, Oracle Payments, and related financial settlement flows. The package operates as an internal, non-public API and is classified under the ETRM "OTHER" category, indicating that it is not a formally published integration interface but rather a supporting utility consumed by other Oracle-owned components.
Its principal business role is to resolve and format Accounts Payable payment information into an outbound document payload for trading-partner exchange. The package bridges the Payments data model (IBY_* tables) with the supplier, bank, and party-model data held in Oracle Payables and Oracle Trading Community Architecture, then maps that content into the ECE document framework so that a payment instruction or remittance can be transmitted to a bank or partner. The ETRM record shows the package body status as VALID, confirming that it compiles cleanly against the referenced dependencies.
Key Procedures and Functions
The documented metadata lists a single callable program unit under a placeholder name, and no parameter signatures are published. Consequently, the exact interface cannot be reproduced here without speculation, and it should not be assumed. Functionally, the lone entry point is described in the ETRM record as the package's public routine; in practice such a routine in the ECE financial packages takes an output run identifier, a trading-partner header, and a document identifier, and performs the extraction and XML transformation of AP payment details. Implementers should obtain the authoritative specification directly from the package source via ALL_SOURCE or the ETRM "show dependent code" link rather than relying on this summary.
Tables Accessed
The package reads and writes across four functional areas, using APPS synonyms:
- Payments core: IBY_PAYMENTS_ALL, IBY_DOCS_PAYABLE_ALL, IBY_PAYMENT_METHODS_B, and IBY_EXT_BANK_ACCOUNTS supply the payment record, the payable document linkage, the payment method definition, and the external bank account details.
- Payables and banking: AP_SUPPLIERS, AP_SUPPLIER_SITES, and CE_BANK_ACCOUNTS provide supplier identity, supplier site context, and the internal bank account used for disbursement.
- Trading Community Architecture: HZ_LOCATIONS, HZ_CONTACT_POINTS, HZ_ORGANIZATION_PROFILES, and HZ_CODE_ASSIGNMENTS supply address, contact, profile, and classification data required for correct partner identification and remittance formatting.
- ECE framework and setup: ECE_TP_HEADERS, ECE_TP_DETAILS, and ECE_OUTPUT_RUNS_S hold the trading-partner definition and the output run that scopes the extraction, while FINANCIALS_SYSTEM_PARAMS_ALL supplies financials system options such as ledger and business-group context.
Usage Notes
ECE_AP_PAYMENT is an internal dependency rather than an entry point for custom development. The ETRM record shows it is referenced by IBY_FD_POST_PICP_PROGS_PVT, a Payments private package, which is the typical invocation path: Oracle Payments processing triggers the ECE output flow that in turn calls this package to build the payment document. It is not referenced by any other APPS package listed in the record and exposes no public API classification.
Because the package is invoked from the Payments posting and payment-instruction pipeline, customizations should not call it directly. Sites requiring additional remittance content should extend the ECE trading-partner and document configuration instead, and recompile dependencies after any patch that touches IBY_FD_POST_PICP_PROGS_PVT. The dependency on SYS.STANDARD indicates only standard PL/SQL language constructs and does not imply any privileged access. Behavior is consistent between 12.1.1 and 12.2.2, though the underlying IBY and HZ object definitions differ slightly across those releases, so validation against the target instance is recommended.
-
PACKAGE: APPS.ECE_AP_PAYMENT 12.1.1
-
PACKAGE: APPS.ECE_AP_PAYMENT 12.2.2
-
PACKAGE: APPS.ECE_AP_PAYMENT 12.1.1
-
PACKAGE: APPS.ECE_AP_PAYMENT 12.2.2
-
SYNONYM: APPS.ECE_TP_DETAILS 12.2.2
-
SYNONYM: APPS.ECE_TP_HEADERS 12.2.2
-
SYNONYM: APPS.AP_SUPPLIERS 12.2.2
-
VIEW: APPS.HR_LOCATIONS 12.2.2
-
SYNONYM: APPS.HZ_LOCATIONS 12.2.2
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
SYNONYM: PUBLIC.DUAL 12.1.1
-
SYNONYM: PUBLIC.DUAL 12.2.2
-
12.2.2 DBA Data 12.2.2
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1