<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000005" xml:lang="en">
   <Header>
      <Title>General sales data</Title>
      <Keyword type="header" order="d1e1331707">
         <Level1>Sales master data</Level1>
         <Level2>general sales data</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1331712">
         <Level1>General sales data</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>Before you can carry out
		the various processes that are related to the sales order functionality, you
		must define general sales master data.</Paragraph>
      <List>
         <ListIntro>The general sales data includes the following:</ListIntro>
         <ListItem>Data to track order changes and to determine the reason for the
		  changes.</ListItem>
         <ListItem>Reasons for order blocking.</ListItem>
         <ListItem>Order priority simulations.</ListItem>
      </List>
   </AimSection>
   <GeneralSection>
      <SectionTitle>To define data to track order changes and to determine the
		reason for the changes</SectionTitle>
      <Keyword type="section" order="d1e1331730">
         <Level1>Change code</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1331733">
         <Level1>Change reason</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1331736">
         <Level1>Change type</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1331739">
         <Level1>Acknowledgement code</Level1>
      </Keyword>
      <Paragraph>Sales orders can be dynamic documents, as a sold-to business
		partner’s requirements can change during the life cycle of the order process.
		In the sales master data, you can define information that enables you to track
		these adjustments and the reasons why these changes were made. Change codes and
		acknowledgement codes are used in LN to track various changes in an order. While
		this functionality was designed to work specifically with EDI, a company
		without EDI functionality can also use these codes for recording
		changes.</Paragraph>
      <Paragraph>You can use change codes to maintain information regarding order
		changes that are tracked for historical purposes. You can use acknowledgement
		codes to manually add change information to the order document, after which
		these changes are communicated to the sold-to business partner by means of a
		sales order acknowledgement.</Paragraph>
      <ProcedureList>
         <ListIntro>To be able to maintain and track changes, take the following
		  steps:</ListIntro>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0197m000" role="session">Change Reasons (tdsls0197m000)</GUIRef> session to maintain codes that represent the change
		  reasons, which can be assigned to a changed order or an order acknowledgement
		  to clarify why a change is made. This information can be tracked for historical
		  reporting.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0198m000" role="session">Change Types (tdsls0198m000)</GUIRef> session to define change types that indicate the kind
		  of change of a changed sales order or order acknowledgement. Possible types of
		  change are, for instance, change order line, add order line, change header
		  data, and so on. The change types are assigned to the sales order after the
		  change is made to the order.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0100s400" role="session">Sales Order Parameters (tdsls0100s400)</GUIRef> session to define various default change
		  codes and change types, which are defaulted to the sales order line in case of
		  changes.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0153m000" role="session">Sales Order - Change Order Sequence Numbers (tdsls0153m000)</GUIRef> session to define
		  optional numbers that are used to assign the occurrence of changes to an order
		  or order acknowledgment. The sequence numbers defined here are used to group an
		  occurrence of changes to an order. This session is usually accessed from the
		  sales order screen, as the actual order number must be specified.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0154m000" role="session">Sales Acknowledgments (tdsls0154m000)</GUIRef> session to define sales order
		  acknowledgements and the destionation of the codes, which can be <GUIRef href="/baanerp/tc/domains/mcs.cdst#header" role="option">Header</GUIRef>, <GUIRef href="/baanerp/tc/domains/mcs.cdst#line" role="option">Line</GUIRef>, or <GUIRef href="/baanerp/tc/domains/mcs.cdst#any" role="option">Any</GUIRef>. The
		  acknowledgement code contains a group of information, which appears on the
		  sales acknowledgment document. This code can represent the reasons for a change
		  of a sales order.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls0155m000" role="session">Sales Acknowledgment Assignments (tdsls0155m000)</GUIRef> session to define the
		  information to be included in the sales order acknowledgment document as
		  indicated by the acknowledgment code. You can assign acknowledgment codes to
		  specific fields on a sales order line, which are the default codes when a
		  change occurs to a specific field. You must also define the action (Add line,
		  Change line) and the source (EDI, Manual, or Any) that result in the
		  acknowledgment code assignment. For example, if you manually add an order line
		  to an existing sales order and the order quantity is changed, LN assigns the specified
		  acknowledgment code to the sales order line.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define reasons for order blocking</SectionTitle>
      <Keyword type="section" order="d1e1331791">
         <Level1>Hold reason</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1331794">
         <Level1>Order blocking</Level1>
      </Keyword>
      <Paragraph>On occasion, it may become necessary to block sales order entry
		for a business partner, or to stop the processing of a business partner’s sales
		order. You can define the conditions for automatically blocking a sales order
		and define hold reasons stating why the order was blocked. This gives you time
		to review the order and to take appropriate action. Many reasons can exist for
		placing a hold on a sold-to business partner’s order. For instance, sold-to
		business partners can have exceeded their credit limit, have overdue invoices,
		or can be disputing an invoice, and so on.</Paragraph>
      <ProcedureList>
         <ListIntro>If you want to use the order blocking functionality, you must
		  define the following master data:</ListIntro>
         <ListItem>To enable blocking review and to take appropriate action, you
		  can use the <GUIRef href="/baanerp/td/sls/tdsls0190m000" role="session">Hold Reasons (tdsls0190m000)</GUIRef> session to define and track this
		  information.</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/td/sls/tdsls0593m000" role="session">Hold Reasons by Business Partner Type (tdsls0593m000)</GUIRef> session, you can specify the
		  action that must be taken when a sales order line is blocked for a particular
		  reason, which depends on the <Link href="/baanerp/tc/glossary/glossary#BusineParTyp_tc" role="glossary">business partner type</Link> and <Link href="/baanerp/td/glossary/glossary#000183" role="glossary">hold reason</Link>.</ListItem>
         <ListItem>In the <GUIRef href="/baanerp/td/sls/tdsls0100s400" role="session">Sales Order Parameters (tdsls0100s400)</GUIRef> session, you define when orders must be
		  blocked automatically. On the <GUIRef href="/baanerp/td/sls/tdsls0100s400#tdsls0100sDF2" role="groupbox">Blocking</GUIRef> tab, you can define standard blocking
		  situations. On the <GUIRef href="/baanerp/td/sls/tdsls0100s400#tdsls0100sDF4" role="groupbox">Reasons</GUIRef> tab, you can attach a reason for a blocking
		  situation.</ListItem>
         <ListItem>Define the step at which the sales order procedure is
		  interrupted automatically in the <GUIRef href="/baanerp/td/sls/tdsls0694m000#tdsls094.blcs" role="manual">Block As of Activity</GUIRef> field of the <GUIRef href="/baanerp/td/sls/tdsls0694m000" role="session">Sales Order Type - Activities (tdsls0694m000)</GUIRef> session. When an order (line) is blocked,
		  the procedure for this order can only be partially carried out. If a blocking
		  step is not defined in this session, the order procedure is not interrupted.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define order priority simulations</SectionTitle>
      <Keyword type="section" order="d1e1331840">
         <Level1>Order priority simulation</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1331843">
         <Level1>Priority simulation</Level1>
      </Keyword>
      <ProcedureList>
         <ListIntro>If you want to use <Link href="/baanerp/td/glossary/glossary#OrderPrioriS_td" role="glossary">order priority simulations</Link>, you must
		  define the following master data:</ListIntro>
         <ListItem>Set the method that is used to determine the order priority to <GUIRef href="/baanerp/td/domains/sls.opri#simulation.code" role="option">Simulation</GUIRef> in the <GUIRef href="/baanerp/td/sls/tdsls0100s400#tdsls000.opri.4" role="manual">Order Priority Method</GUIRef> field of the <GUIRef href="/baanerp/td/sls/tdsls0100s400" role="session">Sales Order Parameters (tdsls0100s400)</GUIRef> session. As a result, the order priority is
		  calculated based on the values of the fields defined in the simulation code.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/sls/tdsls4524m000" role="session">Priority Simulations (tdsls4524m000)</GUIRef> session to define the codes that are used
		  to create priority simulations. A priority simulation consists of an
		  identifying code and description, a sort sequence and a sort mode. The sort
		  sequence and the sort mode are criteria by which sales orders are sorted. The
		  way the orders are sorted determines the priority. To create a simulation, the
		  sorting criteria defined in the simulation code are applied for a group of
		  sales orders selected by the user. You can select six fields for each
		  simulation code to sort sales orders. LN takes the default fields from the sales
		  order lines table, but you can also use fields from sales orders and business
		  partners.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000062" role="manual">Overview of sales order handling</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/sls09410" role="manual">Order blocking</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000058" role="manual">Priority Simulations</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000002" role="manual">Sales item data</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000004" role="manual">Sales organizational data</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>