“Configured Products,” for details on setting up configured products.
In a multi-database environment, users create and maintain sales orders in a central sales database. The system then creates sales order lines in the appropriate remote database after order confirmation. For configured products, structures defining standard configurations and options must be located in the central database in order to be available for configuration processing during order entry. Lower-level structures required to build or cost the product are kept in the manufacturing databases.
A configured product can have a complex, multilevel bill of material that includes three different types of structures:
DR Intercompany CR PO Receipts Std Cost Std Cost Central Central Central Central DR Purchase Price Variance
CR Intercompany PO - Std PO - Std Local Local Local Local DR Intercompany CR PO Receipts PO - Std PO - Std Central Central Central Central Voucher DR PO Receipts CR Accounts Payable PO Cost PO Cost Central Central Central Central DR Purchase Price or AP Variance
CR Accounts Payable Inv - PO Inv - PO Central Central Central Central Check Print DR Accounts Payable CR Cash Inv Cost Inv Cost Central Central Central Central
CONSOLIDATED ORDER PROCESSING 93
• Configured end-item structure, which represents the top-level parent and is defined in Item Master Maintenance with Pur/Mfg code set to C. This item can also be a lower level of another configured structure. In this case, it is defined in Configured Structure Maintenance as Structure Type O (option).
• Base module structure, which defines the required components of a configured item. This consists of a single-level relationship between a configured item (level 0) and its level 1 non-option components. In Product Structure Maintenance, this structure is identified with a blank structure type.
• Manufacturing structure, which identifies the lower-level structure defining the content of configured structure components. In Product Structure Maintenance, it is identified with a blank structure type. Figure 5.9 summarizes the types of configured product data needed in each database.
Fig. 5.9
Distributed Configured Item Data
Where each type of structure resides is governed by some basic rules.
• Configured structures must reside in the central sales order database for use in configuring sales quotes and sales orders.
• Base module structures must reside in the central database for use in configuring sales order bills of material (one level only).
• For standard cost sites, base module structures must also reside in the remote database, for use in standard cost rollups at the remote site. The system calculates standard cost of configured products by rolling up the costs of these components.
Central Site Lower-level structures maintained in manufacturing DB only. A (Type C) A (Type C) C (Type O) C (Type O) B (Type Blank) B
(Type Blank) (Type Blank)D
D (Type Blank)
Upper level structures, to level below configured structure (parent) type, maintained in central DB. Configured Structures Base Model Structures Manufacturing Structures E (Type Blank) E (Type Blank) F (Type Blank) F (Type Blank) G (Type Blank) G (Type Blank) H (Type Blank) H (Type Blank) Manufacturing Site
• Manufacturing structures must reside in the remote manufacturing database for use in such functions as costing and work orders.
• The sales order database must maintain configuration data down to level one. Nonconfigured products on lower levels of the configured product structure can reside strictly in the remote manufacturing database.
• The system determines prices using pricing structures and policies in the central sales database. If pricing is based on mark-up from cost, the cost used for pricing must be appropriate for the sales order site. If the site resides in an inventory database, the cost comes from the item-site in that database.
Setup Options
There are two basic approaches for setting up multi-database configured sales orders: centralized and decentralized. Each provides a different degree of central control.
The centralized approach supports users who want to maintain very tight control over configured products from the central sales order database. Because the central and remote databases maintain all configured product data on all levels, such a model requires extensive replication to keep the databases synchronized.
Upper-level configuration data needed only by the sales site also exists at the manufacturing database, and lower-level details used only by the manufacturing site are replicated in the central database.
To set up a centralized approach:
• Enter both Configuration Structure Maintenance and Product Structure Maintenance data at the central database.
• Duplicate manufacturing and base module structure data at the remote databases that build each product. Or, alternatively, maintain all product structures in all databases.
The decentralized approach assumes that data is stored where it is used. For example, a manufacturing site does not need customer address records. The central sales order database does not need detailed manufacturing data on lower-level items. This approach minimizes duplication among central and remote databases, but requires some
CONSOLIDATED ORDER PROCESSING 95
duplication. For instance, the same data would have to reside in multiple databases in order to enable costing rollups.
To set up a decentralized approach:
• Enter Configured Structure Maintenance data at the central database.
• Enter Product Structure Maintenance data at the remote database that builds the product.
• Enter base module structures at the central database. This only applies to the non-option level 1 components of configured items.
C
HAPTER6
Shipping
This chapter explains how to ship goods in MFG/PRO using the container/shipper method and global shipping features.
Introduction 98
Setting Up Shipping 98 Processing Shipments 118
Processing Issue Transactions 168
Creating Scanned Shipping Documents 175 Creating Custom Shippers 178
Introduction
MFG/PRO can handle a broad range of shipping requirements: from simple sales-order shipments and intrasite transfers to more complex international or global shipments.
This chapter focuses on setting up and using MFG/PRO shipping features for domestic and global sales-order shipments using containers, shippers, and master bills of lading. Issue transactions that are not based on sales orders, such as transfers and returns, are also covered. It concludes with information on how to use scanned information to create shipping documents and how to customize shippers.
ÏSee User Guide
Volume 7: Release Management and Chapter 4, “Sales Orders/Invoices,” on page 55.
Other aspects of shipping are included in the discussion of customer schedules and sales orders and invoices.