2. Proactive Best Practices for Payables and Payments
Oracle E-Business Suite R12
Andrew Lumpe & Stephen Horgan
Oracle Proactive Support Services
October 01, 2014
Session: CON8479
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

4. Introductions
Andrew Lumpe– Senior Principal Technical Support Engineer
24 years Oracle E-Business Suite Experience
Financials, Projects
Stephen Horgan– Senior Principal Technical Support Engineer
15 years Oracle E-Business Suite Experience
Financials, Payables

5. Agenda The challenges we face The tools at our disposal1
The challenges we face
The tools at our disposal
Master GDF Diagnostic
Analyzers
Proactive Patching
Recommended Patch Collections
Proactive Patching Resources
Additional “Get Proactive” resources
Q & A 2 3 4 5

6. The Challenges We Face

7. The Challenges We Face
Framing the Problem
R12 introduced a new accounting engine, tax engine, payments engine, supplier data model, MOAC, and many other enhancements
The application is significantly more flexible and more complex
Processing and accounting are more prone to (and sensitive to) data integrity or configuration issues
Data anomalies or setup issues can affect your ability to perform key functions, such as:
Validate invoices
Create accounting
Calculate tax
Perform funds checks
Process payments
Etc.

8. The Tools We Possess
The MGD & Analyzers

9. The Master GDF Diagnostic
Description
Recommended Usage
Submitting
Use Case
The Tools at our Disposal

10. The Master GDF Diagnostic (MGD)
What is the Master GDF Diagnostic?
A tool which incorporates the data signatures from all released Generic Data Fixes (or GDF’s) and additional data-fixes which are not yet released as GDF’s
Instances of data issues are detected on your system if they exist
Known solutions for issues identified are provided
A core triaging tool used by development and support.

11. The Master GDF Diagnostic (MGD)
Features
Can be run as a concurrent process
You can give access to functional users in your organization
Incorporate into regular business processes
Can scan transactions reactively or proactively.
A single problem transaction
All transactions within a range of dates

12. The Master GDF Diagnostic (MGD)
Features
Self contained
Simple installation and update without dependencies
Contains data signatures for invoices, payments, accounting, suppliers, and EBTax data
351 distinct data signatures checked, 225 from generic data fixes (GDF’s)
Constantly being updated with the latest validations

13. MGD: Recommended Usage
Periodically download the latest version from Doc ID
It will let you know when it is likely out of date
Install as a Concurrent Process
Defining the concurrent process is quick and easy (Doc ID )

14. MGD: Recommended Usage
Run proactively at intervals during the month along with Create Accounting
Create and interface accounting transactions in small batches throughout the month
Validate data and resolve issues as they occur

15. MGD: Submitting Single Transaction Mode Date Range Mode
Single Transaction (Reactive) vs Date Range (Proactive) Modes
Single Transaction Mode
The process is run for a single check, invoice, and/or supplier
Use when specific problem transactions are already identified
Will also validate closely related transactions
Invoices paid by the check, or prepays applied to the invoice
Date Range Mode
Use proactively to identify potential issues throughout the month
Use when the transaction causing a process failure cannot be identified
Restrictions
Only dates in open periods, and only GDF signatures

16. Submit as a Concurrent Process or via SQL *Plus
MGD: Submitting
Single Transaction (Reactive) Mode
SQL*Plus
Concurrent Process

17. MGD: Use Case Example – Closing a Period
Period Close Exception Report shows an invoice validation event not transferred to GL (even though all accounting and transfer processes have been run)

18. MGD: Use Case
Example – Closing a Period
Review the output of the single transaction (run for the problem invoice) (DEMO)
Apply the GDF and root cause patches identified
Review the output for the invoice after the patch was applied.
Re-run processes and try to close the period.

19. The GDF’s (Generic Data Fixes)
Questions about GDFs?
Check out:
GDF FAQ Doc ID
or the Payables Community
Each GDF is well tested and designed to be very robust
They are 100% supported by Oracle Development
They are published solutions: you can use them whenever you find an issue.
There is no need to confirm with Oracle, or open an SR before applying them.
They will not change application code
They will not auto-run the data fix when the patch is applied
Some will run the select automatically, others will not – review the README file for details
They give you control to review and select which transactions to fix
There is no need for down time ► either to apply the patch or run the fix

20. The Analyzers
Description
Features
Use Case
The Tools at our Disposal

21. E-Business Suite Analyzers
Use these scripts as part of your production maintenance program. Easy-to-read result set provides recommendations, solutions, and early warnings
432.1
 E-Business Suite Analyzers
 Financial Analyzers
 Manufacturing Analyzers
 Human Capital Management

22. E-Business Suite Analyzers
Common Features
Checks for recommended patches
Checks for common setup issues
Checks for known data integrity issues
Offers recommendations and solutions
Easy to read HTML output
Dynamic and easily updated
Run as a concurrent process
Run reactively or proactively
Self contained
No data created, updated or deleted

23. EBS Analyzers for Payables
Questions about Analyzers?
Check out:
Analyzer FAQ Doc ID
or the Payables Community
Available to help prevent/resolve Payables issues now!
R12: Master GDF Diagnostic (MGD) (Doc ID )
R12: Period Close Analyzer (Doc ID )
R12: Payables Trial Balance Analyzer (Doc ID )
R12: Oracle Payments (IBY) Funds Disbursement Analyzer (Doc ID )
R12: EBTax Setup and Data Integrity Analyzer (Doc ID )
R12: Internet Expenses Setup Analyzer (Doc ID )

