2. Introduction
Larry Baugh
• 11+ years Oracle Federal Financials Functional/Technical Experience
• Emphasis Areas: GL, Budget Execution, Fed Admin, AR, AP, Fed
Reporting, PA, PO, iProc, Proc Contracts, XML/BI Publisher, Discoverer,
SQL, PL/SQL, etc.
• Sample Federal Customers: USAF/USTC-DEAMS, DFAS, TMA,
SDDC/MTMC, MSC, SBA, DOI-NBC (TDA, VCT, SSS, MCC, CSOSA/PSA),
DOE-Nevada Test Site, US House of Reps, OPM, etc.
3. Agenda
• Project Agreements Enhancements
• Matching of Agreements to AR Advances and clearing revenue against
the advance & driving proper accounting
• Date Effective and Sequential Consumption/Charging of
Agreements/Funding (Tracking Revenue by Agreement ID)
• Federal SLA USSGL Transactions: Cost, Customer Orders, Revenue
• Expenditure Analysis Enhancements
• Supplier Cost Adjustments Enhancements
• Wrap-Up
• Additional Resources
Presentation Goal: To provide a high-level
introduction to new R12.1 Projects Concepts,
Capabilities and Terminology with a focus on
relevant topics to Federal Financials customers.
5. Agreements: 15 Additional DFF Segments
These segments can definitely come in handy for storing customer agreement data that may
need to be parsed out for interfacing, e.g. Federal Line of Accounting data
Note: Attributes 11-25
need to be enabled as
of R12.1.
6. Matching AR Receipts to PA Agreement Advances
AR Standard Receipts in ‘On Account’ Status can be applied to PA Agreements.
7. Matching AR Receipts to PA Agreement Advances
You can apply multiple receipts to a PA agreement. You cannot apply the same receipt to
multiple agreements.
8. Matching AR Receipts to PA Agreement Advances
Once the Receipt is selected, click ‘Apply Receipt’.
9. Matching AR Receipts to PA Agreement Advances
The Advance Amount on the Agreement is updated.
10. Matching AR Receipts to PA Agreement Advances
The AR Receipt now reflects that the receipt has been applied to the Agreement as a
Prepayment.
11. Matching AR Receipts to PA Agreement Advances
To Unapply a receipt, simply click the ‘Unapply Receipts’ button and select the applicable
receipt to Unapply.
12. Matching AR Receipts to PA Agreement Advances
The Advance Amount on the PA Agreement is updated when the Unapply action is saved.
13. Tracking Agreement Fundings by Sequence
R12.1 now allows for identifying the sequence in which agreements are charged against or
consumed. When the customer is a Federal entity, this allows for exhausting agreements
funded by older lines of accounting (LOAs) (e.g. Appropriations that could be cancelling soon),
prior to more current LOAs.
14. This feature allows for controlling that related cost reimbursable and event transaction dates
must be within the agreement start and end dates for agreement billing. In addition, you can bill
transactions against the agreement for revenue and invoice if the full transaction amount can
be funded. The billing sequence and effective dates for each agreement determine the order in
which agreements/customers are invoiced for projects funded by multiple agreements.
Date Effective Funds Consumption
15. Date Effective Funds Consumption
Date Effective Funds Consumption can be configured at the Project Type or Project level
16. Federal Community: “Oracle, Can I please get some
standard PA Budgetary Accounting Functionality?”
“What?”……”Nope”……”Nope”……..…”Working On It”…....”OK Fine, Here”
18. Creating PA Expenditure Accounting Entries w/SLA
Projects Cost SLA Components are now included as seeded. These SLA Components may
work in tangent with established PA AutoAccounting rules.
19. Enter PA Expenditures, e.g. Exp Batch, Interface
Run PRC: Distribute processes
Run PRC: Generate Cost Accounting Events
Run PRC: Create Accounting
Creating PA Expenditure Accounting Entries w/SLA
Process flow of steps involved.
26. Creating PA Funding Entries w/SLA
Projects Budgets SLA Components are now included as seeded.
27. Creating PA Funding Entries w/SLA
The seeded Budget Event sources primarily leverage data from
apps.pa_xla_bc_budget_lines_v.
28. Creating PA Funding Entries w/SLA
The seeded Budget Event sources leverages CCIDs from the Budget Lines.
29. Creating PA Revenue Accounting Entries w/SLA
Projects Revenue SLA Components are now included as seeded. These SLA Components may
work in tangent with established PA AutoAccounting rules.
30. Integrating with the Budget Execution Module of Oracle Federal Financials
When you create a baseline project budget, you can populate the budget execution
interface table to integrate with the Budget Execution module of Oracle Federal
Financials.
When the profile option FV: Federal Enabled is set to Yes, the Project Budget Workflow
process calls the Federal Integration Client Extension. You can modify the default logic
supplied with the client extension to populate the Budget Execution Interface table with
the appropriate values. You can have approval workflow notification sent to your
Budget Execution analyst.
Related Topics
Federal Integration Client Extension, Oracle Projects APIs, Client Extensions, and Open
Interfaces Reference
Project Budget Workflow, Oracle Projects Implementation Guide
Fed Admin Budget Execution Integration
Per Oracle® Projects Fundamentals Release 12.1:
32. AR Receipt Notification
The AR Receipt Notification determines if project managers of projects receive notifications
when AR Receipts are applied to customer invoices.
33. Improved Federal Accounting with Oracle Projects Release 12.1.1+
Neeraj Garg, Project Partners LLC, Monday, April 19, 10:45AM, Breakers L
Other Related Sessions