<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ec/onlinemanual/000076" xml:lang="en">
   <Header>
      <Title>EDI business document Schedule</Title>
      <Keyword type="header" order="d1e306856">
         <Level1>EDI business document</Level1>
         <Level2>schedule</Level2>
      </Keyword>
      <Keyword type="header" order="d1e306861">
         <Level1>Schedule</Level1>
         <Level2>EDI business document</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>The business document Schedule describes the processing of EDI
		messages that are used in a supply chain environment, which makes use of <Link href="/baanerp/td/glossary/glossary#000000000000011" role="glossary"
               Update="No">purchase schedules</Link> to
		communicate requirements to the selling company.</Paragraph>
      <Paragraph>Purchase schedules represent a timetable of planned
		requirements, and support long-term purchasing practices that have frequent
		deliveries. Purchase schedules are used in place of standard purchase orders
		when a more detailed way of specifying delivery dates/times for material
		requirements is needed. Purchase schedules are unique for an item and are sent
		to the purchase business partner in a <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link>.</Paragraph>
      <GeneralSection ID="pur_schedules">
         <SectionTitle>Purchase schedules</SectionTitle>
         <List>
            <ListIntro>LN supports the following types of purchase schedules:</ListIntro>
            <ListItemHead>Push schedules</ListItemHead>
            <ListItem>A push schedule is a list of time-phased requirements,
			 generated by a central planning system, such as LN <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> or LN <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> that are sent to the
			 purchase business partner. Push schedules contain both a forecast for the
			 longer term and actual orders for the short term. A push schedule is also
			 called a <Link href="/baanerp/td/glossary/glossary#000338" role="glossary">non-referenced schedule</Link>. A non-referenced schedule is a
			 schedule that contains lines without a reference number. Because no specific
			 requirement exists for the schedule line, non-referenced schedule lines can
			 first be clustered (grouped to send the lines in one purchase release) and then
			 ordered, shipped, and received together.</ListItem>
            <ListItemHead>Pull forecast schedules</ListItemHead>
            <ListItem>A pull forecast schedule is a list of time-phased planned
			 requirements, generated by LN <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, that are sent to the purchase business partner. Pull
			 forecast schedules are only used for forecasting purposes. To actually order
			 the items, a pull call-off schedule must be generated with the same schedule
			 number as the pull forecast schedule. Like a push schedule, a pull forecast
			 schedule is also a <Emphasis>non-referenced schedule</Emphasis>.</ListItem>
            <ListItemHead>Pull call-off schedules</ListItemHead>
            <ListItem>A pull call-off schedule is a list of time-phased specific
			 requirements of purchased items, triggered from <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>, <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef>, or LN <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> ( <Link href="/baanerp/wh/glossary/glossary#000400" role="glossary">Kanban</Link>, <Link href="/baanerp/wh/glossary/glossary#000424" role="glossary">time-phased order point</Link>). A pull call-off schedule is a <Link href="/baanerp/td/glossary/glossary#000339" role="glossary">referenced schedule</Link>. A referenced schedule contains lines
			 with reference numbers. When goods are shipped, received, and invoiced, the
			 reference numbers are used to communicate with suppliers and other LN packages. Because a
			 specific requirement exists for the schedule line, each single schedule line is
			 ordered, shipped, and received separately.</ListItem>
         </List>
      </GeneralSection>
      <GeneralSection ID="pur_releases">
         <SectionTitle>Purchase releases</SectionTitle>
         <Keyword type="section" order="d1e306932">
            <Level1>EDI messages</Level1>
            <Level2>MRL</Level2>
         </Keyword>
         <Keyword type="section" order="d1e306937">
            <Level1>EDI messages</Level1>
            <Level2>SHP</Level2>
         </Keyword>
         <Keyword type="section" order="d1e306942">
            <Level1>EDI messages</Level1>
            <Level2>SEQ</Level2>
         </Keyword>
         <List>
            <ListIntro>The purchase schedule can be sent by means of the following
			 purchase releases:</ListIntro>
            <ListItemHead>Material release</ListItemHead>
            <ListItem>A schedule on which forecast information is provided about
			 shipping times, delivery times, and quantities. In general, a material release
			 can be considered as a planning release. For push schedules, however, the
			 material release can also contain the actual order. In this case the release is
			 called a material release with shipping capabilities. A material release can
			 contain push schedules or pull forecast schedules.</ListItem>
            <ListItemHead>Shipping schedule</ListItemHead>
            <ListItem>A schedule on which detailed information is given about
			 shipping times or delivery times and quantities. A shipping schedule
			 facilitates just-in-time (JIT) management. A shipping schedule can contain push
			 schedules or pull call-off schedules.</ListItem>
            <ListItemHead>Sequence shipping schedule</ListItemHead>
            <ListItem>A supplement to the material release or the shipping schedule
			 with precise information about the production or deliveries of the
			 requirements. This schedule can include the production or delivery sequence,
			 and the order, the place, and the time of unloading after shipment. A sequence
			 shipping schedule can only contain pull call-of schedules.</ListItem>
         </List>
         <List>
            <ListIntro>As a result, the business document schedule includes the
			 following EDI messages:</ListIntro>
            <ListItemHead>MRL</ListItemHead>
            <ListItem>Material Release</ListItem>
            <ListItemHead>SHP</ListItemHead>
            <ListItem>Shipping Schedule</ListItem>
            <ListItemHead>SEQ</ListItemHead>
            <ListItem>Sequence Shipping Schedule</ListItem>
         </List>
         <Paragraph>
            <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="274" width="463"
                      SRC="../images/business_document_schedule.gif"
                      alt="[...]"/>
         </Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>EDI messages and purchase schedules</SectionTitle>
      <Paragraph>For information about <Link href="/baanerp/td/glossary/glossary#000000000000010" role="glossary">release types</Link>, <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement types</Link> and
		corresponding EDI messages, refer to <Link href="/baanerp/td/onlinemanual/000346" role="manual">Purchase schedule release types</Link>.</Paragraph>
      <GeneralSection>
         <SectionTitle>To prepare EDI messages for push schedules in a purchase
		  release</SectionTitle>
         <ProcedureList>
            <ListIntro>Complete the following steps to prepare EDI messages for
			 push schedules in a purchase release:</ListIntro>
            <ListItem>Create a purchase schedule header in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session and purchase schedule lines in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session.</ListItem>
            <ListItem>Create a purchase release line in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session.</ListItem>
            <ListItem>Approve the purchase release line in the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session.</ListItem>
            <ListItem>Print the purchase release in the <GUIRef href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</GUIRef> session with the <GUIRef href="/baanerp/td/pur/tdpur3422m000#final.report" role="manual">Final Report</GUIRef> and the <GUIRef href="/baanerp/td/pur/tdpur3422m000#prepare.send.edi" role="manual">Prepare EDI messages</GUIRef> check boxes selected.</ListItem>
         </ProcedureList>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>To prepare EDI messages for pull forecast
		  schedules</SectionTitle>
         <ProcedureList>
            <ListIntro>A pull forecast schedule can only be generated from the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> and
			 cannot be created manually. Based on the parameters and triggers, the following
			 steps are carried out automatically to prepare EDI messages for pull forecast
			 schedules in a purchase release:</ListIntro>
            <ListItem>A purchase schedule header is generated in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session and purchase schedule lines are generated in
			 the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session.</ListItem>
            <ListItem>A purchase release is generated in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session.</ListItem>
            <ListItem>The purchase release is approved in the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session.</ListItem>
            <ListItem>The purchase release is printed in the <GUIRef href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</GUIRef> session.</ListItem>
         </ProcedureList>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>To prepare EDI messages for pull call-off
		  schedules</SectionTitle>
         <ProcedureList>
            <ListIntro>A pull call-off schedule can only be generated from <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> by means
			 of the <GUIRef href="/baanerp/ti/asc/tiasc8220m000" role="session">Transfer Assembly Part Supply Messages (tiasc8220m000)</GUIRef> session, or from <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> by
			 means of the <GUIRef href="/baanerp/wh/inh/whinh2200m000" role="session">Generate Orders (KANBAN) (whinh2200m000)</GUIRef> and the <GUIRef href="/baanerp/wh/inh/whinh2201m000" role="session">Generate Orders (TPOP) (whinh2201m000)</GUIRef> sessions. A pull call-off schedule cannot be
			 created manually. Based on the parameters and triggers, the following steps are
			 carried out automatically to prepare EDI messages for pull call-off schedules
			 in a purchase release:</ListIntro>
            <ListItem>A purchase schedule (header) is generated in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session. If the pull call-off schedule is preceded by
			 a pull forecast schedule, LN searches for the corresponding pull forecast schedule in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session. Once found, LN creates a pull
			 call-off schedule with the same schedule number as the pull forecast schedule.
			 In this way, forecasting data and ordering data are separated. If no
			 forecasting data is generated, the pull call-off schedule, as generated in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session, has no corresponding pull forecast schedule.</ListItem>
            <ListItem>Schedule lines are generated in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session. If the release type that is linked to
			 the pull call-off schedule is <GUIRef href="/baanerp/tc/domains/scrd#sequence" role="option">Sequence Shipping Schedule</GUIRef>, a schedule line for each <Link href="/baanerp/td/glossary/glossary#000199" role="glossary">call-off</Link> is generated in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session, but the sequence details for a
			 particular call off, such as VIN number, line station, and so on are stored in
			 the <GUIRef href="/baanerp/td/pur/tdpur3517m000" role="session">Sequence Shipping data (tdpur3517m000)</GUIRef> session.</ListItem>
            <ListItem>A purchase release is generated with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session. With every generation of a schedule line, LN generates a release
			 line detail record in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session. This record has a one-to-one
			 relationship with the schedule line. <List>
                  <ListIntro>If the schedule is a <Link href="/baanerp/td/glossary/glossary#000034" role="glossary">sequence shipping schedule</Link>, however, the following applies:</ListIntro>
                  <ListItem>Only a purchase release header is created. No purchase
				  release lines and purchase release line detail records are created. The reason
				  for this is that items in a sequence shipping schedule are required for a
				  combination of vehicle number (VIN), line station, and assembly kit. For this
				  reason, a link exists between the release header in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session and the release lines in the <GUIRef href="/baanerp/td/pur/tdpur3523m000" role="session">Purchase Release Lines - Sequence Shipping Data (tdpur3523m000)</GUIRef> session.</ListItem>
                  <ListItem>Dependent on the setting of the <GUIRef href="/baanerp/td/pur/tdpur3120m000#tdpur320.mesv" role="manual">Generate Release per Vehicle</GUIRef> check box in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session, the release is either created per item or per
				  vehicle.</ListItem>
               </List>
            </ListItem>
            <ListItem>The purchase release is printed in the <GUIRef href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</GUIRef> session.</ListItem>
         </ProcedureList>
      </GeneralSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>If the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.demr" role="manual">Release EDI Message Directly</GUIRef> check box is selected in
			 the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and/or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session, LN automatically
			 prepares the EDI messages when a purchase release receives the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session.</ListItem>
            <ListItem>Use the <GUIRef href="/baanerp/ec/edi/ecedi7205m000" role="session">Direct Network Communication (ecedi7205m000)</GUIRef> session to generate the outgoing
			 message. A report will list the messages that were generated. The outgoing
			 messages for an external EDI business partner are stored in the appl_from
			 directory for retrieval by translation software.</ListItem>
         </List>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To process EDI messages</SectionTitle>
      <Keyword type="section" order="d1e307180">
         <Level1>EDI messages</Level1>
         <Level2>process</Level2>
      </Keyword>
      <Paragraph>You can use the <GUIRef href="/baanerp/ec/edi/ecedi7205m000" role="session">Direct Network Communication (ecedi7205m000)</GUIRef> session to receive the customer’s new
		release or to update an existing release.</Paragraph>
      <Paragraph>When you receive a new Material Release (MRL), Shipping Schedule
		(SHP), or Sequence Shipping Schedule (SEQ), a sales release and corresponding
		schedule(s) are created in the Sales Order Control module. Depending on the
		release type, an update to an existing sales release results in a new revision
		for the sales release and the corresponding schedule(s), or in updated sales
		release/sales schedule(s).</Paragraph>
      <List>
         <ListIntro>As a result, the following information is automatically
		  entered in LN when EDI
		  messages are processed:</ListIntro>
         <ListItem>A <Link href="/baanerp/td/glossary/glossary#000169" role="glossary">sales release</Link> with revision
		  number one in the <GUIRef href="/baanerp/td/sls/tdsls3512m000" role="session">Sales Releases (tdsls3512m000)</GUIRef> session. If a new EDI
		  message is received for an existing sales release, a sales release revision is
		  created with revision number two, and so on.</ListItem>
         <ListItem>Sales release lines in the <GUIRef href="/baanerp/td/sls/tdsls3508m000" role="session">Sales Release Lines (tdsls3508m000)</GUIRef> session.</ListItem>
         <ListItem>Sales release postition details in the <GUIRef href="/baanerp/td/sls/tdsls3515m000" role="session">Sales Release Line Details (tdsls3515m000)</GUIRef> session, for referenced schedules of
		  the <GUIRef href="/baanerp/td/domains/sls.reltype#shipschedule" role="option">Shipping Schedule</GUIRef> type. If you receive an update of a
		  referenced shipping schedule, LN does not create a new sales schedule revision number. Instead,
		  the sales schedule is updated. If an update arrives for a sales schedule line,
		  also the sales schedule line is updated. To keep track of the updates, LN files the sales
		  schedule line updates as revisions in the <GUIRef href="/baanerp/td/sls/tdsls3515m000" role="session">Sales Release Line Details (tdsls3515m000)</GUIRef> session. As a result, a sales release
		  position detail refers to a sales schedule line.</ListItem>
         <ListItem>A <Link href="/baanerp/td/glossary/glossary#SalesSchedu_td" role="glossary">sales schedule</Link> with <Link href="/baanerp/td/glossary/glossary#000357" role="glossary">sales schedule revision number</Link> one in the <GUIRef href="/baanerp/td/sls/tdsls3111m000" role="session">Sales Schedules (tdsls3111m000)</GUIRef> session. If new requirements are received for an
		  existing sales schedule, a sales schedule revision is created with revision
		  number two, and so on. The previous sales schedule revision and its
		  requirements are no longer valid if the new sales schedule revision is
		  approved.</ListItem>
         <ListItem>Sales schedule lines in the <GUIRef href="/baanerp/td/sls/tdsls3107m000" role="session">Sales Schedule Lines (tdsls3107m000)</GUIRef> session.</ListItem>
         <ListItem>Sequence shipping information in the <GUIRef href="/baanerp/wh/inh/whinh4520m000" role="session">Shipping Sequence (whinh4520m000)</GUIRef> session, and shipping sequence detail revisions in the <GUIRef href="/baanerp/td/sls/tdsls3517m000" role="session">Sequence Shipping Information (tdsls3517m000)</GUIRef> session, provided the schedule is
		  referenced and of the <GUIRef href="/baanerp/td/domains/sls.reltype#seqschedule" role="option">Sequence Shipping Schedule</GUIRef> type.</ListItem>
      </List>
      <Paragraph>As with all incoming EDI messages, the <Emphasis>Remarks in
		Copied Messages</Emphasis> report is generated. The report displays the sales
		release number and corresponding lines added along with related
		remarks.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ec/onlinemanual/000074" role="manual">An overview of EDI business documents</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000347" role="manual">Push schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000348" role="manual">Pull forecast schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000349" role="manual">Pull call-off schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000350" role="manual">Purchase releases</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000130" role="manual">Sales schedule procedure</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ec/onlinemanual/000071" role="manual">An overview of BEMIS</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>