1. Implementing Applications
  2. File Format for Importing Data Loaders of Tree Hierarchies

File Format for Importing Data Loaders of Tree Hierarchies

You can import tree hierarchies to your application by creating separate text files containing values and value set codes. You can then upload these files to the Oracle WebCenter Content document repository.

Here are a few things that you need to keep in mind while creating these files:
  • Use a vertical bar or pipe ( | ) as a delimiter between fields for both the header and the value rows.
  • According to the Oracle WebCenter Content specification, set the file encoding to UTF-8 without the Byte Order Mark (BOM).
  • The first line in the file must be a header line, and the files must look exactly the same as shown in the sample file.
Note: This requirement is specific for a tree with structure code "GL_ACCT_FLEX".

Flat File

To create a file containing tree data loaders, include the headers specified in this table:
Header Data Type Data Size Description Required or Optional
ValueSetCode String 30 This value determines the value used as a parameter for the tree. Required
TreeCode String 30 This value displays the code for the tree. Required
TreeVersionName String 30 This value displays the name for the tree version. Required
TreeVersionStartDate Date -

This value displays the beginning of the date range during which the tree is active and visible on the page. The format is (DD/MM/YYYY).

 Required
TreeVersionEndDate Date - This value displays the end date for the tree version. The application inserts the default date. The format is (DD/MM/YYYY). Optional
Parent 30....Parent1 String 30 This value displays the value set values of the value set code field and represents the internal nodes. Optional
Value String 30 This value displays the value set values of the value set code field and represents the leaf nodes. Optional
IsChild String 1 Set this option to enable or disable the option to add the node as a parent:
  • Y: Enable node as parent or detail value of the hierarchy.
  • N: Disable as parent or detail value of the hierarchy.
Optional

Here's a sample file with the header values at the beginning of the file, followed by the line entries of the hierarchies (tree) data loader. For importing several data loaders, add more line entries in a similar format.

ValueSetCode|TreeCode|TreeVersionName|TreeVersionStartDate|TreeVersionEndDate|Parent30|Parent29|Parent28|Parent27|Parent26|Parent25|Parent24|Parent23|Parent22|Parent21|Parent20|Parent19|Parent18|Parent17|Parent16|Parent15|Parent14|Parent13|Parent12|Parent11|Parent10|Parent9|Parent8|Parent7|Parent6|Parent5|Parent4|Parent3|Parent2|Parent1|Value|IsChild
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941||||N
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366942|||N
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366943|||N
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366942|PARENT3366944||N
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366942|PARENT3366944|3366128|Y
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366943|PARENT3366945||N
Operations Company|OC COA_Company|OC COA_Company|01/1/2019|||||||||||||||||||||||||||||PARENT3366941|PARENT3366943|PARENT3366946|3366126|Y
Operations Company|OC COA_Company|OC COA_Company|01/1/2019||||||||||||||||||||||||||||PARENT3366941|PARENT3366943|PARENT3366947|PARENT3366948|3366127|Y

Related Topics