<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/op000220" xml:lang="en">
   <Header>
      <Title>Item - Ordering (tcibd2100s000)</Title>
      <Keyword type="header" order="d1e163679">
         <Level1>Item - Ordering (tcibd2100s000)</Level1>
         <Level2>planned items</Level2>
      </Keyword>
      <Keyword type="header" order="d1e163685">
         <Level1>Planned items</Level1>
         <Level2>clusters</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>The cluster concept allows you to perform integrated planning
		over multiple sites. A cluster represents one or more warehouses located near
		each other – typically, the warehouses at a particular site or in a particular
		country.</Paragraph>
      <Paragraph>You can define a plan item for each combination of cluster and
		item code.</Paragraph>
      <List>
         <ListIntro>The plan item code includes these segments:</ListIntro>
         <ListItem>The cluster segment prefixes</ListItem>
         <ListItem>The item code segment</ListItem>
      </List>
      <Paragraph>Therefore, the plan item represents the combination of item
		definition and location.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Clustered items and nonclustered items</SectionTitle>
      <Paragraph>You can also define a plan item with an empty cluster segment.
		The empty cluster is used to model the production environment; the other
		clusters are used for modeling the supply chain structure for Distribution
		Requirements Planning (DRP).</Paragraph>
      <List>
         <ListIntro>For plan items, we use the following terms:</ListIntro>
         <ListItemHead>Clustered item</ListItemHead>
         <ListItem>Plan item with the cluster filled.</ListItem>
         <ListItemHead>Nonclustered plan item</ListItemHead>
         <ListItem>Plan items with empty cluster segment</ListItem>
      </List>
      <Paragraph>If it is not relevant if the cluster is filled, we will speak
		just of <Emphasis>plan items</Emphasis>.</Paragraph>
      <Paragraph>The clustered item groups all inventory and planned inventory
		transactions of all warehouses that are assigned to the cluster.</Paragraph>
      <Paragraph>The nonclustered plan item groups all inventory and transactions
		of all warehouses not linked to any cluster.</Paragraph>
      <Paragraph>To view the planned inventory transactions, use the <GUIRef href="/baanerp/wh/inp/whinp1500m000" role="session">Planned Inventory Transactions (whinp1500m000)</GUIRef> session.</Paragraph>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>The planning system ignores inventory and planned inventory
		  transactions of warehouses that are explicitly excluded from the planning
		  process, such as a warehouse for rejected items or spare parts.</Paragraph>
         <Paragraph>To exclude a warehouse from the planning process, clear the <GUIRef href="/baanerp/wh/wmd/whwmd2500m000#tcmcs003.inep" role="manual">Include in Enterprise Planning</GUIRef> check box in the <GUIRef href="/baanerp/wh/wmd/whwmd2500m000" role="session">Warehouses (whwmd2500m000)</GUIRef> session.</Paragraph>
      </Note>
   </GeneralSection>
   <ExampleSection>
      <SectionTitle>Example of clusters</SectionTitle>
      <Paragraph>Suppose you defined item S-3501.</Paragraph>
      <List>
         <ListIntro>You also defined the following clusters:</ListIntro>
         <ListItem>EUR (Europe)</ListItem>
         <ListItem>NA (North-America)</ListItem>
         <ListItem>JAP (Japan)</ListItem>
      </List>
      <List>
         <ListIntro>Now, you can define four plan items all representing the same
		  physical item:</ListIntro>
         <ListItem>EUR S-3501</ListItem>
         <ListItem>NA S-3501</ListItem>
         <ListItem>JAP S-3501</ListItem>
         <ListItem>S-3501</ListItem>
      </List>
      <Paragraph>The planning engine treats these four plan items as four
		different items. For each plan item, the system maintains the anticipated
		receipts and issues, expected inventory levels, and forecast demand
		separately.</Paragraph>
      <List>
         <ListIntro>The plan item concept supports the following
		  functionality:</ListIntro>
         <ListItem>MRP (Material Requirements Planning)</ListItem>
         <ListItem>MPS (Master Planning Schedule)</ListItem>
         <ListItem>PRP (Project Requirements Planning)</ListItem>
         <ListItem>DRP (Distribution Requirements Planning)</ListItem>
      </List>
      <Paragraph>Similarly, you can specify plan items for project items. In that
		case, the plan item code has three segments: cluster, project, and item
		code.</Paragraph>
   </ExampleSection>
</ManualTopic>