Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Performing general server tasks

This chapter contains information on these main topics:

Checking for duplicate data

Due to user errors or other reasons, you may sometimes have duplicate data in your system. You can use Longview Application Administrator to check for duplicate data before you perform a data export or a restatement.

To check for duplicate data:

  1. Open Longview Application Administrator.
  2. Choose Tools > Duplicate Detection. The Duplicate Detection dialog opens.
  3. Complete these fields:
    FieldDescription
    FamilySelect Base (to check Base data only), Schedule (to check Schedule data only), or All (to check all data).
    Data OptionSelect Calculated, Parent, or All types of data.
    Partition ListSpecify the list of partitions you want to check.
  4. Click Run. The results of the duplicate check appear in the Console window.
  5. Click OK.

Working with restatements and recalculations

An enterprise restatement is a mode of calculation in which a rollup of the entire database is performed making all values current. An enterprise restatement is required to calculate the effect of major changes throughout the database.

A partition recalculation is a mode of calculation in which a recalculation of one partition is performed making all values current. A partition recalculation is required to calculate the effect of changes confined to a single partition.

Partition recalculation does not guarantee data integrity under the following scenarios:

  • If the specified partition or partitions do not cover all input leaf data needed to generate data for the specified partition or partitions.
  • If there is output data generated outside of the specified partition or partitions. You will see a warning message in the Longview Data Server Log:

    The output data generated to the following partitions were filtered out during partition recalc on specified_partition_name: list_of_partitions.

You can use Longview Application Administrator to run a recalculation that meets your specific requirements. For information on running a recalculation using line mode, see the Longview Server Manager Guide.

To run a recalculation:

  1. Open Longview Application Administrator.
  2. On the toolbar, click Recalculate. The Recalculate dialog opens.
  3. Select the Recalculation Type. The recalculation types are as follows:
    Recalculation typeSteps included
    AutoPerforms steps based on lvsrvr.cfg parameters set to TRUE.
    Regular
    • Restate Unadjusted
    • Recalculate Journals
    • Restate Adjusting
    Full
    • Restate Unadjusted
    • Recalculate Journals
    • Recalculate Eliminations
    • Restate Adjusting
    Basic
    • Restate Unadjusted
    • Restate Adjusting
    Journal Entries Only

    • Recalculate Journals

  4. Select the partitions you want to include in the recalculation. If you want all partitions included, click Select all.
  5. If you want to enable tracking changes to the Data Server Log file, select Before Recalculation, After Recalculation, or both. In the adjacent text fields, provide the path and file name of the Data Server Log file to which you want this information written.
  6. If you want statistics generated by the recalculation to be recorded, select Run Collect Statistics after recalculation.
  7. If you want to view recalculation statistics, select Display recalculation statistics.
  8. To run the recalculation, click OK. The results of the recalculation appear in the Console window.

Exporting the Data Audit Trail

You can use the Data Audit Trail functionality of Longview to query the database for records of the values in the database that have been changed and by the users who changed them, and to export those records to a text file. This information can be important in recovering from system failures, correcting erroneous entries, and compliance with the Sarbanes-Oxley Act.

Note: Using the Data Audit Trail functionality requires that the Data Audit Trail parameter be set to TRUE in Longview Server Manager (the default value is FALSE). In addition, the RECALC AUDIT RESET command must be performed on the data server. For more information, see the Longview Server Manager Guide. If you do not have access to this functionality, contact your System Administrator.

To export the Data Audit Trail, follow these steps.

  1. Open Longview Application Administrator.
  2. Select Tools > Audit > Export. The Data Audit dialog opens.

    Note: You can enter parameters for as many criteria in the dialog as you choose. If no criterion is specified, all data audit information is returned.

  3. Enter parameters for any or all the following fields:
    1. Symbols
      • To specify a symbol for a dimension, click in the cell under the Symbol column for that dimension to activate a symbol selector button ( ... ). Click the button to view the Symbols dialog and use it to select a symbol for that dimension.

        Note: The data query defaults to the user attribute values found in the UGPD[DimensionNumber]QueryDefault attributes. In addition, if you have access to only one symbol in a dimension, the selection defaults to that symbol.

    2. Schedule Dimension
      • To enable the use of a schedule dimension, select Include Schedule Dimension, and use the drop-down list to select a schedule. To specify a symbol for that dimension, click in the cell under the Symbol column for that dimension to activate a symbol selector button ( ... ). Click the button to view the Select Symbol dialog and use it to select a symbol for that dimension.
    3. User Filter
      • Select User Filter and use the drop-down list to select a user. Changes made by this user only are included in your results.
    4. Date Filter
      • Select Date Filter, and type dates in the MM/DD/YYYY format or use the calendar drop-down menus to select a specific date for each field.
    5. Data Change Threshold
      • Select Data Change Threshold, and use the drop-down menu to select Between, Greater Than, Less Than, or Value Of, then supply a value or values in the field(s) below.
    6. Associated With a Batch
      • Select Associated with a Batch and enter a batch ID number in the field below.
    7. Sorting Options
      • The Sorting Options enable you to specify how to sort the data audit results.
  4. When you have completed configuring the criteria of your query, complete the following fields:
    1. File Name
      • Enter a name for the Export file
    2. Location
      • Enter a location to which you want to save the Export file. Alternately, you can use the Browse button to navigate to the folder to which you want to save the Export file.

        Note: The Export button is unavailable until the File Name and Location are entered.

  5. Click Export. A Data Audit Export progress bar opens.

    Note: Depending on the size of the database and the specificity of your query, a data audit trail export may take several minutes to complete.

  6. After the export finishes, an Export Summary screen opens. This screen summarizes:
    • the number of entries saved
    • the number of errors encountered
  7. Click Close.

Audit Trail Export file syntax

After the Data Audit Export is complete, the data specified by your query is exported to a text file. The syntax of the export file depends on whether only base data was queried, or a schedule was included as well.

Base data

