Skip Headers

Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to Release 12
Release 12.1
Part Number E13482-03
Go to Table of Contents
Go to previous page
Go to next page

Oracle U.S. Federal Financials

This chapter covers the following topics:


U.S. Federal Financials interacts with several products within the Oracle product family, such as Oracle Payables, Oracle Payments, Oracle General Ledger, Oracle Subledger Accounting, Oracle Receivables, Oracle Purchasing, and Oracle Cash Management. Refer to the appropriate sections of this document to gain an understanding of the detail-level impact of these products to the U.S. Federal Financials users.

The following section details the additional impacts to the U.S. Federal Financials product:

Integration with Subledger Accounting

Release 12 introduces the new Subledger Accounting (SLA) module for managing accounting across subledger transactions. With the introduction of SLA, transaction codes no longer need to be entered on a transaction to create the desired accounting. Instead, Oracle U.S. Federal Financials provides account derivation rules that use attributes from transactions to determine the correct accounting.

In Release 11i, journals in GL are kept in detail, so no transaction code journals will be moved into SLA. All accounting reports will combine GL and SLA data. During normal processing, the SLA code will detect if the journal exists in SLA or GL (upgrade case or not) and use the appropriate SLA rule to create the accounting.

USSGL Transaction Codes

With the introduction of SLA, U.S. Federal Financials has seeded, account-derivation rules to replace the use of transaction codes on transactions. The account-derivation rules seeded for use in Oracle Purchasing, Oracle Cost Management, Oracle Payables, and Oracle Receivables are seeded with a six-digit subaccount of the USSGL account. U.S. Federal Financials has provided the USSGL Account Derivation Rules report. This report displays for the US Federal Accounting subledger accounting method, any seeded, account-derivation rules where the USSGL account value is seeded. This report details the attributes of the seeded rules and the seeded six-digit USSGL subaccounts being used by the rule. This report should be reviewed to confirm that the subaccounts that are seeded, exist in the chart of accounts. In addition, this report can be used to determine if there is any desired accounting that would have been previously generated by transaction codes in Oracle Purchasing, Oracle Cost Management, Oracle Payables, and Oracle Receivables that are not reflected in the seeded rules. Custom account derivation rules can be built to change the six-digit subaccount from the seeded rule, to change conditions for the existing rules that are seeded or to create new rules for transaction codes that are not seeded.

Implementation of AR/AP Netting

In Release 11i, Oracle Financials has three netting solutions:

While these solutions provide netting functionality, each address a different specific need.

In Release 12, the new AP/AR Netting solution is introduced in the Oracle Financial Common Module, and is intended to consolidate and improve the functionality to create one total-netting solution built into the standard applications. Therefore, the U.S. Federal Financial AR/AP Netting solution has been made obsolete. The setup data used by the U.S. Federal Financials AR/AP Netting solution will be migrated to the new Release 12 AP/AR Netting solution.

Summary Schedules and Consolidated Files

With the introduction of the new Oracle Payments solution in Release 12, changes were made in the process to issue payments.

For functional knowledge of Oracle Payments, refer to the Oracle Payments Users Guide and Oracle Payments Implementation Guide.

For upgrade information of federal payment formats, refer to the Oracle Payables chapter, Payment Formats section of this guide.

U.S. Federal Financials has integrated with Oracle Payments and, therefore, made changes to the U.S. Federal Financials Summary Schedule and Consolidated Files feature. Consolidated payment files can be generated in Release 12 directly within Oracle Payments. The creation of summary schedules in Release 12 will remain in U.S. Federal Financials. The window name has changed from Summary Schedule and Consolidated Files to Summary Schedules. After upgrade to Release 12, any Release 11i payment batch that is associated with a summary schedule or a consolidated payment file that has not been generated, will have to be voided and re-created in Release 12 through Oracle Payments. To avoid this, these payment files can be generated in Release 11i by using U.S. Federal Financials’ Summary Schedule and Consolidated Files window prior to the upgrade.

Employee Payment Type Mapping

The Employee Payment Type Mapping window has been made obsolete in Release 12. This window was used to associate a Payables payment group to an employee payment types used by Federal payment formats. This enabled payment batches to group invoices by a format’s specific payment type. In Release 12 this association is no longer needed because Oracle Payments has introduced payment reason codes. The employee payment types are now seeded by Oracle Payments as payment reasons. Payment reasons are entered on an invoice and therefore will enable invoices to be grouped into the specific Federal payment formats.