Had a query from a friend about why their XML / BI Publisher template and underlying XML wasn't working.
I wanted to do a quick check on my system to see if I was seeing the same problem.
I don't know where/how the XML was generated from so I "borrowed" an existing concurrent programs output file (XML) and template definition in order to test. Stealing the existing concurrent requests identity also means I didn't have to setup a new data definition, template, concurrent program etc...
So how?
I had previously (for other BIP work) done the following:
- Setup a AR Statement Data Definition and Template
- Run the AR Statement Generation Program, XML file produced - say concurrent request id 112233
- Run an XML Report Publisher concurrent request report for the Statement - say concurrent request id 112244
I now had the following files to use/test:
- /tmp/virtuate.xml - my friend's XML output
- /tmp/virtuate.rtf - my friend's template
Okay, so now to faking it:
1. In Unix as the applmgr user, replace the xml output from statements with the masquerading xml:
cd $APPLCSF/$APPLOUT mv o112233.out o112233.out.stmt cp /tmp/virtuate.xml o112233.out
2. Upload virtuate.rtf over top of the AR Statement template
3. Login to Oracle eBusiness Suite, Copy your Request 112244, and submit.
The output is now your friends template applied to your friends XML data source using your instance.
Unfortunately for my friend, things were working perfectly for me but not for him...