Operations considerations

Operations considerations include order entry, purchasing, inventory control, and transfer order questions.

Order Entry:

Order entry questions +/- Multi-site +/- Single site with multi-warehouse
Is centralized order entry required across sites? + Centralized and decentralized order entry strategies are supported. = Supported via a single site.
What order and invoice number logic is used across sites? = CO prefixes must be used in each site to properly identify and track orders. Invoice sequences will be maintained at the site level. = CO prefixes are available within a site.
Are shared customers required? = Multi-site, with a master site setup, supports centralized adding and maintaining of most customer data. Deletion must be done at sites. = One customer master is utilized within the site.
Are site-level customer credit limits required? + If centralized order entry is set up between sites, and the same customer number is defined in multiple sites, then that customer’s credit limits, posted balance, and on order balances display the total for that customer from all the shared sites.

Local (unshared) customers allow local credit limits and balances.

= Supported via a single site.
Is invoicing required by order with central order entry? + Invoicing is performed by the ship site. If one line on an order is shipped from one site and another line is shipped from another site, two invoices will be generated. However, you can use the Invoice Builder to create and post invoices and credit memos for the current site and other target sites for customer order shipments and returns. = Supported via a single site.
How are performance measurements reported? = Order entry information, such as ship date vs. due date, is maintained at the site level. = Order entry information, such as ship date vs. due date, is maintained at the warehouse level.
Is global pricing maintenance required? - All pricing logic is maintained at the site level. If central order entry is used, the price that defaults to the order line comes from either the site that is taking the order or from the ship site (depending on order entry parameters). The ship site cannot update the quantity or the price on an order that originated in another site.

No mass update utility exists across sites for maintenance.

+ Supported via a single site.
Are sales analysis and booking required across sites? + All sales analysis and booking information is maintained at the site level. However, on the Salesperson Home form you can see the information for various sites, or for all sites. = Supported via a single site.
Are global salespersons and commission logic used? = If centralized order entry is used, the central order site must contain all possible salespersons. Commission information cannot be input at the central order entry level. Commission distributions must be set up and maintained at the site level. = Supported via a single site.

Purchasing:

Purchasing questions +/- Multi-site +/- Single site with multi-warehouse
Is consolidated requirements planning required? - Multi-site has no ability to provide requirements planning across sites. All requirements are planned at the site level. + Supported via a single site.
Is centralized purchasing performed across sites? = Builder purchase orders can be entered at one site to create purchase orders for other sites. Maintenance of these POs is then done at the individual sites. = Supported via a single site.
Is centralized receiving performed across sites? - Multi-site has no ability to provide centralized receiving across sites. All receiving is performed at the site level. + Supported via a single site.
Are shared vendors required? = Multi-site, with a master site setup, supports centralized adding and maintaining of most vendor data. Deletion must be done at sites. = One vendor master is utilized within the site.

Inventory:

Inventory questions +/- Multi-site +/- Single site with multi-warehouse
Is standardized item number logic used across sites? = Multi-site, with a master site setup, supports centralized adding and maintaining of most item data. Deletion must be done at sites. = Supported via a single site.
How is materials planning performed? = Item availability across sites is only available using Item Availability (with drilldown). No reports combine on-hand balances across sites. = Supported via a single site.
Is item cost different at different warehouses? = You can set item costing at either the warehouse or site level. = You can set item costing at either the warehouse or site level.

Transfers:

Transfer questions +/- Multi-site +/- Single site with multi-warehouse
What transfer controls, visibility, and documents are required? = The proper transfer process will be related to the controls, visibility, and documents that the customer requires. = Same logic.
Is profit recognized from inter-site material transfers? + Multi-site allows you to recognize and eliminate inter-site transfer profits. The transfer pricing logic is linked to the price matrix and transfer pricing. The elimination of inter-company profits is linked to the Ledger Consolidation activity. - Warehouse transfers are supported. Inter-company sales are not supported.