Thursday Apr 10, 2014

Should You Apply The R12.1.3+ EBS Wide RPC or Wait for a Payables Specific RPC?

Oracle E-Business Suite Release 12.1.3+ Recommended Patch Collection is Available!

The last RPC for Oracle Payables was released in September 2013 (Doc ID 1397581.1) and usually at this time of year we see development release the next RPC for Payables.   However, this year there will not be a new Payables RPC released until much later in the year.

Instead of a March 2014 Payables RPC development have released the 12.1.3+ RPC that is EBS wide.  This patch includes ALL the recommended patches along with their dependencies. 


If you are running R12.1.3 but have not yet applied the September 2013 RPCs for Payables then you can instead choose to apply this latest R12.1.3+ patch which includes all the RPCs for Payables and the companion RPCs for Workflow, PCard and iSupplier in addition to Cash Management and EBTax RPCs.  

Applying this patch in a single downtime patching window saves effort and time, rather than applying each recommended patch individually.


For more information on the R12.1.3+  RPC please refer to Doc ID 1638535.1 - Oracle E-Business Suite Release 12.1.3+ Recommended Patch Collection 1 (RPC1) 

Note: Before upgrading to Oracle E-Business Suite Release 12.1.3 and applying 12.1.3+ E-Business Suite RPC1, refer to Doc ID 761570.1 - Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1 Upgrade - and ensure that all patches for your specific database release are applied to your environment. 

Tuesday Mar 25, 2014

Understanding Encumbrance Accounting in R12

Encumbrance Accounting has always been one of those tricky areas to understand and it is often quite complex and time consuming to resolve issues that arise.  Having a detailed understanding of how Encumbrance Accounting works in General Ledger, Payables and Purchasing will get you on the right track faster.

Recently a new document was created that attempts to pull together all the information that relates to Encumbrance Accounting so that you can understand everything from what it is, to how the applications are setup to use it, to using diagnostic tools and checking patch levels when something doesn't work just how you expect it to.

Please review R12: MASTER TROUBLESHOOTING GUIDE (MTG) for Encumbrance Accounting Issues in Oracle PO and AP (Doc ID 1578275.1) available on MyOracleSupport which discusses the following topics:  

  • What is Encumbrance Accounting
  • How does Encumbrance Accounting work in Oracle?
  • Funds Reservation Statuses on PO Documents
  • Required Setups (GL, AP, PO)
  • Seeded Oracle Reports for Encumbrance Accounting
  • Recommended Patches
  • Diagnostic Tools 
  • Hot Topics
  • More Resources 

One of the additional resources referenced within the above document is R12 Encumbrances Accounting Bulletin (Doc ID 1583781.1).  This interactive document allows you to filter the knowledge based on a topic of choice and includes Encumbrance Transactions for both Accrue on Receipt and at Period End and shows you the transactions you would see and the values of DR and CR that would be inserted into the XLA tables at the various stages.  

Together these two fantastic documents should enlighten the reader and provide a detailed understanding of Encumbrance Accounting in Oracle Applications. 

Wednesday Mar 12, 2014

Meet the Payables Period Close Analyzer!

See Doc ID 1489381.1 in My Oracle Support to learn all about our latest analyzer script "ap_pclose_detect_pkg.sql".  This script was created just for EBS: Payables, and is designed to find transactions that may be blocking the period close process from closing normally, and offers corrective actions you can take to resolve the problems yourself -- eliminating the need to contact Oracle Support for help! 

Below is an example of the HTML output produced by the Payables Period Close Analyzer (PCA):

    RESOURCES

To learn more about Global Data Fixes (GDFs) and what GDFs are available for Oracle Payables, along with information about the Period Close process in Oracle Payables, and access to other Payables PCA users, see the following:

R12: What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables? [VIDEO] DocID 874903.1

