Configure Longview CXO Export

Connection

To configure Longview CXO Export:

1. Copy the file CXO Export Configuration\Templates\Connection.cfg to the same location as CXOExport.bat
2. Edit the copy of the file as required to connect to the source Longview system.
   1. LVID: Set to the identifier of the source system.
   2. LVServer: Use one of the options (and delete the other line):
      1. Specify URL to the server (if using HTTP Proxy).
      2. Specify host and listener port otherwise.
   3. LVUser: Specify the user to connect to the source system with.
   4. LVPassword: Specify the password for the specified user.
   5. LVGroup: Specify the user group to connect to the source system with.
3. Copy the template configuration file for the export you are executing to a location of your choice and configure as required.

System Attributes

The system attributes configuration file supports the use of tokens as the file is resolved prior to execution, so you can use variables and attributes in the definition of values.

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – The target folder for output files and log.
• CXO.SystemAttributeList - The value specified contains all the attributes that are supported in CXO by default.

To configure CXO export for system attributes:

1. Copy the file CXO Export Configuration\Templates\SystemAttributes.cfg to another location.

   • You can also rename the file, but the name must start with SystemAttributes.

2. Modify the file, as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is attributes\<current period>).
   • Edit the value of the property CXO.SystemAtrtributeList.
     1. Separate each attribute name with ‘|’

        Note: The template file contains all system attributes that are supported by CXO without additional custom configuration in CXO.

     2. Separate each attribute name with ‘|’

        Note: The template file contains all system attributes that are supported by CXO without additional custom configuration in CXO.

Hierarchies

The hierarchy configuration file supports the use of tokens as the file is resolved prior to execution, so you can use variables and attributes in the definition of values.  While not all dimensions need to be included in each configuration file, when supporting a data export from the source system the equivalent symbol structures should be retrieved.

If the CXO.[[Entities]].SpecList property is removed, then the CXO.[[Entities]].AttributeList property should also be removed.

Extracting of schedule dimensions is supported for all Longview implementations and is specified in the same way.

For each schedule in the system (excluding Comments, DataAttributes, FileAttachments, LineItemDetails, ScenarioDetails, VComments, VLineItemDetails, WFStatus) a property with the name CXO.<ScheduleName>.<ScheduleDimensionName>.SpecList is created.

To extract the hierarchy for a specific schedule dimension set the property value equal to “Total”. You can extract multiple schedule dimension hierarchies at once and these can be combined with base dimension hierarchies.

Example

Set PROPERTY CXO.ICStandard.CONTRAS.SpecList = “TOTAL”

Longview Close hierarchies

The extract template for Longview Close hierarchies is configured to support the following reports:

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – target folder for output files and log
• CXO.ICSource.Contras.SpecList = "TOTAL" – symbol specification for the Contras dimension of the ICSource schedule
• CXO.[[Accounts]].SpecList – symbol specifications for accounts
• CXO.[[TimePeriods]].SpecList – symbol specifications for time
• CXO.[[Entities]].SpecList – symbol specifications for entities
• CXO.[[Currencies]].SpecList – symbol specifications for currencies
• CXO.DATAVIEWS.SpecList – symbol specifications for data views
• CXO.SCENARIOS.SpecList – symbol specifications for scenarios
• CXO.COST_CENTRES.SpecList – symbol specifications for custom dimension COST_CENTRES
  • Remove or modify to match your custom dimensions
• CXO.PRODUCTS.SpecList – symbol specifications for custom dimension PRODUCTS
  • Remove or modify to match your custom dimensions
• CXO.[[Entities]].AttributeList – native currency for entities

To configure CXO export for Longview Close hierarchies:

1. Copy the file CXO Export Configuration\Templates\Hierarchy_CLOSE.cfg to another location
   • You can also rename the file, but the name must start with Hierarchy
