<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs2101m000" xml:lang="en">
   <Header>
      <Title>Projects (tipcs2101m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to create, maintain and/or
		  list projects.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In the details
		  session, you can create and maintain projects that are used to calculate, plan
		  and perform logistic activities that are directly related to customer orders.</Paragraph>
         <List>
            <ListIntro>You can only delete a project if:</ListIntro>
            <ListItem>The project has the <GUIRef href="/baanerp/tc/domains/psts#free" role="option">Free</GUIRef> status.</ListItem>
            <ListItem>It is not linked to a
			 sales quotation or a sales order.</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you have started
			 this session by zooming, you can only find and select a record.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tipcs020.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
               <ListItem>Customized item data (BOMs and routings)</ListItem>
               <ListItem>Project planning (activity planning)</ListItem>
            </List>
            <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="cprj.status">
         <Header>
            <Title>Project Status</Title>
         </Header>
         <FuncDesc>Indicates the current progress of the project. The following
		  status values are available:</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/tc/domains/psts" role="domain">Possible values</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="project.dscb">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>An additional field for the project description if the project
		  description does not fit on a single line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs020.refe">
         <Header>
            <Title>Reference</Title>
         </Header>
         <FuncDesc>Displays the reference data of the project. This field is only
		  used for providing information. You can determine the reference data to enter,
		  for instance, the number of a customer's sales order.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field enables
			 you to quickly search for project data using an argument other than the project
			 code.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="search.key">
         <Header>
            <Title>Search Key</Title>
         </Header>
         <FuncDesc>An alternative form of a description used for convenience
		during searching. Typically, it is an abbreviation, an acronym, or a mnemonic
		alternative to a full description.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/basictasks/000010" role="manual">To use search keys</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs020.kopr">
         <Header>
            <Title>Project Type</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs020.ccgr">
         <Header>
            <Title>Calculation Group</Title>
         </Header>
         <FuncDesc>A code representing a group of projects the user wants to
		compare financially.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>You can assign a calculation group to:</ListIntro>
               <ListItem>A budget</ListItem>
               <ListItem>A main project (as long as the calculation group is not
			 assigned to another project or single project)</ListItem>
               <ListItem>A single project (as long as the calculation group is not
			 assigned to another main project or single project)</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>In case of a budget, you must always enter a calculation
			 group. If you copy the budget to a main project or a single project, the
			 calculation group is automatically copied so that the project's calculation
			 group equals the budget's calculation group.</Paragraph>
            <Paragraph>It is not allowed to overwrite the project's calculation
			 group with a calculation group that is in use with any other project. Also if
			 you copy a budget to a new project, and the calculation code is already in use
			 in another project, the budget's calculation code is not copied to the new
			 project.</Paragraph>
            <Paragraph>For subprojects, the calculation group must be the same as
			 the main project's calculation group. If the sub project is linked to the main
			 project, the calculation group is automatically copied from the main project to
			 the sub project.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs020.bpid">
         <Header>
            <Title>Sold-to Business Partner</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">business partner</Link> for whom
		  the project is carried out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs020.pemp">
         <Header>
            <Title>Project Employee</Title>
         </Header>
         <FuncDesc>The person who is in charge of the execution of the project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs020.ffci">
         <Header>
            <Title>First Free Item Code</Title>
         </Header>
         <FuncDesc>The first item code which is used as a default value for the
		  input of new customized items.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tc/onlinemanual/000004" role="manual">To use number groups and series</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs020.cpcc">
         <Header>
            <Title>Price Calculation Code</Title>
         </Header>
         <FuncDesc>A specification of how a cost price, valuation price, or sales
		price is calculated. The code stores specific cost calculation data.</FuncDesc>
         <SimpleSection>
            <Paragraph>The price calculation code that is defined in the Cost Price
		  Calculation (CPR) Parameters determines the standard cost price. Other price
		  calculation codes are used for simulation purposes. The price calculation code
		  for customized items is stored by project.</Paragraph>
         </SimpleSection>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Specific operation rates</ListItem>
               <ListItem>Subcontracting rates</ListItem>
               <ListItem>Simulated purchase prices</ListItem>
               <ListItem>Surcharges</ListItem>
            </List>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs020.clco">
         <Header>
            <Title>Calculation Office</Title>
         </Header>
         <FuncDesc>By default, ERP Enterprise displays the <Link href="/baanerp/ti/glossary/glossary#000053" role="glossary">calculation office</Link> of the <Link href="/baanerp/tc/glossary/glossary#NumberGroup_tc" role="glossary">number group</Link>. If necessary,
		  you can fill in a different calculation office.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs020.peng">
         <Header>
            <Title>Engineering Allowed</Title>
         </Header>
         <FuncDesc>If this check box is cleared, all end items of the <Link href="/baanerp/ti/glossary/glossary#000023" role="glossary">project</Link> are <Link href="/baanerp/ti/glossary/glossary#000026" role="glossary">standard-to-order</Link> items. No
		  customized BOM or routing can therefore be maintained. As soon as a customized
		  item is added to the project, ERP Enterprise automatically selects this check box.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>If this check box is cleared, the following PCS
				functionalities do not apply:</ListIntro>
               <ListItem>Customized item data
				(BOMs and Routings).</ListItem>
               <ListItem>Project Planning.</ListItem>
               <ListItem>Project structures
				(main/sub projects).</ListItem>
               <ListItem>Activities.</ListItem>
               <ListItem>Network planning.</ListItem>
               <ListItem>Module planning.</ListItem>
               <ListItem>General costs.</ListItem>
               <ListItem>Service orders are
				not allowed on the project.</ListItem>
               <ListItem>Project surcharges.</ListItem>
               <ListItem>Cost calculation at
				project level.</ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Projects for which
			 the <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.peng" role="manual">Engineering Allowed</GUIRef> check box is not selected in the <GUIRef href="/baanerp/ti/pcs/tipcs2101m000" role="session">Projects (tipcs2101m000)</GUIRef> session, cannot be copied.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tipcs020.cfdt">
         <Header>
            <Title>Reference Date</Title>
         </Header>
         <FuncDesc>The date on which the bill of material and the routing
		  operations are exploded when a customized product structure is generated with
		  either the <Link href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project PCS) Structure for Sales Orders (tdsls4244m000)</Link> session or the <Link href="/baanerp/ti/pcs/tipcs2220m000" role="session">Generate (Project) Structure for Product Variant (tipcs2220m000)</Link> session. The <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.cfdt" role="manual">Reference Date</GUIRef> is used as a default for the <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef> field in the <GUIRef href="/baanerp/ti/pcs/tipcs2220m000" role="session">Generate (Project) Structure for Product Variant (tipcs2220m000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>If you generate a project using the <GUIRef href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project PCS) Structure for Sales Orders (tdsls4244m000)</GUIRef> session, the <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.cfdt" role="manual">Reference Date</GUIRef> field is filled according to the
			 setting of the <Link href="/baanerp/td/sls/tdsls0100s000#tdsls000.codt" role="formfield">Configuration Date (PCS)</Link> field in the <GUIRef href="/baanerp/td/sls/tdsls0100s000" role="session">Sales Parameters (tdsls0100s000)</GUIRef> session. The following settings are possible:</Paragraph>
            <List>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.pric#order.date" role="option">Order Date</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.pric#system.date" role="option">System Date</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.pric#delivery.date" role="option">Delivery Date</GUIRef>
               </ListItem>
            </List>
            <Paragraph>If the <GUIRef href="/baanerp/td/sls/tdsls0100s000#tdsls000.codt" role="manual">Configuration Date (PCS)</GUIRef> field in the <GUIRef href="/baanerp/td/sls/tdsls0100s000" role="session">Sales Parameters (tdsls0100s000)</GUIRef> session is <GUIRef href="/baanerp/td/domains/pur.pric#system.date" role="option">System Date</GUIRef>, the <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.cfdt" role="manual">Reference Date</GUIRef> field is empty after generating a
			 project structure.</Paragraph>
            <Paragraph>The <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.cfdt" role="manual">Reference Date</GUIRef> field is also used in cost-price
			 calculation of the project, and when transferring RRP orders.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This reference date
			 in <GUIRef href="/baanerp/ti/pcs" role="module">Project Control</GUIRef> overrules reference dates entered in <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> or <GUIRef href="/baanerp/td/sls" role="module">Sales Control</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="disp.txta">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, additional project text
		  is available.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>