<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs0100m000" xml:lang="en">
   <Header>
      <Title>Project Control Parameters (tipcs0100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <List>
            <ListIntro>The overview session contains:</ListIntro>
            <ListItem>A history list of
			 parameter sets and their effective dates. The most recent parameter sets are at
			 the end of the list.</ListItem>
            <ListItem>The current parameter
			 set, at the top of the list (without an effective date).</ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <Paragraph>To view historical
		  sets, double-click one of the historical parameter sets. You can use the <Link href="/baanerp/ti/pcs/tipcs0400m000" role="session">Print Project Control Parameters (tipcs0400m000)</Link> session to print and compare the parameter sets.</Paragraph>
         <Paragraph>To view or change the
		  current parameters, double-click the set without an effective date that appears
		  at the top of the list. The <Link href="/baanerp/ti/pcs/tipcs0100m000" role="session">Project Control Parameters (tipcs0100m000)</Link> session starts.</Paragraph>
         <List>
            <ListIntro>If you make changes and save the new parameter setting, ERP Enterprise performs the following
			 actions:</ListIntro>
            <ListItem>Adds the new set at
			 the end of the history list.</ListItem>
            <ListItem>Updates the current
			 set (at the top of the list).</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>By default, the
			 Description field contains the date and time when the previous parameter
			 setting was saved. To avoid confusion, if you change the parameters, change or
			 delete the default Description text.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title>General</Title>
         <FieldHelp ID="tipcs000.indt">
            <Header>
               <Title>Introduction 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="tipcs000.dsca">
            <Header>
               <Title>Description</Title>
            </Header>
            <FuncDesc>The description of the parameter set. For example, you can
			 indicate why you changed the parameters.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tipcs000.ngpr">
            <Header>
               <Title>Project Number Group</Title>
            </Header>
            <FuncDesc>A group of first free number series that you can assign to a
		specific use.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>For example, you can assign a number group to:</ListIntro>
                  <ListItem>Business partner codes</ListItem>
                  <ListItem>Purchase contracts</ListItem>
                  <ListItem>Sales orders</ListItem>
                  <ListItem>Production orders</ListItem>
                  <ListItem>Service orders</ListItem>
                  <ListItem>Warehousing orders</ListItem>
                  <ListItem>Freight orders</ListItem>
               </List>
            </SimpleSection>
            <SimpleSection>
               <Paragraph>Within a number group you can define multiple series. Each
		  series is identified by the series code. The series numbers that ERP Enterprise generates consist of
		  the series code followed by the first free number in the series. Series codes
		  of the same number group have the same length.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>Alphanumeric
				project codes are not allowed.</Paragraph>
            </Note>
            <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="tipcs000.seri" OtherIDs="tcmcs050.dsca">
            <Header>
               <Title>Series for Project</Title>
            </Header>
            <FuncDesc>If you cannot manually select a series for a PCS project
			 code, the <Link href="/baanerp/tc/glossary/glossary#Series_tc" role="glossary">series</Link> in this field is used to generate the project
			 code. The series is used, for example, if project codes need to be generated
			 using data from an external database by means of a <Link href="/baanerp/tc/glossary/glossary#000090" role="glossary">business object</Link>.</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="tipcs000.cbla">
            <Header>
               <Title>Customize BOM Line automatically</Title>
            </Header>
            <FuncDesc>If this check box is selected, an item with order
			 policy <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> is customized automatically after inserting and saving the item
			 as a component in the single-level BOM of a customized item.</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>The project segment of the newly customized item equals
				the parent item's project segment.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="tipcs000.cdgi">
            <Header>
               <Title>Copy Effective Dates from Generic Item</Title>
            </Header>
            <FuncDesc>If this check box is selected, and you customize a
			 generic item, the effective dates and expiry dates of generic BOM lines and
			 routing operations are copied to the PCS project of the customized item.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is cleared, and you customize a
				generic item, the effective dates and expiry dates of generic BOM lines and
				routing operations are not copied to the PCS project of the customized item.
				Instead, the effective dates of BOM lines and routing operations change to
				January 2, 1970, and the expiry dates to December 31, 2038. The validity period
				is now extended so that the BOM lines and routing operations are always valid
				on the <GUIRef href="/baanerp/ti/pcs/tipcs2101m000#tipcs020.cfdt" role="manual">Reference Date</GUIRef> of the project.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>An extended validity period only applies to BOM lines and
				routing operations. The effective dates and expiry dates of other entities in a
				PCS project that can be date effective, such as supplying relationships and
				item-supplier information, do not change.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="tipcs000.eudt">
            <Header>
               <Title>Enterprise Unit for calc.off. used from</Title>
            </Header>
            <FuncDesc>If you create a PCS project on a sales order or service
			 order, the value in this field indicates the default calculation office for the
			 PCS project. The calculation office is linked to a <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link>, which determines the financial company
			 on which financial transactions are posted.</FuncDesc>
            <AllowedValues>
               <SectionTitle>Allowed values</SectionTitle>
               <Paragraph>
                  <Link href="/baanerp/ti/domains/pcs.eudt" role="domain">Possible Values</Link>
               </Paragraph>
            </AllowedValues>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If no calculation office is specified for the enterprise
				unit of the sales office, service department, or warehouse in the <GUIRef href="/baanerp/tc/emm/tcemm0130m000" role="session">Enterprise Units (tcemm0130m000)</GUIRef> details session, the calculation office is determined
				by means of the order series.</Paragraph>
            </Note>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000063" role="manual">Calculation offices</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.pocm">
            <Header>
               <Title>Percentage of Completion Calculation Method</Title>
            </Header>
            <FuncDesc>With interim revenue recognition, you can calculate interim
			 Cost of Goods Sold (COGS) and interim revenue for a PCS project. The interim
			 COGS and revenue are based on the percentage of the work that is completed on
			 the PCS project. In this field, you must determine how the Percentage of
			 Completion (POC) is calculated for the PCS project.</FuncDesc>
            <SimpleSection>
               <Paragraph>The POC that you select in this field is used as a default
				value in the project details of PCS projects that are generated from a sales
				order line by using the <Link href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project PCS) Structure for Sales Orders (tdsls4244m000)</Link> session.</Paragraph>
            </SimpleSection>
            <AllowedValues>
               <SectionTitle>Allowed values</SectionTitle>
               <Paragraph>
                  <Link href="/baanerp/ti/domains/pcs.pocm" role="domain">Percentage of Completion Method</Link>
               </Paragraph>
            </AllowedValues>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000370" role="manual">Overview of interim revenue recognition in Project Control (PCS)</Link>
               </RelTopic>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000371" role="manual">Procedure for interim revenue recognition in Project Control (PCS)</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.intc">
            <Header>
               <Title>Post Interim COGS and Revenues by Cost Component</Title>
            </Header>
            <FuncDesc>With interim revenue recognition, you can calculate interim
			 Cost of Goods Sold (COGS) and interim revenue for a PCS project.</FuncDesc>
            <SimpleSection>
               <Paragraph>The setting of this check box determines how the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.intc" role="manual">Post Interim COGS and Revenues by Cost Component</GUIRef> check box in
				the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000" role="session">Project Details (tipcs2130m000)</GUIRef> details session is set for PCS projects that are
				generated from a sales order line by using the <Link href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project PCS) Structure for Sales Orders (tdsls4244m000)</Link> session.</Paragraph>
               <Paragraph>If this check box is selected, the interim COGS is specified by detailed
				cost components. You can view and maintain the detailed interim COGS in the <Link href="/baanerp/ti/pcs/tipcs3191m000" role="session">COGS by Cost Component (tipcs3191m000)</Link> session.</Paragraph>
               <Paragraph>If this check box is cleared, the interim COGS is not specified by
				detailed cost components. Instead, the interim COGS is posted on the cost
				component that is specified in the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.incp" role="manual">General Cost Component for Interim Postings</GUIRef> field.</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/ti/P000010_int_result_cost_comp" role="manual">Interim results by cost component</Link>.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcs000.incp" OtherIDs="tcmcs048.dsca">
            <Header>
               <Title>General Cost Component for Interim Postings</Title>
            </Header>
            <FuncDesc>The cost component on which the interim Cost of Goods Sold
			 (COGS) is posted. You can only enter a cost component if the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.intc" role="manual">Post Interim COGS and Revenues by Cost Component</GUIRef> check box is
			 cleared.</FuncDesc>
            <SimpleSection>
               <Paragraph>The cost component that you select in this field is used
				as the default cost component in the project details of PCS projects that are
				generated from a sales order line by using the <Link href="/baanerp/td/sls/tdsls4244m000" role="session">Generate (Project PCS) Structure for Sales Orders (tdsls4244m000)</Link> session.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcs000.fciv">
            <Header>
               <Title>Include Fixed Costs in Project Valuation</Title>
            </Header>
            <FuncDesc>If this check box is selected, <Link href="/baanerp/tf/glossary/glossary#FixedCosts_tf" role="glossary">fixed costs</Link> are included in the project
			 valuation.</FuncDesc>
            <SimpleSection>
               <Paragraph>This parameter also impacts the cost price of customized
				items as displayed in the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000" role="session">Items - Costing (ticpr0107m000)</GUIRef> details session. In this session, the estimated and
				actual cost price for customized items can be compared.</Paragraph>
               <Paragraph>If the <GUIRef href="/baanerp/ti/pcs/tipcs0100m000#tipcs000.fciv" role="manual">Include Fixed Costs in Project Valuation</GUIRef> check box is
				selected, both fixed costs and variable costs are included in the estimated and
				the actual costing data in the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000" role="session">Items - Costing (ticpr0107m000)</GUIRef> session.</Paragraph>
               <Paragraph>If the <GUIRef href="/baanerp/ti/pcs/tipcs0100m000#tipcs000.fciv" role="manual">Include Fixed Costs in Project Valuation</GUIRef> check box is
				cleared, the fixed costs are not included in the costing data in the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000" role="session">Items - Costing (ticpr0107m000)</GUIRef> session. Reason is that if this check box is cleared,
				fixed costs cannot be booked, and are therefore not included in the actual
				costs. Because a comparison between the estimated and actual costing data is
				not reasonable if fixed costs are missing in the actual costs, the fixed costs
				are also excluded from the estimated costing data.</Paragraph>
               <Paragraph>Material costs are always variable. Surcharges on labor
				costs can be either fixed or variable.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcs000.fcis">
            <Header>
               <Title>Include Fixed Costs in Budget Sales Price</Title>
            </Header>
            <FuncDesc>If this check box is selected, <Link href="/baanerp/tf/glossary/glossary#FixedCosts_tf" role="glossary">fixed costs</Link> are included in the sales price
			 of the budget.</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.bkcs">
            <Header>
               <Title>Post Project Transactions on Current Date</Title>
            </Header>
            <FuncDesc>If this check box is selected, the sales price, cost
			 price and the sales revenue are posted for non-closed projects.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tipcs000.eclw">
            <Header>
               <Title>Estimated Cost of Goods Sold Limited by WIP Value</Title>
            </Header>
            <FuncDesc>Determines how ERP Enterprise calculates the costs of goods sold.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is selected, estimated
				costs of the goods sold will never exceed the work-in-process value (per cost
				price component) for the project.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tipcs000.tpsr">
            <Header>
               <Title>Transfer between PCS Projects considered as Selling Relation</Title>
            </Header>
            <FuncDesc>If this check box is selected, the transfer of items
			 from one PCS project (the source project) to another PCS project (the target
			 project) results in a revenue on the source project.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is cleared, the transfer of items from
				one PCS project (the source project) to another PCS project (the target
				project) results in a negative material cost booking on the source project. You
				can consider such a negative booking as a correction of the actual costs on the
				source project.</Paragraph>
            </SimpleSection>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Settings for COGS</Title>
         <FieldHelp ID="tipcs000.wipv">
            <Header>
               <Title>Post Project-related Cost of Goods Sold Against</Title>
            </Header>
            <FuncDesc>Determines how ERP Enterprise calculates the work-in-process values for
			 projects. The parameter is used for calculating the cost prices of sales
			 deliveries and for posting financial project transactions to ERP Enterprise Finance.</FuncDesc>
            <AllowedValues>
               <SectionTitle>Allowed values</SectionTitle>
               <Paragraph>
                  <Link href="/baanerp/tc/domains/wipv" role="domain">Work in Progress Valuation</Link>
               </Paragraph>
            </AllowedValues>
         </FieldHelp>
         <FieldHelp ID="tipcs000.crfc">
            <Header>
               <Title>COGS and Revenues restricted to Financial Company of PCS Project</Title>
            </Header>
            <FuncDesc>If this check box is selected, PCS related COGS and
			 revenues are all posted on the financial company of the PCS project's <Link href="/baanerp/ti/glossary/glossary#000053" role="glossary">calculation office</Link>.</FuncDesc>
            <SimpleSection>
               <Paragraph>If this check box is cleared, PCS related COGS and
				revenues are posted on the financial companies of the service department, sales
				office and/or warehouse.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.dstr">
            <Header>
               <Title>COGS Distribution based on</Title>
            </Header>
            <FuncDesc>If the <Link href="/baanerp/ti/pcs/tipcs0100m000#tipcs000.crfc" role="formfield">COGS and Revenues restricted to Financial Company of PCS Project</Link> check box is cleared, the general COGS is distributed among
			 several departments instead of only on the PCS project's calculation office.
			 You can use this field to indicate whether you want to enter the COGS
			 distribution manually in the <Link href="/baanerp/ti/pcs/tipcs3110m000" role="session">Project COGS Distribution (tipcs3110m000)</Link> session, or
			 that ERP Enterprise calculates the
			 COGS distribution based on the revenue of the sales order, service order,
			 and/or warehouse order.</FuncDesc>
            <AllowedValues>
               <SectionTitle>Allowed values</SectionTitle>
               <Paragraph>
                  <Link href="/baanerp/ti/domains/pcs.distr" role="domain">COGS Distribution based on</Link>
               </Paragraph>
            </AllowedValues>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.ngpo" OtherIDs="ngpo.dsca">
            <Header>
               <Title>Number Group for Project Orders</Title>
            </Header>
            <FuncDesc>If you define an invoice relation between the PCS project and
			 the sales office, service department, or warehouse in the <GUIRef href="/baanerp/tc/emm/tcemm2110m000" role="session">Entity - Entity Relationships (tcemm2110m000)</GUIRef> session, an internal invoice is sent
			 from the PCS project to a sales office, service department, or warehouse. The <Link href="/baanerp/tc/glossary/glossary#NumberGroup_tc" role="glossary">number group</Link> in this field is used to generate a PCS
			 project order number on the internal invoice.</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.srpo" OtherIDs="srpo.dsca">
            <Header>
               <Title>Series for Project Orders</Title>
            </Header>
            <FuncDesc>If you define an invoice relation between the PCS project and
			 the sales office, service department, or warehouse in the <GUIRef href="/baanerp/tc/emm/tcemm2110m000" role="session">Entity - Entity Relationships (tcemm2110m000)</GUIRef> session, an internal invoice is sent
			 from the PCS project to a sales office, service department, or warehouse. The <Link href="/baanerp/tc/glossary/glossary#Series_tc" role="glossary">series</Link> in this field is used to generate a PCS project
			 order number on the internal invoice.</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tipcs000.item" OtherIDs="item.dsca">
            <Header>
               <Title>Item</Title>
            </Header>
            <FuncDesc>If you define an invoice relation between the PCS project and
			 the sales office, service department, or warehouse in the <GUIRef href="/baanerp/tc/emm/tcemm2110m000" role="session">Entity - Entity Relationships (tcemm2110m000)</GUIRef> session, an internal invoice is sent
			 from the PCS project to a sales office, service department, or warehouse. The <Link href="/baanerp/tc/glossary/glossary#000059" role="glossary">cost item</Link> in this field is used to specify the general
			 costs on the internal invoice in <GUIRef href="/baanerp/ci/sli" role="module">Invoicing</GUIRef> (SLI) and <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> (ACP).</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
      </FieldGroup>
   </Fields>
</Session>