<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/com/cpcom0100m000" xml:lang="en">
   <Header>
      <Title>Performance Parameters (cpcom0100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <List>
            <ListIntro>This session contains:</ListIntro>
            <ListItem>A history list of parameter sets and their effective
			 dates</ListItem>
            <ListItem>The current parameter set, at the top of the list (without an
			 effective date)</ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <SectionTitle>Performance aspects</SectionTitle>
         <Paragraph>The settings in this session could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000001_multiple_bshells_concept" role="manual">Parallel processing concept</Link>
         </Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000036" role="manual">To configure Enterprise Planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cpcom000.indt">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>The date and time that the parameters are valid. The parameters
		  are valid up to the effective date of a more recent parameter setting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cpcom000.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description of the parameter set. For example, you can
		  indicate why you change the parameters.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>By default, the Description field contains the date and
			 time when the previous parameter set was saved. In order to avoid confusion, if
			 you change the parameters, change or delete the description as well.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="cpcom000.dtmi">
         <Header>
            <Title>Display Time Interval</Title>
         </Header>
         <FuncDesc>The amount of time (in seconds) that LN waits before it
		  displays new information in the progress bar of the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>Sessions that process large volumes of data usually display
			 some runtime information, which enables you to monitor the session's progress.
			 However, if the screen is refreshed frequently, this can affect system
			 performance.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cpcom000.mnpr">
         <Header>
            <Title>Maximum Number of Planned Orders per Requirement</Title>
         </Header>
         <FuncDesc>The maximum number of planned orders that the order-planning
		  process generates for one requirement. If LN needs more planned
		  orders to fill the requirement, LN generates one more planned order to fill the remainder of the
		  requirement.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can use this field to prevent particular types of
			 errors. These errors can cause LN to generate an extremely large number of planned
			 orders.</Paragraph>
            <Paragraph>For example, if you accidentally set an item's <Link href="/baanerp/td/glossary/glossary#MaximuOrderQ_td" role="glossary">maximum order quantity</Link> to 1 and you
			 require 1000 piece, LN must generate 1000 planned orders of quantity 1, just to fill one requirement.
			 In general, that situation is undesirable. If you set the <GUIRef href="/baanerp/cp/com/cpcom0100m000#cpcom000.mnpr" role="manual">Maximum Number of Planned Orders per Requirement</GUIRef> field to 10, LN generates 10 planned order of quantity 1 and a final planned order with a
			 quantity of 990.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cpcom000.rmps">
         <Header>
            <Title>Average Number of Planned Orders per Item</Title>
         </Header>
         <FuncDesc>In this field, you can indicate the estimated number of planned
		  orders per item.</FuncDesc>
         <SimpleSection>
            <Paragraph>If you use parallel processing, LN reserves a range of
			 order numbers for the planned orders that each bshell generates. LN uses this field to
			 determine the size of the range of reserved order numbers.</Paragraph>
         </SimpleSection>
         <Important>
            <SectionTitle>Important!</SectionTitle>
            <Paragraph>If this value is too small, the servers for parallel
			 processing try to use the same order number, which leads to errors.</Paragraph>
         </Important>
      </FieldHelp>
      <FieldHelp ID="cpcom000.ufdw">
         <Header>
            <Title>Workload per Server</Title>
         </Header>
         <FuncDesc>In this field, you can define the number of items included in
		  each batch that is distributed over the parallel bshells.</FuncDesc>
         <SimpleSection>
            <Paragraph>The multiple-bshell solution dynamically calculates the
			 optimal workload per server. The number you specify in the <GUIRef href="/baanerp/cp/com/cpcom0100m000#cpcom000.ufdw" role="manual">Workload per Server</GUIRef> field is the upper limit.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle>Performance aspects</SectionTitle>
            <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000005_workload_per_server" role="manual">Workload per server</Link>
            </Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cpcom000.prse">
         <Header>
            <Title>Workload Based on Operations</Title>
         </Header>
         <FuncDesc>If this check box is selected, the criterion LN uses for workload
		  distribution over the bshells, is the routing composition of each item. The
		  more operations a routing of an item is composed of, the more weight it
		  has.</FuncDesc>
         <SimpleSection>
            <SectionTitle>Performance aspects</SectionTitle>
            <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000006_workload_based_on_operations"
                     role="manual">Workload based on operations</Link>
            </Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cpcom000.clse">
         <Header>
            <Title>Dynamic Workload Calculation</Title>
         </Header>
         <FuncDesc>If this check box is selected, the total workload is
		  equally distributed over the available bshells.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>