Page Comparison

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 Code, App Short Name, LOB Type, 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 Code,App Short Name, LOB Type, 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.

...

...

...

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. Once you edit the values, make sure to click Evaluate to reevaluate commands and Save your changes after evaluate.

   1. If necessary, you can find values for App Short Name, LOB Code, Territory and Language using following query.

      Code Block
      language sql
      SELECT LOB_CODE, LOB_TYPE, APPLICATION_SHORT_NAME, FILE_NAME, LANGUAGE, TERRITORY, XDO_FILE_TYPE FROM XDO_LOBS

...

If you want to avoid manually entering values like Territory, then following customization script can be used. For example, if file is stored as "/publisher/US/en/abc.rtf" in source control system, then US will be recognized as Territory. This is example for Territory and same logic can be applied for LOB Code, App Short Name, LOB Type, Territory and Language as necessary.

// publisher file customization to allow use of territory and language from path
// User will enter path as /publisher/US/en/XXHR_BIP_ROSTER.rtf
// Format - <parent folder>/publisher/<territory>/<language>/<file name with extension>

// Find what folder name we are using for publisher files
PUB_ROOT=FDEBS_PUBLISHER_ROOT_SOURCE_DIR != null && FDEBS_PUBLISHER_ROOT_SOURCE_DIR != '' ? FDEBS_PUBLISHER_ROOT_SOURCE_DIR : 'publisher';
if (FILE_PATH.indexOf(PUB_ROOT) > -1)
{
    // if file path does not have publisher folder then we can't do anything
    // let's remove anything including first / from path first, then split it
    EFFECTIVE_PATH=FILE_PATH.substring(FILE_PATH.indexOf(PUB_ROOT));
    parts=EFFECTIVE_PATH.split('/');
    if (parts.length >= 4)
    {
        return parts[1];
    }
}
return null;