How To Find Oracle Application File Versions.

How To Find Oracle Application File Versions.

In this post, sharing the way of finding the correct version of Oracle Applicatins file version of different component. This should be helpful while patching the applications.

Use the following information for the appropriate file type.

FORM 

adident
cd $AR_TOP/forms/US
Ex. adident Header ARXTWLIN.fmx

strings -a  form.frm |  grep  Revision
Ex.
cd $AU_TOP/forms/US
strings -a POXPOVCT.fmb | grep Revision

Use \Help Version

Or Help, About Oracle Applications

REPORT
cd $AR_TOP/reports
adident
adident Header report.rdf
Ex. adident Header ARBARL.rdf

strings -a  report.rdf  |  grep  Header
Ex.
strings -a ARBARL.rdf  |  grep Header

SQL 
more  sqlscript.sql  Ex.  more ARTACELO.sql

The version will be in a line that starts with 'REM  $Header', and should be one of the first lines in the .sql file.
grep '$Head' sqlscript.sql
Ex.
grep '$Head' ARTACELO.sql

BIN or EXECUTABLE 
An executable in the bin directory will contain numerous C code modules, each with its own version. All of the following examples use ident or strings,
but the difference is what you grep for.

1.  Get ALL file versions contained in the executable.
adident Header executable (Ex. adident Header RACUST)
strings -a  executable  |  grep  Header  (Ex. strings -a RACUST | grep Header)

2.  Get ALL of the product specific file versions.
adident  Header executable (Ex.  adident Header RACUST)
strings -a  executable  |  grep  Header
(Ex.  strings -a  RACUST  |  grep  Header)

3.  Get only the version of a specified module.
strings -a  executable  |  grep  module  (Ex. strings -a RAXTRX | grep raaurt)

4.   A Collection of class file versions

from the directory where the classfile exists in a command prompt run the following:
strings -a Classname.class | grep Header

Get ALL of the product specific file versions.
  
strings -a  executable  |  grep  'Header: product_short_name'
cd $FND_TOP/bin
strings -a WFLOAD | grep 'Header: afspc'
        
Get only the version of a specified module.
  
strings -a  executable  |  grep  module

ORACLE REPORTS 
From the form, select Help, About Oracle Reports.

RDBMS 
1. Use \Help Version
2. Or Help, About Oracle Applications
3. Get into SQL*Plus using any userid/password. You will get a string that tells you the PL/SQL version and data

Purging Strategy for eBusiness Suite 11i

Purging Strategy for eBusiness Suite 11i


In this Document
Abstract
History
Details
  Concurrent Jobs to purge data
  Additional Notes
Summary
References
APPLIES TO:

Oracle Application Object Library - Version 11.5.10.0 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
Checked for relevance on 30-NOV-2013
ABSTRACT

There is no single Archive/Purge routine that is called by all modules within eBusiness Suite, instead each module has module specific archive/purge procedures.
   
This note lists the Purging routines available for the "System Administrator" (FND module)   Not all of these purging processes will be appropriate for all customers, so review the documentation to confirm which are necessary for your own environment and how often they should be run.

Update : November 2008  - since this note was written, a much more comprehensive article has been published in Note 752322.1 "Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and Information Lifecycle Management"

HISTORY

Author :  Mike Shaw
Create Date 18-Aug-2008

DETAILS

Concurrent Jobs to purge data

Purge Obsolete Workflow Runtime Data (FNDWFPR)
 Oracle Applications System Administrators Guide - Maintenance Release 11i (Part No. B13924-04)
 Note 132254.1  Speeding up and Purging Workflow
 Note 277124.1  FAQ on Purging Oracle Workflow Data
 Note 337923.1  A closer examination of the Concurrent Program Purge Obsolete Workflow Runtime Data

Purge Debug Log and System Alerts (FNDLGPRG)
  Note 332103.1  Purge Debug Log And System Alerts Performance Issues

Purge Signon Audit data (FNDSCPRG)
  Note 1016344.102   What Tables Does the Purge Signon Audit Data Concurrent Program Affect?
  Note 388088.1   How To Clear The Unsuccessful Logins

