Commonly Used Eclipse Files and Descriptions

File name

Contains...

ENTITY

Name and address data for customer bill-tos, customer ship-tos, vendor pay-tos, vendor ship-froms, and branches.

PRODUCT

Product descriptions, groupings for the products, and pricing information. PROD.PRICE and PROD.DYNAM support this file.

AR

Summary information (header and totals, along with associated dates) for closed ledger transactions, such as sales invoices, received purchase orders, cash receipts postings, accounts payable invoices, and completed branch transfers. The ID to the file is the Ledger#.Invoice#. Example: S1012302.002. After transactions process, the summary information moves from the ORDER.QUEUE file to the AR file. Transaction details move to the PSUB file.

PSUB

Line item detail for closed ledger transactions, such as sales invoices, received purchase orders, transfers, and inventory adjustments. Each product on a transaction creates 1 record in this file. For example, a sales invoice with 5 products creates 5 PSUB records. When a transaction is processed, the detailed product information pertaining to the sales order moves from the ORDERS.QUEUE file to the PSUB file.

ENTITY.BR

This file contains branch specific data assigned to a customer/vendor.  These overrides take place in Customer /Vendor file maintenance under the Additional Information, Branch Overrides option.

BUY.LINE

Purchasing-related information, such as Buyer, Target Factor, Target Value, Order Cycle Days, etc. The ID to the file is the Buy Line ID. Information from the Buy Line Maintenance Screen is stored in this file.  Products are linked to this file when a buy line is assigned.

BUY.LINE.BR

This file contains the branch specific / Territory specific data for the Buy line.

CONTACT

Information entered on the Contact Maintenance screen.

COUNT.QUEUE

List of products to be counted for each branch. Products that have a negative on-hand, have been over-committed, or for which there was a manual backorder on a shipped ticket go to this queue.

EDICT

All Eclipse dictionary items for all files. The ID for records in the file is the Filename~DictionaryName. Example: PRODUCT~DESC.

ENTITY.LOG

Activity log information the System.  This data is seen when accessing F2-S-V.

ENTITY.PN.IDS

Customer / Vendor-Specific Part numbers. This file is populated only when customers or vendors are assigned a part number or if the Customer Product Demand Index from the AR/Utilities is run.

FAX.LOG

Activity information about faxes that are sent out using the Eclipse system.

GENLED

G/L account and G/L report template records. This file does not contain G/L balances. The GENLED file has three indexes that can be used in selecting one type of record or the other: &INDEX& for G/L accounts only, &INDEX&.GRP for template groups only, and &INDEX&.ALL for all records.

GL.BUDGET

Information entered on the GL Budget Maintenance screen.

INITIALS

Information entered on the User Maintenance screen, such as user name, title, menu, message tune, keywords, etc.

LEDGER

All sales orders, cash receipts records, purchase orders, journal entries, accounts payable invoices, and branch transfers. This file contains both summary and detail line item information. The ID to the file is the sales order#, purchase order#, etc. This file is rarely used in Report Writer. Detailed information pertaining to shipped tickets should be retrieved from the PSUB file. The following ledger-index files are used in Report Writer: AR, ORDER.QUEUE, PRINT.QUEUE and PSUB.

LEDGER.LOG

All change logs associated with transactions.

MATRIX

All price matrix cells for the Sell Matrix and the Buy Matrix. It includes matrix cells for customer classes, as well as customer-specific prices. The ID to the file is BRANCH~Customer# or Class~Group or Product#~Effective Date.

Examples: ~C2~GWIRE~10354   or   1~4993~1684~10354

Use this file to create a report that will provide a list of matrix cells that are about to expire.

MATRIX.DATES

This file works in conjunction with the MATRIX file and stores information such as expire dates, original and remaining quantities associated with the matrix record found in the matrix file.

MAINT.LOG

Audit change log information for any file for which maintenance logging has been turned on.

MENUS

All menus created in Eclipse.

MESSAGES

All messages sent and received, until the individual users delete them.

MISC.DATA

Items from various sources, including commission plans, product families and manifest information, quote maintenance, user’s last run report, and customer-created product groups from Web Commerce. The ID is the Type Identifier~ID. Example: COMM~INSSLS.

ORDER.QUEUE

