Overcome some limitations of Millennium/Sierra
Ruby
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.gitignore
LICENSE
README.md
payment_info_processor.rb

README.md

Quick download links:

Script not working for you? Check here

Millennium/Sierra Payment Information Processor

A helper for working with payment data exported from III Millennium or Sierra. The Windows .exe version of the script can be run by any Windows user, without the need to install Ruby and other dependencies.

Takes payment data exported from a Review File of order records. Outputs a tab-delimited .txt file that can be opened with Excel. There are two output types to choose from:

  • Individual payments - outputs one line per payment made. Data can be further processed in Excel using PivotTables or other means. Each line contains order record number, fiscal year of payment, (other fields exported), payment data fields.
  • Payments summarized by fiscal year - outputs one line per order record. Each line contains order record number, (other fields exported), and one column for each fiscal year input by script user. Each of these columns contains total payment amount for that fiscal year.

Set up required before first use

ALL versions (Windows .exe and Ruby script (.rb))

Prepare your directory structure

Choose or create a directory/folder in which to place the script (.rb or .exe). This directory can be called whatever you want, but here I'll call it the "ruby_scripts" directory.

In the ruby_scripts directory, create a new directory called "data".

In the ruby_scripts directory, create a new directory called "output".

The structure should look like this:

- ruby_scripts
-- data
-- output

Put the payment_info_processor .rb or .exe file(s) in the ruby_scripts directory.

Note for more advanced users: You can run the script from anywhere; there doesn't have to be a ruby_scripts directory. BUT, there must be a data directory and an output directory in whatever directory you are running the script from. It's clunky and inflexible, but it is the only way I know to make the .exe version work for my colleagues who don't know how to use the command line.

Prepare your configuration file (First use only)

The configuration file will tell the script when your new fiscal year begins. I will use my institution as an example. Our fiscal year runs from July 1 to June 30.

In the ruby_scripts/data directory, create a new text file named payment_processor_config.txt

payment_processor_config.txt will consist of two lines. Except for the number at the end of the line, your text should match what is below exactly. Copy/paste it in to be sure.

fy_begin_month = 7
fy_begin_day = 1

Change the number at the end of each line to reflect when your new fiscal year begins. Save and close payment_processor_config.txt.

Windows .exe version

Download Windows .exe file:

If a window pops up and asks you whether to save or open the file, select save.

Save the file into your ruby_scripts directory.

Ruby script (.rb) version

gem install highline

Regular use

Prepare your input file

Export from a Review File of order records in Millennium.

Required fields

  • ORDER - RECORD NUMBER: required, must be first column
  • ORDER - PAID: required, must be the last column

You can export whatever fields you want in between RECORD NUMBER and PAID, but only include fields that will be output in a single column.

Export settings

FIELD DELIMITER:

  • Control character (1-127) = 42

TEXT QUALIFIER:

  • Text qualifier = None

Exported file name and location

  • File name must be payment_data.txt
  • Save the file in the "data" folder inside your "ruby_scripts" folder

Run the script

.exe version

Just double-click it!

rb version

At command line, from inside ruby_scripts directory:

  • ruby payment_info_processor.rb

Output

The output files will be put in the "output" directory inside your "ruby_scripts" directory

Open the .txt files with Excel. Choose "65001 : Unicode (UTF-8)" as file origin (encoding) to properly display diacritics.

Frequent issues that prevent script from running properly

If the script is failing to work for you, check the following:

If none of those are the culprit, please go here and open a new issue. Please attach the following:

  • your payment_data.txt input file
  • a screenshot of your Create Lists export settings before you start the export

Please summarize the script options you are using---individual payments vs. summary by fiscal year. If the latter, please say which fiscal years you input.