<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000004" xml:lang="en">
   <Header>
      <Title>Field change orders (FCO)</Title>
      <Keyword type="header" order="d1e2426081">
         <Level1>Field change orders (FCO)</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>A <Link href="/baanerp/ts/glossary/glossary#FieldChangeO_ts" role="glossary">field change order (FCO)</Link> is an order to
		modify a part of a <Link href="/baanerp/ts/glossary/glossary#000306" role="glossary">cluster</Link> that is installed at the customer site or in your
		own organization. You mainly use field change orders to solve production errors
		collectively, and to introduce product modifications. You can also subcontract
		the execution of the FCO.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>You mainly use Field
		Change Orders (FCOs) to solve production errors collectively (product recalls)
		or to modify a product. In the case of production errors, the costs are usually
		at the service organization's expense.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="370" width="571"
                   SRC="../images/tr_graph_fieldchangeorders.jpg"
                   alt="[...]"/>
      </Figure>
      <Paragraph>Use the <GUIRef href="/baanerp/ts/soc/tssoc5100m000" role="session">Field Change Orders (tssoc5100m000)</GUIRef> session to define a field change order. Organizations
		that play roles in manufacturing and servicing can use this session. If a
		manufacturing defect is found with an item that has been used as a part of
		clusters, a field change order is raised for global replacement of such
		defective items. The item to be serviced and the activities to be performed are
		registered in this entity.</Paragraph>
      <GeneralSection>
         <SectionTitle>FCO Lines</SectionTitle>
         <Paragraph>After you create the FCO header, in which the anonymous item
		  or <Link href="/baanerp/ts/glossary/glossary#Objects_ts" role="glossary">serialized item</Link> and the related activities that you want
		  to replace are specified, you can either manually define FCO lines or have the
		  lines generated automatically.</Paragraph>
         <Paragraph>Each FCO line represents one specific serialized item or one
		  anonymous item in a cluster. The advantage of automatic generation is that LN checks all related clusters, taking the active dates
		  into account. You can use the <GUIRef href="" role="manual">Generate FCO Lines (tssoc5210m000)</GUIRef> session to generate lines automatically for a range of
		  FCOs, sold-to business partners, and clusters or <Link href="/baanerp/ts/glossary/glossary#SerialNumber_ts" role="glossary">serial numbers</Link>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Generate Service Orders for FCO</SectionTitle>
         <Paragraph>You can generate <Link href="/baanerp/ts/glossary/glossary#ServicOrder_ts" role="glossary">service orders</Link> for field change orders (FCOs). The
		  planned start time on the service order is the planned start date entered in
		  the <GUIRef href="" role="manual">Generate Service Orders for FCO (tssoc5220m000)</GUIRef> session.
		  To determine the planned finish time on the service order, you add the sum of
		  all reference activities’ durations to the planned start time.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Functionality to generate Field Change Order</SectionTitle>
      </GeneralSection>
      <List>
         <ListItem>The first time you
		  define an FCO, the FCO receives the status Free.</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/ts/soc/tssoc5100m000" role="session">Field Change Orders (tssoc5100m000)</GUIRef> session, you can define up to five activities for an
		  FCO. When you generate a service order for an FCO, LN generates a service
		  order activity line for each of the FCO's activities.</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/ts/soc/tssoc5100m000" role="session">Field Change Orders (tssoc5100m000)</GUIRef> session, you select the item code to which the FCO
		  applies, and in the <GUIRef href="/baanerp/ts/soc/tssoc5110m000" role="session">FCO Lines (tssoc5110m000)</GUIRef> session
		  you specify the serialized items (which must have this item code) on which the
		  FCO's activities will be carried out.</ListItem>
         <ListItem>You can manually enter
		  the serialized item(s) to which the FCO applies in the <GUIRef href="/baanerp/ts/soc/tssoc5110m000" role="session">FCO Lines (tssoc5110m000)</GUIRef> session. Alternatively, you can run the <GUIRef href="/baanerp/ts/soc/tssoc5210m000" role="session">Generate FCO Lines (tssoc5210m000)</GUIRef> session, in which LN generates FCO lines
		  for all serialized items derived from the item code entered on the FCO. The
		  FCO's status changes from Free to Lines Generated when you create the FCO's
		  first FCO lines.</ListItem>
         <ListItem>You can generate service
		  orders for a range of FCOs using the <Link href="/baanerp/ts/soc/tssoc5220m000" role="session">Generate Service Order (tssoc5220m000)</Link> session. When you generate the first service orders for an FCO, the FCO's
		  status changes from Lines Generated to Execution.</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session, the <Link href="/baanerp/ts/glossary/glossary#ServicType_ts" role="glossary">service type</Link> selected
		  determines the service type of service orders that you generate from FCOs. This
		  service type also determines the service order's <Link href="/baanerp/ts/glossary/glossary#000390" role="glossary">coverage type</Link>, so you can,
		  therefore, define a <Link href="/baanerp/ts/glossary/glossary#ContraCovera_ts" role="glossary">contract coverage</Link> for FCOs.</ListItem>
         <ListItem>After all of an FCO's
		  service orders are finished, in other words, if the status orders of the
		  service items are either Closed or Canceled, the FCO's status can be Closed.
		  You can then remove the FCO and its FCO lines from LN.</ListItem>
      </List>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ts/onlinemanual/000037" role="manual">To generate service orders for FCOs</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>