Introduction

This post describes Oracle Enterprise Command Center Framework (ECC) upgrade from V2-V4 to V5. It is not meant to replace MOS Doc ID 2495053.1, which is very clear and detailed. We want to share our experience including faced errors and solutions.
For installation instructions of ECC V2 please refer to this post.
For upgrade instructions from ECC V2 to V3 please refer to this post.
For upgrade instructions from ECC V3 to V4 please refer to this post.
And good news for those who would like to see the latest ECC in action. You can try it yourself in our demo environment. Just log in and choose Payables manager or Receivables manager responsibility and navigate to the command center menu entry.

Please also try Blitz Report which is the fastest way to export Oracle EBS data into Excel.

References

Following sources have been used to get ECC upgrade instructions:

Installing Oracle Enterprise Command Center Framework, Release 12.2 (Doc ID 2495053.1)

Requirements

Supported OS versions

Oracle Linux 7 or Red Hat Enterprise Linux 7 (64-bit)

Our existing ECC installation uses standalone Oracle Linux 7 virtual machine.

If you initially installed Oracle Enterprise Command Center Framework Release 12.2 V2 on Oracle Linux 6 or Red Hat Enterprise Linux 6, then you must upgrade the operating system to Oracle Linux 7 or Red Hat Enterprise Linux 7 before you begin the upgrade to Oracle Enterprise Command Center Framework Release 12.2 V5.

Required OS resources

MOS Doc ID 2495053.1 provides table describing OS resources requirements. We started with minimal resources assignment as it can be easily changed for a virtual machine.

Number of users Number of records Number of Cores Required Memory
50 2 million 2 5 GB

Perform backups

Ensure that you have sufficient disk space to back up the existing V2-V4 installation backup and to extract the V5 .bsx file from the V5 quick install package.

Shutdown ECC

[oracle@ecc ~]$ ./stopecc.sh

Compress ECC installation directory

[oracle@ecc u01]$ nohup tar -czvf ecc_demo_v4_bkp.tar.gz ecc_demo>/tmp/bkp_log &

Export Oracle Enterprise Command Center Framework Schema

After adjusting directory path run the following commands to export the ECC_SCHEMA from the database instance as user with DBA privileges:

[oracle@ecc ~]$ sqlplus '/as sysdba'
SQL> create or replace directory ECC_EXP_DIR_NAME as '/backup/snapshots/BACKUPS/ecc/ECC_schema_backup';
SQL> grant read, write on directory ECC_EXP_DIR_NAME to ECC;
SQL> exit
[oracle@ecc ~]$ export ECC_SOURCE_SCHEMA=ECC
[oracle@ecc ~]$ read -s ECC_SOURCE_SCHEMA_PASSWORD
[oracle@ecc ~]$ expdp ${ECC_SOURCE_SCHEMA}/${ECC_SOURCE_SCHEMA_PASSWORD} DIRECTORY=ECC_EXP_DIR_NAME DUMPFILE=ecc_dump_v4.dmp LOGFILE=ECC_EXP_DIR_NAME:exportSchema_v4.log

Startup ECC

[oracle@ecc ~]$ ./startecc.sh

Run upgrade script

Create directory a staging directory

Download patch Patch 30535681 from MOS
Unzip patch into the staging directory

unzip p30535681_R12_GENERIC.zip

Copy two .bsx files to a staging directory. Add executable permissions to them

chmod +x *.bsx

From the stage directory, execute ECC v5 installer files:

for f in *.bsx; do sh $f; done

Installer creates two directories:

  • insta_client: The SQL*Plus client directory
  • Oracle: Oracle Enterprise Command Center Framework quick install scripts and software

Change to the /Oracle/quickInstall directory and run the upgrade.sh script.

cd Oracle/quickInstall
./upgrade.sh

When prompted, enter the following details:

  • The base directory of the existing V2-V4 Oracle Enterprise Command Center Framework installation that you want to upgrade
  • The password for the Oracle Enterprise Command Center Framework domain admin user
  • The password for the Oracle Enterprise Command Center Framework database user

