Does R12.1 Upgrade Require Multi-Org Even For Planning Instance?
(Doc ID 1083573.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Application Install - Version 12.1 to 12.1 [Release 12]
Oracle Financials Common Modules - Version 12.1 to 12.1 [Release 12.1]
Information in this document applies to any platform.
On a 12.1 version, Install/Configuration
When attempting to implement a decentralized instance of APS product suite, the R12 install/upgrade process checks for Multiple Organization (Multi-Org) setups to be completed with funmochk.sql, and requires setting the MO: Operating Unit profile. That profile cannot be set on the APS instance as it references Source EBS instance tables, that are not implemented or populated in the APS installation. During the install, the following error occurs.
2 Run AutoPatch R120 pl hxcasdup.sql FAILED
ERROR at line 1:
ORA-04063: package body "APPS.HR_GENERAL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.HR_GENERAL"
ORA-06512: at line 37
(copied from pnatst since this installation was possibly corrupted)
2 Run AutoPatch R120 pl IGSINPRG.sql FAILED
ORA-04063: package body "APPS.FND_PROFILE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APPS.FND_PROFILE"
ORA-06512: at line 47
(copied from pnatst. I think the failed installation caused these issues)
2 Run AutoPatch R120 pl asrmorgdef.sql FAILED
sqlplus -s APPS/***** @/p071/oracle/pna271/apps/apps_st/appl/as/12.0.0/patch/115
/sql/asrmorgdef.sql &un_as &pw_as
ERROR at line 1:
ORA-20001: FND-ORG_ID PROFILE CANNOT READ: N, OPTION, MO: Operating Unit
(NOT MULTI-ORG ???)
ORA-06512: at "APPS.FND_MESSAGE", line 509
ORA-06512: at "APPS.FND_CLIENT_INFO", line 154
ORA-06512: at "APPS.FND_GLOBAL", line 2108
ORA-06512: at "APPS.FND_GLOBAL", line 2309
ORA-06512: at "APPS.FND_GLOBAL", line 2447
ORA-06512: at "APPS.FND_GLOBAL", line 2385
ORA-06512: at line 105
/p071/oracle/pna271/apps/apps_st/appl/fnd/12.0.0/bin/WFLOAD &ui_apps 0 Y UPGRADE
You use the Multiple Organizations feature, but you do not define the MO: Operat
ing Unit option.
- 1602: Could not save.
- 1400: Could not save to database. MODE=UPGRADE EFFDATE=<null>
- 1401: Could not upload ACTIVITY entity 'OEOI/RUN_ORDER_IMPORT'.
- 1401: Could not upload ATTRIBUTE entity '<null>/ARG10'.
- 210: Oracle Error: ORA-00001: unique constraint (APPLSYS.WF_ACTIVITY_ATTRIBU
ORA-01403: no data found
ORA-06512: at "APPS.WF_LOAD", line 1713
ORA-06512: at line 1. SQL text: BEGIN WF_LOAD.UPLOAD_ACTIVITY_ATTRIBUTE(:activi
ty_item_type, :activity_name, :activity_version, :name, :display_name, :descript
ion, :sequence, :type, :protect, :custom, :subtype, :format, :default, :value_ty
pe, :level_error); END;
MESSAGE 'WFSTD/WFSTD_DEFAULT_VOTE' is protected, no changes were saved.
(SKIPPED for now)
3 Run AutoPatch R120 pl asospar.ldt FAILED
Loading data using FNDLOAD function.
FNDLOAD APPS/***** 0 Y UPLOAD @PER:patch/115/import/peroit.lct @ASO:patch/115/im
Connecting to APPS......Connected successfully.
Calling FNDLOAD function.
Returned from FNDLOAD function.
Log file: /p071/oracle/pna271/apps/apps_st/appl/admin/pna271/log/US_asospar_ldt.
Error calling FNDLOAD function.
You use the Multiple Organizations feature, but you do not define the MO: Operating Unit option.
You should define the MO: Operating Unit profile at the responsibility level if you use the Multiple Organizations feature.
Log filename : L1767492.log
The issue can be reproduced at will with the following steps:
1. install EBS source instance
2. setup MO on source EBS
3. install R12.1.1 APS destination instance
4. it requires for MO to be setup on APS instance
5. install fails
6. profile MO Operating Unit cannot be set on APS instance.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|