BI publisher reporting product from Oracle that provides the ability to create and manage highly formatted reports from a wide range of data sources.
...
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 | 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 |
---|---|---|---|
EBS Publisher Root Source Directory | FDEBS_PUBLISHER_ROOT_SOURCE_DIR | Source folder for publisher files (e.g. xmlpub). | publisher |
EBS Publisher Root Destination Directory | FDEBS_PUBLISHER_ROOT_DESTINATION_DIR | Target directory for Publisher files (e.g. $XXHR_TOP/publisher). | $<PROD_TOP>/patch/115/publisher |
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 |
...
- When populating XML files from SCM, LOB Type is defaulted based file extension and file data. When sourcing files files from EBS, LOB Type is defaulted based on file extension. In either case be sure to make sure that LOB Type is appropriate. For example,
- .pdf, .rtf, .xls, .xsl, .xlf files are TEMPLATE
- .xsd and .dtd files are XML_SCHEMA
- You must make sure that values for App Short Name, LOB Code, Territory and Language are correct when sourcing from SCM or EBS. Once you edit the values, make sure to click Evaluate to reevaluate commands and Save your changes after evaluate.
If necessary, you can find values for App Short Name, LOB Code, Territory and Language using following query.
Code Block language sql theme RDark SELECT LOB_CODE, LOB_TYPE, APPLICATION_SHORT_NAME, FILE_NAME, LANGUAGE, TERRITORY, XDO_FILE_TYPE FROM XDO_LOBS
Troubleshooting
- Data Definition and Template not showing up in target after deployment
- Make sure to deploy AOL of type XDO_DS_DEFINITIONS with Name set to LOB Code used for Data Definition and Template.
- See Automating Oracle EBS XML Publisher Reports Migration with FlexDeploy for reference.
- Once again ensure the LOB Code of the XML
- file and Name of the
- AOL of type XDO_DS_DEFINITIONS
- both 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.