Search Results copy_trxn_extension

Overview

APPS.AR_DEPOSIT_API_PUB is a public Oracle Receivables API package that supports the creation and maintenance of deposit transactions, also known as non-revenue sales credits and prepayments, within Oracle E-Business Suite 12.1.1 and 12.2.2. Deposit handling in Receivables involves recording customer prepayments against future commitments and later applying those amounts to customer transactions. This package provides a programmatic surface through which other Oracle modules, extensions, and custom integrations can create deposit transactions without directly manipulating the underlying distribution and customer transaction tables.

The package is classified as a Public (PUB) API, indicating that it is intended for supported external invocation. Its header carries the source control marker typical of Oracle Receivables packages, and it relies on FND_MSG_PUB message levels and FND_PROFILE / FND_CURRENCY utilities for error handling and currency rounding, consistent with standard Oracle EBS PL/SQL conventions.

Key Procedures and Functions

• CREATE_DEPOSIT — The principal entry point for generating a deposit transaction. It orchestrates creation of the underlying customer transaction, its lines, distributions, and associated salescredit records, applying validation and defaulting consistent with the Receivables deposit model.
• INSERT_NON_REV_SALESCREDIT — Inserts salescredit records for non-revenue deposit transactions. This supports the requirement that deposit lines carry salesperson credit information without generating revenue recognition entries.
• SET_PROFILE_FOR_TESTING — A testing utility that overrides package global variables normally populated from profile option values. It exists so that unit and regression test routines can assign distinct testcase values, rather than relying on the configured application profile settings.
• COPY_TRXN_EXTENSION — Copies transaction extension attribute values, an operation relevant to the flexible transaction extension framework used by Oracle Payments instrumentation and associated attribute columns.

Tables Accessed

The package reads and writes against the core Receivables transaction and payment model. RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, and RA_CUSTOMER_TRX_LINES hold the deposit transaction headers and lines, while RA_CUST_TRX_LINE_SALESREPS and AR_PAYMENT_SCHEDULES capture salescredit and scheduled payment detail. RA_CUST_TRX_TYPES, RA_BATCH_SOURCES, AR_RECEIPT_CLASSES, and AR_RECEIPT_METHODS supply type, batch source, and receipt defaulting information. Customer and site data are resolved through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, and HZ_PARTIES. Banking and account details come from AP_BANK_ACCOUNTS. Transaction extension attributes are sourced from IBY_FNDCPT_TX_EXTENSIONS, which is directly relevant to the searched term COPY_TRXN_EXTENSION.

Usage Notes

AR_DEPOSIT_API_PUB is typically invoked as a public API from custom PL/SQL, workflow processes, or integration layers rather than from end-user forms, since deposit creation is generally handled declaratively in the Receivables UI. Custom code should call CREATE_DEPOSIT and its supporting routines through APPS synonyms, observing the standard commit and error-handling model. Because SET_PROFILE_FOR_TESTING modifies package globals, it is reserved for test harnesses and should not be used in production flows. The two dependent packages referenced in the metadata indicate this API participates in an internal call chain, so consumers should avoid altering package state assumptions between calls. When copying transaction extension attributes, callers should ensure the corresponding Oracle Payments extension context is already established.