Search Results creation_method_code

Overview

JL_BR_AR_RCT_MTHD_2_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the JL – Latin America Localizations product family. Within Release 12.1.1 and 12.2.2, the view persists as a VALID database object and is documented in ETRM as "Retrofitted," indicating it originated in an earlier release and was carried forward into the R12 architecture with minimal functional change.

The view presents a joined, de-normalized projection of Oracle Receivables receipt method configuration, combining the receipt method name, its internal identifier, and the associated creation method code derived from the receipt class. Its principal reporting purpose is to expose the pairing of a receipt method with the creation_method_code value that governs how receipts are created — for example, whether they are entered manually, generated automatically, or remitted. This makes the view a convenient lookup surface for localization logic, concurrent program validation, and custom reporting that must determine the creation mechanics of a given receipt method without navigating the full Receivables table structure.

Underlying Base Objects

The view is defined over five base objects, all accessed through APPS synonyms:

• AR_RECEIPT_METHODS (aliased E) — the primary Receivables receipt method definition, supplying NAME and RECEIPT_METHOD_ID.
• AR_RECEIPT_CLASSES (aliased D) — the receipt class definition, supplying CREATION_METHOD_CODE.
• RA_CUST_RECEIPT_METHODS (aliased A) — customer receipt method assignments, joined on RECEIPT_METHOD_ID.
• AR_RECEIPT_METHOD_ACCOUNTS (aliased B) — the remittance bank account mappings for receipt methods, joined on RECEIPT_METHOD_ID.
• CE_BANK_ACCT_USES_ALL (aliased ACCUSE) — the Cash Management bank account use definitions, joined via REMIT_BANK_ACCT_USE_ID to BANK_ACCT_USE_ID.

The join path links the receipt method to its receipt class, then to its customer assignments, its receipt method accounts, and finally to the bank account use records. Because the view uses SELECT DISTINCT, duplicate rows arising from multiple account uses or customer assignments are collapsed. All five base objects are referenced as synonyms rather than as fully qualified table names, which is standard for APPS-owned views and ensures the view resolves against the same schema regardless of the session's default schema.

Key Columns

• NAME — the receipt method name from AR_RECEIPT_METHODS, the user-facing identifier displayed in Receivables setup and transaction entry.
• RECEIPT_METHOD_ID — the unique primary key identifier of the receipt method, used as the foreign key throughout Receivables, Cash Management, and related localization tables.
• CREATION_METHOD_CODE — sourced from AR_RECEIPT_CLASSES, this code indicates the creation method associated with the receipt class. It is the column most frequently referenced by localization programs and by the search term "creation_method_code."

The projection is intentionally narrow, exposing only the three columns required for lookup and filtering while abstracting the complex multi-table join behind a single selectable view.

Common Use Cases and Queries

The view is typically used to resolve receipt method names to their creation method codes within Brazilian and Latin American localization flows, such as receivables reporting, bank remittance processing, and data validation scripts.

A representative query retrieves the creation method for all receipt methods:

• SELECT name, receipt_method_id, creation_method_code FROM apps.jl_br_ar_rct_mthd_2_v ORDER BY name;

A targeted lookup resolves a specific receipt method by identifier:

• SELECT name, creation_method_code FROM apps.jl_br_ar_rct_mthd_2_v WHERE receipt_method_id = :p_receipt_method_id;

A filter by creation method code supports validation or reporting of receipt methods sharing common creation behavior:

• SELECT receipt_method_id, name FROM apps.jl_br_ar_rct_mthd_2_v WHERE creation_method_code = :p_creation_method_code;

Because the view returns distinct rows, it is safe to use in reporting joins without introducing artificial duplication, though consumers should account for the fact that creation method codes come from the receipt class and therefore apply uniformly to all receipt methods sharing that class.