R12 Federal Financials: Recent Enhancements and Upgrade Impacts

2. R12 Federal Financials: Recent Enhancements and Upgrade Impacts Larry Baugh Apps Ingenuity LLC April 25,2012

3. Agenda • Federal CGAC Enhancements • Treasury Account Symbols, TAS BETC • Budget Codes, FACTS Attributes, FACTS II Edit Codes • Purge Treasury Account Symbols • TAS/Fund/Bud Distributions Rollover • GTAS • Federal Multiple Cash Accounts and Treasury Confirmation Enhancement • Managing SLA Changes in R12 • R12 Federal Payment Processing • Web ADI Capability for FV Budget Distributions • Expired Fund Distribution Objective: to share a variety of information on R12 Updated functionality applicable to Federal Financials customers.

4. Introduction • Larry Baugh • 13+ 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: DOI-NBC, USAF/USTC-DEAMS, DFAS, TMA, SBA, Numerous DOE, DoD, and other Federal Civilian entities. • Recent Role: Solution Architect/Co-PM for US Dept. of Interior National Business Center (DOI-NBC) Shared Services Environment Release 12.1.3 Upgrade

5. CGAC Enhancements • The Common Government-wide Accounting Classification Structure (CGAC) is a new standard structure of financial data elements to be utilized within the US Federal Financial System environment. • Oracle provided numerous enhancements to better support this CGAC integration. Patch 9000001 should be installed to deploy this functionality. DO NOT just apply patch 9307787. • MOS Note: 1277072.1 Federal CGAC Enhancements

6. CGAC Enhancements Treasury Account Symbols Treasury Account Codes form is retired.

7. CGAC Enhancements Treasury Account Symbols

8. CGAC Enhancements Treasury Account Symbols

9. CGAC Enhancements 3-digit Agency Identifier values supported

10. CGAC Enhancements Fund Attributes (aka Fund Parameters)

11. CGAC Enhancements

12. CGAC Enhancements Business Event Type Codes (BETC)

13. CGAC Enhancements Budget Codes Budget Distributions

14. CGAC Enhancements Purge Treasury Symbols

15. CGAC Budget Authority The Enter Budget Authority form is quite similar to the 11i Enter Appropriations form and Earlier R12 form versions. The differences include: • Time Frame field replaced with Authority Duration Code • Category field broken out into 2 distinct fields: Apportionment Category & Direct or Reimb • Established FY field replaced with Beginning Period of Availability • Transaction Code field replaced with Sub-Type

16. CGAC Funds Distributions The R12 CGAC Enter Funds Distributions form. Differences include: • Category field broken out into 2 distinct fields: Apportionment Category & Direct or Reimb • From Distribution Description field added • Transaction Code field replaced with Sub-Type

17. CGAC Budget Authority When Checking Funds for Budget Distributions, R12 provides the capability to view specific Budgetary Control Results Data.

18. CGAC Enhancements Rollover Treasury Symbols

19. GTAS Enhancements New Federal Financial enhancements are imminent to provide agency capability for interfacing to the Government wide Treasury Account Symbol Adjusted Trial Balance System (GTAS) starting Dec. 2012. References/Screenshots to Oracle Federal Development GTAS info is taken from the 17-Apr-12 Oracle Federal Development Spring Briefing. http://www.fms.treas.gov/gtas/index.html

20. GTAS Enhancements

21. CGAC vs GTAS Enhancements CGAC GTAS

22. CGAC vs GTAS Enhancements GTAS CGAC

23. CGAC vs GTAS Enhancements CGAC GTAS

24. CGAC vs GTAS Enhancements GTAS CGAC

25. Key Federal-Related SLA Process Changes The detail accounting entries for AutoCreated Purchase Orders created in R12 is improved. Instead of “washing” the transaction back and forth through 46X051, the Commitment balance will be liquidated and any price/quantity change will impact Allotment Authority balances just for the delta amount.

26. Key Federal-Related SLA Process Changes Upward/Downward Inflation Overstated PYA accounts (e.g.4881), often due to various document modifications, but not true Up/Down adjustments The capability that SLA provides for transaction-driven Upward/Downward Adjustment entries is nice. However, there is currently not a seeded solution for mitigating/correcting PYA “Inflation”, other than through Unreserve/Rereserve PYA suppression on the same distribution_id.

27. FV Accounting Entry Journal Descriptions As desired, the end-state GL journal entries from Budget Distribution events (as well as others), can contain enhanced journal line description data which provides a quick glimpse of source transaction detail attributes.

28. Viewing FV SLA Accounting Entries Budget Distribution and Treasury Confirmation accounting entries can now be viewed from the subsidiary module, in addition to GL, via the SLA: User Main Menu available from Federal Financial application responsibilities.

29. SLA: Multiple Cash Accounts Federal Multiple Cash Accounts and Treasury Confirmation Enhancement MOS Doc ID 1314160.1 Oracle’s SLA solution for using different cash accounts is tied to different bank account CCIDs setup. There are other methods for this if desired w/SLA, but these CCIDs must now be setup.

30. SLA: AR Transaction Category Mapping The seeded FV SLA AR design is dependent on the AR Transaction Category Mapping.