24. Period Close Analyzer (Doc ID 1489381.1)
Description and Key Features
This diagnostic will identify period close issues and provides the corrective actions to resolve them. It compliments the Period Close Exception report.
Validation/Troubleshooting
Checks for standard Period Close exceptions
Checks for data integrity issues causing Period Close exceptions
Validates GL period open
Offers/explains sweep alternative
Proactive checks/Data Collection:
Critical patches that have not been applied
GL Ledger information
Operating Unit information
Period Status Information
Other data needed to expedite research if SR is needed.

25. Period Close Analyzer: Use Case
Example – Orphan Events (Other Exceptions)
The Period Close Exception report shows “Other Exceptions” that are preventing period close. The report shows the suggested corrective action for “Other exceptions” is to log an SR.

26. Trial Balance Analyzer (Doc ID 1553507.1)
Description and Key Features
This diagnostic will allow you to identify transactions which cause trial balance (APTB) reconciliation issues. It helps you identify the issues and provides corrective actions to resolve them.
Validation/Troubleshooting
Invoice(s) missing/incorrectly reported (Transaction Mode)
AP and GL reconciliation (Account and Date range Modes)
Impact of undo (Undo Mode)
Proactive checks/Data Collection:
Critical patches that have not been applied
File versions of Trial Balance Code
Report Definition Data
Invoice/Payment transaction/accounting data needed to expedite research if SR is needed.

27. Trial Balance Analyzer: Use Case
Example – (Transaction Mode) Gl Transferred Data Missing From Trial Balance
The Trial Balance is missing an important large dollar invoice.

28. Oracle Payments (IBY) Funds Disbursement Analyzer (Doc ID 1587455.1)
Description and Key Features
Use this diagnostic proactively to prevent known issues in Oracle Payments funds disbursement flow as well as to collect data and troubleshoot payment process request (PPR) related issues.
Validation/Troubleshooting
Identify PPR related data corruption issues
Invoice not being selected by PPR
Validate BI Publisher configuration
Separate Remittance Advice failures
Validations of setup and database conditions (Max extents and space issues)
Proactive checks/Data Collection:
Critical patches that have not been applied
Payment related invalid objects
Check of XML template version
XML Runtime settings
Output Post Processor related settings
PPR and invoice related data needed to expedite research if SR is needed.

29. Payments Analyzer: Use Case
Example – PPR was terminated but corresponding invoices were not released
A PPR was terminated, and the new PPR submitted is not selecting the invoices originally selected by the terminated PPR.

30. Proactive Patching Preventing Issues

31. Proactive Patching
Recommended Patch Collections
Proactive Patching Resources
Preventing Issues with Proactive Patching

32. Proactive Patching
Recommended Patch Collection (RPC)
Each RPC is a collection of recommended patches created with the following
goals in mind:
Stability: Address issues that occur often and interfere with the normal completion of crucial business processes
Root Cause Fixes: Deliver a root cause fix for data corruption issues
Compact: Bundles a large number of important corrections while keeping the file footprint as small as possible
Reliability: Reliable code with multiple customer downloads and comprehensive testing by QA, Support and Proactive Support

33. Proactive Patching Resources
Recommended Patch Collection (RPC) (Doc ID )
Lists latest RPC for all financial products
Contains reference to each product specific document
Analyzers (Doc ID )
Apply the patches recommended by analyzers
Patch Wizard (Doc Id )
Use to identify recommended patches
Patching & Maintenance Advisor (Doc Id 313.1)
Use to create a proactive and reactive patching plan

34. Additional Get Proactive Resources
432.1
Additional Get Proactive Resources

35. Spotlight on some key offerings
Patching and Upgrading
How to find EBS patches ( )
Advisors and Patch Wizard updated for 12.2
12.2 Info center ( )
Pre-Install patches ( )
EBS Support Analyzers
31 EBS Analyzers
Diagnose and Maintain
Read Only
Enable Functional Users
SR Guided Resolutions
SR create decision tree
Targeted solutions
Expedite resolution
WIP: Simplify template selection and routing
Future: SR File Uploads and Analysis
Step 1 – Automated file handling and validation
Step 2 – Analyze data, find problem
Step 3 – Match to solutions

37. Stay Informed
Follow Oracle Premier Support through social media channels to hear the latest on Proactive Offerings!
Blog
Newsletters – now news consolidations from Blog articles
Twitter | Oracle_EBS | myoraclesupport
My Oracle Support Community
Facebook
Participate in Advisor Webcasts and hear from Oracle Premier Support subject-matter experts who will offer methods and solutions to help you avoid potential pitfalls
Expand your existing knowledge with E-Business Suite accreditation. ( ). A guided learning path of best practices, product-based use cases and recommendations from subject-matter experts.

38. Show your “Get Proactive” sticker and receive a gift!
Support Stars Bar
Talk with experts
Learn what offerings are available for you!
Located in Moscone West Exhibit Hall
#3461 – back of the hall
Show your “Get Proactive” sticker and receive a gift!

39. Q & A

40. Thank you!