R12: Master GDF Diagnostic (MGD) to Validate Data Related to Invoices, Payments, Accounting, Suppliers and EBTax [VIDEO] DocID 1360390.1

Best Practices for E-Business Suite Payables Period Close (one hour webcast)

The "Period Close Analyzer" thread on the Payables Community


Tuesday Mar 04, 2014

Logging a Cash Managment SR? New Problem Types Available in MOS!

Cash Management SR Options Have Changed!

You might recall in an earlier blog entry that we changed the options you have when logging a Payables SR in MyOracleSupport to try and help you get your SRs to the right engineers - first time.  We hope you are finding the new options beneficial and getting your issues resolved faster.  

The good news is that we have now extended this change to include Cash Management SRs.

Next time you create an SR for Cash Management you will notice different options available to you to ensure you get shown the most appropriate content for your problem area.  If the recommended solutions don't resolve your issue, then we ensure we ask relevant questions that will help the support engineer get to the root of your issue faster. We have also revised the diagnotics that we will request from you to further aid the resolution of your issue.

The new options available are structured as follows:

Patch Application Issues For E-Business Patching Community

Reconciliation/Clearing and Accounting

Receipt Issues

Payment Issues

Accounting Issues

Reconciliation and Clearing

Bank Statement

Accounting

Load/Import

Bank Balances

Internal Bank Accounts

Bank Account Transactions

Bank Account Transfers

Sweep

Cashflows

Report Issues

GL Reconciliation Report

Other Reports

Cash Pools/Forecasting/Positioning

Cash Pools

Cash Forecasting

Cash Positioning

Localization Issues

Oracle Financials for EMEA

Oracle Financials for the Americas

Oracle Financials for Asia/Pacific

Oracle Financials for India

Performance Issues

Other Cash Management Issues

We hope these new options are useful and help you log your problem with the correct team - the first time.

Let us know what other topics you want to hear about on the Payables Blog by updating the thread on the Payables Community that was created for your feedback.  

Thursday Feb 20, 2014

Troubleshooting Assistant Now Available for Invoice Validation!

Proactive Support has created another great tool for you to use when facing Invoice Validation issues!

There are  many Troubleshooting Assistants available to help customers find solutions to their issues faster but we have just added another assistant for Invoice Validation because customers continue to have problems in this area and we wanted a quick way to help them find their answers.

Check out the new Troubleshooting Assistant: Oracle Payables (AP) Invoice Validation (Doc ID 1616563.2).

You will also see this tool when raising an SR for validation issues and you should defintely give it a try as it's been created from common issues and takes you directly to the known solutions.

You can interact with the tool to locate specific common error messages, review by symptoms or dig right into the issues we are aware of with the online validation or batch processing sections.  There is even some EBTax common problems included.

We also address corruption in the assistant, because often corruption can be the cause of your problem.  Why waste time trying to figure out what's wrong when you can run a simple request and find out?  

