Tuesday Apr 19, 2016

What Are the Available BSO Web Service Methods Available for Purchasing in 12.2.5?

What Are the Available BSO Web Service Methods Available for Purchasing in 12.2.5?

Review (Doc ID 2120274.1)

The following is a list taken from the Integrated Repository showing the available BSO web service objects available in 12.2.5 (or 12.2.4 where patch 19684688 has been applied).

Service Description
createPurchaseOrder This Service Method Creates a Purchase Order with the data provided in the input object PurchaseOrder.

For Create PO, DocumentSubType, StyleId and OrgId are mandatory attributes.


This Service Method takes the Order Number and Organization Name as the input and retrieves the complete Purchase Order details.


This Service Method Updates an existing Purchase Order document as per the data provided in the input object PurchaseOrder.

- For Update PO, DocumentNumber and OrgId, or PoHeaderId are mandatory, to identify the PO to be updated.

- When updating Lines, either provide PoLineId or LineNum to set the context. The same applies to other entities as well.

- To add new Line, either leave LineNum as null, or provide a new LineNum. The same applies to other entities as well.

- For Schedules, Pay Items and Price Breaks, use entity PoLineLocations.

- For BPA Item Attributes, use entities PoAttrVals and PoAttrValuesTLP.

- For Complex PO Pay Item, PaymentType value is mandatory for both create and update scenarios. Possible values are ADVANCE, DELIVERY, LUMPSUM, MILESTONE, RATE.

- Provide only values of attributes to be updated, along with context attributes (discussed above). If an attribute value is provided, and it is not updatable because of the entity status or some other setup, an error message will be returned back and transaction will fail. This applies even when the new value provided is same as current value in PO.

- To nullify the value of a String type of attribute, pass the literal value "WEBSERVICE_NULL_CONSTANT_STRING" or java constant PoConstants.WEBSERVICE_NULL_CONSTANT_STRING

- To nullify the value of a Number type of attribute, pass the literal value -99999999 or PoConstants.WEBSERVICE_NULL_CONSTANT_NUMBER in java.

- To nullify the value of a Date type of attribute, pass the literal value or PoConstants.WEBSERVICE_NULL_CONSTANT_DATE in java

performDocControlAction This Service Method takes the ControlActionInput object as the input and performs the control action on the purchasing document as per the input provided.

Control Actions that are supported by this method are:

- CANCEL (Supports at Header/Line/Shipment level): Cancels the Purchasing document at the specified level

- CLOSE (Supports at Header/Line/Shipment level): Closes the Purchasing document at the specified level

- OPEN (Supports at Header/Line/Shipment level): Opens the Purchasing document at the specified level in case if it is already closed

- INVOICE CLOSE (Supports at Header/Line/Shipment level): Closes the invoice of the Purchasing document at the specified level

- INVOICE OPEN (Supports at Header/Line/Shipment level): Opens the invoice of the Purchasing document at the specified level in case if it is closed

- RECEIVE CLOSE (Supports at Header/Line/Shipment level): Closes the receiving transaction for the Purchasing document at the specified level

- RECEIVE OPEN (Supports at Header/Line/Shipment level): Opens the receiving transaction for the Purchasing document at the specified level in case if it is already closed

- FINALLY CLOSE (Supports at Header/Line/Shipment level): Performs Finally Close operation on the purchasing document at the specified doc level

- FREEZE (Supports at Header level): Performs Freeze operation on the Purchasing document

- HOLD (Supports at Header level): Holds the Purchasing document

- RELEASE HOLD (Supports at Header level): Releases the Hold on the Purchasing document if it is already on Hold

- DELETE (Supports at Header level): Deletes the Purchase order


This Service Method Creates a Purchase Order Modification document with the data provided in the input object PurchaseOrder.

CLM based document.


This Service Method takes the Modification Number and Organization Name as the input and retrieves the complete Purchase Order Modification details.

CLM based document.


This Service Method Updates an existing Purchase Order Modification as per the data provided in the input object PurchaseOrder.

CLM based document.

Tuesday Jan 05, 2016

How Reapproval Rules can cause Purchasing Documents to require Reapproval?

Are your Reapproval rules causing documents to require Reapproval? What are reapproval rules?

