Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Thursday, March 22, 2012

What languages and currencies are enabled in EBS

Raghava asked me about the languages and currencies being used in a new instance which has gone live. For languages we have this query:

select language_code
from fnd_languages
where installed_flag='I'

For currencies, I told him that in EBS all currencies are enabled. I executed the following query:

select CURRENCY_CODE,symbol
from apps.fnd_currencies
where enabled_flag='Y'

It returned 71 rows.

Total rows in fnd_currencies was 249.

However, I thought of a more logical way of getting this data. That would be to query transaction tables. Which transaction table to query here ? I queried dba_segments for the largest objects:

select object_name,bytes
from dba_segments
order by bytes desc;

After the usual fnd_lobs etc., gl_interface table came up. So I created this query:

SQL> select currency_code,count(*)
from apps.gl_interface
group by currency_code; 2 3

--------------- ----------
VND xxx
EUR xxx
USD xxx
SGD xxx
JPY xxx

VND = Vietnamese Dollar
SGD = Singapore Dollar
JPY = Japanese Yen
EUR = Euro
USD = US Dollar

I feel that this query does give a good estimate about the currencies in use.

Monday, March 5, 2012

inspection.wsil shows incorrect hostname

In SOA Suite the inspection.wsil URL is:


However this was showing the physical hostname of the server on which SOA Suite was installed. We had configured SOA to listen on virtual names. Rajiv Bhalla provided the solution to this problem by providing the My Oracle Support Article: Applications like Oracle IPM fail to retrieve WSDL's to SOA composites via URL's that use different protocol/hostname/port than they are configured to [ID 1290812.1]

1.Access the WebLogic server Admin console: e.g. http://host:port/console.

2.From the left pane, use the following path through the hierarchical menu to navigate to the configuration screen containing the "Front End" configuration

-> Environment
-> Servers
-> soa_server1
-> Protocols

3.Review and adjust the values of the following entries:

Frontend Host: myLoadBalancerHost.myDomain
Frontend Port: 80
Frontend HTTPS Port: 443

You'll need to restart the SOA server for this to take effect, even though it says No restarts necessary.