DBA in the Trenches

After finally getting hold of bursting for BI Publisher I started to play around and with the help of Gareth Roberts I got it up and running sending PDF templates. I would suggest reading his article if you want a quick rundown of how it all work's. One item I would highlight is that when using dataTigger's inside Data Definition's the heading of the XML is case sensitive:  <dataTemplate name="XXXMLEXAMPLE" description="XSL-XML Example" Version="1.0" defaultPackage ="XXOM_AAABBBCCC_INTERFACE_PKG"> Pay special attention when defining the defaultPackage as I was left scratching my head with the defaultPackage was not being picked up. Also the dataTrigger placement is also in the fine print. beforeReport should be placed before the dataStructure and the afterReport trigger should be placed afterwards. Somehow this managed to catch my eye while reading the documentation.   Data Definition Create the data definition ...

The hostname command "one of the most basic of the network administrative utilities" according to linfo.org . I use the command to check whether I am in the TEST or DEV environment to use the FNDLOAD function for copying customizations to the PROD environment. Basically I use a shell script to create the LDT files used for the FNDLOAD to copy paste from TEST to PROD. This ensures no user errors and is much faster using this script. I will go into the FNDLOAD in a future post. So after playing around and googling I found the solution: #!/bin/sh #Creating concurrent and XML Pub reports LDT files APPS_PWD=$1 APPL_NAME=$2 if [ "$APPS_PWD" = "" ] then echo "Usage: make_ldt_files.sh " exit fi; hostname if [ `hostname` = "TEST.ORG.COM" ] then echo "Downloading concurrent definition..." FNDLOAD apps/$APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct ./APPL_CONC.ldt PROGRAM APPLICATION_SHORT_NAME=PLSO CONCURRENT_PROGRA...