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 an interchangeable and high-quality format that can be used as a main archive format for this kind of data.

XDF is used for deploying Editioned Database Objects. Using FlexDeploy, you can extract the table definition from your development database and then deploy it to target environments. Due to a database requirement, you must first insert at least one row into the table before extraction (build) will work.

Object Type Identification

Files with extension .xdf are considered regardless of location.

File Extensions

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 (populating from SCM) EBS (manual creation)	SCM, EBS
Name	NAME	Name of the Object	Name of the File without path or extension.
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_USER see 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_PASSWORD see 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.

Related Project Properties

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

java oracle.apps.fnd.odf2.FndXdfGen jdbc_protocol=thin jdbc_conn_string=$(sed -n 's/.*HOST=\([^)]*\)).*/\1/p' <<< "$AD_APPS_JDBC_URL"):$(sed -n 's/.*PORT=\([^)]*\)).*/\1/p' <<< "$AD_APPS_JDBC_URL"):$(sed -n 's/.*SERVICE_NAME=\([^)]*\)).*/\1/p' <<< "$AD_APPS_JDBC_URL") object_name=XXHR_PER_SOCIETIES xsl_directory=$FND_TOP/patch/115/xdf/xsl object_type=table owner_name=$FDEBS_SCHEMAXXHR_DB_USER xdf_filename=$SOURCE_DIR/XXHR_PER_SOCIETIES

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