Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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.
Tip

See Considerations 937789059 below for configuration Publisher files as they require manual entry and evaluate for some attributes.

...

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

Object Type

NameCode
Publisher FilesPUBLISHER

Object Type Attributes

NameCodeDescriptionDefault ValueSupported Values
SourceSOURCEObject Source Location Type

SCM (**populating from SCM)

EBS (**manual creation)

SCM | EBS

App Short Name

APP_SHORT_NAMEApplication Short NameDefaults to EBS Module Application Short Name property.

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

LOB TypeLOB_TYPEXDO LOB type

XML_SAMPLE

See

Considerations

937789059

BURSTING_FILE | DATA_TEMPLATE | TEMPLATE | TEMPLATE_SOURCE | XML_SCHEMA | XML_SAMPLE
Target LocationTARGET_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 CodeTERRITORYISO two-letter territory code. If no territory code, provide 00 to ignore the value.US
LanguageLANGUAGEISO two-letter language code.en
Custom ModeCUSTOM_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_LANGNLS_LANG environment variable


$NLS_LANG
Target File PermissionsFILE_PERMISSIONSPermissions to apply to the file after it is deployedDefaults to the project property FDEBS_FILE_PERMISSIONS

Related Project Properties

NameCodeDescriptionDefault Value
EBS Publisher Root Source DirectoryFDEBS_PUBLISHER_ROOT_SOURCE_DIRSource folder for publisher files (e.g. xmlpub).publisher

EBS Publisher Root Destination Directory

FDEBS_PUBLISHER_ROOT_DESTINATION_DIRTarget directory for Publisher files (e.g. $XXHR_TOP/publisher).$<PROD_TOP>/patch/115/publisher
EBS Publisher Default Custom ModeFDEBS_PUBLISHER_CUSTOM_MODE

When populating or evaluating files deployed with XDOLoader, set the CUSTOM_MODE of publisher files to this.

FORCE

File PermissionsFDEBS_FILE_PERMISSIONSTarget File Permission. Will be set to target file after deployment using chmod. eg: 755

...