BI publisher reporting product from Oracle that provides the ability to create and manage highly formatted reports from a wide range of data sources.
- You can source files from SCM or Development environment. It is always recommended to source files from SCM systems for obvious reasons of traceability.
- Sourcing files from SCM
- Commit files to SCM configured for your Project.
- You must put the file in folder configured in EBS Publisher Root Source Directory on project properties. For example, publisher. This folder will be under project configuration source root folder.
- Then perform Populate from xxx, then make sure to verify or configure LOB Type, App Short Name, LOB Code, Territory and Language on each newly discovered publisher files then click Evaluate. Click Save.
- For example, you can commit /publisher/XXHR_A.rtf to SCM and XXHR_A will be LOB Code.
- Sourcing files from development environment
- Go to Files tab - select Publisher files, then click Create and provide file name (For example, LOB Code.extension), evaluate and the configure LOB Type, App Short Name, LOB Code, Territory and Language and click Evaluate again. Click Save.
- For example, you can start with /publisher/XXHR_A.rtf and XXHR_A will be LOB Code.
- Go to Files tab - select Publisher files, then click Create and provide file name (For example, LOB Code.extension), evaluate and the configure LOB Type, App Short Name, LOB Code, Territory and Language and click Evaluate again. Click Save.
| Tip |
|---|
See 1361053908 Considerations below for configuration Publisher files as they require manual entry and evaluate for some attributes. |
...
| 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 |
|---|---|---|---|
| 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 |
...