Results for “get_ar_trx_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PA_CLIENT_EXTN_INV_TRANSFER is a public Oracle Projects client extension package that supports the Accounts Receivable transaction type billing flow. Its lifecycle status is active, it is classified under the PA product, and its declared compatibility is S. The package is scoped to the PA_PROJECT and PA_INVOICE business entities and is documented in Oracle Projects API's, Client Extensions, and Open Interfaces Reference (doccd 120pjapi.pdf). The header revision marker references PAXPTRXS.pls and carries an AUTHID CURRENT_USER clause, meaning the packaged program units execute with the privileges of the invoking user rather than the definer. The package exists so that implementers can override or influence the default determination of the AR transaction type used when Oracle Projects interfaces billing transactions to Oracle Receivables.

Key Procedures and Functions

The documented package exposes a single public procedure, GET_AR_TRX_TYPE. Its stated function is the Oracle Projects Billing client extension for determining the AR transaction type. It is a Public API with no prerequisites. Oracle Projects passes the billing context into the procedure and receives the resulting transaction type identifier back through an OUT parameter, together with a return status. The documented status conventions are 0 for successful execution, a value less than 0 to indicate an Oracle error, and a value greater than 0 to indicate an application error. The procedure therefore follows the standard Oracle Projects client-extension contract: read the context, apply customer-specific logic, and return a transaction type identifier and status to the calling billing program. No further procedures or functions are documented for this package.

Tables Accessed

ETRM lists no directly referenced tables for this package through APPS synonyms. The documented parameters nonetheless identify the source columns and reference tables that define the calling contract. The project context corresponds to PROJECT_ID of PA_PROJECTS_ALL. The billing context corresponds to DRAFT_INVOICE_NUM of PA_DRAFT_INVOICES_ALL, with invoice class values of INVOICE, CREDIT_MEMO, WRITE_OFF, and CANCEL. The returned and input transaction type identifier corresponds to CUST_TRX_TYPE_ID of RA_CUST_TRX_TYPES. In a typical implementation the extension is expected to read the receivable transaction type setup in RA_CUST_TRX_TYPES and evaluate the draft invoice attributes drawn from the PA billing tables, but the metadata does not document direct SQL access to those objects from within the package body.

Usage Notes

The extension is invoked from within Oracle Projects billing logic when the AR transaction type must be resolved for an outbound billing transaction. Customers register their implementation of this package in the Oracle Projects client extension framework, and the billing program calls GET_AR_TRX_TYPE in place of the seeded default determination. Typical use cases include deriving a specific receivable transaction type based on project, invoice class, or invoice amount, such as routing credit memos or write-offs to dedicated transaction types. Because the package is declared AUTHID CURRENT_USER and is referenced by one other package, its execution depends on the privileges of the calling user and on the integrity of the caller. Implementers should return accurate status codes, avoid committing or rolling back within the extension, and treat the response of the calling billing program as the sole handler of the returned transaction type identifier.