To understand reapproval rules it is important to make a distinction between new documents and already approved documents, which are modified after approval:

  •  If a new document is created the purchase order, release or requisition will always go through the approval process.
  •  However, adding or changing specific information for an already approved document, may cause the document to unapprove, regardless of whether the revision is incremented. Almost all changes that cause the revision to be incremented also unapprove the document, as does placing the document on hold, reserving it or canceling it.

The reapproval rules help you control whether-or how much of-a revision (for example, to Quantity) requires the document to undergo the entire approval process or to be instantly approved. So in other words the reapproval rules determine if a modified purchasing document requires reapproval or not.

For a complete overview of the Requires Reapproval Rules and the Change Order workflow within Purchasing and understanding which changes can cause a document to require reapproval , you can review How Reapproval Rules Can Cause Purchasing Documents To Require Reapproval? Doc ID 1114515.1

Wednesday Dec 16, 2015

Attention Oracle Exchange and Oracle Supplier Network Customers!

Last weekend, Oracle performed a hardware upgrade to the Oracle Supplier Network. Oracle Development and Oracle Support would like to alert you to some information that could impact you.  If you have any questions regarding this information, please update the My Oracle Support Community thread Changes for Oracle Exchange and Oracle Supplier Network Customers, and someone from Support will respond back to you.

For more information, you can review the following documents available related to these changes:
• Exchange Migration - Changes Planned For The Oracle Exchange Platform (Doc ID 2083643.1)
• New UI (User Interface) In OSN Including Punchout Feature After Hardware Upgrade (Doc ID 2083662.1)

Please take the time to review the information.  It is important that you be aware of these changes and how they may impact you. We will be actively updating content with any and all new information in an effort to make any transitions or changes easier for you and your suppliers.

Wednesday Sep 16, 2015

Don't Miss This! Oracle Exchange Certificate Renew August 19, 2015

You current Oracle Exchange certificates will expire on August 19, 2015.   Avoid potential java errors when loading certificates by following:

Doc ID 2051178.1 'FAQ Oracle Exchange Certificate Renew On August 19, 2015'

Doc ID 1999543.1 'Which Type Of Certificates Are Supported By Oracle Exchange And iProcurement Punchout. Does It Support SHA-2 ( Like SHA 256RSA )?'

Still have questions? Start a discussion thread in the Procurement Community

Wednesday Sep 02, 2015

Getting Jave Errors when Loading Certificates in Oracle Exchange and iProcurement Punchout?

The following error can occur when trying to upload certificates with Oracle Exchange and iProcurement.  

Error Code: 100 Unexpected Error
java.lang.RuntimeException: HTTPSURL Init Failure: java.security.cert.CertificateParsingException: java.io.IOException: subject key, java.security.spec.InvalidKeySpecException: Unknown key spec.
      at sun.security.x509.X509CertInfo.<init>(X509CertInfo.java:157)
      at sun.security.x509.X509CertImpl.parse(X509CertImpl.java:1044)
      at sun.security.x509.X509CertImpl.<init>(X509CertImpl.java:134)

