Search Results full_discount_flag

Overview

AR_TA_REMIT_PROF is a Receivables (AR) view exposed in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents remittance profile definitions. It is classified in the ETRM repository as a SINGLE_ORG view, meaning its result set is filtered to the organization context of the current session rather than returning data for all operating units. In practice, the view is used to resolve the remittance bank and receipt-processing rules that govern how customer receipts are attributed to a bank account, deposit date, and remittance batch policy.

The view is significant because it is the reporting-friendly projection of the underlying multi-organization table. Application logic, concurrent programs, and custom reporting/integration code query it against the session's organization ID to retrieve only the profile rows relevant to the operating unit in context. The presence of the RECEIVABLES_TRX_ID column ties the object directly to the Oracle Receivables transaction type configuration, which is why searches using the term "receivables_trx_id" commonly surface this view.

Underlying Base Objects

The view is defined over a single base object, AR_TA_REMIT_PROF_ALL. This table stores remittance profile records across all operating units, distinguished by the ORG_ID column. The view applies an organization filter using the SESSION CLIENT_INFO mechanism typical of EBS multi-org views:

• The filter compares NVL(ORG_ID, ...) against the organization identifier decoded from USERENV('CLIENT_INFO'), substituting -99 when the value cannot be resolved.
• Because the filter is derived from session context, the view returns only the rows belonging to the current operating unit, or the special organization identity used when no valid context exists.
• No other base tables are documented as being referenced by the view text; all columns are drawn from AR_TA_REMIT_PROF_ALL.

The ETRM metadata notes that the object is "Not implemented in this database" for the documented instance, which indicates the view may be absent in environments where the corresponding remittance profile functionality has not been deployed or where the database is not fully provisioned. This should be verified against the target instance before relying on the object in custom code.

Key Columns

The column list is dominated by profile control attributes and descriptive metadata. Notable columns include:

• PROFILE_ID — Primary identifier of the remittance profile.
• NAME, DESCRIPTION, START_DATE, END_DATE — Identification and effective-dating attributes for the profile.
• DISCOUNT, FULL_DISCOUNT_FLAG, DISCOUNT_BASIS — Discount terms and the basis on which early-payment discounts are calculated.
• RULE_SET_ID, DEFAULT_TRX_SET_ID — References to the receipt rule set and the default transaction set applied by the profile.
• MATCHED_UNDR_PAY_RULE, MATCHED_OVER_PAY_RULE, UNMATCHED_POS_PAY_RULE, UNMATCHED_NEG_PAY_RULE — Treatment rules for underpayments, overpayments, and unmatched positive or negative payment amounts.
• WRITE_OFF_OVER_PAY_FLAG/THRESHOLD, WRITE_OFF_UNDR_PAY_FLAG/THRESHOLD — Controls governing automatic write-off of payment differences.
• RECEIVABLES_TRX_ID — The associated Receivables transaction type, linking the profile to the Remit-to transaction configuration.
• APPLY_DATE_FLAG, DEPOSIT_DATE_FLAG, POSTMARK_DATE_FLAG with matching GRACE_DAYS columns — Date-basis and tolerance settings for receipt dating.
• ORG_ID — The operating unit that owns the profile row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments for customer extensions.

Common Use Cases and Queries

Typical reporting scenarios include reconciling remittance profiles to receipt batches, auditing payment difference handling, and exposing profile configuration to downstream integrations. A basic query to list profiles for the current organization is:

• SELECT profile_id, name, receivables_trx_id, write_off_over_pay_flag FROM ar_ta_remit_prof WHERE receivables_trx_id = :trx_type_id;
• SELECT profile_id, name, start_date, end_date FROM ar_ta_remit_prof WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date;
• SELECT profile_id, matched_over_pay_rule, matched_undr_pay_rule FROM ar_ta_remit_prof WHERE org_id = :org_id;

Because the view is organization-filtered at runtime, callers must ensure the correct operating unit context is set before querying; otherwise the result set may be empty or restricted by the fallback identifier used in the view predicate.