Solved: Workflow Error When Clicking View Status Diagram on Status Monitor

When you want to view the status diagram of workflow process on status monitor page from the workflow administrator responsibility, maybe you get the error page like below:
The solution for the above issue is set the Server Timezone profile option on the Site level.

After that you can able to see the status diagram in workflow status monitor.

Solved: You cannot run a page which is not Self Secured when the MAC fails

Sometimes we will face below issues in R12.

Issue 1:
You have insufficient privileges for the current operation. Please contact your System Administrator.

You cannot run a page which is not Self Secured when the MAC fails.

Resolution:

Set the below 3 profiles to None
1) FND Function Validation Level
2) FND Validation Level
3) Framework Validation Level

JDev-2

Issue 2:
Unexpected URL parameters have been detected and will be ignored Solution:

Resolution:

In JDeveloper, go to menu Tools–>Embedded OC4J Server Preferences–>Global–>Startup–>Select Default Local IP Address.
JDev-3


Oracle Apps Log Files Locations in R12

Autoconfig log file:
Apps:
$INST_TOP/appl/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adconfig.log $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/NetServiceHandler.log

Startup/Shutdown Log files:
$INST_TOP/logs/appl/admin/log

Apache, OC4J and OPMN:
$LOG_HOME/ora/10.1.3/Apache 
$LOG_HOME/ora/10.1.3/j2ee 
$LOG_HOME/ora/10.1.3/opmn

Patch log:
$APPL_TOP/admin/$SID/log/
Workflow Mailer log:
$APPLCSF/$APPLLOG/FNDCPGSC*.txt

Concurrent log:
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log
OAM (Oracle Application Manager) log:
$APPLRGF/oam/

Clone log:
Preclone log files in source instance

Apps:
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log)

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

Clone log files in target instance:
Apps :
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log

- Alert Log File:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log
Concurrent OUT Directory:
$APPLCSF/$APPLOUT  or $APPLCSF/out
APPL_TOP - this is the top level directory for the Applications
  • $APPLCSF - the top level directory where the concurrent manager stores the log and out files of concurrent requests
  • $APPLCSF/$APPLLOG - concurrent request log files( As describe above)
  • $APPLCSF/$APPLOUT - concurrent request out files( As describe above)
  • $APPLTMP - Applications temporary files
  • $APPLPTMP - PL/SQL temporary files   or /usr/tmp (default tmp directory)
Startup and shutdown messages:
–Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/logs/appl/conc/log (CM log files)
Other log files in R12

1) Database Tier
1.1) Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.log

1.2) Alert Log Files :
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

1.3) Network Logs :
$ORACLE_HOME/network/admin/$SID.log

1.4) OUI Logs :
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs

2) Application Tier

$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs

Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/log
$IAS_ORACLE_HOME/j2ee/oafm/log
$IAS_ORACLE_HOME/j2ee/oacore/log
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log
Patching related log files in R12 :
Application Tier– adpatch log – $APPL_TOP/admin//log/
Developer (Developer/Forms & Reports 10.1.2) Patch – $ORACLE_HOME/.patch_storage
Web Server (Apache) patch – $IAS_ORACLE_HOME/.patch_storage
Database Tier opatch log – $ORACLE_HOME/.patch_storage

Purge/Delete Completed Concurrent Requests in Apps

Error:Delete/Purge COMPLETED concurrent requests

Concurrent request history should not exceed 50K rows, or else it will start impacting on performance

SQL> select count(*) from FND_CONCURRENT_PROCESSES;

COUNT(*)
----------
552

SQL> select count(*) from FND_CONCURRENT_REQUESTS;

COUNT(*)
----------
85009 ==>>> Should always be below 50K, Else run "Purge Concurrent Request"
SQL>


SQL> select count(*) from FND_CONCURRENT_REQUESTS

2 where request_date > sysdate-7;

COUNT(*)
----------
19757

SQL> col "Min request|Date" for a20;

SQL> col "Max request|Date" for a20;

SQL> select min(request_date) "Min request|Date",max(request_date) "Max request|Date" from FND_CONCURRENT_REQUESTS;

Min request|Date Max request|Date
-------------------- --------------------
18-NOV-09 01-NOV-11

SQL>


To clean old history of "COMPLETED" requests, follow the below note, to purge the queue

Concurrent Processing Tables and Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) [ID 104282.1]

System Administrator -> Requests -> Run



Select "Single Request"





Mode = 14 days - delete all older than 14 days. Don't make this window to small.




To view the above submitted request, do the following


Enter the request ID and "Find"





While Running:




Status on successful completion is shown below "Completed", "Normal"


Extract from the Log File:

