<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Sales Document in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sales-document/m-p/2127791#M446894</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any one can explain me the Fallowing Terms in Table VBBE( Sales Requirements)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business item number&lt;/P&gt;&lt;P&gt;BOM explosion number&lt;/P&gt;&lt;P&gt;Sales Document&lt;/P&gt;&lt;P&gt;Planning Indicator&lt;/P&gt;&lt;P&gt;Schedule line&lt;/P&gt;&lt;P&gt;WBS Element&lt;/P&gt;&lt;P&gt;Sold-to party&lt;/P&gt;&lt;P&gt;Sales Document Item&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I con't understand this terminology. any one please Explain some Frequently used terms in SD like sales order, Purchase order who places it How it Moves Between Different Departments. what we call it at difference levels Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;kiran.B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Apr 2007 10:25:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-04T10:25:13Z</dc:date>
    <item>
      <title>Sales Document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sales-document/m-p/2127791#M446894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any one can explain me the Fallowing Terms in Table VBBE( Sales Requirements)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business item number&lt;/P&gt;&lt;P&gt;BOM explosion number&lt;/P&gt;&lt;P&gt;Sales Document&lt;/P&gt;&lt;P&gt;Planning Indicator&lt;/P&gt;&lt;P&gt;Schedule line&lt;/P&gt;&lt;P&gt;WBS Element&lt;/P&gt;&lt;P&gt;Sold-to party&lt;/P&gt;&lt;P&gt;Sales Document Item&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I con't understand this terminology. any one please Explain some Frequently used terms in SD like sales order, Purchase order who places it How it Moves Between Different Departments. what we call it at difference levels Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;kiran.B&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 10:25:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sales-document/m-p/2127791#M446894</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T10:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: Sales Document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sales-document/m-p/2127792#M446895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hai,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Understandable terms by you might be:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Business item number :&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;    Sales Document Item(POSNR)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;BOM explosion number :&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Number used by the component supplier to identify the production series from which the customer releases and receives materials.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Sales Document:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The number that uniquely identifies the sales document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use&lt;/P&gt;&lt;P&gt;If, for example, you want to display or change a sales document and you have only the purchase order number from the customer, you can use a matchcode to find the document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;You created a sales order which refers to customer purchase order number 12544-D. To locate the sales order, you can enter =a.12544-D in the sales document field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The document number can be proposed from a user parameter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following parameters are available for the individual document types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AFN - Inquiry number&lt;/P&gt;&lt;P&gt;AGN - Quotation number&lt;/P&gt;&lt;P&gt;AUN - Order number&lt;/P&gt;&lt;P&gt;LPN - Scheduling agreement number&lt;/P&gt;&lt;P&gt;KTN - Contract number&lt;/P&gt;&lt;P&gt;AMN - Assortment number&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Planning Indicator :&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The planning indicator determines which of the following is valid for the planned independent requirement:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;net requirements planning&lt;/P&gt;&lt;P&gt;gross requirements planning&lt;/P&gt;&lt;P&gt;individual requirements planning, or&lt;/P&gt;&lt;P&gt;external requirements planning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Schedule line:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The number that uniquely identifies the schedule line in the sales document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use&lt;/P&gt;&lt;P&gt;When an item has more than one schedule line, the system automatically assigns a unique number to each line. The number is displayed in the details screens for schedule lines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note&lt;/P&gt;&lt;P&gt;The schedule line number serves internal purposes and does not, for example, determine the sequence of schedule lines in the overview screen. The schedule lines on the overview screen are sorted by date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;WBS Element&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Key that identifies a WBS element.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Sold-to party:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Sales Document Item&amp;lt;/b&amp;gt;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The number that uniquely identifies the item in the sales document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope you got some help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward points if it helps you.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regds,&lt;/P&gt;&lt;P&gt;Rama.Pammi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2007 11:20:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sales-document/m-p/2127792#M446895</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-04T11:20:06Z</dc:date>
    </item>
  </channel>
</rss>

