Files Commonly Used in Reports

Description

Name and address for customer bill-to's, customer ship-to's, vendor pay-to's, vendor ship-from's, and branches.

Note: Branch-specific data for this file is contained in the ENTITY.BR file. Link to these branch-specific data elements via the ENTITY file itself.

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

Note: Branch-specific data for this file is contained in the PROD.BR file. Link to these branch-specific data elements via the PRODUCT file itself. Calculated information, such as average cost and forecast period, is stored in the PROD.LOG file.

Accrual Register. 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.

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.

After transactions process, the detailed product information pertaining to the sales order moves from the ORDER.QUEUE file to the PSUB file.

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

Transactions in the Open Order Status Review Queue.

Purchasing-related information entered in Buy Line Maintenance, such as buyer, target factor, target value, order cycle days, etc. The ID to the file is the Buy Line ID. Products link to this file when a buy line is assigned to the product.

Note: Branch-specific data for this file is contained in the BUY.LINE.BR file. Link to these branch-specific data elements via the BUY.LINE file itself.

Information entered in Contact Maintenance.

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 into this queue.

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

Customer/vendor-specific part numbers. This file is populated only when customers or vendors are assigned a part number.

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

G/L account and G/L report template records. This file does not contain G/L balances.

The GENLED file has three indexes, which you can use to select 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.

Information entered in G/L Budget Maintenance.

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

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. Use the PSUB file to retrieve detailed information pertaining to shipped tickets. Use the following ledger-index files in Report Writer: AR, ORDER.QUEUE, PRINT.QUEUE, and PSUB.

All change logs associated with transactions.

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 14993~1684~10354

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

Audit change log information for any file for which maintenance logging is enabled.

All menus created in Eclipse.

All messages sent and received, until the individual user deletes them.

Items from various sources, including commission plans, product families, 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.

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)

After the order is processed the summary information moves to the AR file and the detailed product information moves to the PSUB file.

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 Y. This file is used for reporting purposes only.

Information entered in Buy/Sell Group Maintenance.

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

Note: Branch-specific data for this file is contained in the PRICE.LINE.BR file. Link to these branch-specific data elements via the PRICE.LINE file itself.

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

Information entered in Procure Group Maintenance. Products link to this file using the procure group entered on the product record or its buy line record.

Note: Branch-specific data for this file is contained in the PROCURE.GROUP.BR file. Link to these branch-specific data elements via the PROCURE.GROUP file itself.

All product LIFO information, which updates each time the LIFO update routine runs.

Price and cost information found in Product Price Sheet Maintenance, such as list price and replacement cost, for each product. The product's internal ID is part of the key to this file.

Product notes entered in Product Maintenance. This file has the same key as the product file, so they link to one another.

Information generated by Unquality Event Tracking entries.

Setup information for recurring journal entries.

Reminder notes created from Customer Maintenance,  Vendor Maintenance, or the System Files menu.

List of reports generated within Eclipse and sent to the Hold file. Includes the date and time stamp for the purging routine.

The &HOLD& file stores the detailed information regarding the reports.

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

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

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

Information entered in Territory Maintenance.

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

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

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

Data from different sources, including saved report writer layouts, saved mass load layouts, print price sheets, manifest information, product ranking data, e-mail standard forms, order entry clipboard (Ctrl-F5), detailed daily schedules, physical generations, cycle count generations (RDC), and F10 Quick Access information.

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