Wednesday Apr 01, 2015

The EBS iProcurement Item Analyzer Has A Whole New Look and Feel!

We are pleased to announce a new version (200.1) of the EBS iProcurement Item Analyzer has been released.  The iProcurement Item analyzer still provides the best place to discover why items are not available in iProcurement; but now it has a  nicer look and feel, providing a very user friendly output.  Check it out in Doc ID 1586248.1.

The EBS iProcurement Item Analyzer Analyzer scans your 'Product' footprint, configuration, environment, and transactional data.   For areas of concern, the output will provide recommendations to prevent future issues and point to existing solutions for uncovered problems.  Most existing solutions can be implemented without logging a Service Request.

 Join our discussion today on the new analyzer and provide your feedback here

Thursday Mar 26, 2015

See the new Purchasing Document Open Interface (PDOI) improvements in 12.1.3!

Did you know that the new release of the 12.1.3 Procurement Rollup Up Patch (RUP) 19602627:R12.PRC_PF.B includes the following Purchasing Document Open Interface (PDOI) improvements:

 Bug #
Sourcing Rules were getting created twice (one global and one local) when only a local rule is intended while importing a Blanket Purchase Agreement (BPA).
 19697226 New Items are created when a BPA is imported even though create or update items parameter is passed as ‘Y’ (yes).
 20022541 Supply agreement flag is not honored when importing a BPA.
 19663699 Price breaks were not getting uploaded when a BPA is imported, if the item is not assigned to the inventory organization of the default ship to location of the vendor.
 19479583 Could not import Blanket Purchase Orders.
 19528138 The concurrent program completed in OUT of Memory error when trying to import a Standard PO with more than 10000 lines.
 19288447 The concurrent program failed to import standard POs as variance account generation failed for Shop floor destinations.
 19498303 Import standard Purchase Order program end in error if  the account generator failed with an unexpected error, without showing proper error message.
 18828164 Standard purchase orders could not be imported with multiple shipments.
 2036833 Purchase orders imported are stuck in a status of In-Process though the approved parameter is passed as “APPROVED”.

 For more information on Patch 19602627:R12.PRC_PF.B click here!

Thursday Mar 19, 2015

Just Released!!! March 2015 12.1.3: Procurement Family Update - Rollup Patch : 19602627:R12.PRC_PF.B

We are happy to announce the new March 2015 Rollup Patch (RUP) 19602627:R12.PRC_PF.B has been released for 12.1.3!

Check out the 'Whats New' section of Doc ID 1468883.1 to see all the iProcurement, Purchasing, Sourcing and Supplier Lifecycle Management (SLM) improvements, as well as the PDOI fixes included.

Get all the information you need on this patch; including, how to apply the patch, necessary pre and post patching steps, how to do an impact analyzer, and testing recommendations for your key business flows. Make sure and mark this note as one of your Favorites. Weekly we update the note with any issues found with the patch in the 'Known Issues' section.

Don't delay apply Patch 19602627:R12.PRC_PF.B today!

Need Help? Post your questions to the Procurement Community

Friday Feb 06, 2015

Are you Running the Approval Analyzer and Getting an Error?

Now that the Approvals Analyzer (Doc ID 1525670.1) is being requested on many Procurement Approval Service Requests and we have a new version, some client have reported that they are seeing errors like one of the following:

ORACLE error 6550 in FDPSTP

Cause: FDPSTP failed due to ORA-06550:
line 1,

column 7:
must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ERROR at line 27:
ORA-06550: line 27, column 3:
PLS-00201: identifier 'PO_APPRVL_ANALYZER
_PKG.MAIN_SINGLE' must be declared
ORA-06550: line 27, column 3:
PL/SQL: Statement ignore
FDPSTP failed due to ORA-06550: line 1,
column 7:
PLS-00306: wrong number or types of arguments in
call to 'MAIN_CP'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

The errors above simply mean that the concurrent program definition and Analyzer code are not in sync.

To resolve this error merely download and install the current version po_approval_analyzer.sql from the 'Download Now' button in .(Doc ID 1525670.1). Load the latest version of the concurrent program definition using podiagaa.ldt, then rerun the concurrent program.  Issue resolved!

And while we are talking about the Approval Analyzer remember to provide the correct document type when running it. Take a careful look at the parameters that return in the list of values after choosing the Single Mode.  It must match your document!

