Asif's Oracle Repository

ADOP prepare phase failed with below error:   [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation below error reported in log adop logfile:   / u01/applprod/fs2/EBSapps/appl/au/12.0.0/perl/TXK/ADOPValidationUtils.pm line 1294.  No such file or directory /u01/applprod/fs2/EBSapps/appl/au/12.0.0/perl/TXK/ADOPValidationUtils.pm line 230.  solution: To fix this issue test the following to upload the missing PATCH context file to the database: step 1. Get the value of your patch context file. set the patch enviorment echo $CONTEXT_FILE  step2 : Execute the following command on the run filesystem to upload the patch context file to the database.   $ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer action=upload contextfile='/u01/applprod/fs1/inst/apps/TESTDB2_ebs_appnode28v/appl/admin/TESTDB2_ebs_appnode28v.xml' logfile=/tmp/patchctxupload.log  Step 3: Following query to check the updated context file  SQL> select distinct(...

Report Access Level  EBS version in R12.2.4. Below are method to  restriction/disable viewing concurrent requests submitted by other users in EBS R12.2   11i there is a profile option: "Concurrent: Report Access Level" that defines who can access the output of concurrent requests. It could be set to 'User' or 'Responsibility'. When set to Responsibility, the responsibility the report was created under must be assigned to the user who wishes to view the report. Note: In previous releases, the Concurrent: Report Access Level profile was used to control privileges to report output files and log files generated by a concurrent program. This profile is no longer used    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.  Below are steps which  I performed to restriction on view except sysadmin user.     Functional Administrator --...