Results for “signed_flag”

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

Overview

AR_BR_MAIN_REMIT_BATCH_V is a seed data view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It is a component of the Brazilian localization remittance (Boleto / borderô) printing framework, providing the main remittance batch data set consumed by the concurrent program and report logic that generates bank remittance documents. The view flattens the relationship between a remittance batch (AR_BATCHES), the customer transactions and payment schedules assigned to that batch, the drawee (customer) and drawee site information, and the associated banks and branches, so that a single row represents one transaction within a remittance batch, ready for formatted output.

Because the view is a denormalized reporting object, it abstracts more than twenty base tables and several packaged APIs, exposing only the attributes required for remittance layout. It is registered as VALID in ETRM for both 12.1.1 and 12.2.2, meaning its structure is consistent across these releases.

Underlying Base Objects

The view is defined as a join across the following documented base objects:

• Receivables transaction tables: AR_BATCHES, AR_PAYMENT_SCHEDULES, AR_TRANSACTION_HISTORY, RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, and the AR_LOOKUPS view for lookup translations.
• Trading community (HZ) tables: HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_SITE_USES, HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_CLASSES, HZ_RELATIONSHIPS, and HZ_ORGANIZATION_PROFILES.
• Banking and payments objects: CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_OU_V, IBY_TRXN_EXTENSIONS_V, IBY_FNDCPT_TRXN_PUB, plus the ARP_BR_REMIT_FUNCTION and FND_GLOBAL packages.

The transaction history alias (RAH) and payment schedules anchor each row to a specific installment, while HZ joins resolve party name, account number, fiscal code, category, and address. Bank and branch details are derived from IBY extension views and CE bank account objects, with the organization unit context supplied through CE_BANK_ACCT_USES_OU_V.

Key Columns

• BATCH_ID — Identifier of the remittance batch from AR_BATCHES; the primary grouping key for a remittance run.
• CUSTOMER_TRX_ID, PAYMENT_SCHEDULE_ID, TRX_NUMBER, TRX_DATE, DUE_DATE — Transaction and installment identity, used to print invoice references and due dates.
• AMOUNT_DUE_REMAINING, ACCTD_AMOUNT_DUE_REMAINING — Entered and accounted amounts still outstanding at the time of remittance.
• NAME, SIGNED_FLAG, DRAWEE_ISSUED_FLAG — Transaction type name and indicators from RA_CUST_TRX_TYPES that drive printing logic.
• PRINTING_LAST_PRINTED, COMMENTS, SPECIAL_INSTRUCTIONS — Reprint control and free-text output.
• Party attributes — PARTY_NAME (truncated to 50 bytes), ACCOUNT_NUMBER, JGZZ_FISCAL_CODE, CUSTOMER_CLASS_CODE, CATEGORY_CODE, and profile class NAME identify the drawee.
• Address columns — ADDRESS1||ADDRESS2||ADDRESS3, CITY, POSTAL_CODE, STATE, COUNTRY supply the drawee site address.
• Bank columns — DRAWEE_BANK_NAME, DRAWEE_BANK_NUMBER, DRAWEE_BRANCH_NAME, plus a set of NULL placeholders for branch city, state, country, postal code, and number reserved for format compatibility.
• REMITBANKPARTY.PARTY_NAME — Name of the remitting bank party.
• ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield segments from AR_PAYMENT_SCHEDULES.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN for audit.

Common Use Cases and Queries

The view is typically queried by the Brazilian remittance report to list transactions belonging to a batch, or by support teams to diagnose why a transaction is missing or misprinted on a borderô. A representative query is:

• SELECT batch_id, trx_number, trx_date, due_date, amount_due_remaining, party_name, drawee_bank_name FROM ar_br_main_remit_batch_v WHERE batch_id = :p_batch_id ORDER BY trx_number;
• Reporting outstanding remitted amounts by bank: SELECT drawee_bank_name, SUM(amount_due_remaining) FROM ar_br_main_remit_batch_v GROUP BY drawee_bank_name;
• Audit of flexfield usage: SELECT trx_number, attribute_category, attribute1 FROM ar_br_main_remit_batch_v WHERE attribute_category IS NOT NULL;

Because the view joins through the organization unit context (CE_BANK_ACCT_USES_OU_V) and utilizes FND_GLOBAL to resolve the operating unit, queries should be executed with the correct MO:/org context set, otherwise bank account rows may not resolve and remittance data will be incomplete.