Introduction: Branch Maintenance (30-02-02)
Overview
This selection is used to modify the settings of existing branches and to set up new Non-Inventory Branches.
In the Tyler system, there are two types of branches.
- Inventory Location – a branch that has sales, inventory, or both. These branches can only be added by Tyler, since all the appropriate files must also be added to the system, as well as records in existing files.
- Non-Inventory location – a branch that does not have sales or inventory. Unlike Inventory branches, these locations do not require Tyler to be set up. You can set up as many Non-Inventory locations as needed.
Setting Up The Branch ID for the Warehouse
The following explains why the Warehouse Branch ID should be located alphabetically last in the file for a specific region.
The Sales Transactions Update (02-05) selection updates the transactions by date in alphabetical order by Branch ID. If the orders in Order Processing are shipped from the warehouse rather than the sold at branch, and the warehouse is not the last branch in alphabetical order in the region, the temporary Open Accounts Receivable account on the shipped order may be updated to the A/R Open error account.
For example, a DD transaction is entered and the order is shipped the same day. The DD transaction creates a temporary A/R Open account for the customer and the DZ transaction posts the sale and/or charge to the temporary account. Since the transactions are updated in Branch order, one of the following will happen:
- If the DD transaction’s Branch is “TAMP” and the Warehouse is “WARE”, the update takes place correctly. The DD transaction sets up the A/R Open temporary account and the DZ posts to that temporary account.
- If the DD transaction’s branch is “TAMP” and the warehouse is “BRAD”, the update uses the A/R Error Record. The DZ posts to the A/R Open Error Record because the DD has not been updated and has not created the temporary account. The DD is then updated which creates the account, but the sale and/or charge has already been posted to the Error Record.
From this example, you can see that the Warehouse Branch ID should be located alphabetically last in the file for a specific region. If it is not, all branches should be updated before the update for the Warehouse is run.