Purge Concurrent Request and/or Manager Data (FNDCPPUR)
Oracle Applications System Administrator Guide - Maintenance Release 11i (Part No. B13924-04)
   Note 565942.1   Which Table Column And Timing Period Does The FNDCPPUR Purge Program Use
   Note 104282.1  Concurrent Processing Tables and Purge Concurrent Request and/or Manager Data Program (FNDCPPUR)
 Note 92333.1   How to Optimize the Process of Running Purge Concurrent Request and/or Manager Data (FNDCPPUR)

Delete Diagnostic Logs (DELDIAGLOG)
 Note 466593.1   How To Delete Diagnostic Logs and Statistics?

Delete Diagnostic Statistics (DELDIAGSTAT)
 Note 466593.1   How To Delete Diagnostic Logs and Statistics?

Purge FND_STATS History Records (FNDPGHST)
  Oracle Applications System Administrators Guide - Configuration Release 11i (Part No. B13925-06)
   Note 423177.1  Date Parameters For "Purge Fnd_stats History Records" Do Not Auto-Increment

Page Access Tracking Purge Data (PATPURGE)
  Note 413795.1   Page Access Tracking Data Purge Concurrent Request Fails With Ora-942
  Note 461897.1   Which Tables store the Page Access Tracking Data?
  Note 402116.1   Page Access Tracking in Oracle Applications Release 12

Purge Obsolete Generic File Manager Data (FNDGFMPR)
 Oracle Applications System Administrators Guide - Configuration Release 11i (Part No. B13925-06)
  Note 298698.1   Avoiding abnormal growth of FND_LOBS table in Application
  Note 555463.1   How to Purge Generic or Purchasing Attachments from the FND_LOBS Table

Summarize and Purge Concurrent Request Statistics (FNDCPCRS)
(no references found)

Purge Inactive Sessions (ICXDLTMP)
  Note 397118.1  Where Is 'Delete Data From Temporary Table'  Concurrent Program - ICXDLTMP.SQL

Purge Obsolete ECX Data (FNDECXPR)
  Note 553711.1   Purge Obsolete Ecx Data Error ORA-06533: Subscript Beyond Count
  Note 338523.1   Cannot Find ''Purge Obsolete Ecx Data'' Concurrent Request
  Note 444524.1   About Oracle Applications Technology ATG_PF.H Rollup 6

    The tables being purged by "Purge Obsolete ECX Data (FNDECXPR)" are:

ecx_error_msgs
ecx_msg_logs
ecx_outbound_logs
ecx_external_retry
ecx_inbound_logs
ecx_outbound_logs
ecx_external_logs
ecx_oxta_logmsg
ecx_doclogs
Purge Rule Executions (FNDDWPURG)
      The table being purged by "Purge Rule Executions (FNDDWPURG) is:

fnd_debug_rule_executions
Additional Notes

You can monitor and run purging programs through OAM by navigating to the Site Map--> Maintenence --> Purge section.

SUMMARY

Purging of un-needed data is an activity that needs to be performed on all systems to ensure best performance and minimize disk space requirements.   This note outlines some of the processes that may be required from the FND perspective

REFERENCES

NOTE:104282.1 - Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR)
NOTE:132254.1 - Speeding Up And Purging Workflow
NOTE:277124.1 - FAQ on Purging Oracle Workflow Data
NOTE:298698.1 - Avoiding abnormal growth of FND_LOBS table in Applications 11i
NOTE:332103.1 - Purge Debug Log And System Alerts Performance Issues
NOTE:337923.1 - A Closer Examination Of The Concurrent Program Purge Obsolete Workflow Runtime Data
NOTE:338523.1 - Cannot Find The Purge Obsolete ECX Data Concurrent Request
NOTE:387459.1 - ATG Supplied Data Purge Requests
NOTE:402116.1 - Page Access Tracking in Oracle Applications Release 12
NOTE:388088.1 - How to Purge Data from the FND_UNSUCCESSFUL_LOGINS Table?
NOTE:397118.1 - Where Is 'Delete Data From Temporary Table' Concurrent Program - ICXDLTMP.SQL
NOTE:413795.1 - Page Access Tracking Data Purge Concurrent Request Fails With Ora-942
NOTE:423177.1 - Date Parameters For "Purge Fnd_stats History Records" Do Not Auto-Increment
NOTE:444524.1 - About Oracle Applications Technology ATG_PF.H Rollup 6
NOTE:461897.1 - Which Tables Store the Page Access Tracking Data?
NOTE:466593.1 - How To Delete Diagnostic Logs and Statistics?
NOTE:553711.1 - Purge Obsolete Ecx Data Error ORA-06533: Subscript Beyond Count
NOTE:555463.1 - How to Purge Generic or Purchasing Attachments from the FND_LOBS Table
NOTE:565942.1 - Which Table Column And Timing Period Does The FNDCPPUR Purge Program Use
NOTE:1016344.102 - Concurrent Processing - List of Tables Accessed by the Purge Signon Audit Data Concurrent Program
NOTE:752322.1 - Reducing Your Oracle E-Business Suite Data Footprint using Archiving, Purging, and Information Lifecycle Management
NOTE:92333.1 - Concurrent Processing - How to Optimize the Process of Running Purge Concurrent Request and/or Manager Data (FNDCPPUR)

Coldbackup EBS Script

#Runs preclone process in DB Tier
su - oracle /u01/d01/tech_st/11.1.0/appsutil/scripts/JPROD_training/adpreclone.pl dbTier apps/apps
#Runs preclone process in Apps Tier
su - applmgr /u01/d02/inst/apps/JPROD_training/admin/scripts/adpreclone.pl appsTier apps/apps
#Shutdown process for Apps then DB
su - applmgr /u01/d02/inst/apps/JPROD_training/admin/scripts/adstpall.sh apps/apps
su - oracle /u01/d01/tech_st/11.1.0/appsutil/scripts/JPROD_training/addbctl.sh stop immediate
su - oracle /u01/d01/tech_st/11.1.0/appsutil/scripts/JPROD_training/addlnctl.sh stop JPROD
#Creates a new folder with current date
NOWDATE=`date +%d-%m-%y-%H_JPRODBKP`
export NOWDATE
mkdir /root/Desktop/$NOWDATE
#zip all the Tiers of Database and Apps
#Backup inst (in Apps Tier)
NOWDATE=`date +%d-%m-%y-%H_Apps_inst`
export NOWDATE
tar cvf - /u01/d02/inst | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#zip all the Tiers of Database and Apps
#Backup inst (in Apps Tier)
NOWDATE=`date +%d-%m-%y-%H_Apps_inst`
export NOWDATE
tar cvf - /u01/d02/inst | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#
#Backup apps  (in Apps Tier)
NOWDATE=`date +%d-%m-%y-%H_Apps_apps`
export NOWDATE
tar cvf - /u01/d02/apps | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#
#Backup apps_st (in DB Tier)
NOWDATE=`date +%d-%m-%y-%H_DB_apps_st`
export NOWDATE
tar cvf - /u01/d01/apps_st | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#
#Backup Archive (in DB Tier)
NOWDATE=`date +%d-%m-%y-%H_DB_Archive`
export NOWDATE
tar cvf - /u01/d01/Archive | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#
#Backup tech_st (in DB Tier)
NOWDATE=`date +%d-%m-%y-%H_DB_tech_st`
export NOWDATE
tar cvf - /u01/d01/tech_st | gzip -c > /root/Desktop/`date +%d-%m-%y-%H_JPRODBKP`/$NOWDATE.tgz
#After complition of zipping process it will start the DB and Apps automatically
su - oracle /u01/d01/tech_st/11.1.0/appsutil/scripts/JPROD_training/addbctl.sh start
su - oracle /u01/d01/tech_st/11.1.0/appsutil/scripts/JPROD_training/addlnctl.sh start JPROD
su - applmgr /u01/d02/inst/apps/JPROD_training/admin/scripts/adstrtal.sh apps/apps
#

Query to find the ATG Patch Set Level

For 11i
=====
SET head off Lines 120 pages 100
col p_num format A65
col bug_number format A10
col patch_name format A10
select bug_number, decode(bug_number,
'3438354', '11i.ATG_PF.H'
,'4017300' ,'11i.ATG_PF.H.RUP1'
,'4125550' ,'11i.ATG_PF.H.RUP2'
,'4334965' ,'11i.ATG_PF.H RUP3'
,'4676589' ,'11i.ATG_PF.H RUP4'
,'5382500' ,'11i.ATG_PF.H RUP5 HELP'
,'5473858' ,'11i.ATG_PF.H.5'
,'5674941' ,'11i.ATG_PF.H RUP5 SSO Integrat'
,'5903765' ,'11i.ATG_PF.H RUP6'
,'6117031' ,'11i.ATG_PF.H RUP6 SSO 10g Integration'
,'6330890' ,'11i.ATG_PF.H RUP6 HELP'
) p_num, last_update_date
FROM ad_bugs
WHERE bug_number
IN ( '3438354', '4017300', '4125550', '4334965', '4676589', '5382500', '5473858', '5674941', '5903765', '6117031', '6330890' );


For R12
======

SET head off Lines 120 pages 100
col p_num format A65
col bug_number format A10
col patch_name format A10

select bug_number, decode(bug_number,
'5917344', 'R12.ATG_PF.A.DELTA.2',
'6077669', 'R12.ATG_PF.A.DELTA.3',
'6272680', 'R12.ATG_PF.A.DELTA.4 '
) p_num, last_update_date
FROM ad_bugs
WHERE bug_number
IN ('5917344', '6077669', '6272680');

General Ledger FAQ for R12 Upgrade Scripts and Known Upgrade Issues

1. Where are the R12 upgrade scripts located ?

R12 upgrade SQL scripts can be found in $GL_TOP/patch/115/sql directory.

2. Which are the most important upgrade scripts and what changes do they make?

glrrncol.sql	Script has DDL statements to rename the column set_of_books_id to ledger_id in GL tables which are having column set_of_books_id.
glraslg1.sql	Upgrades all sets of books to ledgers.
glraslg2.sql	Updates the ledger category code to SECONDARY for Secondary Ledgers. Generates configuration ID for Primary Ledgers. Updates SLA accounting method code and type for Cash Ledgers. Updates SLA columns for ALC Ledgers.
glrasgls.sql	Creates GL_LEDGERS_S sequence to start with a value larger than the maximum set of books ID.
glrbaup2.sql	Script populates chart_of_accounts_id, period_set_name columns in GL_JE_BATCHES table for all those upgraded journal batches. In R11chart_of_accounts_id,period_set_name columns are not present in GL_JE_BATCHES table. These columns are added in R12.
glrautop.sql	Upgrades autopost criteria. Populates chart_of_accounts_id, period_set_name & accounted_period_type columns in GL_AUTOMATIC_POSTING_SETS.
glrconso.sql	Upgrades Consolidation Mapping definitions.Creates the Chart of Accounts mapping in the GL_COA_MAPPINGS table.
glrreval.sql	Upgrades Revaluation definitions. Populates chart_of_accounts_id column in GL_REVALUATIONS table.
glrrjeup.sql	Upgrades recurring journal tables.Populates chart_of_accounts_id column in GL_RECURRING_BATCHES table.
glrstinc.sql	Upgrades data for summary templates. Populates data in GL_SUMMARY_HIERARCHIES table.
glrflias.sql	Upgrade script for populating the GL_ACCESS_SETS, GL_ACCESS_SET_NORM_ASSIGN, and GL_ACCESS_SET_ASSIGNMENTS tables. Also populates the GL: Data Access Set profile option values for all applications/users/responsibilities for which GL:Set Of Books profile option is set.
glrmadef.sql	Upgrades MassAllocation definitions. Mainly populates LEDGER_ID, LEDGER_CURRENCY columns in GL_ALLOC_FORMULA_LINES table
glrstbco.sql	Upgrades Summary Template Budgetary Control Options. Populates the new GL_SUMMARY_BC_OPTIONS table
glrpdrat.sql	Upgrades GL_TRANSLATION_RATES table. Populates daily_translation_rate_type info in GL_LEDGERS table. Inserts converstion types data into GL_DAILY_CONVERSION_TYPES table. Populates period rates related info in GL_DAILY_RATES table.
glrsyssu.sql	Populates values for following new profile options 'GL_RECORDS_TO_PROCESS', 'GL_ACCOUNTS_TO_PROCESS' & 'GL_GLLEZL_ARCHIVE_ROWS'.
glrsyusg.sql	Upgrades System Usages table. Populate the new consolidation_ledger_flag and efb_upgrade_flag in GL_SYSTEM_USAGES table.
glrjiint.sql	Updates set_od_books_id column value to -1 in GL_INTERFACE table.
glrlebsv.sql	Upgrades legal entity and balancing segment assignment. Populates data in GL_LE_VALUE_SETS table.
glrjebnm.sql	Updates jounral batch name in GL_JE_BATCHES table to change batch naming convention.
glrbobco.sql	Upgrades Budget Organization & Budgetary Control Options. Populates the new GL_BUDORG_BC_OPTIONS table.
glrasrs2.sql	Creates Secondary ledger relationships.
glrasrs4.sql	Updates ALC GL ledger relationships from SUBLEDGER level to JOURNAL level if it is PURE 'Thin' MRC. Updates SLA and Primary Ledger IDs of ALC JOURNAL/BALANCE ledger relationships to be same as their Source Ledgers if their Source ledgers are Secondary/ALC. Populates the column alc_no_rate_action_code same as their source ledgers i.e. journal/subledger level ALC ledgers.
glrarvcs.sql	Upgrade script for populating the GL_AUTOREV_CRITERIA_SETS.

3. How can I determine the cause of the issues I am facing after R12 upgrade?

1. Find the tables related to the problem.
2. From above upgrade scripts information find the upgrade script which is populating data in those tables.
3. Now open upgrade log file and check whether that script has failed. Check the exact error occurred when the script is executed and fix that error.

4. Why do most of the GL transaction forms (Enter Journals, Budget Journals, etc.) not retrieve any records after the upgrade?

This issue occurs if set_of_books_id column in GL tables is not renamed to ledger_id or if ledger_id column is not populated with values.
So check the upgrade log files for any errors while executing DDL statements in upgrade script glrrncol.sql.If there are any errors fix them or log a SR with Oracle support. Once ledger_id column is populated in GL tables all transactions forms will show data properly.

5. Why journal batches created before upgrade cannot be queried in journals form?

This happens if chart_of_accounts_id column in GL_JE_BATCHES table is null for the batches created before upgrade. Check upgrade log files and see if the script glrbaup2.sql is errored out. If it has errored out please rerun glrbaup2.sql script by following below steps.

1. Navigate to $GL_TOP/patch/115/sql directory:
   cd $GL_TOP/patch/115/sql
2. Connect to database using sqlplus as APPS user.
3. Execute glrbaup2.sql from sql command prompt:
   sql> @glrbaup2.sql

6. On the account inquiry form, after upgrade, when click on Show Journal button the following error occurs: "APP-FND-01347: You no longer have access to the specific information requested in this screen". How do I fix this?

This happens if chart_of_accounts_id column in GL_JE_BATCHES table is null for the batches created before upgrade. Check upgrade log files and see if the script glrbaup2.sql is errored out. If it has errored out please rerun glrbaup2.sql script by following below steps.

1. Navigate to $GL_TOP/patch/115/sql directory:
   cd $GL_TOP/patch/115/sql
2. Connect to database using sqlplus as APPS user.
3. Execute glrbaup2.sql from sql command prompt:
   sql> @glrbaup2.sql

7. When open the Enter Budget amounts form after the upgrade, the following error occurs: "ORA-00942: Table or view does not exist". How do I fix this?

It occurs if the view GL_BUDGET_ASSIGNMENTS_UNIQUE_V is not created or invalid. To fix this error execute below command from $GL_TOP/patch/115/odf path:

> adodfcmp userid=apps/apps mode=views odffile=glgvw.odf touser=apps/apps priv_schema=system/manager changedb=NO

Check the log file created by above command and follow the instructions to create the missing view GL_BUDGET_ASSIGNMENTS_UNIQUE_V.
Once the view is created enter budget amounts form can be opened.

8. Why Auto post criteria form does not retrieve records after upgrade?

If chart_of_accounts_id column is null in GL_AUTOMATIC_POSTING_SETS table, auto post criteria form can not retrieve any record. Check the upgrade log file and see if the script glrautop.sql has errored out. If so rerun glrautop.sql script by following below steps.

1. Navigate to $GL_TOP/patch/115/sql directory:
   cd $GL_TOP/patch/115/sql
2. Connect to database using sqlplus as APPS user.
3. Execute glrautop.sql from sql command prompt:
   sql> @glrautop.sql

9. GL Posting program after upgrade ends with error "PERF0005: Oracle error detected in glpipi() - ORA-00942: table or view does not exist". Why?

This error comes when GL_POSTING_INTERIM table is not created.

Create this table using gl_posting_interim.xdf file. After that posting program will run fine.
See note:308427.1 The XDF Comparison Utility (FndXdfCmp) and note:551325.1 How to verify or create a Database Object using a odf (adodfcmp) or xdf (FndXdfCmp) file ? 

10. After upgrade GL:Data Access Set profile option is not assigned to all GL responsibilities. How to fix this?

This can happen if the script glrflias.sql fails during upgrade.
Check upgrade log files and see whether the script glrflias.sql has failed with ora-01722 error.

If so execute below insert statement after taking the back up of FND_PROFILE_OPTION_VALUES table, then GL:Data access set profile will be assigned to all responsibilities for which GL:Set Of books profile option is set in 11i.

create table FND_PROFILE_OPTION_VALUES_BK as
select * from FND_PROFILE_OPTION_VALUES;
INSERT INTO FND_PROFILE_OPTION_VALUES pov
(APPLICATION_ID,
PROFILE_OPTION_ID,
LEVEL_ID,
LEVEL_VALUE,
LAST_UPDATE_DATE,
LAST_UPDATED_BY,
CREATION_DATE,
CREATED_BY,
LAST_UPDATE_LOGIN,
PROFILE_OPTION_VALUE,
LEVEL_VALUE_APPLICATION_ID)
SELECT
pov1.application_id,
po1.profile_option_id,
pov1.level_id,
pov1.level_value,
sysdate,
1,
sysdate,
1,
0,
ldg.implicit_access_set_id,
pov1.level_value_application_id
FROM
FND_PROFILE_OPTION_VALUES pov1,
GL_LEDGERS ldg,
FND_PROFILE_OPTIONS PO,
FND_PROFILE_OPTIONS PO1
WHERE pov1.application_id = 101
AND pov1.profile_option_id = po.profile_option_id
AND PO.profile_option_name='GL_SET_OF_BKS_ID'
AND po1.profile_option_name='GL_ACCESS_SET_ID'
AND pov1.level_id <> 10004
AND to_char(ldg.ledger_id) = pov1.profile_option_value
AND ldg.implicit_access_set_id IS NOT NULL
AND NOT EXISTS
(select 1 from fnd_profile_option_values pov2
where pov2.application_id = pov1.application_id
and pov2.profile_option_id = po1.profile_option_id
and pov2.level_id = pov1.level_id
and pov2.level_value = pov1.level_value
and nvl(pov2.level_value_application_id, -1)
= nvl(pov1.level_value_application_id, -1));
commit;

How to Migrate AME to R12 During Upgrade from 11i to R12?

How to Migrate AME to R12 During Upgrade from 11i to R12?




FIX

In R12 ,The Item_Type for Payables Invoice Approval Workflow is changed from APINV to APINVAPR and this new workflow is released through file apfhanwf.wft


In-progress workflow items APINV should, in general, upgrade smoothly. However, You could consider reducing the number of in-progress workflow items by turning off Invoice Approval Workflow before starting the upgrade and validate this with testing, especially where you have customized Release 11i pre-seeded workflow processes or activities.

After Upgrade to R12 all newly Initiated Invoices will be started with New Workflow Process with Item_type=APINVAPR.

The Upgrade script in R12 will Update all Pending Workflows from 11i(APINV) which are in 'Initiated' status to 'Required' Status and resetting the approval_ready_flag to Y
Once the upgrade is Completed , User need to Re-Initiate these Workflows for Approval Again by Using Option Action> Initiate OR Running the Approval Concurrent Program.
Once Re-Initiated the Approval Status for these Invoices will be changed to 'Initiated' and new Workflow Process with Item_Type=APINVAPR will be started.

Following Table Lists wfapproval_status before and After the Upgrade to R12



Approval Status in 11i Approval status to in R12 Approval_ready_flag in R12
----------------------- ------------------------- -------------------------

INITIATED REQUIRED Y
APPROVED same as 11i same as 11i
MANUALLY APPROVED same as 11i same as 11i
NOT REQUIRED same as 11i same as 11i
REJECTED same as 11i same as 11i
REQUIRED same as 11i same as 11i
WFAPPROVED same as 11i same as 11i


However, depending on how did you setup your rules, as datamodel changed between 11i and R12, the setup might need to be reviewed/ revisited after upgrade- as there is nothing like automated upgrade, the rules / approval groups are the same

Monitoring User Activity with “Sign-On: Audit Level” Profile Option in Oracle E-Business Suite R12

1.      Overview:

Users Activity in Oracle E-Business Suite can be monitored online (using a given form) or via reports available in the system administration responsibility.

The online monitoring of user activity within Oracle Applications is achieved via the Monitor Users form (Form Name: FNDSCMON.fmx). In order to use this form and also to use the reports the profile option Sign-On: Audit Levelmust be set to an appropriate value. The available options are: - 

• NONE: No monitoring performed on users’ activity.
• USER: Only show a list of logged in users.
• RESPONSIBILITY: Will show the users logged in and the responsibility they are using.
• FORM: show the most detailed level, it will show the User, Responsibility and Form being accessed.

The general overview of the process of monitoring user activity in Oracle Applications R12 is:

1. Enabling users tracking by setting the profile option “Sign-On: Audit level” to take the value for example “Form”.
2. Viewing Users online using “Monitor Users” form.
3. Viewing Monitoring Reports about users and their activity.
4. If not used disable tracking users by changing the “Sign-On: Audit level” to take the value for example “None”.

2.      Enable User Tracking – Setting the Sign-On: Audit Level profile option:

To enable user tracking by changing the value of “Sign-On: Audit Level” profile option use the following steps (we will use the value Form):

1. Log in to Oracle APPS with system administrator responsibility
2. Navigate to Profile > System
3. Make sure the Site option is checked.
4. Navigate to Profile and search for sign > Click Find
5. Select the “Sign-On: Audit Level” > Click Find
6. Change its value to be Form
7. From the Menu bar click File > Save

 

3.      Viewing Users Online Using the “Monitor Users” form:

To monitor users online we use the “Monitor Users” screen or form. To display current users and their information using Monitor Users form:

1. Log in with System Administrator Responsibility
2. Navigate to Security: Users > Monitor
3. Click (CTL + F11) keys to display the result.

The screen shot below indicates what you would see if you had chosen the FORM option for the profile option in question.

 

 

This is a very useful screen since it tells you exactly which users are logged in and what are they doing in the system at any point in time. One may check this screen before bouncing or restarting the system to make sure all users are logged out.

It is a good practice to set the Sign-On: Audit Level profile option to “Form” since it gives the most detailed information above other choices but it will impact the system performance since it collects a lot of information, so you have keep that in mind.

 

4.      Viewing Monitoring Reports about Users and their activity:

Depending on what audit level you have selected for the profile option under discussion you may also generate various reports as indicated below: –

• Sign-On Audit Concurrent Requests: View information about who is requesting what concurrent requests and from which responsibilities and forms.
• Sign-On Audit Forms:View who is navigating to what form and when they do it.
• Sign-On Audit Responsibilities: Used to view who is selecting what responsibility and when they are doing it.
• Sign-On Audit Users:Used to view who signs on and for how long.
• Sign-On Audit Unsuccessful: Show audit information about unsuccessful logins to Oracle Applications.

To view any of the given reports monitoring user activity use following steps:

1. Navigate to System Administrator Responsibility > Concurrent > Requests Or from the Menu Bar go to View > Requests
2. Choose Submit New Request > Single Request
3. Select report you want from the 4 requests given above.
4. Click Submit > Find
5. Select report you choose and click View output button to view the report.

5.      Notifying Users of Unsuccessful Logins to their accounts:

 

Sign-On Audit can track user logins and provide users with a warning message if anyone has made an unsuccessful attempt to sign on with their application username since their last sign-on. This warning message appears after a user signs on. You do not have to audit the user with Sign-On Audit to use this notification feature.

To inform users about unsuccessful logins to their account, you can set the “Sign-On: Notification” profile option to Yes. To do that from System Administrator Responsibility > Profile > System > Find the profile option “Sign-On: Notification” and change its value to Yes.