Background: Branch Maintenance
Use the Branch Maintenance (TBM) program to add or change and copy branches. See Road Map for work flow.
Your enterprise can consist of one or more branches. Each branch can have its own inventory and do its own pricing and purchasing.
Most system options apply to the entire enterprise, but some options can be set for each manufacturing branch or login branch. You can assign order numbers (sales, purchase, manufacturing, receiver, invoice, transfer, etc.) sequentially throughout the enterprise or by branch. Likewise, you can assign batch numbers for programs that use batches enterprise-wide (globally) or by branch (locally).
You can use branch codes as posting criteria when you set up posting accounts in the Posting Criteria Maintenance (XPC) program.
This topic contains these subtopics:
|
Login Branch
Each user is assigned a Default branch in the User Maintenance (UIM) program. The user accesses this branch at logon and can only process transactions or make setup changes for this branch.
Manufacturing Branch
Manufacturing branches are facilities that make or assemble inventory items. You can have multiple manufacturing branches within your enterprise. Manufacturing branches must be peers of one another. Planning is done by manufacturing branch, and requires supply and demand groups. See Background: Branch Groups Maintenance for more information.
MES Interface
If your company has a Manufacturing Execution System Interface (MES) you can designate which branches are using this system to automate inventory adjustments.
Other Branch Types
A Pricing branch has a price hierarchy and price records set up so that it determines prices for items and customers. Each branch can set its own pricing or one branch can set prices for all branches. For a branch that is a warehouse, the pricing branch may be the nearest branch that processes sales orders. Each branch must have a pricing branch.
A Purchase branch is responsible for procuring materials, supplies, and services. Purchasing programs use this branch as the default, but a user can override it by entering the branch code of another branch in his inventory group. Each branch can do its own purchasing or one branch can purchase for all branches. Each branch must have a purchase branch.
A PO drop ship branch is a branch that you create but may not physically exist. The purpose of this branch is to serve as a holding area for drop shipments so that the system can track their movement. When you enter the vendor's invoice, the system automatically receives inventory into the drop ship branch and immediately ships it out again. This allows you to track which items, and specifically which serial numbers, were shipped to a customer.
Each branch must have a PO DS branch. However, a branch can be its own PO DS branch.
A Transfer drop ship branch is a branch that you create but may not physically exist. The purpose of this branch is to serve as a holding area for direct shipments so that the system can track their movement. Each branch must have a transfer drop ship branch. However, a branch can be its own transfer drop ship branch.
Branch Groups
A branch group can consist of one or more branches. Typically you group branches so that they can share inventory. Groups are also used for planning and reporting purposes. A branch can be included in more than one group. See Background: Branch Groups Maintenance for more information.
Structuring Branches in your Enterprise
Each company will structure its branches based on its organization, the location of its branches, and how it does business. These are some common structures that you can modify to match your needs:
Single
Manufacturing Branch
Multiple Manufacturing Branches - Decentralized
Multiple Manufacturing Branches with Centralized Pricing