E1: XMLP: Control Tables Data Source Selected by XML Publisher Kernel (Doc ID 651280.1)

Last updated on APRIL 04, 2025

Applies to:

Goal

The revised special instructions for <bug 10926716> indicate to create Object Configuration Manager (OCM) entries for the F95600, F95610, and F95611 tables pointing to "Control Tables - xxx" for each environment, and then generate these tables for each environment. However, the XML Publisher Kernel does not appear to read the OCM mappings based on the environment where the report is submitted, but instead reads these tables from the Default Environment specified in the server jde.ini.

For example:

1. Follow the instructions in <bug 10926716>, making sure you have at least two pathcodes/environments on your server where the XML Publisher Kernel is running. For example, DV812 and PY812. Make sure DV812 is pointing to Control Tables - Test for the F95600, F95610, and F95611 tables and PY812 is pointing to Control Tables - CRP.
2. Set the server jde.ini default environment setting to be DV812.
3. Log into DV812 and upload a BI Publisher template and associate it with a UBE. Run the UBE, then view the BI Publisher output from Submitted Jobs. Everything works correctly.
4. Log into PY812 and upload a different BI Publisher template and associate it with a UBE.
   Run the UBE, then attempt to view the BI Publisher output. You get an error. If you look at the XML Publisher Kernel jde.log, it says that the Template was not found. Within the jdedebug.log, it shows that the XML Publisher Kernel is looking at TESTCTL.F95600, not CRPCTL.F95600.

The XML Publisher Kernel is using the environment from the JDE.INI rather then the environment that the user is logged into when submitting the report.

This is known to cause BI Publisher Reports to end in FR status error and no output produced.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.