BI publisher reporting product from Oracle that provides the ability to create and manage highly formatted reports from a wide range of data sources.
See Considerations below for configuration Publisher files as they require manual entry and evaluate for some attributes. |
EBS Publisher Root Source Directory on Project Properties tab defaults to publisher, but you can update if you are keeping Publisher Files in different folder. |
Name | Description |
---|---|
.rtf | XML Publisher (XDO) translatable templates and non-translatable RTF templates. |
XML Publisher (XDO) PDF templates. | |
.xsd | XML Publisher (XDO) non-translatable XML Schema. |
Name | Code |
---|---|
Publisher Files | PUBLISHER |
Name | Code | Description | Default Value | Supported Values |
---|---|---|---|---|
Source | SOURCE | Object Source Location Type | SCM (**populating from SCM) EBS (**manual creation) | SCM | EBS |
App Short Name | APP_SHORT_NAME | Application Short Name | Defaults to EBS Module Application Short Name property. | |
LOB Code | LOB_CODE | XDO LOB code. Enter either the Template Code or the Data Definition Code. | <file name> (**without path/extension) | |
XDO File Type | XDO_FILE_TYPE | XDO File type | ||
LOB Type | LOB_TYPE | XDO LOB type | XML_SAMPLE See Considerations below. | BURSTING_FILE | DATA_TEMPLATE | TEMPLATE | TEMPLATE_SOURCE | XML_SCHEMA | XML_SAMPLE |
Target Location | TARGET_LOCATION | Path to where the file should be deployed to. | $<PROD_TOP>/patch/115/publisher Default can be changed using EBS Publisher Root Destination Directory property. | |
Territory Code | TERRITORY | ISO two-letter territory code. If no territory code, provide 00 to ignore the value. | US | |
Language | LANGUAGE | ISO two-letter language code. | en | |
Custom Mode | CUSTOM_MODE | To override Oracle’s upload algorithm and update the custom AOL data regardless - use CUSTOM_MODE= FORCE. | FORCE Default can be changed using EBS Publisher Default Custom Mode property. | NOFORCE | FORCE |
NLS Lang | NLS_LANG | NLS_LANG environment variable | $NLS_LANG | |
Target File Permissions | FILE_PERMISSIONS | Permissions to apply to the file after it is deployed | Defaults to the project property FDEBS_FILE_PERMISSIONS |
Name | Code | Description | Default Value |
---|---|---|---|
Publisher Root Source Directory | FDEBS_PUBLISHER_ROOT_SOURCE_DIR | Source folder for publisher files (e.g. xmlpub). | publisher |
Publisher Root Destination Directory | FDEBS_PUBLISHER_ROOT_DESTINATION_DIR | Target directory for Publisher files (e.g. $XXHR_TOP/publisher). | $<PROD_TOP>/patch/115/publisher |
Publisher Default Custom Mode | FDEBS_PUBLISHER_CUSTOM_MODE | When populating or evaluating files deployed with XDOLoader, set the CUSTOM_MODE of publisher files to this. | FORCE |
File Permissions | FDEBS_FILE_PERMISSIONS | Target File Permission. Will be set to target file after deployment using chmod. eg: 755 |
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD -DB_USERNAME $FDEBS_DB_USER -DB_PASSWORD "$FDEBS_DB_PASSWORD" -JDBC_CONNECTION "$AD_APPS_JDBC_URL" -LOB_TYPE TEMPLATE -APPS_SHORT_NAME XXHR -LOB_CODE XXHR_BIP_ROSTER -LANGUAGE en -TERRITORY US -NLS_LANG $NLS_LANG -XDO_FILE_TYPE XLS mv `ls "TEMPLATE_XXHR_XXHR_BIP_ROSTER_en_US."* | grep -i "TEMPLATE_XXHR_XXHR_BIP_ROSTER_en_US.xls"` ./publisher/XXHR_BIP_ROSTER.xls |
cp "$SOURCE_FILE" "$XXHR_TOP/patch/115/publisher/templates/"; java oracle.apps.xdo.oa.util.XDOLoader UPLOAD -DB_USERNAME $FDEBS_DB_USER -DB_PASSWORD "$FDEBS_DB_PASSWORD" -JDBC_CONNECTION "$AD_APPS_JDBC_URL" -LOB_TYPE TEMPLATE -APPS_SHORT_NAME XXHR -LOB_CODE XXHR_BIP_ROSTER -LANGUAGE en -TERRITORY US -NLS_LANG $NLS_LANG -XDO_FILE_TYPE XLS -FILE_NAME "$XXHR_TOP/patch/115/publisher/templates/XXHR_BIP_ROSTER.xls" -CUSTOM_MODE FORCE |
If necessary, you can find values for App Short Name, LOB Code, Territory and Language using following query.
SELECT LOB_CODE, LOB_TYPE, APPLICATION_SHORT_NAME, FILE_NAME, LANGUAGE, TERRITORY, XDO_FILE_TYPE FROM XDO_LOBS |
If you want to avoid manually entering values like Territory, then following customization script can be used. For example, if file is stored as "/publisher/US/en/abc.rtf" in source control system, then US will be recognized as Territory. This is example for Territory and same logic can be applied for LOB Code, App Short Name, LOB Type, Territory and Language as necessary.
// publisher file customization to allow use of territory and language from path // User will enter path as /publisher/US/en/XXHR_BIP_ROSTER.rtf // Format - <parent folder>/publisher/<territory>/<language>/<file name with extension> // Find what folder name we are using for publisher files PUB_ROOT=FDEBS_PUBLISHER_ROOT_SOURCE_DIR != null && FDEBS_PUBLISHER_ROOT_SOURCE_DIR != '' ? FDEBS_PUBLISHER_ROOT_SOURCE_DIR : 'publisher'; if (FILE_PATH.indexOf(PUB_ROOT) > -1) { // if file path does not have publisher folder then we can't do anything // let's remove anything including first / from path first, then split it EFFECTIVE_PATH=FILE_PATH.substring(FILE_PATH.indexOf(PUB_ROOT)); parts=EFFECTIVE_PATH.split('/'); if (parts.length >= 4) { return parts[1]; } } return null; |