2. Modify the file as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is hierarchy\<current period>)
   • In the schedule dimension section
     • Set the SpecList for the schedule dimensions in the target system to “TOTAL”
     • Set the SpecList for the schedule dimensions in the target system to “TOTAL”
   • In the Standard dimension section (accounts, time, entities, and currencies)
     • Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’
   • In the CLOSE dimensions section (data views, scenarios)
     • No modifications are required unless you have additional custom hierarchies in your system
   • In the Custom CLOSE dimensions section
     • Modify or remove the existing sample dimensions to match the custom dimensions in the source system
     • You need one Set statement for each custom dimension in the system

Longview Tax hierarchies

Longview Tax hierarchies contains several template files, each of which is configured for specific tax systems.

Note: Depending on the source system use either ASC Provision, IAS Provision or ASC Multi-Regional Provision reports. Use Global Transparency only if it is included in the source system.

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – target folder for output files and log
• CXO. CounterpartyAdjustmentDetails.COUNTERPARTY.SpecList = "TOTAL" – symbol specification for the COUNTERPARTY dimension of the CounterPartyAdjustmentDetails schedule
• CXO.[[Accounts]].SpecList – symbol specifications for accounts
• CXO.[[TimePeriods]].SpecList – symbol specifications for time
• CXO.[[Entities]].SpecList – symbol specifications for entities
• CXO.[[Currencies]].SpecList – symbol specifications for currencies
• CXO.DETAILS.SpecList – symbol specifications for details
• CXO.SEGMENTS.SpecList – symbol specifications for segments
• CXO.ELEMENTS.SpecList – symbol specifications for elements
• CXO.CONTROLS.SpecList – symbol specifications for controls
• CXO.[[Entities]].AttributeList – native currency for entities

To configure CXO export for Longview Tax hierarchies:

1. Copy the file CXO Export Configuration\Templates\Hierarchy_TAX.cfg to another location.
   • You can also rename the file, but the name must start with Hierarchy.
2. Modify the file, as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is hierarchy\<current period>).
   • In the schedule dimension section.
     1. Set the SpecList for the schedule dimensions in the target system to “TOTAL”.
   • In the Standard dimension section (accounts, time, entities, and currencies).
     1. Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’
   • In the TAX dimensions section (details, segments, elements, and controls).
     1. Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’
   • In the Attributes section:
     1. No modifications should be required.
     2. CXO only supports the native currency of entities without additional custom configuration in CXO.

Data

The data configuration file supports the use of tokens as the file is resolved prior to execution, so you can use variables and attributes in the definition of values.

Note: If the target CXO implementation includes one or more schedules these dimensions must be specified when extracting base data and schedule data from a specific schedule. Schedule dimensions with no context in the data requested with be extracted with a dimension member of NONE.

For each schedule in the system (excluding Comments, DataAttributes, FileAttachments, LineItemDetails, ScenarioDetails, VComments, VLineItemDetails, WFStatus) a property with the name CXO.<ScheduleName>.<ScheduleDImensionName>.SpecList is created.

For example, when extracting base data to a target system with schedule dimensions, specify each schedule dimension (CXO.<ScheduleName>.<ScheduleDImensionName>) as “NONE”.

To extract schedule data for a specific schedule set the dimension for the specific schedule as “TOTAL”.

Example: Base Data Only

Example: ICSource Schedule data

Example: ICCapital Schedule data

Note: You can extract data only for a s ingle schedule at a time.

Longview Close data

The extract template for Longview Close data is configured to support the following reports:

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – target folder for output files and log
• CXO.ICSource.Contras.SpecList = "TOTAL" – symbol specification for the Contras dimension of the ICSource schedule
• CXO.[[Accounts]].SpecList – symbol specifications for accounts
• CXO.[[TimePeriods]].SpecList – symbol specifications for time
• CXO.[[Entities]].SpecList – symbol specifications for entities
• CXO.[[Currencies]].SpecList – symbol specifications for currencies
• CXO.DATAVIEWS.SpecList – symbol specifications for data views
• CXO.SCENARIOS.SpecList – symbol specifications for scenarios
• CXO.COST_CENTRES.SpecList – symbol specifications for custom dimension COST_CENTRES
  • Remove or modify to match your custom dimensions
