Results for “fun_trx_types_pub”

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

Overview

FUN_TRX_TYPES_PUB is a public PL/SQL API package owned by the APPS schema within Oracle E-Business Suite. It belongs to the Oracle Financials for the Americas (FUN) product family and provides a programmatic interface to transaction type configuration data maintained in Oracle Receivables. In EBS Releases 12.1.1 and 12.2.2, transaction types govern the behavior of receivables and other financial transactions, including whether a transaction requires invoicing, whether it is enabled for use, whether it requires manual approval, and how it maps to corresponding Oracle Receivables transaction types when general ledger transfer or Argentine legal reporting is involved.

The package exists so that other application modules, forms, and custom extensions can retrieve validated transaction type attributes without querying the underlying base tables directly. Its procedures and functions encapsulate lookups by primary key or by user-facing code, and they expose the invoicing and approval options that drive downstream document processing.

Key Procedures and Functions

The package exposes five documented callable units. Each is described below strictly in terms of its documented purpose; parameter lists are not reproduced here.

• GET_TRX_TYPE_BY_ID — Returns the status, transaction type code, and invoicing option for a transaction type identified by its internal trx_type_id. This is the primary retrieval routine for callers that already hold the numeric identifier.
• GET_TRX_TYPE_BY_CODE — Returns the internal identifier, invoicing option, and enabled status for a transaction type identified by its user-entered transaction type code. It is the inverse lookup of GET_TRX_TYPE_BY_ID and supports integrations that key off the descriptive code.
• IS_TRX_TYPE_MANUAL_APPROVE — A function that returns the manual approval option configured for a transaction type, given its trx_type_id. It is typically used to determine whether a transaction must pass through manual approval before posting or invoicing.
• GET_TRX_TYPE_MAP — Returns the mapping details of a transaction type for a given operating unit (org_id) and transaction type identifier, at a specified transaction date. The mapping includes the memo line identifier and memo line name, supporting the localization logic that links FUN transaction types to corresponding structures.
• GET_AR_TRX_CREATION_SIGN — Returns the sign convention used when creating the associated Oracle Receivables transaction. This supports correct debit/credit orientation for downstream AR document creation.

Tables Accessed

The package reads from four base tables through APPS synonyms:

• FUN_TRX_TYPE_AR_MAPS — Stores the mapping between FUN transaction types and their AR counterparts. It is the source for GET_TRX_TYPE_MAP and related lookups.
• RA_CUST_TRX_TYPES_ALL — The Oracle Receivables transaction type definition table, supplying the AR transaction type identifier and creation attributes.
• FUN_TRX_HEADERS — Holds transaction header information, referenced for status and processing context.
• FUN_SYSTEM_OPTIONS — Holds system-level configuration for the FUN product, used to qualify behavior according to installed options.

Usage Notes

FUN_TRX_TYPES_PUB is a PUB-classified API and is expected to be invoked by external callers rather than only internally. In practice it is called from Oracle Forms during transaction entry to validate and default transaction type attributes, from concurrent programs that process or report on FUN transactions, and from custom PL/SQL extensions that need to resolve a transaction type code to its identifier or determine invoicing and approval requirements. The package is referenced by three other database packages, indicating it participates in a layered call stack where higher-level business logic depends on its lookups. Because the routine is a read-only inquiry API, it carries no commit semantics; callers should treat returned values as cached configuration and re-invoke it when configuration changes are possible.