<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tg/ebm/user/us000240" xml:lang="en">
   <Header>
      <Title>Functional decomposition</Title>
      <Keyword type="header" order="d1e2269797">
         <Level1>Functional decomposition</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>A functional decomposition is created for each major function
		represented in the BCD.</Paragraph>
      <Paragraph>These functional decompositions are shown in the business
		function model. A top-level function called Enterprise Business Model (EBM)
		provides an overview of all existing major functions.</Paragraph>
      <Paragraph>A functional decomposition consists of a breakdown of all major
		functions, with all available main functions attached to the major function
		acting as children. The ground rule when making this decomposition is that the
		decomposition is continued until each main function handles only one flow. A
		flow is a description of what must be accomplished by a process, related to a
		business function, regarding a particular work object.</Paragraph>
      <Paragraph>The flow object is the entity that flows through the business
		process, for example, a sales order or a warehouse order. The flow is directly
		related to the flow object. If the characteristics of a flow object change, the
		flow case will also change, which indicates the beginning of a new main
		function, and a new main process.</Paragraph>
      <Paragraph>Because one function can exist in various business typologies,
		variants have been created on the lowest level of the function model. Business
		processes are linked to this level (variant).</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="394" width="393"
                   SRC="images/tr_screen_us000240_1.png"
                   alt="[...]"/>
      </Figure>
   </GeneralSection>
</ManualTopic>