Understanding the Federal Object Class and Program Code Interface
The Digital Accountability and Transparency Act (DATA Act) mandates agencies to report on their financial obligations and outlays by Program Activity and Object Class segments. The Federal Office of Management and Budget issued the new interface specifications in their Circular A-11 Sections S82 for Program Activity and S83 for Object Class.
The following diagram illustrates the high-level steps that PeopleSoft supports for the Federal Object Class and Program Code Interface. The first requirement is to configure accounts, funds, ChartField attributes, PeopleSoft trees, the Federal Object and Program definition, Federal Program Activity mapping, and Federal Object and Program trees. Next, transactions are entered with the appropriate data and attributes. Federal Object Class and Program Code Interface processing extracts data from the ledger, associates it with attributes, loads it to a staging table, creates the bulk file, and generates a report from the staging table. The user can review the data in the bulk file or the report output.
Before you begin, configure the Federal Object Class and Program Code Interface. Enter transactions with appropriate data and attributes, then run the Federal Object Class and Program Code processing. You should review the bulk file or report output before submitting the report to the U.S. Treasury.
The following setup is required for the Federal Object and Program Code Interface:
An agency must be a GWA Reporter to report Object Class and Program Code data.
Componentized TAS and BETCs must be set up for reported funds.
Fund codes must be set up.
For more information about setting up the Agency Location Code for GWA Reporters, see Defining Agency Location Codes.
For more information about setting up TAS/BETC, see Defining Component TAS and BETC Elements in Compliance with Federal Reporting Requirements.
For more information about setting up funds, see the Fund Code Page.