BI publisher reporting product from Oracle that provides the ability to create and manage highly formatted reports from a wide range of data sources.
...
| Tip |
|---|
See Considerations below for configuration Publisher files as they require manual entry and evaluate for some attributes. |
Object Type Identification
...
| 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 NameXXHR | Defaults to EBS Module Application Short Name property. | |
| 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 See Considerations | 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/Default can be changed using EBS Publisher Root Destination Directory property. | |
| 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
Default can be changed using EBS Publisher Default Custom Mode property.(Changed from | NOFORCE in 4.5.1 release)NOFORCE | FORCE |
| NLS Lang | NLS_LANG environment variable | $NLS_LANG |
...
| 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 |
...
- When populating XML files from an SCM, the LOB Type is defaulted based file extension and file data. When sourcing files files from EBS, 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.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
- 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 Failure to do so will result in the attachments not appearing under the data definition in EBS.