Results for “fv_tp_ts_amt_data”

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

Overview

FV_TP_TS_AMT_DATA is a Federal Financials (FV) module table in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores Treasury Symbol amount data associated with payment instructions, bridging the Treasury reporting and disbursement functions of the Federal Financials application. The table is owned by the FV schema and contains six documented columns in the 12.2.2 physical schema. Its role is to record check-run level Treasury symbol amounts that support federal treasury reporting, such as the SF 224 Statement of Transactions and related Treasury reporting extracts.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. This suggests FV_TP_TS_AMT_DATA behaves as a descriptive satellite recording measures and attributes tied to a parent business entity (the payment instruction), rather than acting as an independent hub or a pure connecting link.

Key Information Stored

Only the six columns documented in the ETRM physical schema are described. The table's most significant columns include:

• PAYMENT_INSTRUCTION_ID — Foreign key to IBY_PAY_INSTRUCTIONS_ALL; the associating business identifier that ties each Treasury symbol amount row back to its originating payment instruction.
• TREASURY_SYMBOL — The Treasury Account Symbol (TAS) identifying the federal appropriation or fund account to which the amount applies.
• AMOUNT — The monetary value recorded for the Treasury symbol in the context of the associated check run and payment instruction.
• CHECKRUN_NAME — The name of the payment check run that generated the disbursement, providing grouping and audit context.
• SET_OF_BOOKS_ID — The ledger identifier, supplying the accounting context for the amount.
• ORG_ID — The operating unit identifier, providing multi-org security and reporting granularity.

No standalone surrogate primary key column is documented in the metadata excerpt beyond these attributes; the row identity is effectively driven by the combination of the payment instruction context (PAYMENT_INSTRUCTION_ID) plus the Treasury symbol and check run attributes. Business-key candidates therefore center on the payment instruction and Treasury symbol pairing rather than a single documented synthetic key.

Common Use Cases and Queries

Typical scenarios involve reconciling Treasury disbursement amounts to payment instructions and check runs. Common reporting patterns include:

• Aggregating amounts by Treasury symbol for a given check run to support federal Treasury reporting.
• Reconciling payment instruction disbursements against Treasury symbol totals.
• Filtering by ORG_ID and SET_OF_BOOKS_ID to produce operating-unit and ledger-specific extracts.

A representative query joins the table to its parent payment instruction and groups by Treasury symbol:

• SELECT t.TREASURY_SYMBOL, t.CHECKRUN_NAME, SUM(t.AMOUNT) FROM FV.FV_TP_TS_AMT_DATA t WHERE t.ORG_ID = :org_id AND t.SET_OF_BOOKS_ID = :sob_id GROUP BY t.TREASURY_SYMBOL, t.CHECKRUN_NAME;
• SELECT t.*, p.* FROM FV.FV_TP_TS_AMT_DATA t, IBY.IBY_PAY_INSTRUCTIONS_ALL p WHERE t.PAYMENT_INSTRUCTION_ID = p.PAYMENT_INSTRUCTION_ID;

Related Objects

The most significant relationship is the foreign key to IBY_PAY_INSTRUCTIONS_ALL via PAYMENT_INSTRUCTION_ID, which parent-links each Treasury symbol amount to its payment instruction. Related objects of interest include:

• IBY_PAY_INSTRUCTIONS_ALL — Parent table joined on PAYMENT_INSTRUCTION_ID; the primary documented referential relationship.
• IBY_PAY_INSTRUCTION_DETAILS — Payment instruction detail rows commonly analyzed alongside Treasury symbol amounts.
• IBY_PAYMENTS_ALL — Payment records linked through the payment instruction hierarchy for disbursement reconciliation.
• FV_TP_TS_* objects — Sibling Treasury symbol tables within the FV Treasury reporting family.
• AP_CHECKS_ALL — Check run context supporting CHECKRUN_NAME-based reconciliation.
• GL_LEDGERS / FND_ORG tables — Referenced indirectly through SET_OF_BOOKS_ID and ORG_ID for accounting and multi-org context.

Because the documented metadata is limited to one foreign key and six columns, joins to payment instruction and check-run objects should be validated against the installation's specific configuration.