Thursday Jun 26, 2014

During R12.2.3 Upgrade QP_UTIL_PUB Is Invalid

Release 12.2.3 upgrade below pll files recompile failed.  The following Oracle Forms objects did not generate successfully:

QOTLNSVI.pll         OEXOEGWY.pll
QOTPRDTL.pll         OEXOEADJ.pll
OEXOEBSE.pll         OEXOEBSO.pll
OEXTRTYP.pll         OKSAUDET.pll
QOTLNDET.pll         OEXOEHDR.pll
QPXQPDEB.pll         OEXOELIN.pll

There is a documented workaround for those that are receiving this error in note:  During R12.2.3 Upgrade on Patch 17020683 the pll Recompile Failed Showing That Object APPS.QP_UTIL_PUB Is Invalid, Doc ID 1683318.1

For those that have not yet upgraded, please review the readme and pre-requisites for Patch 18977965 as a pre-install / pre-upgrade step.

Announcing RapidSR for Oracle Payables: Automated Troubleshooting (AT)

What's New?

Customers are now able to create an accounting SR, upload the Master GDF diagnostic, and have the system automatically analyze the MGD output and update the SR with a solution summary.  In most situations we anticipate this to be much faster than waiting for an engineer to pick up and process the SR.  We call it RapidSR because it is FAST!

This first automation phase involves AP Accounting issues and covers the following impact areas:

  • GL Transfer
  • Accounting Failure
  • Accounting Incorrect
  • Period Close
  • Sweep
  • Trial Balance

A valid MGD output is required for automation to work and the requirements are:

  • Minimum version required = 120.213 or above
  • The diagnostic must be run in a single transaction mode. 

Doc ID 1608498.1 - SRDC R12: Collect Validation Information for Data Related to Invoices, Payments, Accounting, Suppliers and EBTax provides the link to the latest version of the MGD.

How Do You Log An Automation SR?

Step 1) Simple, when logging your next SR for an Accounting problem, simply select the following problem type:

Accounting Issues and Reporting > Create Accounting Fails for Specific Invoice, Check or Vendor

Note: Sev1’s and OnDemand/Cloud SRs will not be automated even when choosing this option.

Step 2) The Automated Troubleshooting Instructions: Payables Data Corruption Screening (Doc ID 1672163.1) document will appear explaining in more detail what will happen.

Click Next

Step 3) You have one question to answer - just tell us which impact area is causing you problems...

IMPORTANT: Click on the Note icon and carefully read the description for each impact area to properly select the closest match.  The Impact Area is the primary driver that AT uses to help provide a solution. 

Step 4) Choose severity and submit the SR.

That's it!

What Happens Next? 

Shortly afterwards you will receive a request to upload the MGD (if already uploaded then just ignore this step).  You will be reminded several times to provide files but the system will wait for you to provide this. 

Once the MGD is available our automated system will review it and paste your solution in the SR for you similar to the screenshot below:

How cool is that?

Be aware that if at any time you update the SR (except to upload the MGD file) before automation has completed, you will cause the SR to fall out of automation and be routed to an Accounting engineer.   Please give the process time to work, around 30-60 minutes depending on how long the MGD output is, and we think you will be amazed at how quickly and efficiently you will have a solution available and documented in your SR.

What If Automation Cannot Provide A Solution? 

If the automation engine cannot determine a solution for your issue because the MGD doesn't have any corruption signatures found or an invalid MGD file was uploaded, or if you have problems running the MGD and need assistance then the SR will drop out of automation and be routed to an engineer so you really have nothing to lose giving automation a try! 

We are excited about this new feature, so if you have an Accounting SR to log, please start selecting the Create Accounting Fails for Specific Invoice, Check or Vendor option from under the Accounting Issues and Reporting menu and give it a try!

Please provide any feedback on this process direct on our community post on this topic. 

New Service Contracts Functionality - Contracts Merge

A common contracts problem is that assets are spread across different contracts and customers want to consolidate different contracts into one.  Up until recently the only way to do this (other than at renewal time) was to author new contracts from scratch or amend existing ones manually.  With Release 12.1.3+ (via Patch 17861639:R12.OKS), users can now move assets from multiple source contracts to a single target contract using the new Contract Merge functionality.  This helps in improving the maintainability of customer contracts and avoids duplication of assets across the contract base.

A new profile option “OKS: Change Party in Contract Merge” allows users to move assets across the customer base. The re-pricing of the assets moved to target contract is controlled using “OKS: Pricing Method for Contract Merge” profile option. For more details on the implementation steps and functionality, please refer toOracle Service Contracts – How To Merge Assets Across Contracts (Doc ID 1684658.1).  This explains how the new feature works, how to use it and includes a UPK demo.

Questions on the new functionality?  Post your comments in the discussion thread in the Contracts and Lease Management Community.


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



« June 2014 »