Skip to main content

Users cannot run arabic FSG reports in gl or report manager

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE 


Problem:


Cannot view XML input using XSl stylesheet. Please correct the error
and click Refresh button, or try again later

An invalid character was found in text content
Error processing resource 


"FSG: Database Codeset" profile does not exist while it is mandatory where the codeset is non utf-8.
Running the Program - publish FSG report:
RGFSGXML module: Program - Publish FSG Report

+------------- 1) PUBLISH -------------+
Beginning post-processing of request 521394 on node ERPDEV at 04-FEB-2010 14:19:05.
Post-processing of request 521394 failed at 04-FEB-2010 14:19:16 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.

Publisher log shows the error:
[2/4/10 2:19:16 PM] [UNEXPECTED] [28569:RT521394] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(XSLT10gR1.java:517)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:224)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
at
.....

oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Caused by: java.io.UTFDataFormatException: Invalid UTF8 encoding.

Codeset is:
ISO-8859-6

"FSG: Database Codeset" profile does not exist. 


This is causing the issue as XML is using a wrong codeset to generate the output.
The logfile confirms:
oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
Caused by: java.io.UTFDataFormatException: Invalid UTF8 encoding.





Explanation:


On : 12.0.6 version, Core Functionality


When attempting to submit and publish an FSG report in arabic, the following error occurs.
Submitting this report shows waring in completion.
Also Submitting the report in report manager seems to complete fine, but little squares are shown instead of arabic data


The profile is mandatory when the codeset is a non utf-8 one. 


Solution: Define "FSG: Database Codeset" profile, point it to the correct codeset and retest. 


1. Change the setup as following:
Go to "Application Developer" -> Profile and create a new profile with:
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

2. Go to "System Administrator" -> Profiles -> System and query all profiles with name starting with "FSG%".
Go to the profile "FSG: Database Codeset" , enter your codeset value ISO-8859-6 at the site level and save. 


Reference:


Note 470233.1 'Generating Fsg Xml Publisher Report Ends in 'Invalid UTF8 Encoding' Error' -is relevant for the issue, shows how to check the codeset. This is most probably set incorrectly.
Labels:

Comments

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...
15 comments
Read more

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...
Post a Comment
Read more

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...
Post a Comment
Read more