Open Ledger transactions, such as open (not printed) sales orders, purchase orders, and transfers. The ID to the file is the Ledger.ShipDate.GID. Example: S1012300.10865.1 (GID =Generation ID) Once the order is processed the information moves to the AR file and the detailed information moves to the PSUB file.

OVERRIDES.LOG

Manual overrides to sell and cost values on purchase orders, sales orders, or transfers, if the Log Sell Price, Purchase Price and Cost Overrides Control Maintenance record is set to yes. This file is used for reporting purposes only.

PRICE.GRP

Information entered on the Buy / Sell Group Maintenance screen.

PRICE.LINE

Data related to setting up price lines in Price Line Maintenance, including default units of measure, Basis Field names, and Basis assignments. Products are linked to this file when a price line is assigned to the product.

PRICE.LINE.BR

Information that is branch specific/territory specific for the PRICE.LINE file are posted to this .br file.

PRINT.QUEUE

Ledger transactions that are queued to print. This file is updated from the Print Status prompt on the Status screen of SOE, POE, and TOE. A/P invoices (checks) are also in this file. The ID to this file is the Ledger#.GID. Example: S10112300.1 (GID = Generation ID).

PRINT.REVIEW

Transactions in the Open Order Status Review Queue.

PROCURE.GROUP

Information entered on the Procure Group Maintenance screen Products are linked to this file by the procure group entered on the product record or its buy line record.

PROCURE.GROUP.BR

Branch specific information for Procurement Groups is stored in this .BR file.  Procurement group maintenance is found on the Maintenance menu in the purchasing menu.

PROD.BR

Branch specific / Territory specific information for the product file is stored in this .BR file.

PROD.CALC.BR

Product branch specific/territory specific calculated data such as Average Cost, Product Demand etc are stored in this .BR file.

PROD.DYNAM

Product on-hands, bin locations, average and last cost, and open orders for the product in each branch. Links to the Product file.

PROD.LIFO

All Product Lifo information, which is updated each time the Update routine for the Lifo is run.  This file exists only if your company does “Lifo”.

PROD.PRICE

Prices and costs, such as List Price and Replacement cost, for each product. The pricing information found on the Product Price Sheet Maintenance screen is stored in this file. The product’s internal ID number is part of the key to this file.

PRODUCT.NOTES

Product notes entered using the Notes hot key in Product Maintenance. This file has the same key as the product file therefore they are linked together.

PRODUCT.RENTAL

Information entered on the Rental Product Maintenance screen.

QUAL.LOG

Information generated through the Unquality Event Tracking entries.

RECURRING.JE

Setup information for recurring journal entries.

REMINDER

Reminder notes created in Customer or Vendor Maintenance.  These notes can also be created from the System Files Menu.

REPORTS

List of reports generated within Eclipse and sent to the Hold file. The detailed information regarding the reports is stored in the &HOLD& file. The date and time stamp is included for the purging routine. 

SCHEDULES

Information entered in the Daily Scheduler.

SYSTEM.QUEUE

All scheduled phantom processes. This file is dynamic in that the key to each record changes each time the phantom processes an activity in the Phantom Status screen.

TAX.CODES

Information related to tax jurisdictions, such as tax rates and G/L posting information.

TERMS

Customer and vendor-related terms entered on the Terms Maintenance screen. It includes information on discount percents, discount days, due dates, service charge percents, and service charge due dates. Customer maintenance, vendor maintenance and sales transactions link to the Terms file.

TERRITORY

Information entered on the Territory Maintenance screen.

TRACKING.LOG

Call tracking information for all entities and users in Eclipse. The key to this file is the Tracking ID number generated each time a tracker is created.

UD.WARRANTY

Warranty information entered on a user-defined screen when creating returns from your customers. This is a user-defined file, which contains limited information. You can enhance this file, based on how you handle warranties.

WHSE.OP.QUEUE

In-process RF transactions, until they are closed out.

WORK.MISC

Data from different sources, including saved Report Writer layouts, saved Mass Load layouts, Print Price Sheets, Manifest Information, Product Ranking, E-mail Standard Forms, Order Entry Clipboard (Ctrl-F5), Detailed Daily Schedules, Physical Generations, Cycle Count Generations (RDC), and F10 Quick Access information.

ZIP

ZIP code information entered on the Zip Code Maintenance screen. Each Eclipse system contains all US 5-digit postal codes, including city and state information. This file also contains the tax jurisdiction codes.