FNDCPPUR module: Purge Concurrent Request and/or Manager Data
+---------------------------------------------------------------------------+
Current system time is 01-NOV-2011 12:57:03
+---------------------------------------------------------------------------+
Purged 46616 entrie(s) from FND_CONCURRENT_REQUESTS :-01-NOV-2011 13:07:22

Purged 0 entrie(s) from FND_FILE_TEMP :-01-NOV-2011 13:07:22

Purged 7082 entrie(s) from FND_CRM_HISTORY :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_TM_EVENTS :-01-NOV-2011 13:07:25

Purged 346 entrie(s) from FND_TEMP_FILES :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_ENV_CONTEXT :-01-NOV-2011 13:07:46

Purged 1 entrie(s) from FND_DUAL :-01-NOV-2011 13:07:46

Purged 2 entrie(s) from FND_CONFLICTS_DOMAIN :-01-NOV-2011 13:07:46

+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+

R12 - Enabling/Disabling "FND: Debug Log Enabled" from Putty

When trying to enable “FND: Debug Log Enabled”, in the below window, it might sometime be that the option to set it to Yes/No, is grayed out, and cannot be changed. Without spending too much time fixing this, you can also enable/disable it from within a sqlplus session, connected as the apps user.

To enable it, do the following

SQL> SELECT PROFILE_OPTION_ID,PROFILE_OPTION_NAME FROM FND_PROFILE_OPTIONS_VL
WHERE START_DATE_ACTIVE <= SYSDATE
and NVL(END_DATE_ACTIVE,SYSDATE) >= SYSDATE
and ( SITE_ENABLED_FLAG = 'Y' or APP_ENABLED_FLAG = 'Y' or RESP_ENABLED_FLAG = 'Y' or USER_ENABLED_FLAG = 'Y' or SERVER_ENABLED_FLAG = 'Y' or SERVERRESP_ENABLED_FLAG = 'Y' or ORG_ENABLED_FLAG = 'Y')
and ( UPPER(USER_PROFILE_OPTION_NAME) LIKE '%FND%DEBUG%'
and (USER_PROFILE_OPTION_NAME LIKE '%f%' or USER_PROFILE_OPTION_NAME LIKE '%F%'))
order by user_profile_option_name;
PROFILE_OPTION_ID PROFILE_OPTION_NAME
----------------- -----------------------------------
             4176 AFLOG_ENABLED
             3098 AFLOG_FILENAME
             3099 AFLOG_LEVEL
             8470 AFLOG_BUFFER_MODE
             3100 AFLOG_MODULE
             8468 DEBUG RULE THRESHOLD
6 rows selected.
SQL>
Description: cid:image003.png@01CD17D0.99AE3620
SQL>
col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES
where profile_option_id in ('4176','3098','3099');
SQL>
Description: cid:image005.png@01CD17D0.99AE3620
SQL> update FND_PROFILE_OPTION_VALUES
set PROFILE_OPTION_VALUE = 'Y'
where PROFILE_OPTION_VALUE = 'N'
and PROFILE_OPTION_ID = 4176; 
Description: cid:image006.png@01CD17D0.99AE3620
2 rows updated.
SQL> commit;
Commit complete.
SQL>
col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES 
where profile_option_id in ('4176','3098','3099');  => All will show ‘Y’ now


Description: cid:image007.png@01CD17D0.99AE3620
To disable it, just set it to NO again:
SELECT PROFILE_OPTION_ID,PROFILE_OPTION_NAME FROM FND_PROFILE_OPTIONS_VL
WHERE START_DATE_ACTIVE <= SYSDATE
and NVL(END_DATE_ACTIVE,SYSDATE) >= SYSDATE
and ( SITE_ENABLED_FLAG = 'Y' or APP_ENABLED_FLAG = 'Y' or RESP_ENABLED_FLAG = 'Y' or USER_ENABLED_FLAG = 'Y' or SERVER_ENABLED_FLAG = 'Y' or SERVERRESP_ENABLED_FLAG = 'Y' or ORG_ENABLED_FLAG = 'Y')
and ( UPPER(USER_PROFILE_OPTION_NAME) LIKE '%FND%DEBUG%'
and (USER_PROFILE_OPTION_NAME LIKE '%f%' or USER_PROFILE_OPTION_NAME LIKE '%F%'))
order by user_profile_option_name

PROFILE_OPTION_ID    PROFILE_OPTION_NAME
-----------------    -------------------
4176                 AFLOG_ENABLED
3098                 AFLOG_FILENAME
3099                 AFLOG_LEVEL
8479                 AFLOG_BUFFER_MODE
3100                 AFLOG_MODULE
8465                 DEBUG RULE THRESHOLD

col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES
where profile_option_id in ('4176','3098','3099');
PROFILE_OPTION_ID PROFILE_OP
----------------- ----------
          3099       1
          4176       Y
          3098       NULL
