After upgrading to the latest JD Edwards tools release (9.2.0.5), our AP voucher detail report exported from BI Publisher to XLSX format is missing several critical columns that were present before. The report runs fine in PDF format showing all columns including GL distribution details and tax amounts, but XLSX exports only show basic voucher header information.
The BI Publisher template mapping appears intact when I check it in the designer, and the data model shows all required fields. This is causing significant reconciliation delays as our accounting team relies on the XLSX export for period-end analysis and they need the complete GL distribution breakdown.
Has anyone experienced similar issues with BI Publisher XLSX exports after a tools release upgrade? I’m particularly concerned about template compatibility with the new tools release and whether there’s a specific configuration for XLSX format handling.
The debug logs were helpful - I can see warnings about “complex table structures not fully supported in Excel output”. It looks like the nested GL distribution table is the culprit. Would creating a separate flattened data model specifically for XLSX export be the best approach, or is there a way to modify the existing template to work with both formats?
That’s a classic repeating group issue with XLSX exports in BI Publisher. The PDF renderer handles nested tables differently than XLSX. When you have GL distribution lines as a repeating group within the voucher detail, XLSX export sometimes flattens the structure incorrectly. You need to modify your template to use a flat data structure for XLSX or create a separate template specifically for XLSX that handles the repeating elements properly. I’d also verify that your data model query is returning all rows correctly - sometimes the tools upgrade changes how XML data is generated from the JDE tables.
I worked through this same issue last month after our tools upgrade. Here’s what you need to do:
First, understand that the tools release changed how BI Publisher handles repeating groups in XLSX format. The template mapping itself is fine, but XLSX export requires a different approach than PDF for hierarchical data.
Template Mapping Solution:
Create a conditional template section that detects the output format. In your RTF template, add a property: <?if:$_XDOOUTPUTFORMAT='excel'?> before your GL distribution section. For XLSX, flatten the structure by repeating the voucher header information for each GL line instead of using nested tables. For PDF, keep your existing nested structure.
XLSX Export Format Configuration:
The tools release introduced stricter XLSX format handling. You need to modify your data model to include a flattened view specifically for Excel exports. Add a new query that joins the voucher header (F0411) with GL distribution (F0911) in a single flat recordset. This eliminates the parent-child XML structure that XLSX struggles with.
Tools Release Compatibility:
After upgrading to 9.2.0.5, you must regenerate all BI Publisher templates that use complex table structures. The template XDO file format changed slightly. In BI Publisher Administrator, go to your report definition, edit the template, and click “Regenerate” even if you haven’t changed anything. This updates the internal template metadata to match the new tools release expectations.
Additionally, verify your BI Publisher configuration in Enterprise Manager:
- Navigate to BI Publisher → Administration → Configuration
- Under Output Formats, ensure XLSX is set to use the “Oracle BI Publisher Excel Output” processor (not the legacy processor)
- Set the Excel output property “EnableAccessibility” to false - this was causing column visibility issues in our environment
- Increase the “ExcelMaxRowsPerSheet” if your reports have many GL distribution lines
For immediate reconciliation needs, you can use this workaround: Export to XML format, then use a simple XSLT transformation to convert it to a flat CSV structure that Excel can open properly. This bypasses the XLSX format handler entirely while you’re updating your templates.
The root cause is that BI Publisher’s XLSX export engine in the new tools release applies stricter validation on table structures and won’t render columns that are part of improperly nested repeating groups. Your PDF works because the PDF renderer is more forgiving of complex hierarchies.
I’ve seen this exact issue after tools upgrades. The XLSX export format handler in BI Publisher sometimes needs reconfiguration after major tools releases. Check your BI Publisher configuration file (xdo.cfg) and verify the XLSX output settings are properly defined. Also, make sure your template’s column widths and data mappings haven’t exceeded the XLSX format limits which can cause columns to be silently dropped during export.