EBS Object Types - Publisher Files
BI publisher reporting product from Oracle that provides the ability to create and manage highly formatted reports from a wide range of data sources.
File Extensions
Files with following extension(s) is considered, or files with extension .xml, .xls, .xsl, .pdf, .rtf, .xsd that are in publisher folder (or user defined folder specified by EBS Publisher Root Source Directory on Project Properties).
| 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. |
Attributes
| Name | Description | Default Value | Supported Values |
|---|---|---|---|
| Source | Object Source Location Type | SCM (**populating from SCM) EBS (**manual creation) | SCM | EBS |
App Short Name | Application Short Name | XXHR | |
| 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 | ||
| LOB Type | XDO LOB type | XML_SAMPLE | BURSTING_FILE | DATA_TEMPLATE | TEMPLATE | TEMPLATE_SOURCE | XML_SCHEMA | XML_SAMPLE |
| Target Location | Path to where the file should be deployed to. | $<PROD_TOP>/patch/115/publisher/defs/ | |
| Territory Code | ISO two-letter territory code. If no territory code, provide 00 to ignore the value. | US | |
| Language | ISO two-letter language code. | en | |
| Custom Mode | To override Oracle’s upload algorithm and update the custom AOL data regardless - use CUSTOM_MODE= FORCE. | FORCE Can be set to another default using the
property. (Changed from NOFORCE in 4.5.1 release) | NOFORCE | FORCE |
| NLS Lang | NLS_LANG environment variable | $NLS_LANG |
Related Project Properties
| Name | Description | Default Value |
|---|---|---|
| EBS Publisher Root Source Directory | Source folder for publisher files (e.g. xmlpub). | publisher |
EBS Publisher Root Destination Directory | Target directory for Publisher files (e.g. $XXHR_TOP/publisher). | $<PROD_TOP>/patch/115/publisher |
| When populating or evaluating files deployed with XDOLoader, set the CUSTOM_MODE of publisher files to this. | FORCE |
Sample Build Commands
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 XML_SAMPLE -APPS_SHORT_NAME XXHR -LOB_CODE XXHR_BIP_ROSTER -LANGUAGE en -TERRITORY US -NLS_LANG $NLS_LANG -XDO_FILE_TYPE XML mv XML_SAMPLE_XXHR_XXHR_BIP_ROSTER_en_US.xml ./publisher/XXHR_BIP_ROSTER.xml
Sample Deploy Commands
cp $SOURCE_FILE $XXHR_TOP/patch/115/publisher/defs/; 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 XML_SAMPLE -APPS_SHORT_NAME XXHR -LOB_CODE XXHR_BIP_ROSTER -LANGUAGE en -TERRITORY US -NLS_LANG $NLS_LANG -XDO_FILE_TYPE XML -FILE_NAME "$XXHR_TOP/patch/115/publisher/defs/XXHR_BIP_ROSTER.xml" -CUSTOM_MODE NOFORCE
Considerations
- When populating XML files from an SCM, the LOB Type is defaulted to XML_SAMPLE. Be sure to update the LOB Type to the appropriate type and regenerate the commands for bursting files, data templates, etc.
- Ensure the LOB Code of the XML files and Name of the Data Definition (XDO_DS_DEFINITION - AOL) match the LOB Code of the report template, as this is what ties them together. Failure to do so will result in the attachments not appearing under the data definition in EBS.
The following macros are not currently supported in the footer:
- style