SQL>
update FND_PROFILE_OPTION_VALUES
set PROFILE_OPTION_VALUE = 'N'
where PROFILE_OPTION_VALUE = 'Y'
and PROFILE_OPTION_ID = 4176;  => AFLOG_ENABLED will show ‘N’ now


How to View/Access Other User Concurrent Request in Oracle Apps R12

When user OPERATIONS submit a request at System Administratorresponsibility, this user can see the log and output files of this request. But the other user (ex: SYSADMIN) cannot do that even has the same responsibility. If we use the View All Concurrent Requests (System Administrator Mode) form, we only can see the request but not the output file of this request.
So, if we want to access the request output of the same responsibility from another user’s requests, then we need to follow the below setup steps:
1. Login as SYSADMIN with Functional Developer responsibility and update the object Concurrent Requests
1.a. Search Concurrent Requests object and click the link to update it.
CR_1
1.b. Create new Instance Set
CR_2
1.c. Enter Name, Code, Description and Predicate for the new instance Set.
Predicate:
&TABLE_ALIAS.request_id in (select cr.request_id from fnd_concurrent_requests cr where cr.responsibility_id = fnd_global.resp_id and cr.responsibility_application_id = fnd_global.resp_appl_id)
.
CR_3

1.d. New Instance Set successful created.
CR_4

2. Login as SYSADMIN with User Management responsibility and using theRoles and Role Inheritance Tab
2.a. Create Role and then create a Grant for the Role, Data Security Object choose Concurrent Requests
RRI_1
RRI_2
RRI_3
2.b. Choose the Data Context Type Instance Set and choose the Instance Set created in above step (EY – Access Request Output of Same Responsibility)
RRI_4
2.c. Choose Permission Set Request Operations
RRI_5
2.d. Role and Grant created.
RRI_6

3. Assign the role to users as needed. The users with this role will be able to see the log and output files for the same as responsibility.
3.a. Query the user that you want to add this new role and click Update.
UR_1
3.b. Assign the new Role and Apply to activated
UR_2
UR_3

4. User OPERATIONS submit request Signon Audit Users with Request ID 5831028.User SYSADMIN will be able to find the Request ID 5831028 and the View Output and View Log buttons are Enable also.
OPR_CR
SYS_CR
But if otherwise, user OPERATIONS cannot find the Request that userSYSADMIN submitted, because the Role just grant to the user SYSADMIN.
Reference: Doc ID 804296.1

R12 - How to Find XML Publisher Version

Method One: MetaInfo.class

The version of a specific Java Class has a one to one relationship with the currently installed version of Oracle XML Publisher.

/home/applprod >strings $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class|grep -i 'XML Publisher'

Oracle XML Publisher 5.6.3

/home/applprod >



Version 5.6.3 ships with update pack 12.1.3, which is Patch 8919491

“Patch R12.ATG_PF.B.delta.3: Oracle Applications Technology 12.1.3 Product Family Release Update Pack”

Method Two: SQL Query
SELECT DECODE (bug_number
, ‘3554613’, ‘4.5.0’
, ‘3263588’, ‘XDO.H’
, ‘3822219’, ‘5.0.0’
, ‘4236958’, ‘5.0.1’
, ‘4206181’, ‘5.5.0’
, ‘4561451’, ‘5.6.0’
, ‘4905678’, ‘5.6.1’
, ‘5097966’, ‘5.6.2’
, ‘5472959’, ‘5.6.3’) PATCH, bug_number
FROM ad_bugs
WHERE bug_number IN
(‘3554613′
, ‘3263588’
, ‘3822219’
, ‘4236958’
, ‘4206181’
, ‘4561451’
, ‘4905678’
, ‘5097966’
, ‘5472959’);
Method Three: Output PDF of the report (Document Properties)

doc_properties
 

R12 - GL-Receiving India Drill Down Query

Here is the query for Link between General Ledger and Receiving India data's.

SELECT msib.segment1 item,
  msib.description,
  rsh.receipt_num,
  mp.organization_code,
  gjl.accounted_dr,
  gjl.accounted_cr,
  gjh.je_source,
  gjh.je_category
FROM apps.gl_je_headers gjh,
  apps.gl_je_lines gjl,
  apps.gl_code_combinations_kfv gcc,
  apps.gl_import_references gir,
  apps.rcv_transactions rt,
  apps.rcv_shipment_headers rsh,
  apps.rcv_shipment_lines rsl,
  apps.gl_je_batches gjb,
  apps.mtl_parameters mp,
  apps.mtl_system_items_b msib