The script displays messages indicating the actions performed to carry out the upgrade.
These messages are also recorded in a log file in the directory specified for the ECC_LOG_DIR configuration property in your installation. The log file is named $ECC_LOG_DIR/upgrade.log.

Note: The following warning message may appear during the upgrade process:

java.rmi.RemoteException: [Deployer:149145]Unable to contact "eccManaged". Deployment is deferred until "eccManaged" becomes available.
WARNING: If this is a redeploy app and contains JSP pages that have been touched, these JSP changes won't be reflected when the server starts unless precompile is set to true in weblogic.xml

You can safely ignore this message. This is an informational message indicating that deployment is marked as delayed because the Oracle Enterprise Command Center Framework domain managed server is shut down at this point. The upgrade will proceed to the next step, and new deployment along with relevant changes will take effect when the upgrade script restarts the managed server.

Verify the upgrade

After the upgrade script finishes running, verify the upgrade by opening the ECC Developer function under ECC Developer responsibility

Check Enterprise Command Center ECC version

EBS 12.2.10 required patches

EBS patches need to be applied before configuring ECC. Below list of patches is specific for our EBS 12.2.10 instance as we have some of the patches applied. For example we had R12.AD.C.Delta.12 and R12.TXK.C.Delta.12 applied as we recently upgraded to EBS 12.2.10. First two patches: ATG consolidated patch and adapter patch are mandatory. Other patches depend on the products with Enterprise Command Centers that you want to use and installed languages.
Patches must be applied in the order below. MOS Document 2495053.1 prohibits merging between ATG consolidated patch,adapter patch and the product family consolidated patches. Following this rule I  applied ATG consolidated patch and its NLS patches, then adapter patch and its NLS patches. Then I merged and applied all product family consolidated patches including their NLS patches.

[-]30535546:R12.ATG_PF.C ATG CONSOLIDATED PATCH FOR ECC V5 SUPPORT IN 12.2.10
	[+]R12.AD.C.delta.12
	[+]R12.TXK.C.delta.12
	[+]30399994 R12.ATG_PF.C.delta.9
[-]30535550:R12.ATG_PF.C adapter patch
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]31826707:R12.TXK.C ECC CLIENT for EBS - V5 UPDATES -( ECC jar updated )
[-]30535650:R12.CC_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]30535649:R12.FIN_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]30535654:R12.HR_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]30535647:R12.PRC_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]30535653:R12.PJ_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]30535619:R12.SCM_PF.C
	[+]12.2.4
	[+]R12.AD.C.delta.11
	[+]R12.TXK.C.delta.11
[-]31128826:R12.CSE.C
[+]29399610:R12.PO.D
[+]30215625:R12.PER.C
[+]30441751:R12.PO.D
[-]31539415:R12.INV.C
[-]31696168:R12.ICX.D 
[-]31691276:R12.OKL.C
	[+]12.2.3
	[+]R12.AD.C.delta.7
	[+]R12.ATG_PF.C.delta.5
	[+]R12.FIN_PF.C.delta.5
	[+]R12.TXK.C.delta.7
[-]30554810:R12.PN.C
	[+]12.2.3
	[+]R12.AD.C.delta.5
	[+]R12.ATG_PF.C.delta.4
	[+]R12.PJ_PF.C.delta.4
	[+]R12.TXK.C.delta.5
[+]31054002:R12.ICX.D
[-]31713023:R12.PO.D
[+]30990390:R12.ICX.D
[-]31604775:R12.PA.C 
[-]31457942:R12.PA.C

Start ADOP patching cycle

{ echo $appspass; echo $systempass; echo $wlspass; }|adop phase=prepare

Apply ATG consolidated patch and adapter patch plus NLS without merging them. Adop will apply them in the sequence they appear in the patch list.

{ echo $appspass; echo $systempass; echo $wlspass; }| adop phase=apply patchtop=/backup/patches/ECC_upgrade patches=30535546:u30535546.drv,30535546_ZHS:u30535546.drv,30535550:u30535550.drv,30535550_ZHS:u30535550.drv

Apply rest of the patches plus NLS merging them (the command is truncated due to a large number of patches)