31. Managing FV SLA Changes in R12 • Moving forward to uptake new enhancements is usually always a good thing, but due to the sensitivity and complexity of the R12 Federal SLA functionality, we must be a bit more careful with patching at this point in R12 than we might have been w/11i recently. • Oracle makes mention of this issue in the patch 9000001 readme: • "If customer has customized the following AADs, they might need to revisit the below AADs to make sure they have uptaken their Customized JLT per the new changes." • …however if you ask me, it should be in bold

32. Managing FV SLA Changes in R12 • Try to make sure your agency (& supporting contractors if applicable) get to know what is really going on with SLA under the hood. This will help you be able to identify what kind of patches could impact your SLA configuration and assess any level of rework required. • Insulate your environment from changes to JLTs and ADRs by creating agency-specific versions. • Although not easy, if you’re in the process of an R12 upgrade project, try to baseline your SLA configurations & objects as soon as possible, to mitigate re-work from additional changes that could come about from future SLA-related patches (rework would likely include reconfiguration time & re-testing). Having to restart a R12 upgrade testing cycle due to a bunch of SLA Accounting updates won’t make our R12 Upgrade Project Managers too happy. • Once stable/in production, keep an eye out continually for patches that could throw your SLA rules for a loop, especially changes to the FV_SLA% packages.

33. Managing FV SLA Changes in R12

34. Managing FV SLA Changes in R12

35. Managing FV SLA Changes in R12

36. R12 Federal Payment Processing • With the new architecture of the core EBS Payment Processing solution in R12, Federal Payment Processing design has gone under wholesale change. • Key changes include: • The introduction of the IBY Oracle Payments Manager GUI • IBY Utilization of new XML and BI Publisher technology for payment file creation • Introduction of new Payment Validation processes and edits • Utilization of R12 Payment Reason Codes • Any custom payment formats developed or tweaked in 11i will need to be recreated using the R12 Oracle IBY/BI Publisher approach.

37. R12 Federal Payment Processing • The new R12 Payments GUI is significantly different for creating Payment Process Requests (PPRs), i.e. the next generation of 11i Payment Batches

38. R12 Federal Payment Processing • The Payment Formatting structure of a PPR is driven by the Payment Process Profile tagged to the PPR Instruction.

39. R12 Federal Payment Processing Design • Payment Process Profile definitions are accessible via the Payment Administrator functionality.

40. R12 Federal Payment Processing Design • Many standard US Treasury Federal Payment Formats are provided as seeded Payment Process Profile definitions in R12. • Agency-specific Payment Process Profiles may need to be created to meet other requirements, e.g. ITS, Clearing, DoD Disbursing system integration, etc.

41. R12 Federal Payment Processing Design • Payment Process Profile definitions are linked to IBY Payment Format records.

42. R12 Federal Payment Processing Design • IBY Payment Formats are fundamentally comprised of BI Publisher Data Definitions and Templates.

43. R12 Federal Payment Processing Design • This process flow does a great job of illustrating the new R12 IBY Payment Output flow. • The Fund Disbursement XML extract is used as the baseline for all outbound payment formats, presented differently as required by the applicable eText BI Publisher Templates. • Format Customization in Oracle Payments for Oracle Applications Release 12 [ID 787467.1]

44. R12 Federal Payment Processing Design • Each R12 BI Publisher Payment format includes a mapping to the Funds Disbursement Extract as the Data Definition used, along with the eText BI Publisher template.

45. R12 Federal Payment Processing Design The eText BI Publisher Templates are structured similar to a Interface File Specification layout and provides the capability for applying additional functions to the XML data. A key reference on eText BI Publisher Templates is: Oracle XML Publisher Report Designer’s Guide, Chapter 4: Creating an eText Template

46. R12 Federal Payment Processing Design • For agencies creating payment files for systems beyond the FV seeded list, there are multiple methods and components to address such requirements. • If all the data required for outbound file creation is provided within the seeded Funds Disbursement XML Extract, then the requirement can likely be met through 1) creating a custom BI Pub Payment Format Template, registering the 2) Payment Format and 3) Payment Profile. • If additional data is required beyond what is provided in the seeded Funds Disbursement XML Extract, then the IBY_FD_EXTRACT_EXT_PUB package can be used to extend the extract creation to include additional XML data elements as required. • Key MOS Note: Format Customization in Oracle Payments for Oracle Applications Release 12 [ID 787467.1]

47. R12 Federal Payment Validations R12 Payments provides new functionality of Payment Validation processes. For Federal, a FV Payment validation process is delivered for seeded formats. Custom validations can also be added. These seeded FV validation functions are in the iby_payment_format_val_pvt package. In 11i, a number of these validations existed in the Payment Format Code, but some have changed. Example: the TAS_VALIDATION function disallows the use of dashes in FV Treasury Symbols any further.

48. R12 Federal Payment Reason Codes The R12 design to support required FV Payment processing codes eliminates the 11i Paygroup->ECS Payment Type mapping and replaces it with Invoice Payment Reason Codes. Payment Reason codes are required on all PPD+ Payments and some BD NCR Check Payments.

49. Creating FV Budget Dists with Web ADI The new R12 Desktop Integration Framework supports the capability to create a Web ADI Integrator to load the fv_be_interface table w/Budget Distribution details from an Excel ADI worksheet.

50. Creating FV Budget Dists with Web ADI