Overview of the multisite concepts
To adopt the multisite functionality in a multicompany or single company environment previously without sites, these multisite concepts must have the Active status in the Concept Activation (tcemm4600m000) session:
- Item Type Product
- Standard Cost by Enterprise Unit
- Planning Cluster Mandatory
- Sites
- Job Shop by Site
- Configurations by Site
Item type Product
The supply of an item can differ for each site. The item can be purchased at one site and subcontracted or produced at another site. However, the item type is a static and global setting. Consequently, the item types Purchased and Manufactured must be merged into the item type Product.
Standard cost by enterprise unit
In a multisite environment, the calculation of an item's standard cost must be performed at a more detailed level than the company level. Therefore, the item costing data must be available by enterprise unit instead of by company. Additionally, data such as the costing warehouse, costing source, and intercompany trade settings are required in the item costing data.
Planning cluster mandatory
Item planning is performed for one or more sites if Enterprise Planning is implemented. Therefore, planning clusters must be linked to sites. This is to accomplish that planning is performed for the items related to the sites and the underlying entities.
Sites
Various logistics data, commercial data, planning data, and other master data must be available at a more detailed level than the company level. For this purpose, this data must be grouped by site or by office for each company within the multicompany structure.
Job shop by site
In a multisite environment, there can be differences in the bills of material (BOMs) and routings used to manufacture items at the various production sites. To accommodate such variations, BOMs, routings and other master data must be maintained at the site level.
Resources by site
In multisite environments, multiple types of resources must be available in Enterprise Planning to model the available capacity. Resources provide an insight into the available, used, and required capacities, expressed in machine hours, labor hours, or product volume.
Resources are derived from these operational entities in Manufacturing and Purchase Control:
Entity | Capacity |
---|---|
Work center | Labor hours |
Machine capacity group | Machine hours |
Work cell | Labor hours |
Work cell machine | Machine hours |
Operation subcontractor | Machine hours |
Product subcontractor | Product volume |
Supplying cluster | Product volume |
Supplier | Product volume |
The subcontractor entity has been introduced to model the resources and resource capacities for both product subcontracting and operation subcontracting.
Subcontractors relate to a buy-from business partner and include one or more subcontractor locations. At a production site you can assign the subcontractor locations to which the production of items or operations is outsourced. A production site is a site at which an item is produced. A subcontractor location is a location at which the subcontractor performs the subcontracted activities.
Configurations by Site
To support multisite production for the PCF configured products, new master data is in place to model the different production sites. Generic Job Shop bill of material and routing data is defined for a site, which replace the generic bill of material and the generic routing.
If multiple production sites are available, you can select the site where the configured product must be produced. You can also subcontract a configured product or a part of the product.