ID{Dim_0{Dim_1{...{Dim_N{Old Value{New Value{Delta{Date{User{Comments

Where:

  • ID is the batch ID number.
  • Dim_0{Dim_1{...{Dim_N are the symbols queried in each base dimension.
  • Old Value is the old value of the data.
  • New Value is the new value of the data submitted to the database.
  • Delta is the difference between Old Value and New Value.
  • Date is the date on which the changes were submitted to the database.
  • User is the username of the user that made the changes.
  • Comments is any comments associated with the changes, enclosed in double quotation marks. If the comments already contain quotation marks, they are enclosed in a second set of double quotation marks (""comment"").

Example:

2174{A11510{A10OPEN{B0910{DIM3SET{DIM4SET{DIM5SET{DIM6SET{DIM7SET{0{99{99{11/26/2010 11:11:58 AM{TAXADMIN{"Trial balance input"

Schedule data

ID{Dim_0{Dim_1{...{Dim_N{Schedule{Sched_Dim1{..{Sched_DimN{Old Value{New Value{Delta{Date{User{Comments

Where:

  • ID is the batch ID number.
  • Dim_0{Dim_1{...{Dim_N are the symbols queried in each base dimension.
  • Schedule is the name of the schedule selected in the Schedule Dimension dropdown list.
  • Sched_Dim1{...{Sched_DimN are the symbols queried in each schedule dimension.
  • Old Value is the old value of the data.
  • New Value is the new value of the data submitted to the database.
  • Delta is the difference between Old Value and New Value.
  • Date is the date on which the changes were submitted to the database.
  • User is the username of the user that made the changes.
  • Comments is any comments associated with the changes, enclosed in double quotation marks. If the comments already contain quotation marks, they are enclosed in a second set of double quotation marks (""comment"").

Example:

3{SALES4{QAFOR01{XL2{DIM3SET{DIM4SET{VALIDATION{DIM6SET{DIM7SET{S1043{L0001{C0001{ 1126{-112{-1238{29/11/2010 12:04:13 PM{LONGVIEW\MIHA228461{"Data submission"

Resetting the Data Audit Trail

If your system has Data Audit Trail selected in the Server Configuration settings, you can reset Data audit detail. If you reset Data audit detail, the trail is deleted and the initial audit values are reset to the current leaf table values. Batch and event information is also deleted, along with related log, error, and history files.

To reset the Data Audit Trail:

  1. In Longview Application Administrator, choose Tools > Audit > Data > Reset. A confirmation dialog opens.

    Caution: Clicking Yes in the next step removes all audit trail values and batch and event information, as well as log, error, and history files in the file paths defined in the Server Configuration settings.

  2. Click Yes. The Data Audit Trail is reset.

Resetting the Metadata Audit Trail

If your system has Metadata Audit Trail selected in the Server Configuration settings and you have the appropriate authorizations, you can reset Metadata Audit trail. If you reset Metadata Audit trail, the trail is deleted according to the specified selections. If the Metadata Audit Trail Log Files location is set in the Server Configuration, a log of the audit records that were reset will be created in the specified location.

To reset the Metadata Audit Trail:

  1. In Longview Application Administrator, choose Tools > Audit > Metadata > Reset. A dialog opens.
  2. Enter parameters for any or all the following fields:
    • Date
      • Type dates in the YYYY/MM/DD format or use the calendar dropdown menus to select a specific date for each field.
    • Category
      • To reset Metadata Audit Trail for specific category types, select one or more of the following:
        • Select All
        • Attribute Maintenance
        • Authorization Maintenance
        • Group Maintenance
        • Group Membership Maintenance
        • Role Maintenance
        • Symbol Maintenance
        • User Maintenance
    • Comment
      • Optionally, type a comment to be included with the reset action.

      Caution: Clicking Reset in the next step removes the specified metadata audit trail information.

  3. Click Reset. The Metadata Audit Trail is reset.

Configuring Journal Entries

Before using Journal Entries, you can modify journal entry settings to meet your company’s needs. You can also create sub-categories for schedule journal entries.

Specifying Journal Entries settings

You can use the Journal Entries Setup dialog to quickly set up and modify settings for Journal Entries more easily than setting individual attributes. You can use this dialog only if you have the necessary permissions to change settings for Journal Entries.

To use the Journal Entries Setup dialog to set up or modify Journal Entries settings, follow these steps:

  1. Open Longview Application Administrator.
  2. Select Tools > Journal Entries Setup. The Journal Entries Setup dialog opens.
  3. On the General tab, set the following parameters:
    ParametersDescription
    Allow the Journal Entry Application ID to be modifiedSpecify whether the Application ID is set only during the initial creation of the journal entries, or whether it can be modified later.
    Share New Journal Entries by defaultSpecify whether you want journal entries to be shared by default.
    Share Posted Journal EntriesSpecify whether all journal entries are shared after posting.
    Allow Journal Entries on areas marked submitted or invisible by workflowSpecify whether you want users to be able to submit journal entries on areas of workflow that have been submitted for approval or are invisible.
    Retain Deleted Journal Entries in the databaseSpecify if you want deleted journal entries to be retained by the database, and users to have the option to retrieve deleted journal entries.
    Number of Decimal Places for Financial Journal EntriesEnter a value between 0-100 or use the arrow buttons to raise and lower the value, to specify the number of decimal places you want financial journal entries to display.
    Number of Decimal Places for Nonfinancial Journal EntriesEnter a value between 0-100 or use the arrow buttons to raise and lower the value, to specify the number of decimal places you want non-financial journal entries to display.
    Dimensions that can be unbalanced in Journal EntriesSelect the check box associated with a dimension to allow it to be unbalanced in journal entries.
  4. Click the Symbols tab.
  5. For each dimension in the database, select a post-able root symbol. This symbol does not have to be a dimension root symbol; however, make sure it contains all possible leaf symbols to be used for adjusting journal entries. Ignore any unused dimensions.
    1. To select a symbol, click in the Default Symbol cell for a dimension. A symbol selector button ( ... ) appears. Click it to open the selection dialog. You can locate and select the default symbol for that dimension. Repeat this step for all applicable dimensions.
  6. When you have completed the general settings and symbol selections, click OK.

Creating sub-categories for journal entries

You can create new journal entry sub-categories in addition to the out-of-the-box sub-categories that are built into Longview. Sub-categories can be associated with schedules.

For more information on schedules, see “Understanding schedules”.

To create a journal entry sub-category, follow these steps.

  1. Open Longview Application Administrator.
  2. The Longview Application Administrator window opens.
  3. In the Server Explorer pane, expand Journal Entries, and select Sub-Categories. The list of sub-categories appears in the Contents window.
  4. Right-click and select New JE Sub-Category. The New JE Sub-Category dialog opens.

  5. Complete the following fields:
    DescriptionType the name of the new sub-category.
    Schedule NameUse the drop-down list to select a schedule to base the sub-category on. For Elimination journal entries, select an Intercompany Transaction schedule such as ICStandard. This field is optional.
    ReclassificationSelect this option to allow base details to have different amounts than the total of the sub-details when the subcategory is applied. This field is available only if you select a Schedule.

    Note: By default, this option is not selected, which forces base details to equal the total of the sub-details.

  6. Click OK. The new sub-category appears in the list in the Contents window.

Specifying NDD settings

The N-Dimensional Distribution, or NDD, functionality of Longview facilitates the distribution of data to all the dimensions in a database. This can be useful when, for example, it is necessary to copy data from an Entity or Account symbol to a Product symbol.

Setting up or modifying NDD

To set or modify your system’s NDD settings, follow these steps:

  1. Open Longview Application Administrator.
  2. Select Tools > NDD Setup. The NDD Setup dialog opens.
  3. Select the Modulating Dimension from the drop-down list.
  4. Select Valid Root Symbols for the Modulating Dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

  5. Select the dimension(s) that you want to be Independent from the Type column drop-down beside the dimension. There must be at least one independent dimension for a valid NDD setup.

  6. Select the Valid Root Symbols for the Independent dimension(s). Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.
  7. Select the dimension(s) that you want to be Dependent from the Type column drop-down beside the dimension. There must be at least one Dependent dimension for a valid NDD setup.

  8. Select the Valid Root Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.
  9. Select the Dependent Default Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

  10. Select the Dependent Modulating Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

  11. For every other dimension that is not Independent or Dependent, select Other as the type, and select the Valid Root Symbols for those dimensions.

  12. Once you have finished selecting types for all dimensions and assigning symbols to them (fields are highlighted yellow to indicate that they must be completed before you can finish the NDD setup), the OK button becomes available. Click OK. Your NDD settings are updated in the system.

    Note: If you manually enter the symbol name for the last field to be completed, you must press Enter before the OK button becomes available.

Setting up or modifying the NDD Pattern Table

The NDD pattern table displays each dimension specified in your system’s NDD setup.

To set up or modify the NDD Pattern Table, follow these steps:

  1. Open Longview Application Administrator.
  2. Select Tools > NDD Pattern Table Setup. The Pattern Table Setup dialog opens.
  3. For each dimension, follow these steps:
    1. Click the symbol selector button ( ... ) associated with the dimension’s root symbol. A symbol selection dialog appears.
    2. Select the symbol you want to serve as the root symbol for that dimension or click the Search icon at the top of the dialog to locate and select the symbol.

      Note: If the symbol you want to select is not one of the actual root symbols, expand the hierarchies to access symbols deeper in the hierarchy. To search for a symbol, click the Search icon at the top of the dialog, enter a search string in either the name or description and click OK. The first matching instance will be shown in the dialog. To find subsequent instances, click the Search Again icon, which is represented by binoculars with a plus symbol.

  4. When you have finished selecting symbols, click OK.

Specifying Event rule settings

You can specify event rule settings that determine the merging of events and their dependencies in your system. You can also specify event rules as persistent to improve system performance. Event rule dependencies apply only if you are using event sequencing.

For more information on event sequencing, see “Configuring Event timing”.

For more information, see:

Specifying Event rule merge settings

You may have event rules that trigger the exact same process based on different circumstances. If this is the case, you can consider merging these rules so that they don’t trigger the process multiple times unnecessarily.

Caution: If you have purchased Tax Provision, your system is preconfigured with event rule merge settings for optimal performance. Changing these settings may have undesirable consequences.

For information on creating Event rules, see “Creating rules”.

To specify Event rule merge settings:

  1. Open Longview Application Administrator.
  2. Select Tools > Event Rule Merging Setup. The Event Rule Merging Setup dialog opens.
  3. Specify a comma-delimited list of IDs, per line, of the Event rules that run the same process. For example:

    30054,30058,30061
    20063,20067,20068,20069
    69952,69953,69954

  4. When you are finished, click OK.

Specifying Event rule dependencies

If your system includes a rule that always triggers another rule, you can specify this dependency so that if those two rules are triggered simultaneously, the system waits for the preceding rule to finish before it allows the dependent rule to process, which uses system resources more efficiently.

Caution: If you have purchased Tax Provision, your system is preconfigured with event rule dependencies for optimal performance. Changing these dependencies may have undesirable consequences.

To specify Event rule dependencies:

  1. Open Longview Application Administrator.
  2. Select Tools > Event Rule Dependency Setup. The Event Rule Dependency Setup dialog opens.
  3. On each line, specify the Event rule ID of the event that triggers a dependent rule, followed by the ID of the dependent rule, separated by a comma. For example:

    30124,30125
    20234,20236
    69850,69950

  4. When you are finished, click OK.

Specifying Persistent Event rules

Whenever an event rule is triggered in your system, an Application Framework process is launched to handle the event. If you have event rules that are triggered frequently, you can specify these events as persistent. A single Management Server process is launched to handle persistent events in the following scenarios:

  • When the server is started
  • If maintenance is turned off
  • If application framework is disconnected and a persistent event rule is triggered

The Management Server process remains in the system until the data server is shut down, to handle each successive triggering of the persistent event. This improves performance, as Application Framework is not initialized each time the event rule is triggered. All event rules in Longview Tax are persistent by default.

Specifying event rules as persistent increases memory consumption on the data server. If you do not allocate enough memory, specifying event rules as persistent may cause your system performance to degrade instead of improving.

If you do not want to use this feature, set the Maximum Persistent Event Rules server configuration parameter to 0. Persistent event rules are also impacted by the setting for the Server Timeout server configuration parameter. For more information on setting server configuration parameters, see the Longview Server Manager Guide.

Caution: Do not specify event rules that turn Maintenance On and Off in Application Framework as persistent. If you do so, the data server will return an error.

System variables are used to set up procedures for use with persistent event rules.

For more information, see “Working with system variables for persistent event rules” in the Longview Developer’s Guide.

To specify persistent Event rules:

  1. Open Longview Application Administrator
  2. Select Tools > Persistent Event Rule Setup. The Persistent Event Rule Setup dialog opens.
  3. Enter the Event rule IDs of events to specify as persistent, one rule ID per line. For example:

    30066
    20089
    69971

    When Event rule IDs are specified in this dialog, a corresponding rulepersists.txt file is created in the data server working directory (for example, C:\Longview\DataServers\LongviewCPM). You can also specify event rules as persistent or not persistent by adding or removing them respectively, from this text file.

    If you make any changes to the list of persistent event rules (in either the Persistent Event Rule Setup dialog, or the rulepersists.txt file) or the name of the procedure launched by the persistent event rules, you must restart the servers for your changes to take effect.

    Note: Multiple persistent event rules that use the same event procedure are handled by the same Management Server process.

  4. When you are finished, click OK.

  5. If you want to organize persistent event rules into groups in separate files, you can create additional persistent event rule text files in the data server working directory. Persistent event rule files must adhere to the following naming convention:

    rulepersistsFileName.txt

    In the text file, enter the Event rule IDs of additional persistent events, one rule ID per line.

    If you are working in Longview Tax, the following persistent event rule text files are preconfigured:

    • RulePersists_ASC.txt
    • RulePersists_Common.txt
    • RulePersists_IAS.txt

    Do not add any persistent event rules to these files. If you want to specify additional event rules as persistent in Longview Tax, specify them in the Persistent Event Rule Setup dialog, or the rulepersists.txt file.

    Note: When you create additional persistent event rule text files or edit existing text files, you must restart the servers for your changes to take effect.

Specifying Parallel Event rules

If your system includes a rule that runs on multiple symbols in a dimension, you can specify this rule to run in parallel. The system will trigger the rule to run at the same time for each independent intersection instead of running one intersection at a time. In addition, each time a specific rule is triggered it will fire immediately. This may allow the event to complete more efficiently, depending on the nature of the calculations. An event rule can be set to run up to 32 events in parallel. If 0 or 1 is specified, then the rule will not run in parallel. If the maximum number of parallel events have been fired, subsequent instances of the same even will be held as pending until at least one of the parallel instances complete. Each of these subsequent instances will be fired independently.

Caution:

    • A persistent event rule will be ignored as persistent if the event rule is also defined as a parallel event.
    • Parallel event rules cannot be merged. Any event rules that are merged and are defined as a parallel event, will be ignored as parallel events.
    • It is not recommended to set parallel event rules to be dependent on other event rules. If a parallel event rule is set to be dependent on another rule the dependent setting will be ignored.

    • To specify Parallel Event rules:

    1. Open Longview Application Administrator.
    2. Select Tools > Parallel Event Rule Setup. The Parallel Event Rules Setup dialog opens.
    3. On each line, specify the Event rule ID of the event that you want to run in parallel, followed by the maximum number of parallel events you want to run for the specified event, separated by a comma. Valid values for the maximum number of parallel events are 0-32, where 0 will not run the event in parallel. For example:

      30124,3
      20234,0
      69850,32

    4. When you are finished, click OK.

    Working with intercompany eliminations

    Eliminations occur when intercompany transactions such as loans, investments, sales and so on, between the parent and subsidiary organizations, are automatically deducted from the consolidated balance sheet and the consolidated income statement. Intercompany accounts are recognized, and automatic journal entries are posted to these accounts. Data is imported into the General Ledger through a bridge so when an intercompany transaction is detected, it automatically creates journal entries at the intersection of an elimination account and elimination entity.

    For example, if operations in Toronto were to have a receivable from operations in Dallas, there would be two entries in the General Ledger for this transaction—an intercompany accounts payable entry for Dallas, and an intercompany accounts receivable entry for Toronto.

    Setting up a New Standard Elimination

    To set up a new standard intercompany elimination, follow these steps:

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the eliminations currently on the server appears in the Contents window.
    3. Right-click anywhere in the Contents window and select New Standard Elimination. The New Standard Elimination dialog opens.
    4. Enter a name and description for the new elimination, and select the Offset tab.
    5. Type the name of the offset account or click the symbol selector button ( ... ) to choose the offset account. Click OK once you have selected the account from the selection dialog.
    6. Select the Accounts tab.
    7. Use the Schedule drop-down list to select the schedule holding intercompany transactions for your account.
    8. Click Add to define an account for the elimination. The Add Account dialog opens.

    9. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    10. Repeat step 9 for the Reporter and Contra fields.
    11. Click Finish. The Add Account dialog closes.
    12. When you have finished defining accounts for the elimination, click OK. The new elimination appears in the list of eliminations.

    Setting up a New Investment Elimination

    To set up a new investment elimination, follow these steps:

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the eliminations currently on the server appears in the Contents window.
    3. Right-click anywhere in the Contents window and select New Investment Elimination. The New Investment Elimination dialog opens.

      Enter a name and description for the new elimination.

    4. Select the Offset tab.
    5. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    6. Select the Capital Accounts tab.
    7. Use the Schedule drop-down list to select the schedule holding intercompany transactions for your account.
    8. Click Add to define an account for the elimination. The Add Account dialog opens.

    9. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    10. Repeat step 10 for the Reporter and Contra fields.
    11. Use the radio buttons to select the Ownership Percentage Method:
      • Default
      • Manual Input
    12. Click Finish once you have finished with these selections.
    13. Select the Investment Accounts tab.
    14. Use the schedule drop-down list to select the schedule holding intercompany transactions for your account.
    15. Click Add to define an account for the elimination. The Add Investment Account dialog opens.

    16. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    17. Repeat step 17 for the Ownership, Reporter, and Contra fields.
    18. Click Finish. The Add Investment Account dialog closes.
    19. When you have finished defining accounts for the elimination, click OK. The new elimination appears in the list of eliminations.

    Editing an intercompany elimination

    To make changes to an existing intercompany elimination, follow these steps.

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the Intercompany Eliminations currently on the server appears in the Contents window.
    3. Right-click the elimination you want to modify and select Properties. The Properties dialog opens for the selected elimination.
    4. Make your changes as needed and click OK.

    Published:

    Performing general server tasks

    This chapter contains information on these main topics:

    Checking for duplicate data

    Due to user errors or other reasons, you may sometimes have duplicate data in your system. You can use Longview Application Administrator to check for duplicate data before you perform a data export or a restatement.

    To check for duplicate data:

    1. Open Longview Application Administrator.
    2. Choose Tools > Duplicate Detection. The Duplicate Detection dialog opens.
    3. Complete these fields:
      FieldDescription
      FamilySelect Base (to check Base data only), Schedule (to check Schedule data only), or All (to check all data).
      Data OptionSelect Calculated, Parent, or All types of data.
      Partition ListSpecify the list of partitions you want to check.
    4. Click Run. The results of the duplicate check appear in the Console window.
    5. Click OK.

    Working with restatements and recalculations

    An enterprise restatement is a mode of calculation in which a rollup of the entire database is performed making all values current. An enterprise restatement is required to calculate the effect of major changes throughout the database.

    A partition recalculation is a mode of calculation in which a recalculation of one partition is performed making all values current. A partition recalculation is required to calculate the effect of changes confined to a single partition.

    Partition recalculation does not guarantee data integrity under the following scenarios:

    • If the specified partition or partitions do not cover all input leaf data needed to generate data for the specified partition or partitions.
    • If there is output data generated outside of the specified partition or partitions. You will see a warning message in the Longview Data Server Log:

      The output data generated to the following partitions were filtered out during partition recalc on specified_partition_name: list_of_partitions.

    You can use Longview Application Administrator to run a recalculation that meets your specific requirements. For information on running a recalculation using line mode, see the Longview Server Manager Guide.

    To run a recalculation:

    1. Open Longview Application Administrator.
    2. On the toolbar, click Recalculate. The Recalculate dialog opens.
    3. Select the Recalculation Type. The recalculation types are as follows:
      Recalculation typeSteps included
      AutoPerforms steps based on lvsrvr.cfg parameters set to TRUE.
      Regular
      • Restate Unadjusted
      • Recalculate Journals
      • Restate Adjusting
      Full
      • Restate Unadjusted
      • Recalculate Journals
      • Recalculate Eliminations
      • Restate Adjusting
      Basic
      • Restate Unadjusted
      • Restate Adjusting
      Journal Entries Only

      • Recalculate Journals

    4. Select the partitions you want to include in the recalculation. If you want all partitions included, click Select all.
    5. If you want to enable tracking changes to the Data Server Log file, select Before Recalculation, After Recalculation, or both. In the adjacent text fields, provide the path and file name of the Data Server Log file to which you want this information written.
    6. If you want statistics generated by the recalculation to be recorded, select Run Collect Statistics after recalculation.
    7. If you want to view recalculation statistics, select Display recalculation statistics.
    8. To run the recalculation, click OK. The results of the recalculation appear in the Console window.

    Exporting the Data Audit Trail

    You can use the Data Audit Trail functionality of Longview to query the database for records of the values in the database that have been changed and by the users who changed them, and to export those records to a text file. This information can be important in recovering from system failures, correcting erroneous entries, and compliance with the Sarbanes-Oxley Act.

    Note: Using the Data Audit Trail functionality requires that the Data Audit Trail parameter be set to TRUE in Longview Server Manager (the default value is FALSE). In addition, the RECALC AUDIT RESET command must be performed on the data server. For more information, see the Longview Server Manager Guide. If you do not have access to this functionality, contact your System Administrator.

    To export the Data Audit Trail, follow these steps.

    1. Open Longview Application Administrator.
    2. Select Tools > Audit > Export. The Data Audit dialog opens.

      Note: You can enter parameters for as many criteria in the dialog as you choose. If no criterion is specified, all data audit information is returned.

    3. Enter parameters for any or all the following fields:
      1. Symbols
        • To specify a symbol for a dimension, click in the cell under the Symbol column for that dimension to activate a symbol selector button ( ... ). Click the button to view the Symbols dialog and use it to select a symbol for that dimension.

          Note: The data query defaults to the user attribute values found in the UGPD[DimensionNumber]QueryDefault attributes. In addition, if you have access to only one symbol in a dimension, the selection defaults to that symbol.

      2. Schedule Dimension
        • To enable the use of a schedule dimension, select Include Schedule Dimension, and use the drop-down list to select a schedule. To specify a symbol for that dimension, click in the cell under the Symbol column for that dimension to activate a symbol selector button ( ... ). Click the button to view the Select Symbol dialog and use it to select a symbol for that dimension.
      3. User Filter
        • Select User Filter and use the drop-down list to select a user. Changes made by this user only are included in your results.
      4. Date Filter
        • Select Date Filter, and type dates in the MM/DD/YYYY format or use the calendar drop-down menus to select a specific date for each field.
      5. Data Change Threshold
        • Select Data Change Threshold, and use the drop-down menu to select Between, Greater Than, Less Than, or Value Of, then supply a value or values in the field(s) below.
      6. Associated With a Batch
        • Select Associated with a Batch and enter a batch ID number in the field below.
      7. Sorting Options
        • The Sorting Options enable you to specify how to sort the data audit results.
    4. When you have completed configuring the criteria of your query, complete the following fields:
      1. File Name
        • Enter a name for the Export file
      2. Location
        • Enter a location to which you want to save the Export file. Alternately, you can use the Browse button to navigate to the folder to which you want to save the Export file.

          Note: The Export button is unavailable until the File Name and Location are entered.

    5. Click Export. A Data Audit Export progress bar opens.

      Note: Depending on the size of the database and the specificity of your query, a data audit trail export may take several minutes to complete.

    6. After the export finishes, an Export Summary screen opens. This screen summarizes:
      • the number of entries saved
      • the number of errors encountered
    7. Click Close.

    Audit Trail Export file syntax

    After the Data Audit Export is complete, the data specified by your query is exported to a text file. The syntax of the export file depends on whether only base data was queried, or a schedule was included as well.

    Base data

    ID{Dim_0{Dim_1{...{Dim_N{Old Value{New Value{Delta{Date{User{Comments

    Where:

    • ID is the batch ID number.
    • Dim_0{Dim_1{...{Dim_N are the symbols queried in each base dimension.
    • Old Value is the old value of the data.
    • New Value is the new value of the data submitted to the database.
    • Delta is the difference between Old Value and New Value.
    • Date is the date on which the changes were submitted to the database.
    • User is the username of the user that made the changes.
    • Comments is any comments associated with the changes, enclosed in double quotation marks. If the comments already contain quotation marks, they are enclosed in a second set of double quotation marks (""comment"").

    Example:

    2174{A11510{A10OPEN{B0910{DIM3SET{DIM4SET{DIM5SET{DIM6SET{DIM7SET{0{99{99{11/26/2010 11:11:58 AM{TAXADMIN{"Trial balance input"

    Schedule data

    ID{Dim_0{Dim_1{...{Dim_N{Schedule{Sched_Dim1{..{Sched_DimN{Old Value{New Value{Delta{Date{User{Comments

    Where:

    • ID is the batch ID number.
    • Dim_0{Dim_1{...{Dim_N are the symbols queried in each base dimension.
    • Schedule is the name of the schedule selected in the Schedule Dimension dropdown list.
    • Sched_Dim1{...{Sched_DimN are the symbols queried in each schedule dimension.
    • Old Value is the old value of the data.
    • New Value is the new value of the data submitted to the database.
    • Delta is the difference between Old Value and New Value.
    • Date is the date on which the changes were submitted to the database.
    • User is the username of the user that made the changes.
    • Comments is any comments associated with the changes, enclosed in double quotation marks. If the comments already contain quotation marks, they are enclosed in a second set of double quotation marks (""comment"").

    Example:

    3{SALES4{QAFOR01{XL2{DIM3SET{DIM4SET{VALIDATION{DIM6SET{DIM7SET{S1043{L0001{C0001{ 1126{-112{-1238{29/11/2010 12:04:13 PM{LONGVIEW\MIHA228461{"Data submission"

    Resetting the Data Audit Trail

    If your system has Data Audit Trail selected in the Server Configuration settings, you can reset Data audit detail. If you reset Data audit detail, the trail is deleted and the initial audit values are reset to the current leaf table values. Batch and event information is also deleted, along with related log, error, and history files.

    To reset the Data Audit Trail:

    1. In Longview Application Administrator, choose Tools > Audit > Data > Reset. A confirmation dialog opens.

      Caution: Clicking Yes in the next step removes all audit trail values and batch and event information, as well as log, error, and history files in the file paths defined in the Server Configuration settings.

    2. Click Yes. The Data Audit Trail is reset.

    Resetting the Metadata Audit Trail

    If your system has Metadata Audit Trail selected in the Server Configuration settings and you have the appropriate authorizations, you can reset Metadata Audit trail. If you reset Metadata Audit trail, the trail is deleted according to the specified selections. If the Metadata Audit Trail Log Files location is set in the Server Configuration, a log of the audit records that were reset will be created in the specified location.

    To reset the Metadata Audit Trail:

    1. In Longview Application Administrator, choose Tools > Audit > Metadata > Reset. A dialog opens.
    2. Enter parameters for any or all the following fields:
      • Date
        • Type dates in the YYYY/MM/DD format or use the calendar dropdown menus to select a specific date for each field.
      • Category
        • To reset Metadata Audit Trail for specific category types, select one or more of the following:
          • Select All
          • Attribute Maintenance
          • Authorization Maintenance
          • Group Maintenance
          • Group Membership Maintenance
          • Role Maintenance
          • Symbol Maintenance
          • User Maintenance
      • Comment
        • Optionally, type a comment to be included with the reset action.

        Caution: Clicking Reset in the next step removes the specified metadata audit trail information.

    3. Click Reset. The Metadata Audit Trail is reset.

    Configuring Journal Entries

    Before using Journal Entries, you can modify journal entry settings to meet your company’s needs. You can also create sub-categories for schedule journal entries.

    Specifying Journal Entries settings

    You can use the Journal Entries Setup dialog to quickly set up and modify settings for Journal Entries more easily than setting individual attributes. You can use this dialog only if you have the necessary permissions to change settings for Journal Entries.

    To use the Journal Entries Setup dialog to set up or modify Journal Entries settings, follow these steps:

    1. Open Longview Application Administrator.
    2. Select Tools > Journal Entries Setup. The Journal Entries Setup dialog opens.
    3. On the General tab, set the following parameters:
      ParametersDescription
      Allow the Journal Entry Application ID to be modifiedSpecify whether the Application ID is set only during the initial creation of the journal entries, or whether it can be modified later.
      Share New Journal Entries by defaultSpecify whether you want journal entries to be shared by default.
      Share Posted Journal EntriesSpecify whether all journal entries are shared after posting.
      Allow Journal Entries on areas marked submitted or invisible by workflowSpecify whether you want users to be able to submit journal entries on areas of workflow that have been submitted for approval or are invisible.
      Retain Deleted Journal Entries in the databaseSpecify if you want deleted journal entries to be retained by the database, and users to have the option to retrieve deleted journal entries.
      Number of Decimal Places for Financial Journal EntriesEnter a value between 0-100 or use the arrow buttons to raise and lower the value, to specify the number of decimal places you want financial journal entries to display.
      Number of Decimal Places for Nonfinancial Journal EntriesEnter a value between 0-100 or use the arrow buttons to raise and lower the value, to specify the number of decimal places you want non-financial journal entries to display.
      Dimensions that can be unbalanced in Journal EntriesSelect the check box associated with a dimension to allow it to be unbalanced in journal entries.
    4. Click the Symbols tab.
    5. For each dimension in the database, select a post-able root symbol. This symbol does not have to be a dimension root symbol; however, make sure it contains all possible leaf symbols to be used for adjusting journal entries. Ignore any unused dimensions.
      1. To select a symbol, click in the Default Symbol cell for a dimension. A symbol selector button ( ... ) appears. Click it to open the selection dialog. You can locate and select the default symbol for that dimension. Repeat this step for all applicable dimensions.
    6. When you have completed the general settings and symbol selections, click OK.

    Creating sub-categories for journal entries

    You can create new journal entry sub-categories in addition to the out-of-the-box sub-categories that are built into Longview. Sub-categories can be associated with schedules.

    For more information on schedules, see “Understanding schedules”.

    To create a journal entry sub-category, follow these steps.

    1. Open Longview Application Administrator.
    2. The Longview Application Administrator window opens.
    3. In the Server Explorer pane, expand Journal Entries, and select Sub-Categories. The list of sub-categories appears in the Contents window.
    4. Right-click and select New JE Sub-Category. The New JE Sub-Category dialog opens.

    5. Complete the following fields:
      DescriptionType the name of the new sub-category.
      Schedule NameUse the drop-down list to select a schedule to base the sub-category on. For Elimination journal entries, select an Intercompany Transaction schedule such as ICStandard. This field is optional.
      ReclassificationSelect this option to allow base details to have different amounts than the total of the sub-details when the subcategory is applied. This field is available only if you select a Schedule.

      Note: By default, this option is not selected, which forces base details to equal the total of the sub-details.

    6. Click OK. The new sub-category appears in the list in the Contents window.

    Specifying NDD settings

    The N-Dimensional Distribution, or NDD, functionality of Longview facilitates the distribution of data to all the dimensions in a database. This can be useful when, for example, it is necessary to copy data from an Entity or Account symbol to a Product symbol.

    Setting up or modifying NDD

    To set or modify your system’s NDD settings, follow these steps:

    1. Open Longview Application Administrator.
    2. Select Tools > NDD Setup. The NDD Setup dialog opens.
    3. Select the Modulating Dimension from the drop-down list.
    4. Select Valid Root Symbols for the Modulating Dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

    5. Select the dimension(s) that you want to be Independent from the Type column drop-down beside the dimension. There must be at least one independent dimension for a valid NDD setup.

    6. Select the Valid Root Symbols for the Independent dimension(s). Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.
    7. Select the dimension(s) that you want to be Dependent from the Type column drop-down beside the dimension. There must be at least one Dependent dimension for a valid NDD setup.

    8. Select the Valid Root Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.
    9. Select the Dependent Default Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

    10. Select the Dependent Modulating Symbols for each Dependent dimension. Either enter the symbol name or click the symbol selector button ( ... ) and use the symbol selection dialog to select a symbol.

    11. For every other dimension that is not Independent or Dependent, select Other as the type, and select the Valid Root Symbols for those dimensions.

    12. Once you have finished selecting types for all dimensions and assigning symbols to them (fields are highlighted yellow to indicate that they must be completed before you can finish the NDD setup), the OK button becomes available. Click OK. Your NDD settings are updated in the system.

      Note: If you manually enter the symbol name for the last field to be completed, you must press Enter before the OK button becomes available.

    Setting up or modifying the NDD Pattern Table

    The NDD pattern table displays each dimension specified in your system’s NDD setup.

    To set up or modify the NDD Pattern Table, follow these steps:

    1. Open Longview Application Administrator.
    2. Select Tools > NDD Pattern Table Setup. The Pattern Table Setup dialog opens.
    3. For each dimension, follow these steps:
      1. Click the symbol selector button ( ... ) associated with the dimension’s root symbol. A symbol selection dialog appears.
      2. Select the symbol you want to serve as the root symbol for that dimension or click the Search icon at the top of the dialog to locate and select the symbol.

        Note: If the symbol you want to select is not one of the actual root symbols, expand the hierarchies to access symbols deeper in the hierarchy. To search for a symbol, click the Search icon at the top of the dialog, enter a search string in either the name or description and click OK. The first matching instance will be shown in the dialog. To find subsequent instances, click the Search Again icon, which is represented by binoculars with a plus symbol.

    4. When you have finished selecting symbols, click OK.

    Specifying Event rule settings

    You can specify event rule settings that determine the merging of events and their dependencies in your system. You can also specify event rules as persistent to improve system performance. Event rule dependencies apply only if you are using event sequencing.

    For more information on event sequencing, see “Configuring Event timing”.

    For more information, see:

    Specifying Event rule merge settings

    You may have event rules that trigger the exact same process based on different circumstances. If this is the case, you can consider merging these rules so that they don’t trigger the process multiple times unnecessarily.

    Caution: If you have purchased Tax Provision, your system is preconfigured with event rule merge settings for optimal performance. Changing these settings may have undesirable consequences.

    For information on creating Event rules, see “Creating rules”.

    To specify Event rule merge settings:

    1. Open Longview Application Administrator.
    2. Select Tools > Event Rule Merging Setup. The Event Rule Merging Setup dialog opens.
    3. Specify a comma-delimited list of IDs, per line, of the Event rules that run the same process. For example:

      30054,30058,30061
      20063,20067,20068,20069
      69952,69953,69954

    4. When you are finished, click OK.

    Specifying Event rule dependencies

    If your system includes a rule that always triggers another rule, you can specify this dependency so that if those two rules are triggered simultaneously, the system waits for the preceding rule to finish before it allows the dependent rule to process, which uses system resources more efficiently.

    Caution: If you have purchased Tax Provision, your system is preconfigured with event rule dependencies for optimal performance. Changing these dependencies may have undesirable consequences.

    To specify Event rule dependencies:

    1. Open Longview Application Administrator.
    2. Select Tools > Event Rule Dependency Setup. The Event Rule Dependency Setup dialog opens.
    3. On each line, specify the Event rule ID of the event that triggers a dependent rule, followed by the ID of the dependent rule, separated by a comma. For example:

      30124,30125
      20234,20236
      69850,69950

    4. When you are finished, click OK.

    Specifying Persistent Event rules

    Whenever an event rule is triggered in your system, an Application Framework process is launched to handle the event. If you have event rules that are triggered frequently, you can specify these events as persistent. A single Management Server process is launched to handle persistent events in the following scenarios:

    • When the server is started
    • If maintenance is turned off
    • If application framework is disconnected and a persistent event rule is triggered

    The Management Server process remains in the system until the data server is shut down, to handle each successive triggering of the persistent event. This improves performance, as Application Framework is not initialized each time the event rule is triggered. All event rules in Longview Tax are persistent by default.

    Specifying event rules as persistent increases memory consumption on the data server. If you do not allocate enough memory, specifying event rules as persistent may cause your system performance to degrade instead of improving.

    If you do not want to use this feature, set the Maximum Persistent Event Rules server configuration parameter to 0. Persistent event rules are also impacted by the setting for the Server Timeout server configuration parameter. For more information on setting server configuration parameters, see the Longview Server Manager Guide.

    Caution: Do not specify event rules that turn Maintenance On and Off in Application Framework as persistent. If you do so, the data server will return an error.

    System variables are used to set up procedures for use with persistent event rules.

    For more information, see “Working with system variables for persistent event rules” in the Longview Developer’s Guide.

    To specify persistent Event rules:

    1. Open Longview Application Administrator
    2. Select Tools > Persistent Event Rule Setup. The Persistent Event Rule Setup dialog opens.
    3. Enter the Event rule IDs of events to specify as persistent, one rule ID per line. For example:

      30066
      20089
      69971

      When Event rule IDs are specified in this dialog, a corresponding rulepersists.txt file is created in the data server working directory (for example, C:\Longview\DataServers\LongviewCPM). You can also specify event rules as persistent or not persistent by adding or removing them respectively, from this text file.

      If you make any changes to the list of persistent event rules (in either the Persistent Event Rule Setup dialog, or the rulepersists.txt file) or the name of the procedure launched by the persistent event rules, you must restart the servers for your changes to take effect.

      Note: Multiple persistent event rules that use the same event procedure are handled by the same Management Server process.

    4. When you are finished, click OK.

    5. If you want to organize persistent event rules into groups in separate files, you can create additional persistent event rule text files in the data server working directory. Persistent event rule files must adhere to the following naming convention:

      rulepersistsFileName.txt

      In the text file, enter the Event rule IDs of additional persistent events, one rule ID per line.

      If you are working in Longview Tax, the following persistent event rule text files are preconfigured:

      • RulePersists_ASC.txt
      • RulePersists_Common.txt
      • RulePersists_IAS.txt

      Do not add any persistent event rules to these files. If you want to specify additional event rules as persistent in Longview Tax, specify them in the Persistent Event Rule Setup dialog, or the rulepersists.txt file.

      Note: When you create additional persistent event rule text files or edit existing text files, you must restart the servers for your changes to take effect.

    Specifying Parallel Event rules

    If your system includes a rule that runs on multiple symbols in a dimension, you can specify this rule to run in parallel. The system will trigger the rule to run at the same time for each independent intersection instead of running one intersection at a time. In addition, each time a specific rule is triggered it will fire immediately. This may allow the event to complete more efficiently, depending on the nature of the calculations. An event rule can be set to run up to 32 events in parallel. If 0 or 1 is specified, then the rule will not run in parallel. If the maximum number of parallel events have been fired, subsequent instances of the same even will be held as pending until at least one of the parallel instances complete. Each of these subsequent instances will be fired independently.

    Caution:

    • A persistent event rule will be ignored as persistent if the event rule is also defined as a parallel event.
    • Parallel event rules cannot be merged. Any event rules that are merged and are defined as a parallel event, will be ignored as parallel events.
    • It is not recommended to set parallel event rules to be dependent on other event rules. If a parallel event rule is set to be dependent on another rule the dependent setting will be ignored.

    • To specify Parallel Event rules:

    1. Open Longview Application Administrator.
    2. Select Tools > Parallel Event Rule Setup. The Parallel Event Rules Setup dialog opens.
    3. On each line, specify the Event rule ID of the event that you want to run in parallel, followed by the maximum number of parallel events you want to run for the specified event, separated by a comma. Valid values for the maximum number of parallel events are 0-32, where 0 will not run the event in parallel. For example:

      30124,3
      20234,0
      69850,32

    4. When you are finished, click OK.

    Working with intercompany eliminations

    Eliminations occur when intercompany transactions such as loans, investments, sales and so on, between the parent and subsidiary organizations, are automatically deducted from the consolidated balance sheet and the consolidated income statement. Intercompany accounts are recognized, and automatic journal entries are posted to these accounts. Data is imported into the General Ledger through a bridge so when an intercompany transaction is detected, it automatically creates journal entries at the intersection of an elimination account and elimination entity.

    For example, if operations in Toronto were to have a receivable from operations in Dallas, there would be two entries in the General Ledger for this transaction—an intercompany accounts payable entry for Dallas, and an intercompany accounts receivable entry for Toronto.

    Setting up a New Standard Elimination

    To set up a new standard intercompany elimination, follow these steps:

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the eliminations currently on the server appears in the Contents window.
    3. Right-click anywhere in the Contents window and select New Standard Elimination. The New Standard Elimination dialog opens.
    4. Enter a name and description for the new elimination, and select the Offset tab.
    5. Type the name of the offset account or click the symbol selector button ( ... ) to choose the offset account. Click OK once you have selected the account from the selection dialog.
    6. Select the Accounts tab.
    7. Use the Schedule drop-down list to select the schedule holding intercompany transactions for your account.
    8. Click Add to define an account for the elimination. The Add Account dialog opens.

    9. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    10. Repeat step 9 for the Reporter and Contra fields.
    11. Click Finish. The Add Account dialog closes.
    12. When you have finished defining accounts for the elimination, click OK. The new elimination appears in the list of eliminations.

    Setting up a New Investment Elimination

    To set up a new investment elimination, follow these steps:

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the eliminations currently on the server appears in the Contents window.
    3. Right-click anywhere in the Contents window and select New Investment Elimination. The New Investment Elimination dialog opens.

      Enter a name and description for the new elimination.

    4. Select the Offset tab.
    5. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    6. Select the Capital Accounts tab.
    7. Use the Schedule drop-down list to select the schedule holding intercompany transactions for your account.
    8. Click Add to define an account for the elimination. The Add Account dialog opens.

    9. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    10. Repeat step 10 for the Reporter and Contra fields.
    11. Use the radio buttons to select the Ownership Percentage Method:
      • Default
      • Manual Input
    12. Click Finish once you have finished with these selections.
    13. Select the Investment Accounts tab.
    14. Use the schedule drop-down list to select the schedule holding intercompany transactions for your account.
    15. Click Add to define an account for the elimination. The Add Investment Account dialog opens.

    16. Do one of the following:
      • Type an account name.
      • Use the symbol selector button ( ... ) to open the selection dialog and choose an account. Click OK once you have selected the account.
    17. Repeat step 17 for the Ownership, Reporter, and Contra fields.
    18. Click Finish. The Add Investment Account dialog closes.
    19. When you have finished defining accounts for the elimination, click OK. The new elimination appears in the list of eliminations.

    Editing an intercompany elimination

    To make changes to an existing intercompany elimination, follow these steps.

    1. Open Longview Application Administrator.
    2. In the Server Explorer pane, select Intercompany Eliminations. A list of the Intercompany Eliminations currently on the server appears in the Contents window.
    3. Right-click the elimination you want to modify and select Properties. The Properties dialog opens for the selected elimination.
    4. Make your changes as needed and click OK.

    For an optimal Community experience, Please view on Desktop