Results for “initial_seq_value”

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

Overview

The FV_PB_SEQ_ASSIGNMENTS_ALL table is a Federal Financials (FV) module object in Oracle E-Business Suite, holding the definitions that govern payment batch sequence assignments. It is the base table underlying the Payment Batch Sequence Assignments form, and it is owned by the FV schema. Each row defines the numbering policy applied to a payment batch associated with a given payment reason code and organization, controlling the sequence values and the optional prefix/suffix text used when payment documents or batch identifiers are generated.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a satellite (satellite-leaning classification). Its grain is defined by payment-related business attributes, and its primary outbound dependency points to a reference table rather than to other transactional hubs, which is consistent with a descriptive satellite hanging off a payment-reason business key.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• SEQ_ASSIGNMENT_ID — the surrogate primary key identifying each sequence assignment record.
• PAYMENT_REASON_CODE — foreign key to IBY_PAYMENT_REASONS_B, tying the assignment to a specific payment reason.
• ORG_ID — the operating unit (multi-org) identifier, present in both unique indexes.
• PAY_GROUP_CODE — the payment group the assignment applies to.
• INITIAL_SEQ_VALUE, FINAL_SEQ_VALUE, NEXT_SEQ_VALUE — the starting, ending, and next sequence numbers for the batch numbering range.
• PREFIX, SUFFIX — text appended before and after the generated sequence value.
• START_DATE, END_DATE — the effective period during which the assignment is active.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for auditing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) columns for extensibility.

The surrogate primary key is SEQ_ASSIGNMENT_ID. Two documented unique indexes serve as business-key candidates: FV_PB_SEQ_ASSIGNMENTS_U1 (ORG_ID, PAYMENT_REASON_CODE) and FV_PB_SEQ_ASSIGNMENTS_U2 (ORG_ID, PREFIX, SUFFIX). These enforce that a payment reason code, and a prefix/suffix combination, are unique within an operating unit.

Common Use Cases and Queries

Typical scenarios include validating that each payment reason has a distinct, active sequence assignment, auditing prefix/suffix conventions, and verifying the next value a batch will consume. A representative query joining the reference table follows:

• SELECT s.SEQ_ASSIGNMENT_ID, s.PAYMENT_REASON_CODE, s.ORG_ID, s.PREFIX, s.SUFFIX, s.NEXT_SEQ_VALUE FROM FV_PB_SEQ_ASSIGNMENTS_ALL s, IBY_PAYMENT_REASONS_B r WHERE s.PAYMENT_REASON_CODE = r.PAYMENT_REASON_CODE AND s.ORG_ID = :p_org_id;
• Retrieve active assignments by date: WHERE TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, TRUNC(SYSDATE)).
• Check duplicates against the business keys U1 or U2.
• Report the sequence range and next value per operating unit for reconciliation.

Related Objects

• IBY_PAYMENT_REASONS_B — referenced via FV_PB_SEQ_ASSIGNMENTS_ALL.PAYMENT_REASON_CODE; the primary FK relationship.
• FV_PB_SEQ_ASSIGNMENTS_U1 / U2 — unique indexes enforcing the business keys (ORG_ID + PAYMENT_REASON_CODE; ORG_ID + PREFIX + SUFFIX).
• Payment batch and payment process objects in the FV/IBY modules that consume sequence values when batches are created.
• The Payment Batch Sequence Assignments form, which reads and maintains this table.