Unable To Create PO Via PBWC If MO: Default Operating Unit Profile Is Not Set (Doc ID 783711.1)

Last updated on AUGUST 19, 2015

Applies to:

Oracle Purchasing - Version 12.0.5 and later
Information in this document applies to any platform.


On R12, when attempting to click the button (Go) to create Standard Purchase Order (PO) in the Professional Buyer Work Center (PBWC), the following error occurs:

oracle.apps.fnd.framework.OAException: java.lang.Exception: Assertion failure: orgId cannot be null
at oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAException.java:980)
at oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:211)
## Detail 0 ##
java.lang.Exception: Assertion failure: orgId cannot be null
at oracle.apps.po.common.Assert.fail(Assert.java:79)
at oracle.apps.po.common.Assert.assertTrue(Assert.java:37)
at oracle.apps.po.common.Assert.assertNotNull(Assert.java:305)

If profile MO: Default Operating Unit is set the issue does not occur any more.
System works correctly if creating Purchase Order via regular form.


Steps to Reproduce :

1. Leave profile MO: Default Operating Unit blank at all levels.
2. Using Purchasing Super User responsibility, navigate to Professional Buyer Work Center > Orders
3. Click on Create Standard Purchase Order > (Go) button
4. Error message is displayed on page.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms