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, leaving the planning cluster segment black will link all warehouses to a blank cluster to accommodate 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 code
Step 1. Defining the segment

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

Step 2. Defining 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 code 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.
Note

  • The item code segment is mandatory.

  • The segment definition cannot be easily changed at a later date. Be careful when you specify the segments.

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

Related topics