EBS Object Types - XML Definition Files (XDF)

XDF is used to store high-dimensional data and information related to it in compact XML format. The purpose is to have interchangeable and high-quality format that can be used as a main archive format for this kind of data.

Object Type Identification

  • Files with extension .xdf are considered regardless of location.

File Extensions

File content is also further analyzed by populate process.

Name

Description

Name

Description

.xdf

XML Definition File for storing high-dimensional data and related information.

Object Type

Name

Code

Name

Code

XML Definition Files (XDF)

XDF

Object Type Attributes

Name

Code

Description

Default Value

Supported Values

Name

Code

Description

Default Value

Supported Values

Source

SOURCE

Object Source Location Type

SCM

SCM

Target Location

TARGET_LOCATION

Path to where the file should be deployed to.

$<PROD_TOP>/patch/115/xdf/

 

Primary Object Schema Property

PRIMARY_OBJECT_SCHEMA

FlexDeploy property to use as the user to connect to the database with.

If the xdf file contains "Primary Object Schema Name :"

then the value becomes

FDEBS_SCHEMA${SCHEMA_NAME}_DB_USERsee note1 otherwise it defaults to

FDEBS_DB_USER

 

Primary Object Password Property

PRIMARY_OBJECT_PASSWORD

FlexDeploy property to use as the password for the DB User Property.

If the xdf file contains "Primary Object Schema Name :"

then the value becomes

FDEBS_SCHEMA${SCHEMA_NAME}_DB_PASSWORDsee note1 otherwise it defaults to

FDEBS_DB_PASSWORD

 

JDBC Protocol

JDBC_PROTOCOL

Driver type for the database.

thin

thin | oci8

Object Type

TYPE

XDF Object Type

all

all | table | qtable | mview | mviewlog | sequence | type | trigger | view | policy

XSL Directory

XSL_DIRECTORY

Path to where the xsl folder is located.

$FND_TOP/patch/115/xdf/xsl

 

Target File Permissions

FILE_PERMISSIONS

Permissions to apply to the file after it is deployed

Defaults to the project property FDEBS_FILE_PERMISSIONS

 

note1

If the FDEBS_SCHEMA${SCHEMA_NAME}_DB_USER and FDEBS_SCHEMA${SCHEMA_NAME}_DB_PASSWORD properties are used, these properties need to be added to the workflow as user defined Targets properties and then configured on the topology screen.

Name

Code

Description

Name

Code

Description

File Permissions

FDEBS_FILE_PERMISSIONS

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

Sample Build Commands 

N/A - Build commands not supported for this type.

Sample Deploy Commands 

cp "$SOURCE_FILE" "$XXHR_TOP/patch/115/xdf/"; java oracle.apps.fnd.odf2.FndXdfCmp $FDEBS_DB_USER $FDEBS_DB_PASSWORD $FDEBS_DB_USER $FDEBS_DB_PASSWORD thin "$AD_APPS_JDBC_URL" all "$XXHR_TOP/patch/115/xdf/POS_BANK_PAYEE_BO.xdf" $FND_TOP/patch/115/xdf/xsl
The following macros are not currently supported in the footer:
  • style