You may encounter errors when running Publish FSG reports in R12.2 .. Especially for languages different than US.
In the logfile of the concurrent request you may see the following;
oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.fnd.cp.opp.PostProcessorException:
oracle.apps.xdo.XDOException: No corresponding LOB data found :SELECT L.FILE_DATA FILE_DATA,DBMS_LOB.GETLENGTH(L.FILE_DATA) FILE_LENGTH, L.LANGUAGE LANGUAGE, L.TERRITORY TERRITORY, B.DEFAULT_LANGUAGE DEFAULT_LANGUAGE, B.DEFAULT_TERRITORY DEFAULT_TERRITORY,B.TEMPLATE_TYPE_CODE TEMPLATE_TYPE_CODE, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.START_DATE START_DATE, B.END_DATE END_DATE, B.TEMPLATE_STATUS TEMPLATE_STATUS, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.DS_APP_SHORT_NAME DS_APP_SHORT_NAME, B.DATA_SOURCE_CODE DATA_SOURCE_CODE, L.LOB_TYPE LOB_TYPE FROM XDO_LOBS L, XDO_TEMPLATES_B B WHERE L.APPLICATION_SHORT_NAME= :1 AND L.LOB_CODE = :2 AND L.APPLICATION_SHORT_NAME = B.APPLICATION_SHORT_NAME AND L.LOB_CODE = B.TEMPLATE_CODE AND (L.LOB_TYPE = 'TEMPLATE' OR L.LOB_TYPE = 'MLS_TEMPLATE') AND ( (L.LANGUAGE = :3 AND L.TERRITORY = :4) OR (L.LANGUAGE= B.DEFAULT_LANGUAGE AND L.TERRITORY= B.DEFAULT_TERRITORY ))
+---------------------------------------+
Cause:
In the logfile of the concurrent request you may see the following;
oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.fnd.cp.opp.PostProcessorException:
oracle.apps.xdo.XDOException: No corresponding LOB data found :SELECT L.FILE_DATA FILE_DATA,DBMS_LOB.GETLENGTH(L.FILE_DATA) FILE_LENGTH, L.LANGUAGE LANGUAGE, L.TERRITORY TERRITORY, B.DEFAULT_LANGUAGE DEFAULT_LANGUAGE, B.DEFAULT_TERRITORY DEFAULT_TERRITORY,B.TEMPLATE_TYPE_CODE TEMPLATE_TYPE_CODE, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.START_DATE START_DATE, B.END_DATE END_DATE, B.TEMPLATE_STATUS TEMPLATE_STATUS, B.USE_ALIAS_TABLE USE_ALIAS_TABLE, B.DS_APP_SHORT_NAME DS_APP_SHORT_NAME, B.DATA_SOURCE_CODE DATA_SOURCE_CODE, L.LOB_TYPE LOB_TYPE FROM XDO_LOBS L, XDO_TEMPLATES_B B WHERE L.APPLICATION_SHORT_NAME= :1 AND L.LOB_CODE = :2 AND L.APPLICATION_SHORT_NAME = B.APPLICATION_SHORT_NAME AND L.LOB_CODE = B.TEMPLATE_CODE AND (L.LOB_TYPE = 'TEMPLATE' OR L.LOB_TYPE = 'MLS_TEMPLATE') AND ( (L.LANGUAGE = :3 AND L.TERRITORY = :4) OR (L.LANGUAGE= B.DEFAULT_LANGUAGE AND L.TERRITORY= B.DEFAULT_TERRITORY ))
+---------------------------------------+
Cause:
The report template is not present in the system, or the template is present but it is not configured for the FSG report use. Another possibility is that there may be a logical problem in the tables which have the template - report definitions.
Solution:
What you need to do is ;
1. Navigate to XML Publisher Administrator > Templates.
2. Query for Template NAME_OF_THE_TEMPLATE
3. Click on download icon and download the template.
4. Update the template and load it again with a new name and click 'Apply' button.
Then retry the FSG report..
If you have no template defined for your language here; download the one which is there for US , and update it for your language too.. This will at least prevent the report to completed in warning..Note that: If this is a standard report and if you cant find its template for your language; then open an SR and request the template.
In my case the template was FSGXML basic template. It was normal for FSG report to complete with warnings because there was no template associated with Turkish language for the Report. In this case; the solution was to download the US template and upload it back again both for US and TR. This solved the problem..
Solution:
What you need to do is ;
1. Navigate to XML Publisher Administrator > Templates.
2. Query for Template NAME_OF_THE_TEMPLATE
3. Click on download icon and download the template.
4. Update the template and load it again with a new name and click 'Apply' button.
Then retry the FSG report..
If you have no template defined for your language here; download the one which is there for US , and update it for your language too.. This will at least prevent the report to completed in warning..Note that: If this is a standard report and if you cant find its template for your language; then open an SR and request the template.
In my case the template was FSGXML basic template. It was normal for FSG report to complete with warnings because there was no template associated with Turkish language for the Report. In this case; the solution was to download the US template and upload it back again both for US and TR. This solved the problem..
No comments :
Post a Comment
If you will ask a question, please don't comment here..
For your questions, please create an issue into my forum.
Forum Link: http://ermanarslan.blogspot.com.tr/p/forum.html
Register and create an issue in the related category.
I will support you from there.