R12: Master GDF Diagnostic (MGD) to Validate Data Related to Invoices, Payments, Accounting, Suppliers and EBTax [VIDEO] (Doc ID 1360390.1

The MGD (Master Generic Data Fix) concurrent request can be ran for a date range or for a single transaction and the output will tell you exactly what is wrong with that transaction and tell you what you need to do to fix it. This is the reason why under the data corruption topic we refer to the MGD as your solution!  

It should ALWAYS be the first thing you check any time you have a payables issue so if you aren't aware of it, please read up on Payables #1 problem solving document or watch the video and get your data corruption issues fixed and prevent those headaches at month end.

References

EBS: Assistant (Search Helper) Index (Doc ID 1501724.1

So next time you have an Invoice Validation problem give the Troubleshooting Assistant a try and you might be surprised how easy it was to resolve! 

Wednesday Feb 12, 2014

ORAchk Health Checks for the Oracle Stack

ORAchk includes EXAchk’s functionality and replaces the popular RACcheck tool, extending the coverage based on prioritization of top issues reported by users, to proactively scan for known problems within:

  • E-Business Suite Financials Accounts Payables
  • Oracle Database
  • Sun Systems

ORAchk features:

  • Proactively scans for the most impactful known problems across your entire Engineered System as well as various layers of your stack
  • Simplifies and streamlines how to investigate and analyze which known issues present a risk to you
  • Lightweight tool runs within your environment; no data will be sent to Oracle
  • High level reports show your system health risks with the ability to drill down into specific problems and understand their resolutions
  • Can be configured to send email notifications when it detects problems
  • Collection Manager, a companion Application Express web app, provides a single dashboard view of collections across your entire enterprise

ORAchk will expand in the future with more high impact checks in existing and additional product areas. If you have particular checks or product areas you would like to see covered, please post suggestions in the ORAchk community thread accessed from the support tab on the below document.

For more details about ORAchk see Document 1268927.1

Monday Feb 10, 2014

New Form to Identify Unexpected Tax Errors For Transactions and Ability To Rectify Through Concurrent Program!

Development have created a new form that will allow users with Unexpected Tax Errors to be able to run, via the familiar user interface, a diagnostic to determine the problem.  

This new functionality, which converts data detection and data fix scripts into packaged procedures, is made available with the application of patch 18108467:R12.ZX.B

The new form contains access to the following diagnostic programs:

• Transaction Tax Data Diagnostic
• Populate Legal Establishment
• Synchronize Summarization Column Values
• Rectify Tax Distributions
• Populate Regime to Rate Details
• Populate Recovery Rate Details
• Remove Orphan Tax Lines
• Remove Orphan Transaction Lines
• Create Missing Transaction Lines
• Create Missing Tax Distributions for Purchase Orders
• Update Configuration Owner
• Upgrade Missing Transaction Tax Data
• Set Migrated Tax Lines as Overridden
• Synchronize Migrated Tax Distributions Amounts
• Synchronize Tax Repository

Users can run the diagnostic detection process for a specific date range or for a specific transaction and they can run in either in "Analyze" or "Analyze and Fix" Mode.

The output can be viewed as a concurrent request output file and will make it much easier for end users to quickly run diagnostics on their erroneous tax transactions.


Note: It is recommended that you first run "Analyze" Mode and check the Data and then run in "Analyze and Fix" mode to rectify the issue.


All R12.1 customers should use this form when facing 'Unexpected Tax Errors' and submit all the data detection diagnostics on the transaction data.  The output can then be reviewed to determine recommendations and steps to resolve.


For full details please review the following My Oracle Support document:

R12.1.X: Tax Diagnostic Framework (Doc ID 1621617.1)

Thursday Feb 06, 2014

Webcast: Using The New Trial Balance Helper (TBH) To Troubleshoot Payables Trial Balance (APTB) Issues

ADVISOR WEBCAST: Using The New Trial Balance Helper (TBH) To Troubleshoot Payables Trial Balance (APTB) Issues

Webcast.jpg

This one-hour webcast shows you:

- Trial Balance Overview
- Troubleshooting Accounts Payables Trial Balance (APTB)
- Using the Trial Balance Helper (APTB) diagnostics for smoother reconciliation


This session will help customers to understand and use the TBH and generic troubleshooting tips on APTB for smoother reconciliation                     

Topics will include:

  • The proactive approach in reconciling AP with the effective usage of the diagnostics available

A short, live demonstration (only if applicable) and question and answer period will be included.

Oracle Advisor Webcasts are dedicated to building your awareness around our products and services. This session does not replace offerings from Oracle Global Support Services.

WebEx Conference Details:

Topic: Using The New Trial Balance Helper (TBH) To Troubleshoot Payables Trial Balance (APTB) Issues

Date and Time:

Thursday, March 13, 2014 3:30 am, Mountain Daylight Time (Denver, GMT-06:00)
Thursday, March 13, 2014 3:00 pm, India Time (Mumbai, GMT+05:30)

Thursday, March 13, 2014 5:30 am, Eastern Daylight Time (New York, GMT-04:00)

Thursday, March 13, 2014 9:30 am, GMT Time (London, GMT)


Event number: 596 428 540

REGISTER.jpg


For more details and how to register see Doc ID 1620914.1 - Using The New Trial Balance Helper (TBH) To Troubleshoot Payables Trial Balance (APTB) Issues.

Tuesday Feb 04, 2014

ER Implemented - New Supplier Update API's Supported in R12 Oracle Payables!

Well we have great news for you! 

In 11i there were API's (Update_Vendor, Update_Vendor_Site and Update_Vendor_Contact) but they were not supported in R12 due to integration with Multiple product teams. The reason being was that the entities Supplier, Sites and Contacts had representations in multiple products like TCA, IBY, ZX etc and all these representations needed to be in sync.

However, most of our customers have huge volumes of supplier data which they need to be able to control programmatically so the fact that they no longer had access to these API's was frustrating.

It was requested through Enhancement Request Bug 17575099: ENHANCEMENT FOR SUPPORT OF SUPPLIER UPDATE APIS that Oracle Payables provides API's for updating Supplier / Supplier Sites / Supplier Contacts in AP_VENDOR_PUB_PKG in R12.

Well, this functionality is now available and the following new APIs had been created: 

                      - Update_Vendor_Public
                      - Update_Vendor_Site_Public
                      - Update_Vendor_Contact_Public

*** Note: These are the only procedures supported to update suppliers, sites or contacts.

We are sure that this ER being implemented will be welcome news for many.  Enjoy! 


To download the document with additional information about these new procedures please review Doc ID 1618099.1 - New Supplier Update API's in Oracle Payables


Further Information:

R12: What are New Supplier Related Tables/Packages/Programs. APIs Supportability (Doc ID 812918.1


Picture Get Proactive

Tuesday Jan 28, 2014

Logging an SR for Payables? Choose The Correct Problem Type For Faster Resolution

Did you know that you can affect how your SR is routed based on the Problem Type you choose in My Oracle Support?

The initial routing of your SR to an engineer is all dependent on how you choose to classify your issue.  If you don't understand the problem type options and choose the incorrect one, your SR will still get routed to the correct team but it will go the scenic route - around the houses instead of as the crow flies!

Choosing the best problem type means it's routed to the correct group working those issues first time which means the engineers with the skill set to handle your issue or question will get working on it right away.  If it goes to a different team, they will review the issue and decide which is the appropriate group for that issue and transfer that SR.  So speed up the resolution of your issue by getting it to the right team - first time.


Screenshot


When you are in MOS and you have chosen Oracle Payables as a product, the problem type drop down box (as shown above) contains the following options:

1099 US Tax Reporting
Accounting Issues and Reporting
Payables Payments Issues and Reporting
Invoice Processing and Reporting
Supplier Issues and Reporting
EBTax (Payables) Issues e.g. Tax related processing and calculation
Internet Expense/Procurement Card Issues
Localization Issues
Technical Issues
Patch Application Issues
Other Payables Issues 

You might be unsure what to select if you can't account an invoice or your trial balance is causing you concern.  What about a question about Transfer to GL or Period Close? Well that would always be an accounting issue because the problem is with accounting code.

What about if you have a payment workbench problem, payment reports are wrong, users can't print a check or you have questions about AP/AR Netting? What about PPR problems? Those are all payments issues.  

If you cannot enter an invoice or are struggling to discard an invoice line, have holds you don't understand, cannot match an invoice or mass additions isn't picking up certain invoice distributions and you don't understand why, then those would be an invoices issue. The Invoices team also handles prepayment questions and helps troubleshoot report issues where figures are not as expected. Invoice Approval Workflow is also an invoices area.  Generally, if it's related to processing of an invoice but not accounting or paying an invoice then it would be an Invoices issue.

1099 issues have their own option in the drop down menu as specialist knowledge of 1099 US tax reporting is required.  

Supplier setup, merge or import problems, supplier report concerns and even Supplier Bank Accounts all fall under the suppliers category.

EBTax (Payables) issues is a tricky one, because you might think an error when validating an invoice or a problem trying to match to a PO would be invoices, but if that error relates to the tax distributions or the error message is EBTax related those issues would not be handled by the Invoices team but by the EBTax experts. If the EBTax team decides it's not specifically related to EBTax code they will transfer the issue as appropriate but starting with the EBTax experts is your best bet due to the complexity of tax setup.

The technical team handle anything performance related or issues with invalid objects, locks, flexfield setup, document sequencing and upgrade issues..

If you are using localizations and the piece of functionality you have an issue or question with is a localization specific question or the error indicates the code failing is localization code then that should always go to the localization team for review.

All patch issues are handled by the patching community so that should be easy enough to know when to use that option.

Other Payables Issues is a catch all bucket which should only be used if you cannot find another topic that your issue would fall into.  It will need to be reviewed and categorized and the receiving engineer will then transfer the ownership of the SR to the team they feel would be best equipped to handle that issue.  This may be the correct team but it could take a couple of transfers to find the correct engineer.  Since there is a delay in this review and reassign process, it stands to reason that initial contact with an engineer with the correct skillset will take longer, hence the reason to avoid this option if at all possible.


We hope understanding the Problem Type structure will help you get your SR to the right team quicker but there are additional benefits in taking a minute to choose the correct template:

1) The knowledge documents that you will be shown during the SR logging process are specifically selected depending on the problem type you choose as they are the documents that other customers have found the most useful, when having problems in that area. For example, seeing our Invoice Matching troubleshooting assistant or a technical white paper explaining a new piece of functionality might give you a good chance of finding your answer before the SR reaches an engineer!  

2) If the suggested documents don't help you resolve your problem then at least the questions you are asked in the next step of the SR logging process are specific to that problem type and providing these answers will allow the receiving engineer to get a jump start on understanding your problem.

3) We also request customers to upload diagnostic files that will help resolution so choosing the correct problem type means you are asked for the correct type of diagnostic information.  No-one wants to waste time generating and uploading irrelevant diagnostic files.