WHERE gjh.je_header_id = gjl.je_header_id
AND gjh.je_header_id   = gir.je_header_id
AND gir.je_header_id   = gjl.je_header_id
AND gir.je_line_num    = gjl.je_line_num
AND gjb.je_batch_id    = gir.je_batch_id
AND GJH.JE_SOURCE      = 'Purchasing India'
AND gjh.period_name    ='Nov-14'
AND gjl.reference_2 = 'India Localization Entry'
AND gjl.code_combination_id = gcc.code_combination_id
AND rt.organization_id      = mp.organization_id
AND rt.transaction_id       = gjl.reference_5
AND rt.shipment_header_id   = rsh.shipment_header_id
AND rsl.shipment_header_id  = rsh.shipment_header_id
AND rsl.shipment_line_id    = rt.shipment_line_id
AND msib.inventory_item_id  = rsl.item_id
AND msib.organization_id    = rt.organization_id
AND gjl.period_name        IN
  (SELECT DISTINCT period_name
  FROM APPS.GL_PERIODS
  WHERE START_DATE BETWEEN :P_FROM_PERIOD AND :P_TO_PERIOD
  );

Note: This one was not linked with India Localization SLA Tables, its a direct link between GL and Localization Info's

Difference between Oracle E-Business Suite R12.1 and R12.2

A journey from Oracle E-Business Suite R12.1 to R12.2:

I will try to analyze architectural overview of the latest updates, installation and upgrade options, new configuration options, and new tools for hot-cloning and automated “lights out” cloning in R12.2.

Oracle E-Business Suite 12.1 Architecture

Oracle E-Business Suite 12.2 Architecture

Release 12.2 will replace Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g

Release 12.2 Database tier will run RDBMS 11gR2 to support online patching



There will be number of updates coming in release R12.2, from a technology stack perspective, EBS 12.2 will be notable for two things:

1-Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g

EBS 12.2 will use WebLogic Server from Fusion Middleware 11g in place of OC4J 10g as part of the release’s internal technology stack. Other additional new Fusion Middleware 11g components used will include WebLogic JSP and UIX 11g

2-Online Patching support via 11gR2 Edition-Based Redefinition

EBS 12.2 will use the 11gR2 Database’s Edition-Based Redefinition features to provide support for Online Patching. Edition-Based Redefinition is really exciting new technology. From the 11gR2 Application Developer’s Guide:

“Edition-based redefinition enables you to upgrade the database component of an application while it is in use, thereby minimizing or eliminating down time.

“To upgrade an application while it is in use, you copy the database objects that comprise the application and redefine the copied objects in isolation. Your changes do not affect users of the application—they continue to run the unchanged application. When you are sure that your changes are correct, you make the upgraded application available to all users.”

It is not released yet but It will include significant changes to the Application Server architecture, It will use RDBMS Version 11gR2 or higher, It will change Patching, Cloning, the User Experience

Comparison of Oracle E-Business Suite 12.1 vs 12.2 Installation Steps
Oracle E-Business Suite 12.1 installation

Database Technology Stack
Database
Apps Technology Stack
Apps File System


Oracle E-Business Suite 12.2 installation
Following will be main features planned for R12.2 installations:
Native Technology Stack Install
Database RMAN Restore
Dual File System
Optional 11g Home for Upgrades
WebLogic Server (WLS)
Graphical UI to manage WLS Domain
Administration (Start/Stop WLS Instances)
Configuration (Config and Deploy, Cluster, Host, JDBC, JMS Messaging)
Monitoring (Server & Application Performance)
Troubleshooting (Performance Tuning, Log Viewer)

Following will be main features planned for R12.2 Native Technology Stack Install:
Better integration with Oracle
Universal Installer
Faster Technology Stack Installation
Silent-mode calls to install and configure Oracle Database 11.2, WebLogic Server (WLS) and Oracle HTTP Server (OHS)
AutoConfig Integration


Following will be main features planned for R12.2 Database RMAN Restore:
Simplifies Integration with Grid Infrastructure
Seamless integration with different storage methods (OCFS2, NFS, etc)
Faster integration with Automatic Storage Management (ASM)

Following will be main features planned for R12.2 Dual File System:
Online Patching allows users to continue using the application while patching
Dual File System allows replacing files with minimum downtime
Improves High Availability

Dual Port Pool configuration
Easier port assignments
Allows port customization in runtime and patching file systems

Following will be main features planned for R12.2 Optional 11g Home for Upgrades:
Allow integration with an existing 11gR2 Oracle Home
Simplified Technology Stack Upgrade
Reduced Upgrade time

Following will be main features planned for R12.2 WebLogic Server (WLS):
Graphical User Interface
WebLogic Scripting Tool (WLST)
High Availability & Failover
Consolidated Administration, Configuration and Deployment
Monitoring & Messaging
Troubleshooting framework
Integration with OAM