java.io.IOException: javax.net.ssl.SSLException: Received fatal alert: handshake_failure (no cipher suites in common)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.b(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA12275

This occurs because SHA 256RSA (also known as SHA-2 or SHA2)  are inadvertently loaded to the Exchange certificate bundle file and they are not supported.

So how can these certificates be identified and what can be done about it?  See Doc ID 1999543.1 for all you need to know!

Friday Aug 21, 2015

New White Paper on Using Web ADI Spread Sheet in the Buyer Work Center Orders (BWC)

See this just released white paper for the BWC covering the following topics:

1.    Overview
2.    Limitations
3.    Prerequisites
4.    Demo Test Cases
       a.    Update existing PO lines, shipments, pay items, and distributions
       b.    Adding New Line to Exiting PO
5.    Technical changes
6.    Troubleshooting
7.    Known issues

Any questions? Start a discussion in the Procurement Community.

Thursday Aug 13, 2015

Have you used R12: Master Data Fix Diagnostic to Validate Data Related to Purchase Orders and Requisitions?

Check out the Master Data Fix Diagnostic to Validate Data Related to Purchase Orders and Requisitions for Release 12!

This diagnostic will allow you to address many data integrity issues without requiring you to log a Service Request with support. The script produces an html output of known problems relating to the purchasing transactions created in the specified date range.  It additionally nicludes information on notes and/or data-fix patches, which may already be available to resolve the data issues.

Use it proactively to scan all transactions in the specified date range and head off potential issues. This script may be run in production safely at any time. No data is created, updated, or deleted.

Run this diagnostic 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.

For more information on Master Data Fix Diagnostic to Validate Data Related to Purchase Orders and Requisitions, please see Doc ID 1474734.1.

For a list of available Generic fixes, see Oracle Purchasing Generic Datafix Index Doc ID 1348821.1.

Sunday Aug 02, 2015

Procurement Analyzers

Have you discovered the E-Business Suite Product Based Support Analyzers? From Doc ID 1545562.1 scroll down to the Procurement section and see these valuable offerings.  Each analyzer is specialized to help you diagnose issues before logging a Service Request, click on ACT for direct access.  What makes analyzers special is they not only provide you with errors found, but provide solutions as well. The analyzers are safe to run in Production and can be setup as a concurrent requests so all your users can access the valuable output.  Check them out today!

As new analyzers are created we will add them to Doc ID 1545562.1 so don't forget to bookmark the document!

Wednesday Jul 08, 2015

Does the Approval Analyzer show "Authentication failed" in the Output?

An issue has been reported for some customers that after running the Procurement Approval Analyzer and saving the html output, the output file shows: 

"Authentication failed."

The cause of this issue is linked to the Temp ID given to the report output.  The source data for the page becomes cached, so is no longer valid.  This invalid state fails the page source data build, so when going to save the page data, there is no source data present to generate the saved file.  The way this is prevented is to force a page rebuild each time, so the cached state does not occur.

So what is the solution?

For Firefox: enter the following string into the URL location box in the Firefox browser


Click through warning dialog box
•  Search for "browser.cache.check_doc_frequency"
•  Change the value to "1"
•  Exit the browser session window to save

For Internet Explorer:

•  In the IE Browser go to "Tools" => "Internet Options"
•  Select the "General" tab => "Browsing History" => "Settings"
•  Set "Check for newer versions of Stored Pages" to "Every time I visit the webpage"
•  Exit Tools section to save setting change

Still have questions?  Click here to post your question.

New to the Procurement Accounting Space - Introducing the EBS iProcurement Change Request Analyzer!

Newly released in the Procurement Accounting space is the EBS iProcurement Change Request Analyzer for Release 12!

The single document provides all the information needed to troubleshoot the problem with the change request process.

The analyzer scans your iProcurement 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.

Checks include:

  • Lists existing change requests associated to the document and the workflow processes involved
  • Provides change order tolerances, related archive tables and data collection
  • Document Validations include:
    • Supervisor Hierarchy and Approver List Validations
    • PO with Pending Changes that are In Process
    • Purchase Orders that are not Open/Approved or Shipment Level Open
    • Non-Catalog Requisition Prices Change
    • Purchase Order is Partially Received or Billed
    • Requisition is on a Complex Purchase Order
    • Requisitions with pending Receiving transaction
    • Allow Price Override is not checked
    • Accrue on receipt flag is Y
    • Purchase Order Shipments do not correspond to the same requisition line

Simply run the analyzer as a SQL script or as a concurrent request, by following EBS iProcurement Change Request Analyzer, Doc ID 1917475.1

Previous suggestions and feedback were used to develop the analyzer.  Now you have the ability to drive us in your direction.  Post your comments to improve the usefulness of this tool in your environment by adding a reply here.

Try this analyzer before logging  a Service Request when you are experiencing change request issues.

Monday Jul 06, 2015

Need Help with PO Output for Communication Issues?

See our data collection for everything you need to know:

 Doc ID
 Title  Purpose
1535771.1 POXPOPDF: PO Output for Communication Collection of Known Code Issues and Patch Fixes Divided into Releases from through12.2 see supports list of recommended patching.
1532387.1 Frequently Asked Questions POXPOPDF: PO Output for Communication Visit the FAQ which provides answers to questions ranging from  basic setup to attachment issues to customization tips and tricks, and more!
1377764.1 Troubleshooting Assistant: Oracle Purchasing PO Output for Communication / Supplier Notification Issues Use the assistant by selecting your symptoms and be guided to supported solutions.
1375082.1 Master Troubleshooting Guide for POXPOPDF: PO Output for Communication Providing targeted steps for troubleshooting, try these before logging a Service Request.

 Still have questions?  Start a discussion in the Procurement Community.

Thursday Jun 25, 2015

Just Released! Version 200.2 of the iProcurement Item Analyzer

What's new in version 200.2?

We've added additional profiles to the iProcurement Specific Profile Options section:
   - POR : Amount Based Services Line Type
   - POR : Goods Line Type
   - POR : Rate Based Services Line Type

New Patch Checks are included along with a check is now made for custom packages.  Additionally we have added the Procurement Code level section for 12.0.x, 12.1.x, 12.2.x and some code changes for EBS Framework version 3.0.25.

Download it today at Doc ID 1586248.1!

Do you have additional questions or feedback?  Well post them here.

Wednesday Jun 10, 2015

New version 200.5 of the 12.1.3 Procurement Approval Analyzer Just Released!

Like a fine wine we keep getting better over time! Download the new version 200.5 of the 12.1.3 Procurement Approval Analyzer today here.

Improvements include:

1. Bug fix for the request ending up in warning
2. Change of wfstat signatures that were defined backwards - results should be the same as before
3. Added the following signatures to the DX summary: APP_HIER_CHECK1, APP_HIER_CHECK2, APP_HIER_CHECK3, APP_HIER_CHECK4, APP_HIER_CHECK5, APP_HIER_CHECK6

Need more information?  Reply here.

Monday Jun 08, 2015

Important Update on the March 2015 12.1.3 Procurement Rollup Patch

If you haven't heard there is a new replacement for 12.1.3 March 2015 Patch 19602627:R12.PRC_PF.B in Patch 21198991:R12.PRC_PF.B.  For details and complete patching instructions see Note 1468883.1.

Questions or concerns?  Reply here.

Friday Jun 05, 2015

Have you applied the March 2015 12.1.3 Procurement RUP? Or have you seen a problem with the Action History of Requisitions being Deleted?

We have been notified by Procurement Development that there is critical issue where upon deletion of an incomplete Requisition the action history of all requisitions are deleted.  This occurred because of Patch  19289104:R12.ICX.B which has since been set to obsolete, but was already included in the March 2015 RUP.

There has also been an additional symptom seen where a single requisition action history is getting deleted on edit by the approver.

 If you have applied either Patch 19289104:R12.ICX.B or the March 2015 Procurement Rollup Patch (RUP) 19602627:R12.PRC_PF.B in order to prevent this problem, please perform the following:

1. Download Patch 19686669:R12.ICX.B 'This patch resolves the issue of deleted incomplete requisition history in po_action_history table' and Patch 20042118:R12.ICX.B 'This patch resolves the issue of ORA-06512 IN WORKFLOW WHEN USING EDIT REQUISITION'.   Be sure to follow the readmes for any important patching steps.

2. Ensure that you have taken a backup of your system before applying the recommended patches.

3. Apply the patch in a test environment and confirm the following file versions:

patch/115/sql  ICXVUTLB.pls  120.18.12010000.14     
patch/115/sql  ICXVUTLS.pls  120.14.12010000.4     
java/por/req/server  ShoppingCartSvrCmd.java  120.9.12010000.15  
patch/115/manualsteps/ad_apply_patch.xml 120.3.12000000.2     
patch/115/sql/PORUTILB.pls 120.20.12000000.41   
patch/115/sql/PORUTILB.pls 120.69.12020000.53   
patch/115/sql/PORUTILB.pls 120.132             
patch/115/sql/PORUTILB.pls 120.28.12010000.62

4. Clear the cache on the server.

a. Responsibility: Functional Administrator
b. Click the Core Services tab.
c. Click the Caching Framework subtab.
d. Click the Global Configuration link on the left side of the page.
e. Click the Clear All Cache button, then click "Yes" to confirm the deletion of the java cache on the server.  Allow this to complete.
f. Log out of the applications.

5. Bounce the iAS/OC4J processes on the applications middle tier(s) in order for the code changes to take effect.

6. Migrate the solution to other environments where 19602627:R12.PRC_PF.B has been applied.

If you have any questions/concerns reply here


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



« May 2016