{ echo $appspass; echo $systempass; echo $wlspass; }| adop phase=apply patchtop=/backup/patches/ECC_upgrade patches=31826707:u31826707.drv
....................
31457942_ZHS:u31457942.drv,31457942:u31457942.drv merge=yes

Issue

{ echo $appspass; echo $systempass; echo $wlspass; }|adop phase=actualize_all

Faced issue during actualize_all phase for FPA_ objects related to Projects application:

SQL> alter package APPS.FPA_MAIN_PROCESS_PVT compile;
alter package APPS.FPA_PORTFOLIO_PROJECT_SETS_PVT compile
*
ERROR at line 1:
ORA-04045: errors during recompilation/revalidation of
APPS.FPA_PORTFOLIO_PROJECT_SETS_PVT
ORA-00600: internal error code, arguments: [kql_tab_diana:dep copy],
[0x0D3EE13F0], [0x7F8D85D77260], [3], [], [], [], [], [], [], [], []

Workaround for this problem can be found in Bug 24489846 and Doc ID 2426230.1

The workaround process to accomplish cleanup of old editions is to connect to APPS account via sqlplus and execute the following

$ sqlplus apps/****
-----------------------------------------------------------------
exec ad_zd.set_edition('PATCH')
 
declare
cursor FPATYPES is
select object_name from user_objects
where object_type='TYPE' and object_name like 'FPA%';
begin
for rec in fpatypes loop
execute immediate 'alter type '||rec.object_name||' compile';
end loop;
end;
/

Please note that it’s not required to run actualize_all phase and finalize and cleanup phases in full mode every patching cycle. I did it to get rid of old patching editions in the database.

{ echo $appspass; echo $systempass; echo $wlspass; } | adop phase=finalize finalize_mode=full
 
{ echo $appspass; echo $systempass; echo $wlspass; } | adop phase=cutover
 
source ~/EBSapps.env run
{ echo $appspass; echo $systempass; echo $wlspass; } | adop phase=cleanup cleanup_mode=full
 
{ echo $appspass; echo $systempass; echo $wlspass; } | adop phase=fs_clone

Import Enterprise Command Center Applications

Copy $ECC_BASE/Oracle/quickInstall/scripts/patchEccFiles.pl script from ecc host to EBS host.

Login to EBS server and apply run fs environment.

[oracle@demo ~]$ . ./EBSapps.env run

Create empty staging directory.

[oracle@demo scripts]$ mkdir /tmp/staging

Run patchEccFiles.pl script

[oracle@demo tmp]$ ./patchEccFiles.pl
Enter temporary directory for ECC Files (Should be used only for this task and be empty): /tmp/staging
Enter EBS DB apps user id (default: apps) :
 
Enter EBS DB apps user password:
List of languages installed in EBS:
--------------------------------------------------
| Language| ECC Language Code|
--------------------------------------------------
| ARABIC | ar |
| GERMAN | de |
| FRENCH | fr |
| AMERICAN | en |
| SIMPLIFIED CHINESE | zh-Hans |
---------------------------------------------------
 
List of languages supported in ECC:
Arabic(ar), Brazilian Portugese(pt), Canadian French(fr-CA),Croatian(hr), Cyrillic Kazakh(kk), Cyrillic Serbian(sr), Czech(cs), Danish(da), Dutch(nl), English(en), Finnish(fi), French(fr), German(de), Greek(el), Hebrew(he), Hungarian(hu), Indonesian(id), Italian(it), Japanese(ja), Korean(ko), Latin Spanish(es-419),Latin Serbian(sr-Latn), Lithuanian(lt), Norwegian(no), Polish(pl), Portugese(pt-PT),Romania(ro), Russian(ru), Simplified Chinese(zh-Hans), Slovak(sk), Slovenian(sl), Spanish(es), Swedish(sv), Thai(th), Traditional Chinese(zh-Hant), Turkish(tr), Ukranian(uk), Vietnamese(vi)
 
NOTE: Only languages installed and enabled in ECC will be processed successfully
Example: Enter ar,pt for Arabic and Brazilian Portugese language respectively. Enter all(ALL) for all languages
 
Enter the Language code(s) from the list mentioned above to run the translation for:
 
Do you want to add all products at once(Y) or specify the subset(N): Y
 
Adding product top AP
 
Adding product top AR
 
Adding product top BOM
 
Adding product top CN
 
Adding product top CS
 
Adding product top EAM
 
Adding product top FA
 
Adding product top GMO
 
Adding product top ICX
 
Adding product top INV
 
Adding product top JMF
 
Adding product top OKL
 
Adding product top OKS
 
Adding product top ONT
 
Adding product top OZF
 
Adding product top PA
 
Adding product top PO
 
Adding product top WIP
 
Importing application /tmp/staging/ap/12.0.0/patch/115/ecc/applications/ap_ecc.zip
ECC WEB ENTRY URL:http://demo.enginatics.com:80/ecc
ECC Application File:/tmp/staging/ap/12.0.0/patch/115/ecc/applications/ap_ecc.zip
Importing file /tmp/staging/ap/12.0.0/patch/115/ecc/applications/ap_ecc.zip finished with response [{"STATUS":200,"logFileName":"import_20190529095220.log"}]
Imported application /tmp/staging/ap/12.0.0/patch/115/ecc/applications/ap_ecc.zip successfully
 
Importing application /tmp/staging/ar/12.0.0/patch/115/ecc/applications/ar_ecc.zip
ECC WEB ENTRY URL:http://demo.enginatics.com:80/ecc
ECC Application File:/tmp/staging/ar/12.0.0/patch/115/ecc/applications/ar_ecc.zip
Importing file /tmp/staging/ar/12.0.0/patch/115/ecc/applications/ar_ecc.zip finished with response [{"STATUS":200,"logFileName":"import_20190529095227.log"}]
Imported application /tmp/staging/ar/12.0.0/patch/115/ecc/applications/ar_ecc.zip successfully
 
Importing application /tmp/staging/fa/12.0.0/patch/115/ecc/applications/fa_ecc.zip
ECC WEB ENTRY URL:http://demo.enginatics.com:80/ecc
ECC Application File:/tmp/staging/fa/12.0.0/patch/115/ecc/applications/fa_ecc.zip
Importing file /tmp/staging/fa/12.0.0/patch/115/ecc/applications/fa_ecc.zip finished with response [{"STATUS":200,"logFileName":"import_20190529095228.log"}]
Imported application /tmp/staging/fa/12.0.0/patch/115/ecc/applications/fa_ecc.zip successfully
 
Importing application /tmp/staging/okl/12.0.0/patch/115/ecc/applications/okl_ecc.zip
ECC WEB ENTRY URL:http://demo.enginatics.com:80/ecc
ECC Application File:/tmp/staging/okl/12.0.0/patch/115/ecc/applications/okl_ecc.zip
Importing file /tmp/staging/okl/12.0.0/patch/115/ecc/applications/okl_ecc.zip finished with response [{"STATUS":200,"logFileName":"import_20190529095229.log"}]
Imported application /tmp/staging/okl/12.0.0/patch/115/ecc/applications/okl_ecc.zip successfully
 
SUMMARY REPORT:
-----------------------------------------------
| Product| Application | Status|
-----------------------------------------------
| AP | ap_ecc.zip | Success |
| AR | ar_ecc.zip | Success |
| FA | fa_ecc.zip | Success |
| OKL | okl_ecc.zip | Success |
-----------------------------------------------

Loading product data to ECC

Run concurrent programs for each product to perform full data load into the ECC. Programs should also be scheduled to perform periodic incremental loads to update the data. For the full list of the loader concurrent programs please refer to Doc ID 2495053.1. For an overview of the many different load programs, you can also use the ECC Concurrent Programs report to check which ones are already scheduled.

Example for the Oracle Receivables : Receivables Command Center Data Load

To run this request you need to switch to Receivables responsibility as it’s not available under System Administrator responsibility. I used ‘Receivables manager’ responsibility.

Running ECC data load request
Running ECC data load request

To update data, requests can be rerun in INCREMENTAL_LOAD mode. Example of Payables Command Center Data Load:

Running ECC data load request

Providing users access to ECC

This step needs to be performed for the new command centers after the upgrade. Also perform this step if you notice any changes in the roles, responsibilities or permission sets names provided in the MOS Doc ID 2495053.1.
Product-specific roles are used to provide access to ECC.
For list of the roles please refer to Doc ID 2495053.1.
Below is the example of role assignment performed in our system.

Providing access manually

In Oracle E-Business Suite, log in to the User Management responsibility, and navigate to the Roles and Role Inheritance page.

Search for desired responsibility

Setting ECC access control

Click the “View In Hierarchy” icon for your responsibility

Setting ECC access control

Click the Add Node icon for your responsibility

Setting ECC access control

Search for the role you want to add and click ‘Select’

Setting ECC access control

Next step is to update the associated grant for the product-specific Enterprise Command Center roles to reference the specific responsibility as the security context.

Click on expand to see the added role and click on update icon for the new role:

Setting ECC access control

If this is the first responsibility to which you are adding to the role, click the Update icon for the grant you want to update.

Enter the name of the responsibility to which ECC role is added and click Apply

Setting ECC access control
Setting ECC access control

After this step Receivables Command Center should appear under Receivables Manager responsibility.

Testing Receivables Command Center
Testing Receivables Command Center

Note: If you don’t see function appear after the responsibility, you may need to clear EBS cache using Functional Administrator responsibility.

Automating access provision using script

To automate roles and grants configuration following script can be used. It should be ran from EBS run fs:

source EBSapps.env run
$FND_TOP/bin/UMX_ENDECA_RBACAuto.sh

It will prompt for csv file location, which should be prepared before running the script. If csv file is called UMX_ENDECA_RBAC.csv and located under same directory as UMX_ENDECA_RBACAuto.sh, it will be used automatically. Example of the file we used in our system to assign payables and receivables ecc roles to Payables manager, Receivables manager and ECC Developer:

PERMISSION_SET_CODE,RESPONSIBILITY_CODE,ENDECA_ROLE_CODE
AP_ECC_ACCESS_PS,FND_RESP|SQLAP|PAYABLES_MANAGER|STANDARD,UMX|AP_ECC_ACCESS_ROLE
AP_ECC_ACCESS_PS,FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD,UMX|AP_ECC_ACCESS_ROLE
AR_ECC_ACCESS_PS,FND_RESP|AR|RECEIVABLES_MANAGER|STANDARD,UMX|AR_ECC_ACCESS_ROLE
AR_ECC_ACCESS_PS,FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD,UMX|AR_ECC_ACCESS_ROLE
IAR_ECC_ACCESS_PS,FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD,UMX|IAR_ECC_ACCESS_ROLE
IAR_ECC_INT_ACCESS_PS,FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD,UMX|IAR_ECC_INT_ACCESS_ROLE

Example output:

[oracle@demo bin]$ ./UMX_ENDECA_RBACAuto.sh
 
APPS username: apps
 
APPS password:
 
Executing for Permission_set AP_ECC_ACCESS_PS , Responsibility_name FND_RESP|SQLAP|PAYABLES_MANAGER|STANDARD and Endeca_Role UMX|AP_ECC_ACCESS_ROLE
old 6: L_MENU_NAME varchar2(100) := '&1';
new 6: L_MENU_NAME varchar2(100) := 'AP_ECC_ACCESS_PS';
old 8: l_responsibility_name varchar2(300) := '&2';
new 8: l_responsibility_name varchar2(300) := 'FND_RESP|SQLAP|PAYABLES_MANAGER|STANDARD';
old 10: endeca_role_name varchar2(300) := '&3';
new 10: endeca_role_name varchar2(300) := 'UMX|AP_ECC_ACCESS_ROLE';
Completed Successfully.
 
PL/SQL procedure successfully completed.
Executing for Permission_set AP_ECC_ACCESS_PS , Responsibility_name FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD and Endeca_Role UMX|AP_ECC_ACCESS_ROLE
old 6: L_MENU_NAME varchar2(100) := '&1';
new 6: L_MENU_NAME varchar2(100) := 'AP_ECC_ACCESS_PS';
old 8: l_responsibility_name varchar2(300) := '&2';
new 8: l_responsibility_name varchar2(300) := 'FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD';
old 10: endeca_role_name varchar2(300) := '&3';
new 10: endeca_role_name varchar2(300) := 'UMX|AP_ECC_ACCESS_ROLE';
Completed Successfully.
 
PL/SQL procedure successfully completed.
Executing for Permission_set AR_ECC_ACCESS_PS , Responsibility_name FND_RESP|AR|RECEIVABLES_MANAGER|STANDARD and Endeca_Role UMX|AR_ECC_ACCESS_ROLE
old 6: L_MENU_NAME varchar2(100) := '&1';
new 6: L_MENU_NAME varchar2(100) := 'AR_ECC_ACCESS_PS';
old 8: l_responsibility_name varchar2(300) := '&2';
new 8: l_responsibility_name varchar2(300) := 'FND_RESP|AR|RECEIVABLES_MANAGER|STANDARD';
old 10: endeca_role_name varchar2(300) := '&3';
new 10: endeca_role_name varchar2(300) := 'UMX|AR_ECC_ACCESS_ROLE';
Role - Responsibility relationship already exists
Grant already exists
 
PL/SQL procedure successfully completed.
Executing for Permission_set AR_ECC_ACCESS_PS , Responsibility_name FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD and Endeca_Role UMX|AR_ECC_ACCESS_ROLE
old 6: L_MENU_NAME varchar2(100) := '&1';
new 6: L_MENU_NAME varchar2(100) := 'AR_ECC_ACCESS_PS';
old 8: l_responsibility_name varchar2(300) := '&2';
new 8: l_responsibility_name varchar2(300) := 'FND_RESP|FND|ECC_DEVELOPER_RESP|STANDARD';
old 10: endeca_role_name varchar2(300) := '&3';
new 10: endeca_role_name varchar2(300) := 'UMX|AR_ECC_ACCESS_ROLE';
Completed Successfully.
 
PL/SQL procedure successfully completed.

Access provision for all command centers.

I prepared UMX_ENDECA_RBAC.csv containing all responsibilities, permission sets and roles matched between each other.

CSE_ECC_ACCESS_PS,FND_RESP|CSE|CSE_SUPER_USER_RESP|STANDARD,UMX|CSE_ECC_ACCESS_ROLE
FA_ECC_ACCESS_PS,FND_RESP|OFA|FIXED_ASSETS_MANAGER|STANDARD,UMX|FA_M_ECC_ACCESS_ROLE
FA_ECC_ACC_ACCESS_PS,FND_RESP|OFA|FIXED_ASSETS_ACCOUNTANT|STANDARD,UMX|FA_A_ECC_ACCESS_ROLE
OZF_CLAIM_ECC_MENU,FND_RESP|OZF|OZF_USER|STANDARD,UMX|OZF_ECC_ACCESS_ROLE
OZF_CLAIM_ECC_MENU,FND_RESP|OZF|OZF_AR_DED_SET_RESP|STANDARD,UMX|OZF_ECC_ACCESS_ROLE
PO_CLM_ECC_CO_PS,PUR_CLM_SUPER_USER,UMX|PO_CLM_ECC_CO_ROLE
PO_CLM_ECC_PMO_PS,SELF_SERV_CLM_PURCHASING_5,UMX|PO_CLM_ECC_PMO_ROLE
CST_ECC_ACCESS_PS,FND_RESP|BOM|COST_MANAGEMENT|STANDARD,UMX|CST_ECC_ACCESS_ROLE
CST_ECC_ACCESS_PS,FND_RESP|CST|COST_MANAGEMENT|STANDARD,UMX|CST_ECC_ACCESS_ROLE
CST_ECC_ACCESS_PS,FND_RESP|GMF|OPM_FINANCIALS|STANDARD,UMX|CST_ECC_ACCESS_ROLE
CST_ECC_GMF_ACCESS_PS,FND_RESP|BOM|COST_MANAGEMENT|STANDARD,UMX|CST_ECC_GMF_ACCESS_ROLE
CST_ECC_GMF_ACCESS_PS,FND_RESP|CST|COST_MANAGEMENT|STANDARD,UMX|CST_ECC_GMF_ACCESS_ROLE
CST_ECC_GMF_ACCESS_PS,FND_RESP|GMF|OPM_FINANCIALS|STANDARD,UMX|CST_ECC_GMF_ACCESS_ROLE
CSD_ECC_RO_MGR_ACCESS_PS,FND_RESP|CSD|DEPOT REPAIR|STANDARD,UMX|CSD_ECC_RO_MGR_ACCESS_ROLE
CSD_ECC_RO_TECH_ACCESS_PS,FND_RESP|CSD|DEPOT REPAIR|STANDARD,UMX|CSD_ECC_RO_TECH_ACCESS_ROLE
WIP_ECC_ACCESS_PERM_SET,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,UMX|WIP_ECC_ACCESS_ROLE
EAM_ECC_ACCESS_PS,FND_RESP|EAM|MSU_VIS_OPS|STANDARD,UMX|EAM_ECC_ACCESS_ROLE
CSF_ECC_TASK_PS,FND_RESP|CSF|CONTROL TOWER|STANDARD,CSF_ECC_TASK_ACCESS_ROLE
PER_ECC_PERSON_SEARCH_PS,FND_RESP|PER|US_SHRMS_MANAGER|STANDARD,UMX|PER_ECC_PEOPLE_SEARCH_ROLE
CN_ICM_ECC_ACCESS_PS,FND_RESP|CN|CN_INC_COMP_MANAGER|STANDARD,UMX|CN_ICM_ECC_ACCESS_ROLE
INV_ECC_RCV_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,INV_ECC_RCV_ACCESS_ROLE
WSH_ECC_DASHBOARD_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,UMX|WSH_ECC_DASHBOARD_ACCESS_ROLE
INV_ECC_AGING_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,INV_ECC_AGING_ACCESS_ROLE
INV_ECC_CYCLE_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,INV_ECC_CYCLE_COUNTING_ACCESS_ROLE
INV_ECC_ACTIVITY_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,INV_ECC_ACTIVITY_ACCESS_ROLE
INV_ECC_ITEM_ACCESS_PS,FND_RESP|INV|INV_HTML|STANDARD,INV_ECC_ITEM_ACCESS_ROLE
INV_ECC_RCV_ACCESS_PS, ,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,INV_ECC_RCV_ACCESS_ROLE
WSH_ECC_DASHBOARD_ACCESS_PS,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,UMX|WSH_ECC_DASHBOARD_ACCESS_ROLE
INV_ECC_AGING_ACCESS_PS, FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,INV_ECC_AGING_ACCESS_ROLE
INV_ECC_CYCLE_ACCESS_PS,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,INV_ECC_CYCLE_COUNTING_ACCESS_ROLE
INV_ECC_ACTIVITY_ACCESS_PS,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,INV_ECC_ACTIVITY_ACCESS_ROLE
INV_ECC_ITEM_ACCESS_PS,FND_RESP|MSC|MFG_AND_DIST_SUPER_USER_APS|STANDARD,INV_ECC_ITEM_ACCESS_ROLE
IAR_ECC_ACCESS_PS,FND_RESP|AR|ARI_EXTERNAL|STANDARD,UMX|IAR_ECC_ACCESS_ROLE
IAR_ECC_ACCESS_PS,FND_RESP|AR|ARI_INTERNAL|STANDARD,UMX|IAR_ECC_ACCESS_ROLE
IAR_ECC_INT_ACCESS_PS,FND_RESP|AR|ARI_EXTERNAL|STANDARD,UMX|IAR_ECC_INT_ACCESS_ROLE
IAR_ECC_INT_ACCESS_PS,FND_RESP|AR|ARI_INTERNAL|STANDARD,UMX|IAR_ECC_INT_ACCESS_ROLE
INL_LCA_ECC_ACCESS_PS,FND_RESP|INL|INL|STANDARD,INL_LCA_ECC_ACCESS_ROLE
OKL_ECC_OKL_PS,FND_RESP|OKL|LEASE SUPER USER|STANDARD,UMX|OKL_ECC_ACCESS_ROLE
PN_ECC_PN_PS,FND_RESP|PN|PN_SU|STANDARD,UMX|PN_ECC_ACCESS_ROLE
ONT_ECC_PS,FND_RESP|ONT|ONT_HTMLUI_RESP|STANDARD,UMX|ONT_ECC_ROLE
JMF_ECC_ACCESS_PS,FND_RESP||JMF||JMF_SHIKYU_SUPER_USER||STANDARD,UMX|JMF_ECC_ACCESS_ROLE
AP_ECC_ACCESS_PS,FND_RESP|SQLAP|PAYABLES_MANAGER|STANDARD,UMX|AP_ECC_ACCESS_ROLE
GMO_ECC_ACCESS_PS,FND_RESP||GME||PRODUCTION SUPERVISOR||STANDARD,UMX|GMO_ECC_ACCESS_ROLE
PA_PPCC_ECC_ACCESS_PS,FND_RESP|PA|PA_PRM_PROJ_SU_SVCS|STANDARD,UMX|PA_PPCC_ECC_ACCESS_ROLE
PO_PPCC_ECC_ACCESS_PS,FND_RESP|PA|PA_PRM_PROJ_SU_SVCS|STANDARD,UMX|PO_PPCC_ECC_ACCESS_ROLE
PA_PPCC_ECC_ACCESS_PS,FND_RESP|PO|PO_PROJ_PROC_ECC_BUYER|STANDARD,UMX|PA_PPCC_ECC_ACCESS_ROLE
PO_PPCC_ECC_ACCESS_PS,FND_RESP|PO|PO_PROJ_PROC_ECC_BUYER|STANDARD,UMX|PO_PPCC_ECC_ACCESS_ROLE
PA_ECC_ACCESS_PS,FND_RESP|PA|PA_PRM_PROJ_SU_SVCS|STANDARD,UMX|PA_ECC_ACCESS_ROLE
PO_PCC_ECC_PS,FND_RESP|PO|PURCHASING_OPERATIONS|STANDARD,UMX|PO_PCC_ECC_ROLE
QA_ECC_ACCESS_PS,FND_RESP|QA|QA_SSQR_JSP|STANDARD,UMX|QA_ECC_ACCESS_ROLE
AR_ECC_ACCESS_PS,FND_RESP|AR|RECEIVABLES_MANAGER|STANDARD,UMX|AR_ECC_ACCESS_ROLE
CS_ECC_SR_MGR_PS,FND_RESP|CS|CS_ECC_SERVICE_MANAGER|STANDARD,UMX|CS_ECC_SR_MGR_ACCESS_ROLE
CS_ECC_SR_MGR_PS,FND_RESP|CS|CSZ_CS_SPECIALIST|STANDARD,UMX|CS_ECC_SR_MGR_ACCESS_ROLE
CS_ECC_SR_AGNT_PS,FND_RESP|CS|CS_ECC_SERVICE_MANAGER|STANDARD,UMX|CS_ECC_SR_AGNT_ACCESS_ROLE
CS_ECC_SR_AGNT_PS,FND_RESP|CS|CSZ_CS_SPECIALIST|STANDARD,UMX|CS_ECC_SR_AGNT_ACCESS_ROLE
OKS_ECC_ACCESS,FND_RESP|OKS|OKS_MANAGER|STANDARD,UMX|OKS_ECC_ACCESS_ROLE

Clear cache

Command centers didn’t appear under the responsibilities after running above script. It was fixed by clearing EBS cache using Functional Administrator responsibility.

Conclusion

At this stage ECC installation and integration is complete. Reminding you again that you can try ECC in our demo instance. Just log in as DEVELOPER and choose desired product responsibility and find associated command center menu entry.
Please leave your comments if this article helped you or you faced any issues – we’re always happy to help you.
And please check out Blitz Report which complements ECC nicely with the fast excel export feature.

Author: