<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ti/onlinemanual/000176" xml:lang="en">
   <Header>
      <Title>Main project and subproject parts</Title>
      <Keyword type="header" order="d1e2092838">
         <Level1>Main and sub project parts</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>Working with main projects and subprojects has the following consequences:</Paragraph>
      <List>
         <ListItem>The main project contains the overall planning for its subprojects.
This means that the start and delivery dates for the network planning of the
subprojects are directly derived from the overall network planning for the main
project! Umbrella activities can be defined for the main project in order to
control the subprojects. This allows you to perform a rough cut of capacity
requirements planning, depending on the value of the rough capacity requirement
which can be recorded for each activity by means of the <GUIRef href="/baanerp/ti/pcs/tipcs4101m000" role="session">Activities (tipcs4101m000)</GUIRef> session.</ListItem>
      </List>
      <List>
         <ListItem>Logistically, the main project lets you perform rough-cut planning and control
the subprojects. A main project is not clearly relevant for detailed planning of
the flow of materials and capacities. Therefore,
NO customized product structures can be recorded for a main project.</ListItem>
      </List>
      <List>
         <ListIntro>For a main project, a variety of project data can be recorded which is also
applicable for subprojects, unless data has been recorded separately for the
subprojects. This data includes:</ListIntro>
         <ListItem>Operation rates</ListItem>
         <ListItem>Subcontracting rates</ListItem>
         <ListItem>Cost-price surcharges</ListItem>
         <ListItem>Chart of accounts</ListItem>
      </List>
      <List>
         <ListIntro>The umbrella activities of the main project can be included in the estimated
data of the (main) project.
The main project acts as the aggregate project for the subprojects. So, some
data of the subprojects is automatically aggregated to the main projects, that
is:</ListIntro>
         <ListItem>Rough capacity, aggregated capacity and hours spent by means of the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</ListItem>
         <ListItem>Budgeted costs, estimated costs, actual costs and total invoice amount   by
means of the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session.</ListItem>
      </List>
      <List>
         <ListIntro>Various functions are performed for the main project. This is performed for the
subprojects as well, that is:</ListIntro>
         <ListItem>Network planning</ListItem>
         <ListItem>Cost price accounting</ListItem>
         <ListItem>Closing project</ListItem>
         <ListItem>Archiving project</ListItem>
      </List>
      <List>
         <ListIntro>The following cost and revenue transactions are possible for main projects:</ListIntro>
         <ListItem>Hours that are or are not directly posted to an activity of the main project</ListItem>
         <ListItem>Sales orders or sales invoices for services rendered</ListItem>
      </List>
   </GeneralSection>
</ManualTopic>