XML Publisher Reports Important Tables
Below are Important database tables which stores data related to data definitions
and templates of XML Publisher-
XDO_LOBS
XDO_DS_DEFINITIONS_B
XDO_TEMPLATES_B
XDO_TEMPLATE_FIELDS
Translation tables- This tables stores traslated values of template fields
XDO_TRANS_UNIT_PROPS
XDO_TRANS_UNITS --UNDERSTAND POSITION OF FIELDS AND THEIR UNIT ID
XDO_TRANS_UNIT_VALUES -- THEIR UNIT ID AND TRANSALTED VALUES
Use the below code to delete Data definition.
BEGIN
XDO_DS_DEFINITIONS_PKG.DELETE_ROW(<APPL_SHORT_NAME>,<DATA DEFINITION CODE>);
END;
Use the below code to delete template definition.
BEGIN
XDO_TEMPLATES_PKG.DELETE_ROW(<APPL_SHORT_NAME>,<DATA DEFINITION CODE>);
END;
Use the below code to remove the uploaded template and translation files
DELETE FROM XDO_LOBS
WHERE LOB_CODE = 'XXMI_VAT_INVOICE_UKRAINE';
For deleting the translations, we have to delete data from all below tables after deleting temaplate-
Delete from XDO_TRANS_UNIT_PROPS
Where TEMPLATE_CODE = 'XXMI_LIBRO_DIARIO_CHILE';
Delete from XDO_TRANS_UNITS
Where TEMPLATE_CODE = 'XXMI_LIBRO_DIARIO_CHILE';
Delete from XDO_TRANS_UNIT_VALUES
Where TEMPLATE_CODE = 'XXMI_LIBRO_DIARIO_CHILE';
While uploading XLFF file use encoding ‘UTF-8’ method.
Transfer the rdf and rtf file in ‘binary’ mode.
Remaining in ‘ASCII’ mode.
Use below code while designing rtf-
<fo:bidi-override direction="ltr" unicode-bidi="bidi-override"><?CF_JL_DEBIT_3X_FORMAT?></fo:bidi-override>
To Fix Java Memory Error-
Data Template Code: XXCWB_CNTRY_MVMNT_RPT
Data Template Application Short Name: XXCWB
Debug Flag: N
{P_SHIPTO=, P_TNDR=Y, P_TRMNL=, P_GRN_CLASS=, P_PROD_AUTH=Y, P_GEN=Y, P_GRN=01, P_TRN_RN=, P_DEST=, P_ADVCARS=Y, P_STN=, P_WK_TO=200920, P_CO=, P_WK_FROM=200916, P_ZONE=}
Calling XDO Data Engine...
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...JVMDG318: Heap dump file written to /appsoft_pebs/pebs/oracle/pebsdb/pebscomn/admin/log/PEBS_wpgapp01/heapdump1237120.1267482644.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /appsoft_pebs/pebs/oracle/pebsdb/pebscomn/admin/log/PEBS_wpgapp01/javacore1237120.1267482651.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
****Warning!!! Due to high volume of data, got out of memory exception...***
****Please retry with scalable option or modify the Data template to run in scalable mode...***
********************************************************************************
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
Solution:
--Increment 1024 *2,4,6
"UPDATE fnd_cp_services
SET developer_parameters =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');
SET developer_parameters =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');
OR
Use options
Also from find request window , choose concurrent program -> Diagnostics -> view XML
Check the xml file in the end for error.
Please check the details in the DD and template creation e.g.lang, territory,default output,default file.
No comments:
Post a Comment