Use Tool #332 Database Search Assistant. This tool lets you enter part or all of a table (file) name, a column (field) name, or even a portion of a table or column description to help locate where data is stored in your member files.

The NSF Statistics Dashboard (Tool #557) will track this information for you automatically. It is separated into the NSF category and the Courtesy Pay Category. Credit unions are using this dashboard to help predict averages of NSF/Courtesy Pay fee income and also to track how many members may be using the service. You can click on any of the origins (listed in blue text) and you can drill further to members who had more than X transactions in a specific month. There are a lot of graphical oppor  More...

No. The way that normal CU*BASE features work is to use the CU*BASE Workstation Configuration settings to determine a default printer for certain functions, or you can choose a printer directly when printing most CU*BASE reports. But since IBM Query is not a CU*BASE program but rather a generic program offered by IBM, it does not have any way of looking at CU*BASE configs for the info it would need to direct the print job. Therefore a Query definition will go to your list of spooled files and  More...

This occurs when the release includes changes to the files that your Query uses. For example, if we add a new field to the MASTER file, any Query you have that uses that file will display an error message. Fortunately, it is very easy to refresh your Query so that you can use it again. All you need to do is access the Query and save it. That's all. You don't have to make changes to it, it's just important that you save it so it can refresh itself to match the new file layout.   More...

To analyze Member Trackers, simply run a report in Tool #664 Print Member Trackers . When configuring Tracker Type ( Tool #277 Configure Tracker Types ) and Memo Type ( Tool #260 Configure Memo Type Codes for Trackers ), you created specific codes that track these types of records. Tool #664 allows you to generate a report based on multiple search criteria, including Tracker Type and Memo Type, as well as date range, and Employee ID. Additional options are available to analyze Sales Trackers via  More...

Beginning with the 17.10 CUBASE Release (October 22, 2017 for online clients), CU*Answers implemented the CUFMAINT table, which includes data from the CUFMNT table, as well as additional data not included in CUFMNT. CU*Answers recommends using the CUFMAINT table for all report building and query activity. If you currently have any Queries using the CUFMNT table, they will still work, as CUFMNT is now a View over the C UFMAINT table but without all of the additional information, so it will s  More...

Generally, no. We do purge files you create via a Query (see the link below), but not the Query definitions themselves.

Launch Tool #100 CU*BASE Report Builder (Query) Make sure the Location reads QUERYxx (where xx is your CUID) Click the Lookup button next to the Name input field Use the tab key to jump down to the list at the bottom of the screen, and use tab or page down to scroll to the first query you wish to print Tap the letter “P” or choose Print definition from the drop-down menu Repeat steps 4 5 for a small batch of Queries (to avoid an error message, choose no more than 8-10 at a time)   More...

There is a file HBMASTER that you can query to find the membership applications you have received via online and mobile web banking. To work these applications, use Tool #13 Work Online Banking Apps/Requests .

For things like expanded balance and transaction $ amounts, Query will automatically adapt to larger amounts, and you generally won’t need to do anything. (The only exception is if you send the output to a vendor, they’ll need to be made aware of the larger amounts. Or perhaps if your report is completely full side to side and you need to remove a column in order for everything to still fit across a printed page.) As far as dates, if a date was formerly 3 separate fields for year  More...

The numbers will be different because two different files are used. One file is LAHSTAT, and the other file is AUDICC. AUDICC will give the true total of internet logons that the member has performed for the month. The other file LAHSTAT, will add all internet logons and will stop when our operations team begins our end of month processing, but members can still sign on to online banking during end-of-month processing and that is tracked in the AUDICC file.

Since the list of valid values changes periodically, we suggest you use the Database Search Assistant to look up the most current set of values in this field: Launch Tool #332 Database Search Assistant Select Table and enter AUDICC in the search box and press Enter to search Click the View columns lookup button in front of the AUDICC table in the list Click the More information button in front of the CCLOGT column/field name

Whenever you add files to your Query definition or remove files from it, you also need to refresh the automation configuration, which is basically just a list of the files needed by the Query and must match the Query definition. See the link below for step-by-step instructions.

A quick way to clean house is to click the Lookup button next to “Name” on the initial Query screen (Tool #100) to display all of the definitions in your QUERYxx library. Use the drop down lists to choose Delete (the keyboard shortcut is “D”) on any that you no longer need. To avoid errors, we recommend you delete only small batches at a time.

Use the link below to read about this in CU*BASE GOLD online help.

With the File Expansion Project (FEP) in 2014 we introduced new formats for date fields in the account and transaction database tables. Referred to as the ISO date format, dates with this format can easily be used in search and selection criteria, as well as in calculations (such as the number of days between dates, etc.). In the past, a date field that didn't have any data entered into it was simply blank. But with the ISO date format, a null date, meaning no date has been recorded,  More...

Use Tool #654 “Print List of Custom Rpts/Inqs”

The system will advance the next payment due date depending on the payments made during the “payment period” window, which runs from due date to due date (which is not always calendar month). Once the next payment period begins, any payments made will count towards the payment amount due until it is fully satisfied, at which point the due date will advance to the next payment period. Payments may still be made during the current payment period; however, any overpayments will be c  More...

If the member is delinquent (even by one day), the member is then in the next payment cycle (due date to due date). Therefore, if the member pays the regular payment amount, the loan will advance the date by one period, or by two periods if the amount of the delinquent payment is double the regular payment that is scheduled . For example, John Doe has a Overdraft Protection LOC account that is configured as single payment per period. At the end of September John is due for October 4. John does   More...

If you are looking in Tool #100 Report Builder (Query) then you are not actually seeing a table/file. What you see is actually a list of query definitions - the saved parameters used to create the table. A query definition and a table can sometimes be confused for each other if they have identical names. As an example, you might have a CDDIVS query definition which you run to create or refresh the CDDIVS table. The practice of giving a table the same name as its query definition is a common one  More...

Queries used in Query Scheduler cannot contain end-of-month files. If you are using output option Database file (3) be sure to set the Data in file option to Replace File (2) or for Queries that build on each other, use Add to Member (5). Make sure the Authority of your Queries is set to *ALL. Be sure to always run the Query first to generate a database file before using it in the Query Scheduler. If you update the Query that the scheduled Query is based on, return to the scheduled Query and u  More...

There is not currently a way to export a canned Query directly into an Excel file. If you want to export data from a canned Query, you'll need to create a similar custom Query via Tool #100 CU*BASE Report Builder (Query) . Once you have the Query built, then you can export the resulting database file. (See the related link below for instructions on downloading files.) Keep in mind that download authority is still required in order to export any data from the QUERYxx library.

Yes! This is definitely not a save it and forget it process. Set a monthly reminder to check that your Queries are running as expected. Once the automated Queries are run, the Automated Run of Scheduled Queries – Audit Report (PRUNAQ) will appear in your DAILYxx OUTQ. Be sure to review this report. Also remember that after CU*BASE software releases you may need to refresh your Query to adapt to changes made to the underlying database tables. Use the link below to learn how.

With the 16.10 release a new cross-reference system was implemented that automatically funnels all incoming company IDs from the Social Security Administration and treat them as if they came from one, consistent company ID we’re referring to as the “Primary ID.” In cases where the Depositor ID is the same, for example a husband and wife, these ACH transactions will be handled by the same master ACH distribution record under the Depositor ID since duplicate Depositor IDs are no  More...

Using CU*BASE to Comply with New Rules for Tracking Beneficial Ownership FinCEN has issued new rules under the Bank Secrecy Act that require financial institutions to identify and verify the identity of the beneficial owners of all legal entity members (corporations, etc.). Under the final rule, credit unions are required to have written procedures to identify and verify beneficial owners of legal entity members who open new accounts on or after May 11, 2018. In addition to identifying and coll  More...