If you forget to choose the correct Document Type you will find errors in the output like the following:

For additional questions or comments on the Approval Analyzer click here.

Thursday Jan 29, 2015

See the New and Improved Buyer Work Center (BWC) Assistant

Need information about the Buyer Work Center (BWC) or solutions to issues?  See the new and improved BWC Assistant here!

  • New solutions have been added for known Release 12.1.X and 12.2 issues.
  • There is now a link to the Frequently Asked Questions information
  • Under Miscellaneous > General see a link to Recommending Patch, ERs, Tracing and further diagnostics as shown below:

So don't delay and check out Doc ID 1394392.2 today!

Friday Jan 09, 2015

Check out the New and Improved R12 Approval Analyzer Diagnostic Script!

A new version of the R12 Approval Analyzer (120.22) has just been released.  Improvements include:

  • The Procurement Code level is included in the output. There is no longer a need to run separate sql queries to get your code level when submitting Service Requests.
  • We added a new wrapper so that the analyzer can be run on a single document or all documents. If run on a single document the wfstat information will be automatically included.

Analyze_single.sql: Intended to be run on a single document type and number.  May be required to provide this output on a representative document, when logging an SR.

Analyze_all.sql: All mode is used on a routine basis to check ALL documents within a specific date range, or used before or after an upgrade.

  • We have additionally provided the simple steps on how to setup the Analyzer as a concurrent process, so users can run it on the front end from the Purchasing Responsibility Reports>Run  (then the wrappers are only necessary if run from SQL*Plus).

The Analyzer tools are the most impactful tools available for troubleshooting an issue!  They can analyze hundreds of problem signatures and tie them directly to known solutions.  When run on a single PO document, it provides you with comprehensive data to quickly resolve your issue.  

Get all the information you need to know from Doc ID 1525670.1 and download today! Run the quick video in the note to get the full steps on downloading, setting up and running the Analyzer.

Want more information?  Click here to the Procurement Community Post.

Thursday Jan 08, 2015

Are you occasionally getting complaints that the Purchase Order pdf file is not making it to the Supplier or Approver?

When the output format for a Purchasing document is in PDF format, a concurrent request is submitted during the approval of the document to generate the PDF.  On occasions this process may fail which results in the Approver and/or Supplier not receiving the PDF file.

Need help on finding these failed processes and the Purchase Orders they correspond to?

See Doc ID 1955731.1 'Aid to Returning Purchasing Documents that have Failed in the PO Output For Communication (POXPOPDF) Concurrent Request' which provides a quick sql script that can be run to identify these transactions.

Run this on a routine basis to check for failed items or when a user or supplier is reporting they didn't receive the document.

Need more help? Reply at this link with any questions.

Monday Jan 05, 2015

Want to take a look (and replay) our 2014 Procurement Webcasts?

Wish you could see a Procurement webcast you missed in 2014 or replay one you found of value?  Goto Doc ID 1456150.1 and click on the 'Archived 2014' tab.  Then you can click on the 'Recording' link to replay any of our webcasts or choose the '.pdf; link to review the slide deck.

Don't miss these valuable presentations from our Subject Matter Experts!

Monday Dec 15, 2014

Procurement Code Level added to the Approval Analyzer Output!

Hi, I just wanted to let everyone know about a recent addition to the Approval Analyzer.  We have included the Procurement Code level in the output.

First open  Doc Id 1525670.1 and download (and apply) the new version 120.19.

After running the analyzer review the .html output and scroll down to the 'Patches Applied' section.  You will see something like the following:

So don't forget download the new version today!

Questions or comments? Click here to join our discussion.

Friday Dec 12, 2014

We're Nearing Year End and Here's a Procurement Activity I would Recommend

Planning for Year End? For those in Release 12 I would highly recommend running your data through the Approvals Analyzer at Doc ID 1525670.1.  This analyzer is not just for approvals issues but will report on workflow errors, data corruption issues, critical patching, invalids and more.  And more importantly it will provide you with solutions on the problems reported.  When you run the analyzer at the parameter 'Document Type' choose ALL and then it will report on all your Purchasing documents including Purchase Orders, Requisitions, Agreements and Releases.  Then at the parameter 'Documents Created Since'  maybe just run it for the last few months or the last year.  What a great way to clean house and start the New Year Fresh!

