TÉCNICAS E INSTRUMENTOS DE RECOLECCIÓN DE DATOS

MFG/PRO’s consolidated order processing supports management of sales and purchase orders in a multisite, multi-database environment.

Introduction 78

Using Multiple Databases 82 Creating Consolidated Orders 84 Financial Transactions 90

Introduction

In consolidated order processing, a central database handles all sales orders, then informs its distribution and/or manufacturing sites what to ship. These sites are each located in their own local databases.

Purchasing can either be centralized or distributed among sites.

Companies using consolidated order processing benefit in their ability to make larger orders and reduce the overhead involved in multiple order processing departments. Fig. 5.1 One Form of Consolidation: Centralized Order Processing

ÏSee User Guide

Volume 5: Supply Chain Manage- ment for details

on DRP.

In MFG/PRO, consolidated order processing refers to activities supported by central sales orders and distributed purchase orders. Distribution Requirements Planning (DRP) also supports multisite, multi-database operations.

ÏSee User Guide

Volume 11: Manager Functions for details on multiple databases.

Three multisite demonstration databases—newyork, chicago, and seattle—are included with MFG/PRO. Some examples in this chapter correspond to these databases.

In the demonstration database scenario, New York is the central sales office. New York sells binders, which are manufactured in Chicago. New York ships from both New York and Chicago, and replenishes its

inventory using DRP. Chicago obtains most of its raw materials from Seattle, and also replenishes its inventory using DRP. New York is the distributed purchase order site for Seattle. Orders are created in New York, material is shipped to Seattle, then reshipped to Chicago.

Inventory Database Inventory Database Inventory Database Central Sales Orders Central Purchase Orders Inventory Database

CONSOLIDATED ORDER PROCESSING 79

Example New York receives an order for 250 binders and 250 covers. New York has only 125 binders in stock, and only Seattle has covers. A sales clerk in New York creates a single sales order with three line items:

• One directing 250 covers to be shipped from Seattle

• One directing 125 binders to be shipped from Chicago

• One directing 125 binders to be shipped from New York

After the sales order is created, the events shown in Figure 5.2 occur.

Fig. 5.2

Sales Order Supplied by Three Separate Sites

For sales orders, MFG/PRO supports only the centralized model shown in Figure 5.2. For purchase orders, it is more flexible.

Example Binders made of glue, cardboard, and metal are manufactured in Chicago. Glue is available locally, but cardboard and metal must be ordered in bulk, with prices varying geographically. Binder materials are ordered as shown in Figure 5.3. All requisitions are created in Chicago.

New York Chicago Customer Seattle 1 2 4 3 5 6

1. Sales order comes to New York. 2. 250 covers shipped from Seattle. 3. 125 binders shipped from New York.

4. 125 binders shipped from Chicago. 5. Invoice comes from New York. 6. Payment recorded at New York.

Fig. 5.3

Distributed Purchasing

Continuing this example, computers on a network connect the three sites. Database functions are assigned according to each site’s real-world functions. Since New York handles all sales orders and purchasing, MFG/PRO’s sales order and purchasing functions are only active in the New York database.

Fig. 5.4

Database Configuration for Fully Centralized Orders

MFG/PRO MRP in Chicago receives and processes sales order demand from New York just as if it had come from Chicago. New York’s MRP receives and processes requirements from Chicago or Seattle just as it would requirements originating in New York.

1. Requisition for one roll of cardboard created in Chicago with PO site New York. 2. PO created in New York, sent to supplier. 3. Cardboard shipped to Chicago.

New York Chicago Supplier 1 5 3 6 2 4

4. On receipt, line item closed in New York.

5. Invoice received in New York. 6. Payment made to supplier.

= Not installed

New York DB (Orders & Inventory)

Sales Orders Manufacturing (MRP) Purchase Orders Sales Orders Manufacturing (MRP) Purchase Orders Chicago DB (Inventory) Sales Orders Manufacturing (MRP) Purchase Orders Seattle DB (Inventory)

CONSOLIDATED ORDER PROCESSING 81

It is important to note, however, that consolidated order processing only requires that certain database operations be centralized, not necessarily site operations. In the example above, part of the sales force could be in Chicago, where they would process orders through the New York database using remote connections.

The choice could be made to distribute purchasing among sites, in which case a configuration like the one in Figure 5.5 would be appropriate.

Fig. 5.5

A Distributed Purchase Orders Configuration

Example Chicago requires metal for binders and sends a requisition to New York, in order to take advantage of centralized purchasing power. New York issues the purchase order for the metal. The metal is shipped to Chicago, with billing and payment handled in New York. Chicago also requires glue for binders, which they order locally, using a purchase order generated in Chicago.

More complex scenarios can also be created. For example, metal could be ordered centrally from New York, while cardboard is ordered centrally from Seattle. To MFG/PRO, actual physical locations of people and computers are unimportant, as long as data transaction paths are clearly mapped.

= Not installed

New York DB (Orders & Inventory)

Sales Orders Manufacturing (MRP) Purchase Orders Sales Orders Manufacturing (MRP) Purchase Orders Chicago DB (Inventory) Sales Orders Manufacturing (MRP) Purchase Orders Seattle DB (Inventory)

Fig. 5.6

Distributed Purchase Orders by Site

Example The Seattle and New York databases each have two inventory sites where requisitions are issued and purchased items received. Chicago has one inventory site. Central purchasing for most items is handled in Site 4 (New York). However, the system is set up so that Site 3 can order cardboard from Site 1 in order to take advantage of a better price. Similarly, Site 5 can order from itself when appropriate, or order from both itself and Site 4.