If you are unsure which bucket to put your problem, please take a few minutes to review the sub-menus under each option and ensure you understand the types of issues handled by that team before categorizing your issue as 'something else' by using the Other Payables Issues option.


Tuesday Jan 21, 2014

Swiss (CHE) Tax Registration Number Change Notice

Replacement VAT number six figure identification number of firms (FDI) with the VAT extension

The federal law on business identification number has changed with effect from 1 Jan 2014.  The old registration number format was 8 characters but the new format supports 19-20 characters. 

Old Behavior

The current VAT number validation format is CH + 6 digits (the six digits after the prefix should be numeric). Example: CH123456. Swiss companies can continue to use the current VAT number format until the end of 2013.

New Behavior

Effective from January 2014, there are changes in the validation of Tax Registration Number. The new VAT number validation is formatted as CHE + nine numeric positions + extension. Example: CHE-123.456.789 MWST.

The following validation is implemented.

  • CHE - is a fixed value. It represents the country code.
  • to separate the country code and the tax number portion.
  • 123.456.789 - nine numeric positions, separated by periods.
  • (Blank) - blank position that separates the numeric portion and the extension portion.
  • XXXX  : Depending on the specific part of Switzerland the company address belongs to. The three possible extensions are: MWST, TVA or IVA.

The total length of the new VAT number, therefore, can be 19 or 20 digits.