• CXO.PRODUCTS.SpecList – symbol specifications for custom dimension PRODUCTS
  • Remove or modify to match your custom dimensions

To configure CXO export for Longview Close data:

1. Copy the file CXO Export Configuration\Templates\Data_CLOSE.cfg to another location.
   • You can also rename the file, but the name must start with Data.
2. Modify the file as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is data\<current period>).
   • In the schedule dimension section, do one of the following:
     1. To extract base data set the SpecList for each schedule dimension to “NONE”.
     2. To extract schedule data set the SpecList for the dimensions of one schedule to “TOTAL”, with the rest as “NONE”.
   • In the Standard dimension section (accounts, time, entities, and currencies):
     1. Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’
   • In the CLOSE dimensions section (data views, scenarios).
     1. No modifications are required unless you have additional custom hierarchies in your system.
   • In the Custom CLOSE dimensions section:
     1. Modify the or remove the existing sample dimensions to match the custom dimensions in the source system.
     2. You need one Set statement for each custom dimension in the system.

Longview Tax data

Longview Tax contains several template files, each of which is configured for specific reports.

Note: Depending on the source system use either ASC Provision, IAS Provision or ASC Multi-Regional Provision reports. Use Global Transparency only if it is included in the source system.

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – target folder for output files and log
• CXO. CounterpartyAdjustmentDetails.COUNTERPARTY.SpecList = "TOTAL" – symbol specification for the COUNTERPARTY dimension of the CounterPartyAdjustmentDetails schedule
• CXO.[[Accounts]].SpecList – symbol specifications for accounts
• CXO.[[TimePeriods]].SpecList – symbol specifications for time
• CXO.[[Entities]].SpecList – symbol specifications for entities
• CXO.[[Currencies]].SpecList – symbol specifications for currencies
• CXO.DETAILS.SpecList – symbol specifications for details
• CXO.SEGMENTS.SpecList – symbol specifications for segments
• CXO.ELEMENTS.SpecList – symbol specifications for elements
• CXO.CONTROLS.SpecList – symbol specifications for controls

To configure CXO export for Longview Tax data:

1. Copy the file from CXO Export Configuration\Templates to another location.
   • You can also rename the file, but the name must start with Data.
2. Modify the file, as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is data\<current period>).
   • In the schedule dimension section, do one of the following:
     1. To extract base data set the SpecList for each schedule dimension to “NONE”
     2. To extract schedule data set the SpecList for the dimensions of one schedule to “TOTAL”, with the rest as “NONE”.
   • In the Standard dimension section (accounts, time, entities, and currencies):
     1. Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’
   • In the TAX dimensions section (details, segments, elements, and controls):
     1. Edit the value of the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’

Data Table

The data table configuration file supports the use of tokens as the file is resolved prior to execution, so you can use variables and attributes in the definition of values.

Template file

The template file contains configuration for the following properties:

• CXO.TargetFolder – target folder for output files and log
• CXO.DataTableName – used to specify the name of the data table to extract
• CXO.[[TimePeriod]].ColumnName – used to specify the column name to perform filtering of time symbols against
• CXO.[[TimePeriod]].SpecList – used to specify the time symbols to restrict data table export to

To configure CXO export for a data table:

1. Copy the file CXO Export Configuration\Templates\DataTable.cfg to another location.
   • You can also rename the file, but the name must start with DataTable.
2. Modify the file, as required:
   • Edit the value of the property CXO.TargetFolder to set the desired location for the file generated (Default is datatable\<current period>).
   • Edit the value of the property CXO.DataTableName to specify the name of the table to export.
   • To filter data exported using symbol columns, for each symbol column:
     1. Specify the name of the column using the property CXO.<Dimension>.ColumnName
     2. Specify the symbols to restrict using the property CXO.<dimension>.SpecList, separating each symbol name with ‘|’