Item definition in Enterprise Planning

Enterprise Planning allows a very flexible definition of item codes using segmentation.

An administrator must define the item segmentation, before you can use Enterprise Planning.

Currently Enterprise Planning supports the following logical segments:

Note: If multisite functionality is active, a planning cluster is mandatory. If multisite is not implemented, using a planning cluster is optional. Leaving the planning cluster segment black will link all warehouses to a blank cluster. The planning cluster is still necessary if you want to have distribution planning functionality.

With the optional project segment you can define project items.

You can define anything between 1 and 3 segments. Item code segments have the following order:

  • Planning Cluster
  • Project
  • Item
Defining the item-code segments
Step 1. Define the segment

You define the segments in the Segmented Domains (ttgfd4122m000) session and the Item Code Segmentation (tcibd0500m000) session.

Step 2. Define domain(s)

The segments must correspond to the domain definition of related domains. This is extremely important. This means that the conversion (upper, lower case), alignment and length of the segment and its related domain must be the same.

  • The item-base segment must correspond to the definition of the cpitem domain.
  • The planning cluster segment must correspond to the definition of the tcemm.clus domain.
  • The project segment must correspond to the definition of the tccprj domain.
How to define the item-code segments
Note

  • The item-base segment is mandatory.

  • The segment definition cannot be changed easily afterwards. So be careful when you specify the segments!

  • The item-base segment in Enterprise Planning must have the same length as the item-base segment in the other packages.

Related topics