Friday, August 16, 2019

View Other Users concurrent Request Output

View Other Users concurrent Request Output


R11
System Administrator à Profile à System
Search for profile à 'Concurrent: Report Access Level'

Level

Value

Result

Site

User

The user can only view the requests submitted by him

Responsibility

Responsibility

That user can also review the log and report output files from all requests submitted from the current responsibility

User

Responsibility

Any user of that responsibility can also view the log and report output files from all requests submitted by any other user of that responsibility



R12
Unfortunately in R12 profile 'Concurrent: Report Access Level' does not work, it is a bit more complex process to achieve this
In R12 this was replaced by Role Based Access Control. The UMX Role Based Access Control (RBAC) is to control who can view request output files.
Note :-  You should have SYSADMIN user access.
Functional Developer -> Core Services
 >> Search for 'Concurrent Requests'

Click on 'Concurrent Requests' and then on tab 'Object Instance Set'
Ø  Click Create Instance Set

 Ø  Give Name/Code/Description
Ø  For Predicate
è Enter below code if you want to see request output for all concurrent programs . 
&TABLE_ALIAS.request_id in(
select  cr.request_id
  from apps.fnd_concurrent_requests cr, apps.fnd_concurrent_programs cp
where cr.concurrent_program_id = cp.concurrent_program_id
     and cr.program_application_id = cp.application_id)
è Modify the above query based on your requirement.
n  Add and cp.concurrent_program_name  if you want to give access only for particular program name, etc.
Ø  'Apply' it and it will give the Confirmation with Code you have entered.
 >>> Now login as a SYSADMIN User.
Ø  Goto User Management > Role & Role Inheritance
è Click on 'Create Role'
      Ø  Category – Miscellaneous / Application – Application Object Library
      Ø  Role Code (Prefix UMX| will be added whatever you provide example : UMX|AKTEST)
Ø  Display Name/ Description
Ø  'Apply'
Ø  Click on 'Create Grant'
Ø  Provide Name / Description
Ø  Data Security ->  Object -> 'Concurrent Requests'
Ø  Click on 'Next'
Ø  Data Context Type -> 'Instance Set'
Ø  Instance Set  -> Instance you Created above, AKTEST
Ø  Click 'Next'
Ø  Set -> Set -> 'Request Operations'
  
Ø  Click on 'Next' -> Preview and then 'Finish'

Ø  It should give you the message for successful creation of Grant.
Known Issue
 

Sometimes it will give below Error. Just try 3-4 times, it should be fine.

Sorry didn't dig much into it to find the exact reason behind it.

Error Page

You have encountered an unexpected error. Please contact the System Administrator for assistance.
Goto 'User tab 
Ø  Search for the user you want to assign the grant.
Ø  Click  'Update'
Ø  Click 'Assign Role'
Ø  Search for Role you have created above 'View All Concurrent Requests outputs' (Code - UMX|AKTEST)
Ø  Give Justification
Ø  You can put active date from past to view previous requests outputs.


   Ø  DONE... :)

* Now assigned user can see the output of other user's request from the responsibility from  which that request had been launched.

>> You can also use the below script to assign the grant to a user.

begin
     wf_local_synch.PropagateUserRole(p_user_name => 'USERNAME'
                                                               ,p_role_name => 'UMX|AKTEST ');
     commit;
End;

Function Not Available To This Responsibility. Change Responsibilities Or Contact Your System Administrator

Error:
Function not available to this responsibility. Change responsibilities or contact your System Administrator 

Generally we are getting this type of error when we are using Help --> Diagnostics





Cause:

If you are not assign the 'Utilities:Diagnostics' Profile Option at any level ,we are getting this type of Error.

Solution:

Assign 'Utilities:Diagnostics' Profile Option at Responsibility or User Level

Navigation:

System Administrator --> Profile --> System



Here i am assigning this profile option at User Level
Enter User Name and Profile Option and then Click on Find button.

Assign Utilities:Diagnostics Profile option at user level Yes and save your work.


Now check your error. Now we should not get this type error in your form.


Oracle Apps 12.1.3 upgrade post upgrade steps for Oracle E-Business Suite Integrated SOA Gateway:

Oracle Apps 12.1.3 upgrade post upgrade steps for Oracle E-Business Suite Integrated SOA Gateway:


Oracle Apps 12.1.3 upgrade post upgrade steps for Oracle E-Business Suite Integrated SOA Gateway:

If you have upgraded the applications to 12.1.3 and you have SOA gateway integrated with EBSO, The below steps are mandatory to perform.

0)Techstack Upgrade

The Minimum patch set for Applications Server required for SOA is 10.1.3.5.0
A)upgrade your system to Oracle10g Application Server Patch Set 5 (10.1.3.5.0).

i)Apply the latest opatch
- cd $IAS_ORACLE_HOME
- mv OPatch OPatch_old

- unzip -d $IAS_ORACLE_HOME /tmp/p6880880_101000_LINUX.zip (Download the patch from support.oracle.com)
- chmod -R 755 OPatch
- $IAS_ORACLE_HOME/OPatch/opatch version
- OPatch Version: 1.0.0.0.63

ii)Install 10.1.3.5 Patchset 8626084
- Source the env file under $INST_TOP/ora/10.1.3

- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env
- uname -i
- If it is a 64-bit OS (x86_64) then do the following 
- linux32 ksh
- uname –i 
- It should give i386

iii)Verify the inventory and ensure it has proper values

iv)Invoke the runInstaller from VNC
- cd /patches/8626084/Disk1
- ./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc
- Screen 1) Select the 1013 ORACLE_HOME from the drop down list
- Screen 2) Provide the oc4jadmin password

- Complete the upgrade

Command to check version After the Upgrade:
- $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'

B)Verify the 10.1.2.X  Oracle Home version and the required version is 10.1.2.3:

Example:
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc | egrep 'Oracle Application Server 10g|Patch of Oracle Application Server 10g'
Oracle Application Server 10g                                    10.1.2.0.2
Patch of Oracle Application Server 10g                           10.1.2.3.0


1)Source the file $INST_TOP/ora/10.1.3/.env and then apply the following patches to the Oracle10g 
Application Server 10.1.3.5 Oracle Home using opatch:

- Source the env file under $INST_TOP/ora/10.1.3
- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env

Apply the below techstack patches using opatch 
- 9435187
- 9371120
- 9668283
- 7366746


2)Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3

A)Apply the following Oracle E-Business Suite patch:

i) 9668283

- unzip p9668283_10135_GENERIC.zip
- cd $INST_TOP/ora/10.1.3
- . ./$CONTEXT_NAME.env
- cd 9668283
- opatch apply

ii) 9905881
Apply the above patch 9905881 using adpatch 

B)Follow the configuration steps from Step 2 to Step 11 described in the section 3.3 Configuring 
Oracle E-Business Suite Integrated SOA Gateway Release 12.1.2 to enable Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3.  

i)Set applications environment and stop all application tier processes.

- From the applications instance $APPL_TOP, set the environment by running the APPS<CONTEXT_NAME>.env script
- Stop all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstpall

ii)Run TXK development script to install Oracle Application Server Adapter for Oracle Applications as shown below:

- $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp -applicationname=pcapps -oracleinternal=Yes  - oc4jpass=welcome12 -runautoconfig=No

Note: If the 'oc4jadmin' password for the OAFM oc4j instance is not known, then reset the password in the file  
 $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml before running the script. Take the backup of system-jazn-data.xml before resetting the password.
 Replace the modified system-jazn-data.xml with backup of system-jazn-data.xml after running the script.


        For example, if you want to reset the password to 'welcome12', below should be the entry:

              <user>
                  <name>oc4jadmin</name>
                  <display-name>OC4J Administrator</display-name>
                  <guid>23C8E4F0BDDE11DCBFB8AF3B7E0DDB2D</guid>
                  <description>OC4J Administrator</description>
                  <credentials>!welcome12</credentials>
              </user> 

iii)Run TXK deployment script to install forms-c4ws.ear and configure container Forms-c4ws J2EE group correctly, as shown below:
- $FND_TOP/bin/txkrun.pl -script=DeployForms-c4ws

iv)Enable the new container forms-c4ws. (By default, the new OC4J container forms-c4ws will be disabled.)

- To enable the new container forms-c4ws, modify the following values of context variables in the $CONTEXT_FILE:
- Set 's_forms-c4wsstatus' to "enabled".
- Set 's_forms-c4ws_nprocs' to "1".

v)Run AutoConfig on MT Node

vi)Start all application tier processes for the instance by running the script $ADMIN_SCRIPTS_HOME/adstrtal

vii)Enable ASADMIN user using the following steps:

         1. Log on to Oracle E-Business Suite using sysadmin/sysadmin.
         2. Select the User Management responsibility in the Navigator.
         3. Click the Users link from the navigation menu to open the User Maintenance window.
         4. Locate 'ASADMIN' user by entering information in the search area to retrieve the 'ASADMIN' user.
         5. Click the Update icon next to the ASADMIN user to open the Update User window.
         6. Remove the Active To date field and click Apply.
         7. Click the Reset Password icon next to the ASADMIN user to open the Reset Password window.
         8. Enter new password twice and click Submit.


viii)After activating the ASADMIN user, verify if the ASADMIN user has the 'Apps Schema Connect Role' (UMX|APPS_SCHEMA_CONNECT) role in wf_user_roles.

- If the 'Apps Schema Connect Role' role is not present in the wf_user_roles for the ASADMIN user, then run the 'Workflow Directory Services User/Role Validation' concurrent program to grant the role.
ix)Reset the 'ASADMIN' password in the file system.

 After 'ASADMIN' user is enabled from Oracle E-Business Suite, update the file

 $INST_TOP/ora/10.1.3/j2ee/oafm/config/system-jazn-data.xml as shown below to reset the password:

 <user>
 <name>ASADMIN</name>

 <display-name>Default Apps SOA User</display-name>
 <description>Used by SOAProvider for DB connection</description>
 <credentials>!<NEW PASSWORD></credentials>
 </user>

3)Bring up all the services and perform complete health check


Creating Additional Administrative Users

ewallet p12 vs cwallet sso

The  ewallet.p12  stores credentials and certificates protected by a user password, while  cwallet.sso  provides an obfuscated, random passw...