Results for “agency_name”

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

Overview

FV_TP_BULK_FMT_DATA is a Federal Financials (FV) transaction table within Oracle E-Business Suite, owned by the FV schema and valid in both 12.1.1 and 12.2.2. The table stores agency-related payment information generated during the bulk payment formatting process, capturing the total payment amount alongside the aggregate count of payment records included in a bulk format run. It functions as the staging and summary layer that bridges Oracle Payables payment instructions and the formatted output files delivered to federal agencies, treasury, or disbursing offices.

Based on the foreign key relationship to FV_DMS_AGENCY_DEFINITIONS_ALL, the table records agency-level attributes required for payment formatting, including agency identifiers, addresses, and telephone contact data. It is primarily a formatting and reporting support table rather than an operational transaction table, and its rows correspond to a specific checkrun, payment format, and pay group combination. From a Data Vault modeling perspective, this object is classified heuristically as a standalone entity; because it references a single parent (agency) without acting as an associative link between multiple hubs, it is best modeled as a hub or satellite anchored on the bulk format business key rather than a link table.

Key Information Stored

FV_TP_BULK_FMT_DATA contains 19 documented columns. The most significant include:

• CHECKRUN_NAME — identifies the payment batch (checkrun) that produced the bulk format data.
• SET_OF_BOOKS_ID — the ledger context for the payment records.
• ORG_ID — operating unit identifier, supporting multi-org security.
• PAYMENT_FORMAT_NAME and FORMAT_PAYMENTS_FRIENDLY_NAME — the payment format program and its user-facing label.
• PAY_GROUP_CODE — payment grouping classification used during formatting.
• RFC_IDENTIFIER and FED_EMPLOYER_ID_NUMBER — federal routing and employer identification values.
• AGENCY_ID — foreign key to FV_DMS_AGENCY_DEFINITIONS_ALL.
• AGENCY_ALC_CODE, AGENCY_NAME, AGENCY_ADDRESS_LINE_1, AGENCY_ADDRESS_LINE_2, AGENCY_CITY_STATE_ZIP, AGENCY_TELEPHONE_NUMBER1 — denormalized agency demographic data used for formatting output files.
• CHECK_DATE — date associated with the payment run.
• EMP_ECS_PAY_TYPE_CODE — employee electronic payment type classification.
• SCHEDULE_RECORD_COUNT and TOTAL_SCHEDULE_AMOUNT — the aggregate number of payment records and summed payment amount for the schedule, providing the summary totals referenced in the object description.

The documented metadata does not explicitly identify a surrogate primary key column or unique business index; the natural business key is likely the composite of CHECKRUN_NAME, PAY_GROUP_CODE, and AGENCY_ID.

Common Use Cases and Queries

Typical usage centers on reconciliation, agency payment reporting, and audit. Analysts frequently join this table to FV_DMS_AGENCY_DEFINITIONS_ALL to resolve agency details, and to payment/checkrun tables to verify scheduled totals against disbursed amounts.

A representative query retrieves summary totals by agency for a given checkrun:

• SELECT AGENCY_NAME, SCHEDULE_RECORD_COUNT, TOTAL_SCHEDULE_AMOUNT FROM FV_TP_BULK_FMT_DATA WHERE CHECKRUN_NAME = :checkrun ORDER BY AGENCY_NAME;

Additional scenarios include validating that the sum of individual payment records equals TOTAL_SCHEDULE_AMOUNT, producing formatted agency cover sheets using the stored address and telephone columns, and feeding downstream bulk file generation programs.

Related Objects

• FV_DMS_AGENCY_DEFINITIONS_ALL — parent table joined on AGENCY_ID; supplies canonical agency code, name, and address definitions.
• Oracle Payables checkrun and payment instruction tables (AP_CHECKS_ALL, AP_INVOICE_PAYMENTS_ALL) — source of the underlying payment records summarized here.
• FV payment format and treasury disbursement objects within the FV module that consume the formatted output.

Because ATTRIBUTE-based relationships are limited to the single documented foreign key, integration is principally through the agency dimension and the checkrun name.