Solomon IV – Read Consolidation File

iMIS provides support to meet export/import requirements for Solomon IV Read Consolidation File.  This support is in place in iMIS LAN version 3.00e or greater and iMIS version 3.30d or greater.

The standard Solomon IV Interface makes use of the built-in Solomon IV general ledger consolidation option. The export file created by iMIS when the Solomon IV option is chosen from the GL Interface down drop list is formatted according to the requirements of the import file needed by the General Ledger - Read Consolidation File window (01.510.00).

Make sure all GL accounts in iMIS match the accounts in Solomon’s charge of accounts (and sub-accounts, if used in Solomon). When you enter a GL account in iMIS, use the format AAAA-SSSS, where A=the account number (i.e. 1200 for AR) and SSSS=sub-account number (defined in Solomon). The length of the account or sub-account can vary, and is defined in Solomon.

Note: iMIS currently supports two methods to export/import general ledger or financial data to Solomon IV. Financial transaction data can either be exported/imported using the Read Consolidation File method discussed here, or through the Transaction Import Utility. You may wish to review the import steps for both options before deciding which one you would prefer to use. For those users who are licensed for the iMIS Accounts Payable Interface, AP vendor and transaction data can only be imported using the Transaction Import Utility.

Note: Address line 3, which was added in iMIS 10.6, is not exported because the Transaction Import utility does not support it.

To set up iMIS for Solomon IV – Read Consolidation File

A Currency ID is required in the Read Consolidation import file as of Solomon IV version 4.21. A field was added to the AR/Cash General Ledger Interface window in iMIS version 4.41.

  1. From AR/Cash, select Set up module, and click G/L Interface to open the AR/Cash General Ledger Interface window.
  2. Click Edit.
  3. From the GL interface type drop-down list, select Solomon IV.
  4. Select an option from the Summarize by drop-down list.
  5. Enter the Output File Path/Name, which dictates how iMIS should name the export/import file and where it should be stored.

    6. For best results, set the extension of the file name to .txt (i.e., I:\IMIS\GLINT.TXT). 

    • Use a # sign in the file name to instruct iMIS to create files for each iMIS organization code, with the ORG code inserted in the file name.
    • Use a ? mark in the file name to instruct iMIS to create sequentially numbered files with each subsequent file that is generated.

    For example, #glint?.dta will create ORG1glint1.txt and ORG2glint1.txt for the first export and ORG1glint2.txt and ORG2glint2.txt for the next export.

  6. Enter the Currency ID from your Solomon GL Setup (Module > General Ledger > GL Setup > Currency Info tab). The Currency ID field only displays when the Solomon IV GL interface type is chosen.
  7. Click Save.

To create the export file from iMIS (Solomon IV – Read Consolidation File)

  1. Generate the general ledger transaction export files using AR/Cash > Process month-end procedures > Create GL Journal. If batch processing is enabled, only posted batches are included.

To import data into Solomon IV – Read Consolidation File

The steps to import data into Solomon IV using this method are:

  1. Choose General Ledger > Read Consolidation.
  2. At the prompt, Name of File to be Read, enter the export file name including the path name that you specified in iMIS.  Notice that a Browse button is available to help you locate the file without typing it in.
  3. At the prompt, Period to Post, enter the appropriate fiscal month and year for the transactions that are being imported.  For example, the second fiscal period of 2002 would be entered as 02-2002.
  4. Click the Begin Processing button to start the import process.  A status box will appear to processing status information.  When finished, it will inform you of the location of the log file to check for any errors, etc.
  5. If errors occurred, the most likely problem may relate to validity errors with the GL account or the sub account.  The error messages will point you to the exact error for your review.
  6. If the import was successful, you can review the imported iMIS batch by choosing General Ledger > Journal Transactions.  To locate the iMIS batch, you can press the F3 function key at the Batch Nbr prompt.
  7. From this window, you may wish to select the Quick Print button to get a printout of the imported iMIS batch.
  8. To make the batch ready for posting, select Release Now from the Batch Handling drop-down list.
  9. To post the iMIS batch, choose General Ledger > Post Transactions.

File Layout Example

'1200' '1' '1200' '06/01/2001' 'AR, GEN-MEETING-AR' '1500.00' 'D' 'BAS'
'4300' '1' '4300' '06/01/2001' 'DIST, DEMO_AR_LABELS' '1500.00' 'C' 'BAS'
@
 
File layout definition:
# Field Name , Sample Data , Comments
1 account number, '1200', iMIS account number field, up to first dash (-)
2 subaccount number, '1', from iMIS account number field, after the dash (-)
3 ref number, '1200', iMIS account number field, up to first dash (-); Solomon Ref#
4 date, '06/01/2001'
5 description, 'AR, GEN-MEETING-AR'
6 amount, '1500.00'
7 credit or debit, 'D'
8 currency, 'BAS', entered in AR/Cash GL Interface setup in iMIS
9 end of file marker, '@'