Recommendation

a) Apply Patch 15964400 as detailed in Doc ID 1521534.1 - New Swiss (CHE) Tax Registration Number

and

b) Enter/update existing tax registration number as per new format before January 2014 to avoid any user interface, reporting or data issue. The tax registration number as per old format will not be valid effective from January 2014.

You can enter the registration number using multiple navigations but the most common interface is: Tax Manager > Parties: Party Tax Profiles > Tax Registrations

Change


References

For full details on this change in legislation, please review the Federal Administration website.

Thursday Jan 16, 2014

Mass Additions Create Giving You Headaches? New Troubleshooting Assistant Available!

Don't Struggle Interfacing Invoice Distribution Lines from Payables To Fixed Assets - Help Is Available!

Mass Additions Create (APMACR) is the process by which Oracle Payables Invoice Distribution Lines are checked for eligibility and they if meet the critiera, they are inserted into the FA Mass Additions table as Mass Addition Lines.  

Oracle Assets users then prepare those Mass Addition Lines, by populating additional information, and run Post Mass Additions (FAMAPT) to convert that Mass Addition into an Asset.

Capital Project Related Invoice Distribution Lines are treated a little differently as they have to firstly interface from Oracle Payables into Oracle Projects before Oracle Projects interfaces them into Fixed Assets.  However, Create Mass Additions still examines project related invoice distribution lines and flags them as Capital Project related so that the relevant Projects concurrent programs can process them.  

