FSG (Financial Statement Generator) Debugging Tips [ID 367429.1]

Post date: Mar 11, 2011 3:46:12 AM

In this Document

Goal

Solution

References

Applies to:

Oracle General Ledger - Version: 11.5.2 to 11.5.10

Information in this document applies to any platform.

EXECUTABLE:RGRARG - Financial Statement Generator

Goal

1.How to improve FSG Performance:

2.How to get the correct formatting for Decimal/Thousand Seperator:

3.How to addess FSG XML Publisher issues:

Solution

1. How to improve FSG Performance:

=========================

a) By default a dynamic select statement (you can see it in a log file) is created for CBO.

In some cases performance boost can be achieved by creating a new profile option

and setting proper value of the profile at the Site level.

Using the "Application Developer" responsibility navigate to Profile and create the new

profile option with the following information:

Name : RG_REMOVE_CBO_HINT

Application : Application Report Generator

User Profile Name : FSG: Remove CBO Hint

Description : Remove CBO Hint

Active Dates Start : 01/01/1951

All check boxes should be checked.

Save it.

With the "System Administrator" responsibility go to Profiles > System. Query all profiles

with name starting as "FSG%".

Go to profile "FSG: Remove CBO Hint" , enter proper value at Site level and save it.

Proper values are :

Y - remove CBO hints, nvl's still present;

N - do not remove CBO hints, nvl's still present;

YY - remove CBO hints, remove nvl's;

YN - remove CBO hints, nvl's still present;

NY - do not remove CBO hints, remove nvl's;

NN - do not remove CBO hints, nvl's still present;

If profile "FSG: Remove CBO Hint" is not present, FSG works as for NN.

b) Please check the value of FSG profile "FSG: String Comparison Mode".

It can have two values : 0 or 1.

Value "0" means that AOL routine fdnwsc() will be used for comparing two character

strings. It is VERY important that this routine works fine for ANY codeset including ASCII.

Value "1" means that AOL routine strcmp() will be used for comparing two character

strings. It is very important that this routine works fine ONLY for ASCII codeset. In this

case customer can boost performance. If value "1" is occasionally used for ANY other

codeset, then results are absolutely unpredictable.

Also ensure that you apply the latest FSG patch. Refer Note 189282.1 for details

on latest FSG patches.

2. How to get the correct formatting for Decimal/Thousand Seperator:

===============================================

To get the correct formatting for different countries using different decimal/thousand

separators, the following should be done:

- Set the following profile options "Currency: Thousands Separator" to "Yes";

- ICX: Language set to local language

- ICX: Teritory set to local teritory

- ICX: Numeric characters set to 10.000,00 or 10,000.00 depending on the format needed.

- Run the following SQL scripts:

select parameter,value

from nls_database_parameters

where parameter in ('NLS_LANGUAGE','NLS_TERRITORY',

'NLS_NUMERIC_CHARACTERS');

.

select parameter,value

from nls_instance_parameters

where parameter in ('NLS_LANGUAGE','NLS_TERRITORY',

'NLS_NUMERIC_CHARACTERS');

.

select parameter,value

from nls_session_parameters

where parameter in ('NLS_LANGUAGE','NLS_TERRITORY',

'NLS_NUMERIC_CHARACTERS');

Please, pay special attention to the LAST sql script, because the output of THIS script

defines FORMATTING in FSG. It should be relevant to what user wants in formatting

amount values for output.

3. How to address FSG XML Publisher issues:

===============================

FSG XML processing works fine when customer uses two steps processing.

It means that customer first runs FSG for XML output and only later runs XML Publisher

to publish FSG output. This method works for ANY version of XML Publisher. The only

thing customer should pay attention to is codeset.

If customer uses UTF-8 codeset, then no additional action is required.

If customer uses any other codeset, please, do the following :

Using the "Application Developer" responsibility go to Profile and create a new profile

option with the following information:

Name : RG_XML_CODESET

Application : Application Report Generator

User Profile Name : FSG: Database Codeset

Description : Database Codeset

Active Dates Start : 01/01/1951

All check boxes should be checked.

Save it.

With the "System Administrator" responsibility go to Profiles > System and query all profiles

with name starting as "FSG%".

Go to profile "FSG: Database Codeset" , enter <codeset value -- 3 --> on a site level, save it.

Run the following script to check which codeset is being used:

SELECT tag FROM fnd_lookup_values

WHERE lookup_type = 'FND_ISO_CHARACTER_SET_MAP'

AND lookup_code = SUBSTR(USERENV('LANGUAGE'),

INSTR(USERENV('LANGUAGE'), '.')+1) AND language = 'US';

If FSG step worked fine (FSG output for XML is correct; you can verify it by opening

output file in Internet Explorer and first line of the output shows CORRECT codeset), but

XML Publisher run brings a problem, please, address this issue to XML Publisher team.

SRS program "Program - Publish FSG Report" Earlier used to work ONLY for XML

Publisher 4.5, but currently this functionality can work for XDO versions 5.0, 5.5, 5.6.0,

5.6.1, 5.6.3 by applying patch 5610948.

References

BUG:5087693 - ORACLE.XDO.PARSER.V2.XMLPARSEEXCEPTION: END TAG DOES NOT MATCH START TAG 'FSG:R

BUG:5097039 - CANNOT CONTROL DECIMAL AND THOUSANDS SEPARATOR IN FSG REPORTS(FORMAT MASK)

BUG:5097575 - FSG PUBLISHER DOES NOT WORK IN 5.6.1 BUT WORK IN XML PUBLISHER 5.6

NOTE:1079504.6 - FSG Performance - New Profile Option FSG: String Comparison Mode

NOTE:292655.1 - While running FSG : Unable to read value for profile option RG_REMOVE_CBO_HINT

Related

Products

• Oracle E-Business Suite > Financial Management > Financial Control and Reporting > Oracle General Ledger

Keywords

Back to top