Questions on the Approval Analyzer? Join our conversation here.

Tuesday Dec 02, 2014

Considering Customizations with POR_CUSTOM_PKG for iProcurement Requisitions? Check this out!

Doc ID 1942913.1 has just been released compiling these important questions and providing answers when considering customizations using  POR_CUSTOM_PKG for iProcurement Requisition Headers, Lines and Distributions.  Review the document for questions like:

1. What are the profiles relevant to POR_CUSTOM_PKG?
2. Is it necessary to bounce oc4j (iAS/Apache) for the 'POR: Enable Req%Customization' profile changes to take effect?
3. How can the custom package be used to default DFF line level attributes from header level DFF attribute values?
4. How do you modify the POR_CUSTOM_PKG code?
5. Is the POR_CUSTOM_PKG used only for updating DFF attributes, or can it be used for updating other values on requisitions?
6. Is it necessary for the user to navigate to a page where the DFF attributes or other field values are enabled in order for the POR_CUSTOM_PKG to be called?
7. How is personalization implemented to show DFF attributes referenced in the POR_CUSTOM_PKG?
8. Are the POR_CUSTOM_PKG.CUSTOM_DEFAULT... procedures called when there is an update to the requisition header, line, or distribution?
9. Can the POR_CUSTOM_PKG.CUSTOM_VALIDATE... procedures be used to UPDATE values?

Click here to see the complete details.

Friday Nov 21, 2014

Visit the iProcurement Item Analyzer

The iProcurement (IP) Item Analyzer is a great way to find out why items you expect to see in your iP Shopping page are not displaying.  This simple tool will perform multiple checks then provide clear instructions.  Below is a sample:

The analyzer also performs iProcurement health checks providing valuable recommendations on patching, invalids, profile options and more.

See Doc Id 1586248.1 to access the analyzer.

Want to see more?  Check out the use case for the iP Item Analyzer here!

Tuesday Nov 11, 2014

Have you seen the new Interactive Troubleshooting (IT) Flows for Procurement?

When logging a new Service Request (SR) for a few of the Problem Types in Procurement and Receiving, the new Interactive Troubleshooting (IT) Flow will be triggered and you will see a prompt similar to the following below:

Respond to the question prompts to find a potential solution and try the solution offered, before logging the SR.  But if assistance is still needed, continue to log the SR providing the information requested in the Service Request Data Collector (SRDC). Providing the requested information will help the analyst clarify your issue and cut down on time to resolution.

We also welcome your feedback!  Choose the feedback button in the flow and provide your comments.

 To date we have 5 interactive flows in the areas of:

  • Approvals
  • Receiving
  • Controls
  • Communication
  • Autocreate
Additionally you can post your comments (or questions) here!

Tuesday Nov 04, 2014

Don't Miss This! Leverage Endeca extension with iProcurement to Increase Operating Profit

Presenting at Sangam14 - Sunday November 9th 2014 in Bangalore, India

is our own

AnbuKartikeyan Jagadeeswaran.

Join him as he presents his white paper 'Leverage Endeca extension with iProcurement to Increase Operating Profit'.

Sangam is the largest independent Oracle Event in India and this is its 6th Annual Oracle Users Conference.  Beginning Friday, November 7th there are a variety of great topics and events. 

To get more information and to Sign Up Now! click here.

Thursday Oct 30, 2014

PDOI New Features and Enhancements!

The Purchasing Document Open Interface (PDOI) code was rewritten in order to accommodate new features that enhances the PDOI functionality and to make it consistent across the Purchasing module. Some of the features implemented are:

  • Ability to create a Purchase Order (PO) with Requisition Reference
  • Ability to create a Global Blanket Purchase Agreements (GBPA) and Global Contract Purchase Agreement (GCPA) reference through PDOI
  • Ability to use Advance Pricing in PDOI
  • Importing Contract Agreements through PDOI
  • Maintain consistency of defaulting values across the Buyer Work Center (BWC), Autocreate and PDOI programs

Want to know more?  Click here

It is highly recommended to apply the latest Procurement Rollup Patch (RUP). Currently it is patch 18911810:R12.PRC_PF.B  (Jul-14 RPC).  For the complete details on the RUP (aka RPC) refer to Note 1468883.1.


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



« April 2015