For more information on Interfacing Project Related Invoice  Distributions to Oracle Assets Via Oracle Projects please review Doc ID 866310.1 - PAXCPGAL & PAXCPCAL - What Are The Steps to Generate Asset Lines and Interface Them to Oracle Fixed Assets?

What Help Is Available? 

It's very common for Payables users to fail to understand why their Invoice Distribution Lines didn't get selected by APMACR but the following documents should help you understand and resolve your issues.

1) We have the Mass Additions Diagnostics that have been around for a while:

These diagnostics allow you to enter a responsibility, operating unit, GL Date, Invoice ID and Asset Book and the report will examine the conditions required for successful interface to Mass Additions and it will explain why the line didn't meet the conditions. 

The screenshot below is taken from a sample output and it shows the invoice distribution didn't interface because the account used on the invoice distribution is not defined as an Asset or CIP Clearing account in any category for the asset book.  

Output

2) We have White Papers, Troubleshooting Guides and Functional Overviews to help explain this process in detail:

  • R12: Master Note: APMACR - Mass Additions Create Program - Functional Overview (Doc ID 1321002.1)
  • Understanding Mass Additions Create (APMACR) and Troubleshooting from FA Perspective (Doc ID 1070597.1)
  • White Paper on Mass Additions Create Process in R12 (Doc ID 567690.1)


3) If you are unsure what you should read to help you resolve your Mass Additions Create issues, then look no further than a Troubleshooting Assistant

  • Troubleshooting Assistant: Create Mass Additions From Payables (AP) to Fixed Assets (FA) (Doc ID 1609542.2)

 This document was created to help you quickly locate the relevant document that will explain your issue and help you interface your invoice distribution lines to Oracle Assets.

Screenshot1

Screenshot2

4) If you are still unsure, why not use the Payables Community which is there for you to use to post your questions and enter into discussions with Oracle and other customers using Oracle Payables.

Monday Jan 13, 2014

Webcast: Best Practices for Fixing Known Data Corruptions In Payables

Webcast.jpg

ADVISOR WEBCAST: Best Practices for Fixing Known Data Corruptions In Payables

Date:  January 23, 2014 at 2:30 am, Mountain Standard Time (Denver, GMT-07:00), 4:30 am, Eastern Standard Time (New York, GMT-05:00), 10:00 am MT, 9:30 am, GMT Time (London, GMT)

This one-hour webcast shows you how to use GDF Diagnostic (MGD) to Validate Data Related to Invoices, Payments, Accounting, Suppliers and EBTax . This will cover steps to run Data validation report, get the output files, understanding output generated and taking corrective steps. This will also include recommendation for self service of GDF. Also include how to run GDF's to fix known corruptions.

