Warehouses (tcemm1112m000)

Use this session to view and maintain the warehouse's enterprise modeling data.

You can:

  • Assign the warehouse to a planning cluster that is used in Enterprise Planning.
  • Change the enterprise unit to which you assigned the warehouse in the Warehouses (tcmcs0103s000) session if this is required.

If the multisite concepts are activated, planning clusters are mandatory, and the planning cluster of the warehouse is retrieved from the site of the warehouse.

Before you can use this session, you must enter the warehouse's logistic data in the Warehouses (tcmcs0503m000) session.

 

Operational Company

The operational company to which the warehouse belongs.

Warehouse
Site

A business location of an enterprise that can maintain its own logistical data. It includes a collection of warehouses, departments and assembly lines at the same location. Sites are used to model the supply chain in a multisite environment.

These restrictions apply to sites:

  • A site cannot cross countries. The warehouses and departments of the site must be in the same country as the site.
  • A site is linked to one planning cluster. Consequently, all warehouses and work centers of a site must belong to the same planning cluster.
  • A site is linked to one logistic company.

You can link a site to an enterprise unit or an enterprise unit to a site.

If an enterprise unit is linked to a site, the entities of the site belong to the enterprise unit. Conversely, if a site is linked to an enterprise unit, the entities of the enterprise unit belong to the site.

Related topics

Include in Enterprise Planning

If this check box is selected, the transactions recorded for this warehouse are taken into account in the Generate Master Planning (cprmp1202m000) session and the Generate Order Planning (cprrp1210m000) session in Enterprise Planning. If this check box is cleared, any inventory on hand and planned warehouse transactions recorded for this warehouse will be ignored in the planning process. The inventory in this warehouse is also ignored when the ATP is checked upon entry of sales orders and quotations. You can use such a warehouse to store rejected items and other inventory that is not intended to fulfill item demand.

Note

This check box is cleared and cannot be changed if the Warehouse Type field is one of the following:

  • Project
  • Service Customer Owned
  • Service Reject
  • Consignment (Owned)
  • Financial
Note
  • If you change this check box from cleared to selected, the transactions recorded for this warehouse are included in the next regenerative run. A net-change run will not take this warehouse's transactions into account, because the system does not set the net-change flag.
  • Before you can clear this check box, you must first delete any existing planned order recorded for this warehouse. No plan item must use this warehouse as its default warehouse in the Items - Planning (cprpd1100m000) session or the Items - Planning Defaults (cprpd1110m000) session.
  • If you select this check box for a warehouse of type Service, the effects are:

    • The order-planning process takes the service requirements into account.
    • Planned production orders can consume the inventory in the warehouse.

    The first effect is usually intended, the second effect can be an undesired side-effect. To avoid that planned production orders consume inventory in a service warehouse, you can assign the service warehouse and the production warehouse to two different clusters.

Default value

If the Warehouse Type field is Normal, Shop Floor, or Consignment (Not Owned), the check box is selected by default. If the Warehouse Type field is Service, the check box is cleared by default.

Planning Cluster

If you use planning clusters in Enterprise Planning, this is the warehouse's cluster.

If the warehouse is used as the default warehouse in the Items - Planning (cprpd1100m000) session, you cannot change the warehouse's cluster.

If the multisite concepts are activated, planning clusters are mandatory, and the planning cluster of the warehouse is retrieved from the site of the warehouse.

Enterprise Unit

The enterprise unit to which the warehouse is assigned. The financial transactions that result from the warehouse orders are posted to the financial company that is linked to the warehouse's enterprise unit.

Note

Once you have set up the multicompany structure, you cannot change the existing links between key entities, enterprise units, and financial companies, for the following reasons:

  • In many countries it is illegal to change the enterprise units because this affects the financial reporting of profits and loss.
  • Technically, it is only possible to change the enterprise unit if there are no open entries for the enterprise unit. For performance reasons, LN does not check the complete database for open entries, but always assumes that open entries exist.
Intercompany Trade Classification

An attribute consisting of a code and a description that is used to create groups of entities or enterprise units. To create a group, a number of entities or enterprise units is linked to an intercompany trade classification. These groups can be used to define intercompany trade relationships.

Example

A large international organization includes these enterprise units:

In Europe

  • UK
  • France
  • Belgium

In Asia

  • India
  • China
  • Japan

Trade classification Europe is linked to the European enterprise units and trade classification Asia is linked to the Asian enterprise units. You can set up trade relations, for example to define different trade agreements in Europe and Asia, such as:

  • Asia to Europe
  • Europe to Asia
  • Asia to Asia
  • Europe to Europe