Results for “creation_method_code”

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

Overview

JL_BR_AR_RCT_MTHD_1_V is a reporting view owned by the APPS schema within the JL (Latin America Localizations) product family, specifically associated with the Brazilian Accounts Receivable localization retrofitted for Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates receipt method configuration data — including receipt method names, validity dates, customer assignments, bank account usage, currency, and multi-currency eligibility — across several Accounts Receivable and Cash Management base tables. Its principal role is to present a flattened, query-ready dataset describing how receipt methods are defined and assigned for customers within a given operating unit and set of books. The inclusion of the MULTI_CURRENCY_FLAG column (sourced from CE_BANK_ACCOUNTS.RECEIPT_MULTI_CURRENCY_FLAG) makes this view particularly relevant when validating whether a receipt method can accept receipts in multiple currencies, a frequent requirement in Brazilian localization reporting and integration scenarios.

Underlying Base Objects

The view is constructed from a join across seven documented base objects:

• AR_RECEIPT_METHODS (synonym) — provides the receipt method name, ID, and effective start/end dates.
• AR_RECEIPT_CLASSES (synonym) — supplies the creation method code associated with the receipt method.
• RA_CUST_RECEIPT_METHODS (synonym) — links customers and site uses to receipt methods, with customer-level effective dates.
• AR_RECEIPT_METHOD_ACCOUNTS (synonym) — ties receipt methods to remittance bank account uses.
• CE_BANK_ACCT_USES_ALL (synonym) — resolves the bank account use record and its associated operating unit (ORG_ID).
• CE_BANK_ACCOUNTS (synonym) — supplies the currency code, multi-currency flag, and inactive date.
• HR_OPERATING_UNITS (view) — provides the set of books ID via the organization ID.

The join is driven by receipt method ID and class ID, then extended through bank account use and organization identifiers to produce a single denormalized row per receipt method/customer/site/account combination.

Key Columns

• NAME — the receipt method name.
• RECEIPT_METHOD_ID — primary identifier for the receipt method.
• RECEIPT_START_DATE / RECEIPT_END_DATE — validity window of the receipt method itself.
• CREATION_METHOD_CODE — the creation method of the receipt class.
• SET_OF_BOOKS_ID — set of books derived from the operating unit.
• CURRENCY_CODE — currency of the associated bank account.
• MULTI_CURRENCY_FLAG — indicates whether the receipt method supports multiple currencies.
• CUSTOMER_ID / SITE_USE_ID — customer and site use assignment.
• INACTIVE_DATE — bank account inactive date, defaulted to 01/01/2200 when null.
• CUST_RCPT_START_DATE / CUST_RCPT_END_DATE — customer receipt method effective dates.
• RCPT_MTHD_START_DATE / RCPT_MTHD_END_DATE — receipt method account effective dates.

Common Use Cases and Queries

Typical usage includes auditing which receipt methods are multi-currency enabled for a given operating unit, and reconciling customer-level receipt method assignments against bank account configuration. A representative query follows:

SELECT name,
       receipt_method_id,
       set_of_books_id,
       currency_code,
       multi_currency_flag,
       customer_id,
       site_use_id,
       inactive_date
FROM   apps.jl_br_ar_rct_mthd_1_v
WHERE  multi_currency_flag = 'Y'
AND    set_of_books_id = :p_set_of_books_id
AND    NVL(inactive_date, TO_DATE('01/01/2200','DD/MM/YYYY')) > SYSDATE;

The view is also useful for localization reporting where Brazilian receipt method eligibility must be validated against currency and customer assignment data.