Topics will include:

  • Proactive approach in fixing know corruption
  • Effective usage of available diagnostics

REGISTER.jpg


For more details and how to register see Doc ID 1607812.1.

Wednesday Jan 01, 2014

What Is So Special About The Payables #1 Document - The Master GDF Script?

So by now you know that our #1 document of 2013 was the Master Generic Data Fix script, otherwise known as the MGD.  If you are already familiar with our MGD then great, but if you aren't sure what it is or you are unclear on when and how you use this fantastic script, then read on...


What is the MGD?

Doc ID 1360390.1 - R12: Master GDF Diagnostic (MGD) to Validate Data Related to Invoices, Payments, Accounting, Suppliers and EBTax [VIDEO] was created because a significant amount of data corruption had been reported by customers and we needed a way to quickly identify all transactions that were affected so we could:

a ) fix the corrupt data

b) fix the code to prevent future corruption


Doc ID 1360390.1 also contains a link to watch the webcast video that fully explains the usage of this script and includes a demo of how it is used.  Just click on the video link as shown in the following screenshot:



This script may be safely run at any time.  It can be used in the following ways:

a) reactively - when you are experiencing errors when performing a particular action that is invoice, payment, or supplier related
or
b) proactively
- to scan all transactions in a date range or an operating unit and head off potential issues.  

The script will produce an HTML output of all known problems relating to the transactions you specify along with information on notes and/or data-fix patches which may already be available to resolve the data issues. 

No data is created, updated, or deleted by this script and it is fully supported by Oracle Development and Support.

You should always run this script prior to logging a Service Request when you suspect there is data corruption or if you simply want to proactively verify the data integrity of your transactions.

Want to give it a try?

1) Query Doc ID 1360390.1, and click the Download Now button to save the ap_gdf_detect_pkg.zip.  Unzip this and you will see this contains three files:
a) ap_gdf_detect_pkg.sql: the package definition file 
b) single_trx.sql: This script can be used to submit the validation procedure for a single transaction.
c) date_range.sql: This script will submit the validation procedure for a range of dates within specified operating units
2) Run ap_gdf_detect_pkg.sql as the APPS user to create the package definition.

3) Run the appropriate SQL file to submit the detection procedure:
a) In order to validate a single invoice, payment, or supplier run single_trx.sql which will prompt for an invoice id, check id, and supplier id.  You must supply at least one of these values, but you can any combination of two, or even all three.
or
b) To validate all invoices, payments, or suppliers in a date range for specified operating units, run date_range.sql  This script will prompt you for your date range, operating unit (or operating units), and the type of transactions to be validated.  Dates for the date range must fall in open periods.  To indicate more than one operating unit, separate values with a comma.  If operating unit is left blank the process will run for all operating units (though this is generally not recommended for performance reasons).  The transaction type specified should be either INVOICE, PAYMENT, SUPPLIER, or ALL to validate all three types.
3) The detection procedure will create an output file of the format AP-GDF-<timestamp>.html  and will indicate the location of this file and the log file.   Review this output and follow the instructions highlighted to resolve your corruption issues.

What if you aren't technical?  

Great news, the script can also be installed by the DBA as a concurrent program as detailed in Doc ID 1361255.1 so that monthly usage is simplified and functional users can run and alert the DBA if they find a problem.  The output doesn't require any SQL knowledge as the script provides a nicely formatted HTML output, highlighting any issues that were detected, and points the user to the solution document needed to resolve each issue detected.

Simple!  What are you waiting for? 

Still got questions?  

Please let us know by updating the Master GDF Diagnostic Thread in the Payables Community.



HAPPY NEW YEAR!!

Tuesday Dec 17, 2013

Payables Most Frequently Used Knowledge Content of 2013

