Melissa Labadia
Epicor, Sr. Business Process Consultant
Before you begin, review and answer all of the questions below to ensure a
thorough and correct setup of your new branch.
1. I s the branch you are creating for pricing purposes only? (Yes/No)
2. Is the new branch part of the existing company you already have running
on the Eclipse system or a separate company? Separate/Existing
If the branch is separate:
• Is the new branch a startup company or will data need to be converted
into Eclipse?
• Can your existing customers purchase material from the New Branch?
• Will you have the same vendors as your existing branches
• Is the warehouse empty or are you buying the inventory from previous
owners?
• Will your existing employees be able to sell material out of the new
branch?
• Can existing products be sold out of the new branch?
If the branch is separate:
• If you have existing products that can be sold, is there a branch that has
demand you think can be copied to the new branch for use with
suggested PO’s?
• Do you have special forms that will be required for your invoices, checks,
statements, ship tickets, etc.
If the branch is already existing:
• Is the branch close enough in proximity to an existing branch, where
current product demand would move to the new one?
• If the previous question is No, can the product demand of an existing
branch be used to copy into the new branch?
• Will material be tranferred from an existing branch to the new branch for
stock replenishment?
• Can your existing price matrix be used in the new branch?
• Will the List price on products be the same as existing branches?
• Will your existing emplyees be able to sell material out of the new
branch?
• Is it an empty warehouse or did you buy inventory from previous owners?
 Is the new branch being created because an existing branch is
moving to a new location?
 Do your employees know about the new branch?
 Do you have all the hardware and licenses required for the new
branch?
 Before the new branch is added, are you a single branch
establishment?
 Control – Branch specific control records will need to be
updated to appropriate settings for the new branch.
 Territory – The Territory File stores the branch information
and territories that exist within Eclipse
 Entity – Existing customer and vendor records may need to
be update with new branch. If you are creating a separate
company, and you have customers and vendors that will
exist in both, these records will need to be duplicated.
 Product – Your product file can be branch authenticated, which
means products you sell in your existing branch, cannot be sold in
the new branch.
 PROD.PRICE – If your pricing can be leveraged, then you will not
need to worry about geographical price sheets, otherwise that needs
to be added to the list.
 Matrix – If your existing matrix setup cannot be leveraged, then a
matrix cell that is territory specific will need to be put in place.
 BUY.LINE – New buy lines will need to be created with targets if you
are not using existing.
 PRICE.LINE – New price lines that will only exist in the
new branch will need to be crated and marked branch
specific.
 INITIALS – User Profiles will need to be updated.
 PROCURE.GROUP – If material can be transferred from an
existing branch to new branch (separate company will not
do this), the procurement groups will need to be updated.
This file will need to be updated regardless of methods to
allow for suggested purchase orders to run.
 SYSTEM.QUEUE – Phantom process may need to be created
and/or updated.
 TTY.DEFINE – New Terminal configurations will need to be
created for terminals operating in the new branch location.
 PRINTER.LOCS – New printer locations must be defined in the
new branch and then assigned to users and terminal setup
We recommend completing these steps in the order listed.
 Note: Depending on the type of branch you are setting up not all
steps will apply to you.
In some cases, multiple options are available in a step. The
answers to the questionnaire above will help you choose the
appropriate option.
1.
Create the branch entity in Customer File Maintenance
2.
Create the branch in Branch File Maintenance
3.
Authorize yourself for new branch and log in again.
4.
Create / update territories and delete cache records.
5.
Authorization for customers.
6.
Authorization for Vendors.
Authorization for Product/Price Lines.
8.
Geographical Price sheets / Discount Classes.
Geographical Sell Groups (optional)
Branch-specific / territory-specific product
settings.
9. Update procurement groups
10. Update buy lines with targets / buyers
11. Update branch-specific control parameters
12. Add demand to new branch (optional)
13. Create transfer matrix cells.
14. Copy or create matrix cells for new branch
(optional).
15. Delete and recreate phantom processes.
16. Create any new phantom processes required.
7.
17. Create printer locations for new branch.
18. Update terminal maintenance for terminals
in new branch
19. Update fax setting for new branch.
20. Create any new G/L accounts.
21. Verify ship via records assigned to new
branch
22. Authorize other users to access new
branch / territories
23. Verify product families in new branch
Consider the following if this branch is existing or separate:
•Existing – If the branch is new to an existing company only one entity
record is required.
•Separate – If the branch is for a separate company, you will want to create
two entity records. One for the branch where the inventory moves through
and the other branch to define your remit to address.
 You are able to mass load branches to Customers and
Vendors
 Need to setup dictionary item
 Mass load to Add branch will append the new branch
to the end of the current branch list with the ACTIVE
flag set to “Y”
When the branch record is updated, the system prompts
you to load all valid ship-via records to the new branch
record. You can choose to answer no to this prompt, if your
current ship-via records need to be reviewed before they
are added to the new branch.
Update users authorized branches with new branch.
A mass load can be created to add the new branch
to your users.
 System has many control maintenance record settings;
you must review and update the Control records.
 Easiest way to find all Control File Records that need
to be reviewed is create a Report Writer Report.
 Report is created over the CMP file.
New Branch field will be blank. You can use
“SET ALL” option if all branches use the same
value.
 If material will be transferred between branches, Sell
Matrix need to be in place.
 Complete guide on setting up a New Branch is
located on the Customer Support Website.
 Documentation > Solar > New Branch Setup