Adjutant Wiki MW Pivot Skin

General Import Template File Notes

• Template files are typically generated from their respective Import screen using an 'Export Template' button.
• Using the 'Export Template' button from an updated system will help ensure that you are using the most up-to-date import file, and will help avoid errors.
• Templates generally (but not in all cases) contain 3 rows of header information.
  • The first row is generally labelled with f1 through f## and is used to give a consistent column id to each data column. Do not remove this row unless instructed.
  • The second row is labelled with the column data/field name. The values in this row are used for the file mapping screen. Editing these values is generally not needed and may make the field mapping process difficult.
  • The third row (if present) is labelled either with the same values from row 2, or with more detailed field descriptions. The third row is available to create a customer-friendly name for the associated data column.
    • The third row should be removed from the source file prior to importing. It will cause errors since it will be treated as the first import record on the file.
• Import files MUST always be saved as 'Microsoft Excel 5.0/95 Workbook (*.xls)' format until further notice. The import screens will generate errors if the file type is not correct.

• It is a good idea to perform a Mapping Table Import using a current source list before beginning on any imports. Without a current mapping table, the quality of imports can be compromised. The Mapping Table Import only needs to be run once on a newly set up Adjutant system. It does not need to be run before each import.
  • Export a current list from the Mapping Table Import screen from an updated system (or contact your Implementation Consultant for an updated file).
  • Perform a Mapping Table Import on the target system with the XLS file from the step above.

GL Budget Import Notes

Timing and Preparation

The GL Budget Import can be requested at any time after the GL chart of accounts has been established and the CID Maintenance Fiscal Calendars have been completed.

General Notes

The GL Budget Export screen can be used to create an import template with the GL account and GL description column details already completed.

The GL Budget Import can build the current year budget and future year budgets as long as the corresponding year's fiscal calendar is set up.

The imported budget details display in the Budgets tab of the GL Account screen. After importing budget details, the GL Accounts screen must be closed and reopened before the new budget details will display.

GL Budget Import File Data Scrubbing

Budget Name - Make sure the budget name (bname) column is filled out for all detail lines. If the budget name value is blank, or does not match for all entries, it may create unexpected records.

Fiscal Year - Make sure the fiscal year (fisyear) column is filled out with the correct year (YYYY) for all detail lines. If the fiscal year value is blank, the budget period details will not build correctly, and the data will be unusable.

GL Budget Export Screen (GLBUDGETEXP)

Menu Location: Transaction>>Importers/Exporters>>Accounting>>GL Budget Export

Starting GL Account: Enter a starting GL account to filter the export file by a GL account range.

Ending GL Account: Enter an ending GL account to filter the export file by a GL account range.

Mask to Export: Enter the GL account segment values in the correct space to export all accounts that match the entered segment value.

Budget: Select the existing budget details to export. If 'BLANK' is selected, an export of the selected GL accounts without any budget name, period, or details will be created.

Export: Generates an export file with the selected GL accounts, selected budget name, and budget details filled out. This file can be edited and used as an import file without changing any of the file layout details.

GL Budget Import Screen (IMPORTBUDGET)

Menu Location: Transaction>>Importers/Exporters>>Accounting>>GL Budget Import

File Name/Browse: Use the Browse button to locate and select the completed GL Budget import template file (in XLS format)

Export Template: Generates a blank GL Budget Import template file. The GL Budget Export screen is prefered over this method, since the GL Budget Export screen can create a nearly ready-to-go template.

Map Fields: Fields must be mapped prior to importing. If no changes have been made to the column headings, the mapping screen should show all green, and you can click OK to continue. If any of the Input Field Name columns on the left are red, single-click on the line on the left column, and then double-click the desired mapped field in the right column to complete the mapping. Repeat for any red lines on the left that should be mapped. If there are additional columns in the source file that should NOT be mapped, they can be left unmapped (displayed in red). Mandatory fields will require that they be mapped before clicking OK.

GL Budget Import File Definitions

Required fields are indicated with *

*f1 - GLACCT - GL account number

f2 - GLDESC - GL account description. This column is not required for import. It is automatically filled in when using the GL Budget Export, and the description can be helpful for identifying accounts.

*f3 - BNAME - Budget name (up to 30 characters alphanumeric)

*f4 - FISYEAR - Fiscal year for the budget details (YYYY)

f5 - f19 - PERIOD### - Budget dollar amount for the corresponding fiscal period. The fiscal periods 1 through 15 correspond to the sequence of fiscal periods defined in the CID Maintenance Fiscal Calendar screen, and will match the 'YearPrd' entries displayed in the GL Balances tab.

f20 - f34 - SPERIOD### - Budget statistical amount for the corresponding fiscal period. The statistical fiscal periods 1 through 15 correspond to the sequence of fiscal periods defined in the CID Maintenance Fiscal Calendar screen, and will match the 'YearPrd' entries displayed in the GL Balances tab.

GL Budget Import Reconciliation

Prior to posting any imported data, run the GL Distribution detail report to verify the imported totals. Spot-check several accounts for totals.

The GL Distribution report can be exported to Excel for performing easy calculations if there any balance issues or unexpected totals.

Once the batch has been posted, run the GL Trial Balance for the month imported, and review for any GL out of balance situations caused by accounts withe wrong account type or accounts imported with the wrong debit/credit value.

Once the batch has been posted, run the General Ledger report for the month imported and review the detail for accuracy and look for any issues.

Imported GL Batches can be deleted (voided) from the GL Journal Entry Batch Header screen before they are posted, if the import file needs to be adjusted and re-imported.

GL Balance Import Additional Steps

Imported GL Batches must be posted before they hit the GL.

GL Balance Import Database Tables

Importing GL Balance records can affect the following databases:

GLBATCHH - Each import creates a unique KEYNO tied to the imported BATCHNO. This record contains the header information only.

GLDIST - The import details are saved in GLDIST with the BATCHNO value and the KEYNOH value which links to the KEYNO in the GLBATCHH table.

GLBALS - The GL Balances are updated in the GLBALS table by GL account and fiscal period from GLDIST records that get posted. If entries in the GLDIST table are deleted or changed, it will affect the totals saved in the GLBALS table. The GL Tools screen can help rebuild GL Balances from the current GLDIST entries, but making changes directly in the GLDIST or GLBALS table can have a ripple effect of issues and corrections. Be very careful about performing data updates in either of these tables.