So how was 2013 for you?  For the Payables Proactive team it was a busy year as we were working on all sorts of wonderful projects, trying to make life a little easier for you.  

Here’s a rundown of some of the major knowledge that we created or improved this year that has had the biggest impact on you.  You keep FINDING it, READING it and most importantly USING it to resolve your issues without the need to log a Service Request.

So what documents made it onto the 'Most Frequently Used Documents' list of 2013?  

The following list shows you the knowledge content that you, the reader, found in My Oracle Support over the last 12 months, ranked by the total number of hits.  Sorry, but there are no prizes for guessing which amazing script came in the #1 spot because, let's face it, that would just be far too easy...  

#1 - R12: Master GDF Diagnostic (MGD) to Validate Data Related to Invoices, Payments, Accounting, Suppliers and EBTax [VIDEO] [Doc ID 1360390.1]

When to use it? Monthly to identify known data integrity issues within your Payables application and learn exactly how to fix those issues – all without the need for a service request.  

#2 - Information Center: Using Oracle Payables [Doc ID 1417577.2]

When to use it?  When you want to quickly see an overview of all our KM content for a particular functional area of the product such as EBTax, Workflow or Prepayments information.

#3 - R12.1: Payables Recommended Patch Collection (AP RPC), Sep 2013 [Doc ID 1397581.1]

When to use it?   This is a one time application which will provide you with all the important fixes since the release of 12.1.3.  Many of these fixes affect Critical Business Processes such as Period Close and are observed as reoccurring very often in the Installed Base. 

#4 - Information Center: Oracle Payables Accounting R12 [Doc ID 1476284.2]

When to use it?  This is a sub-document that can also be accessed from our #2 document, and the use of it would be in the same way, selecting the accounting tab from the Using Payables Information Center brings you directly to this document which highlights the accounting documents that are most useful to you.

#5 - Troubleshooting Assistant: R12 Payables Prepayments (Search Helper) [Doc ID 1559751.2]

When to use it?  Anytime you have a prepayment question or issue and you want to find the solution fast.  This interactive assistant will guide you through to the solutions that resolved issues for others customers experiencing the same symptoms.

#6 - Information Center: Oracle Internet Expenses [Doc ID 1381228.2]

When to use it?  Anytime you want to learn more about OIE, or troubleshoot an issue.  This index of content is invaluable for fnding your way around the OIE content quickly and easily.

#7 - Troubleshooting Assistant: R12 Oracle Payables (AP) Accounting [Doc ID 1573154.2]

When to use it?  Like in #5, troubleshooting assistants are always useful when you have a specific issue, you know the error message or the symptoms that cause the problem and you are trying to quickly find the common solutions for that specific issue.

#8 - R12: Information Center: Troubleshooting Payments to Suppliers and Other Creditors using Oracle Payables (AP) and Oracle Payments (IBY) [Doc ID 1383396.2]

When to use it?  This information center is your central point of resource for all things related to supplier payments.  

#9 - Information Center: Oracle Payables for Suppliers [Doc ID 1363041.2]

When to use it?  This is your central resource for payables supplier issues ranging from issues with employee suppliers to general setup and usage of suppliers. A great resource to use when you have questions or errors related to suppliers.  

#10 - Troubleshooting Assistant: R12 Suppliers (Search Helper) [Doc ID 1410773.2]

When to use it?  Whether you have issues with merging a supplier or you are unable to import or update a supplier, this troubleshooting assistant has your answer.  

Note: Please bear in mind that these might be the top 10 documents that you found when searching on MOS but this is dependent on the volume of incoming searches, so this list is missing some amazing articles in the smaller functional areas.  

For a full listing of all the available Assistants (Search Helpers) please review EBS: Assistant (Search Helper) Index [Doc ID 1501724.1]

For a full listing of all the available Information Centers please review E-Business Suite Product Information Center Index [Doc ID 444.2]

Happy Holidays!

About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
5
6
12
13
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today