Custom Program Calling Seeded API's Failing With "Operating unit access is not allowed" Error

(Doc ID 2096251.1)

Last updated on MAY 25, 2017

Applies to:

Oracle Application Object Library - Version 12.1.3 to 12.2.5 [Release 12.1 to 12.2]
Oracle Applications DBA - Version 12.1.3 to 12.2.5 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

E-Business Suite 12.1.3, Patch Application Issues

After a patch concurrent requests using seeded API - AP_VENDOR_PUB_PKG.CREATE_VENDOR_SITE fail with with error 'Operating unit access is not allowed'.

<Patch 18936791> results in the concurrent program error below during request initialization by organization id:

'Operating unit access is not allowed. Please check that you have access to the operating unit: XXXXXX,XXX Operating Unit Info is null.'

The request uses an organization based global responsibility for the applications initialization, and is used to create/update vendor sites.
The errors not only impact the create/update functions for a supplier , as they can effect any program performing apps initialization programmatically.


ERROR
-----------------------
Operating unit access is not allowed. Please check that you have access to the operating unit: XXXXXX,XXX Operating Unit Info is null.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install <Patch 18936791>.

2. Run a concurrent request calling API AP_VENDOR_PUB_PKG.CREATE_VENDOR_SITE.

3. Confirm the request fails with error 'Operating unit access is not allowed'.

Cause

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