Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Current »

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 for some attributes.

Object Type Identification

  • Files with extensions .pdf, .rtf, .xsd, .xlf are included regardless of location, Or
  • Files with extensions .xml, .xls, .xsl, .pdf, .rtf, .xsd that are in the publisher folder1

1 - 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.

File Extensions

NameDescription
.rtfXML Publisher (XDO) translatable templates and non-translatable RTF templates.
.pdfXML Publisher (XDO) PDF templates.
.xsdXML Publisher (XDO) non-translatable XML Schema.

Attributes

NameDescriptionDefault ValueSupported Values
SourceObject Source Location Type

SCM (**populating from SCM)

EBS (**manual creation)

SCM | EBS

App Short Name

Application Short NameDefaults to EBS Module Application Short Name property.

LOB CodeXDO LOB code. Enter either the Template Code 
or the Data Definition Code.
<file name> (**without path/extension)
XDO File TypeXDO File type

LOB TypeXDO LOB type

XML_SAMPLE

See Considerations

BURSTING_FILE | DATA_TEMPLATE | TEMPLATE | TEMPLATE_SOURCE | XML_SCHEMA | XML_SAMPLE
Target LocationPath 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 CodeISO two-letter territory code. If no territory code, provide 00 to ignore the value.US
LanguageISO 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

Default can be changed using EBS Publisher Default Custom Mode property.

NOFORCE | FORCE
NLS LangNLS_LANG environment variable


$NLS_LANG

Related Project Properties

NameDescriptionDefault Value
EBS Publisher Root Source DirectorySource 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

  1. 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,
    1. .pdf, .rtf, .xls, .xsl, .xlf files are TEMPLATE
    2. .xsd and .dtd files are XML_SCHEMA
  2. You must make sure that values for App Short Name, LOB Code, Territory and Language are correct when sourcing from SCM or EBS.
  3. 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.
  • No labels