Results for “document_count_limit”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBY_REMIT_ADVICE_SETUP is a configuration table in the Oracle Payments (IBY) product that governs how remittance information — commonly referred to as remittance advice — is created and delivered to a payee independently of the payment instrument itself. Rather than treating remittance advice as an incidental artifact of payment processing, this table externalizes the decision of whether to produce an advice, what format it takes, how it is transmitted, and how it relates to the underlying payment documents. Configuration is keyed at the payment process profile level, meaning that each profile defined in IBY_SYS_PMT_PROFILES_B can carry its own remittance advice behavior and constraints.
In terms of Data Vault modeling heuristics mined from the foreign-key structure, this object is best classified as a link. It associates a payment process profile (by SYSTEM_PROFILE_CODE) with a remittance advice format (by REMITTANCE_ADVICE_FORMAT_CODE), and additionally carries descriptive satellite-style attributes describing delivery behavior. In practice it functions as a set of descriptive attributes hanging off the profile-to-format association, so a hub-and-link reading with dependent descriptive columns is an appropriate conceptualization.
Key Information Stored
The table carries 16 documented columns. The most operationally significant are:
- SYSTEM_PROFILE_CODE — the primary key of the table (via IBY_REMIT_ADVICE_SETUP_PK) and the foreign key to IBY_SYS_PMT_PROFILES_B. It ties each setup row to one payment process profile.
- REMITTANCE_ADVICE_FORMAT_CODE — foreign key to IBY_FORMATS_B, selecting the output format used to render the advice (for example, XML or a printer-ready layout).
- REMIT_ADVICE_DELIVERY_METHOD — the channel through which the advice is transmitted to the payee, independent of payment delivery.
- DOCUMENT_COUNT_LIMIT — a threshold governing how many payment documents may be consolidated into a single advice.
- PAYMENT_DETAILS_LENGTH_LIMIT — a cap on the volume of payment detail lines carried on the advice.
- ALLOW_MULTIPLE_COPY_FLAG — controls whether more than one copy of the advice may be generated.
- SRA_OVERRIDE_PAYEE_FLAG — determines whether supplier remittance advice (SRA) settings may be overridden at the payee level.
- AUTOMATIC_SRA_SUBMIT_FLAG — indicates whether supplier remittance advice submission occurs automatically.
- SEEDED_FLAG — marks Oracle-seeded setup rows versus customer-defined rows.
- OBJECT_VERSION_NUMBER and the standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — provide optimistic locking and row-level audit history.
- ZD_EDITION_NAME — the editioning column, part of the unique index IBY_REMIT_ADVICE_SETUP_U1 (SYSTEM_PROFILE_CODE, ZD_EDITION_NAME), which reflects the edition-based redefinition strategy in Oracle EBS 12.2.2.
Note that SYSTEM_PROFILE_CODE is simultaneously the declared primary key (a surrogate-like identifier) and the leading column of the unique business index, reflecting the profile-centric natural key of this configuration.
Common Use Cases and Queries
Typical work includes auditing which payment process profiles generate remittance advice, verifying delivery channels, and diagnosing why advice was or was not produced for a given disbursement run. A representative query joins the setup row to its format definition:
- List profiles with their advice format and delivery method:
SELECT s.SYSTEM_PROFILE_CODE, s.REMITTANCE_ADVICE_FORMAT_CODE, s.REMIT_ADVICE_DELIVERY_METHOD FROM IBY.IBY_REMIT_ADVICE_SETUP s, optionally joining IBY_FORMATS_B on REMITTANCE_ADVICE_FORMAT_CODE to resolve format names. - Identify profiles configured with document consolidation limits: filter on DOCUMENT_COUNT_LIMIT and PAYMENT_DETAILS_LENGTH_LIMIT to find thresholds that may truncate payment detail on large advices.
- Distinguish seeded versus customized setups using SEEDED_FLAG, useful during upgrades from 12.1.1 to 12.2.2.
- Reconcile profile-level delivery configuration against actual advice records for reporting on remittance delivery compliance.
Related Objects
The following objects are most directly tied to this table through documented key relationships:
- IBY_SYS_PMT_PROFILES_B — referenced by SYSTEM_PROFILE_CODE; the parent definition of each payment process profile.
- IBY_FORMATS_B — referenced by REMITTANCE_ADVICE_FORMAT_CODE; defines the advice output format.
- IBY payment process profile and format configuration pages in the Payments Manager, which read and write these rows.
- Remittance advice generation and delivery processes that consume these settings at payment run time.
- The unique index IBY_REMIT_ADVICE_SETUP_U1 and primary key constraint IBY_REMIT_ADVICE_SETUP_PK as the enforcing database objects.
-
IBY_REMIT_ADVICE_SETUP stores information on creating and delivering remittance information, or remittance advice, for a payee separately from the payment itself. Remittance advice setup is organized by payment process profile. Each payment
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI