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

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

 

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

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

The concurrent request can be submitted via shell script. This can be done by a standard utility named CONSUB. It can be used to schedule a request too.
The syntax for CONCSUB is given below:
CONCSUB <APPS username>/<APPS password>
<responsibility application short name>
<responsibility name>
<username>
[WAIT=N|Y|<n seconds>]
CONCURRENT
<program application short name>
<program name>
[PROGRAM_NAME=<description>]
 
[ORG_ID=<#>] – R12 onwards only
[REPEAT_TIME=<resubmission time>]
[REPEAT_INTERVAL= <number>]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=<resubmission end date and time>]
[START=<date>]
[IMPLICIT=< type of concurrent request>
[<parameter 1> … <parameter n>]
These are the compulsory Parameters:
PARAMETER
DESCRIPTION
ORACLE ID
Username and Password of the ORACLE ID for Applications, separated by a slash (“/”). This would be apps/appspass
Responsibility Application Short Name
Enter the short name of the application for your responsibility. This name, along with your responsibility name, will be used to select a responsibility for your request to run in. eg : SYSADMIN
Responsibility Name
This name, along with your responsibility application short name, will be used to select a responsibility for your concurrent request to run in.
eg : ”System Administrator”
User name
Enter the name of your Application Object Library user. This name will be used to update the Who information for any data your concurrent manager changes.
eg : SYSADMIN
CONCURRENT
A flag that separates the program–specific parameters from the operating system parameters.
Program application short name
The application short name of your concurrent program. 
eg : FND
Program name
The uppercase name of your program. It must be the short name that you enter in the Concurrent Programs window when defining a concurrent program.

Here is an example of the command to run CONCSUB:

$ CONCSUB APPS/APPS
SYSADMIN
System Administrator
SYSADMIN
WAIT=N
CONCURRENT
FND
FNDFMRTC
PROGRAM_NAME=Register Custom Tables Weekly
REPEAT_INTERVAL=7
REPEAT_INTERVAL_UNIT=DAYS
REPEAT_INTERVAL_TYPE=START
START='”08“JUN96 23:55:00€”‘
CGL
APPLSYS
ALL
CGL
Notes:
1] For parameters that follow the CONCURRENT parameter and include spaces, enclose the parameter argument in double quotes, then again in single quotes. Oracle Application Object Library requires this syntax because it parses the argument string twice.
2] The above example uses the UNIX line continuation character ”, not all operating systems support the use of this character.  If the line continuation character is not supported then the CONCSUB command should be submitted as one continuous line.
3] COCNSUB is also used to shutdown the concurrent managers, however to start the concurrent manager you have to use startmgr utility.
CONCSUB apps/apps SYSADMIN ‘System Administrator’ SYSADMIN WAIT=N CONCURRENT FND SHUTDOWN
CONCSUB apps/apps SYSADMIN ‘System Administrator’ SYSADMIN WAIT=N CONCURRENT FND ABORT
4] The CONCSUB executable is located at $FND_TOP/bin/CONCSUB.