<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/pur/tdpur3432m000" xml:lang="en">
   <Header>
      <Title>Update Received CUMs (tdpur3432m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to update the <Link href="/baanerp/td/glossary/glossary#000006" role="glossary">received cumulative</Link> of a receipt that cannot be updated
		  by ERP Warehouse Management anymore, because the purchase schedule line is
		  already invoiced.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Usually, when an error is made during the creation or
		  confirmation of a receipt in ERP Warehouse Management, the receipt is
		  corrected in the <GUIRef href="/baanerp/wh/inh/whinh3121s000" role="session">Receipt Correction (whinh3121s000)</GUIRef> session and the
		  received CUM is automatically updated. However, when the purchase schedule line
		  status is set to <Emphasis>Invoiced</Emphasis> very quickly, for instance when <Link href="/baanerp/tf/glossary/glossary#000008" role="glossary">self billing</Link> is used, there
		  is no time to perform a receipt correction in ERP Warehouse Management. In
		  this case, you must update the received CUMs in this session.</Paragraph>
      </Note>
      <Important>
         <SectionTitle>Important!</SectionTitle>
         <Paragraph>If the received cumulatives are not corrected, your received
		  cumulatives will constantly dispute your sold-to business partner's shipped
		  cumulatives, because the <Link href="/baanerp/td/sls/tdsls3131m000" role="session">Sales Schedule Reconciliation (tdsls3131m000)</Link> session
		  only solves disputes on the sales side. As a result, when the received CUM is
		  reconciled in the <GUIRef href="/baanerp/td/sls/tdsls3131m000" role="session">Sales Schedule Reconciliation (tdsls3131m000)</GUIRef> session,
		  you must also update the received CUM in the current session.</Paragraph>
      </Important>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="2">
               <TR no="1" isLast="false">
                  <TD rowspan="1" colspan="1">Delivery:</TD>
                  <TD rowspan="1" colspan="1">two parts are
				  delivered on a sales schedule and the shipped CUM is updated to two.</TD>
               </TR>
               <TR no="2" isLast="true">
                  <TD rowspan="1" colspan="1">Receipt:</TD>
                  <TD rowspan="1" colspan="1">due to a data entry error, three parts are
				  received. No receipt correction can be made, because the error is not
				  discovered before the schedule line has the <Emphasis>Invoiced</Emphasis> status.</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>As a result, when the purchase schedule is sent to the
		  buy-from business partner, and when the sales schedule is approved, a dispute
		  is created. On the sales side, it is decided to adjust the received CUM to
		  equal the shipped CUM. If you do not update the received CUM on the purchase
		  side, the next time the purchase schedule is sent, the received CUM is
		  communicated incorrectly again, which results in a dispute on the sales side.
		  If you do not update the received CUM in this session, the purchase schedule
		  will always communicate an incorrect CUM to Sales Control (SLS).</Paragraph>
      </ExampleSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000362" role="manual">Reconciling sales schedules</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000353" role="manual">Purchase schedule cumulatives</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000354" role="manual">Receipts on push schedule lines</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000008" role="manual">Self billing</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdpur332.schn">
         <Header>
            <Title>Schedule</Title>
         </Header>
         <FuncDesc>The number of the <Link href="/baanerp/td/glossary/glossary#000000000000011" role="glossary">purchase schedule</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur332.crdt">
         <Header>
            <Title>CUM (Reset) Date</Title>
         </Header>
         <FuncDesc>A purchase release is used to send out, under one release
		number, those schedules that share the following common characteristics:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Buy-from business partner.</ListItem>
               <ListItem>Ship-from business partner.</ListItem>
               <ListItem>Ship-to address.</ListItem>
               <ListItem>Release type (material release/ shipping schedule/ sequence
			 shipping schedule).</ListItem>
               <ListItem>Shipment based schedule/ delivery based schedule.</ListItem>
               <ListItem>Communication method.</ListItem>
               <ListItem>Warehouse.</ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can reset the cumulatives in the <Link href="/baanerp/td/pur/tdpur3230m000" role="session">Reset Cumulatives (tdpur3230m000)</Link> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdpur332.trdt">
         <Header>
            <Title>Transaction Date</Title>
         </Header>
         <FuncDesc>The date on which the items are actually received in the
		destination warehouse.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur332.qicr">
         <Header>
            <Title>Received CUM</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000006" role="glossary">received cumulative</Link> expressed in the <Link href="/baanerp/wh/glossary/glossary#000337" role="glossary">inventory unit</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.cuni">
         <Header>
            <Title>Received CUM</Title>
         </Header>
         <FuncDesc>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</FuncDesc>
         <SimpleSection>
            <Paragraph>The inventory unit is also used as the base unit in measure
		  conversions, especially for conversions that concern the order unit and the
		  price unit on a purchase order or a sales order. These conversions always use
		  the inventory unit as the base unit. An inventory unit therefore applies to all
		  item types, also to item types that cannot be kept in stock.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpur332.reno">
         <Header>
            <Title>Receipt Number</Title>
         </Header>
         <FuncDesc>The sequence number assigned to every individual receipt of
		goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur332.qidl">
         <Header>
            <Title>Received Quantity</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000068" role="glossary">delivered quantity</Link>, which
		  you can update. The delivered quantity is expressed in the <Link href="/baanerp/wh/glossary/glossary#000337" role="glossary">inventory unit</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur332.dino">
         <Header>
            <Title>Packing Slip</Title>
         </Header>
         <FuncDesc>The number of the <Link href="/baanerp/wh/glossary/glossary#000359" role="glossary">packing slip</Link>.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>