<?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 Re: so in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959639#M698218</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PLease go through the doccument&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SALES DOCUMENTS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sales related business transactions are recorded in the system as sales documents. These are grouped in to 4 categories:&lt;/P&gt;&lt;P&gt;Pre-sales document: Inquires &amp;amp; Quotations.&lt;/P&gt;&lt;P&gt;Sales Orders: OR/ RO/ CS.&lt;/P&gt;&lt;P&gt;Outline Agreements- Contracts &amp;amp; Scheduling Agreements.&lt;/P&gt;&lt;P&gt;Customer Complaints- Free of Charge Delivery (CD), Free of Charge Subsequent Delivery (SDF), Credit Memo (G2), Debit Memo (L2), Returns (RE).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DOCUMENT FLOW OR SALES ORDER CYCLE:&lt;/P&gt;&lt;P&gt;Sales Order Cycle starts with:&lt;/P&gt;&lt;P&gt;Inquiry- Quotation- Sales Order- Delivery- Invoice- Debit or Credit memo followed by SDF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STRUCTURE OF SALES DOCUMENT:&lt;/P&gt;&lt;P&gt;Header Data:(VBAK): no of the sold to party, no of the ship to party &amp;amp; payer, document currency &amp;amp; exchange rate, pricing elements for the entire document, delivery date and shipping point.&lt;/P&gt;&lt;P&gt;Item Data:(VBAP): material no, order qty, no of the ship to party &amp;amp; payer (an alternative ship to party or payer can be defined for a particular item), plant &amp;amp; storage location specifications and pricing elements for the individual item. This is controlled by sales item category, such as TAN.&lt;/P&gt;&lt;P&gt;Schedule Line Data:(VBEP): is responsible for delivery dates &amp;amp; delivery quantities. (It includes: schedule line qty, delivery date &amp;amp; confirmed qty). This is controlled by schedule line category, such as CP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FUNCTIONS OF SALES DOCUMENT:&lt;/P&gt;&lt;P&gt;Availability check&lt;/P&gt;&lt;P&gt;Delivery scheduling&lt;/P&gt;&lt;P&gt;Transfer of Requirements: to mat planning i.e. MRP&lt;/P&gt;&lt;P&gt;Calculating pricing and taxes&lt;/P&gt;&lt;P&gt;Checking credit limits&lt;/P&gt;&lt;P&gt;Output&lt;/P&gt;&lt;P&gt;Text&lt;/P&gt;&lt;P&gt;Sales information system.&lt;/P&gt;&lt;P&gt;INQUIRIES: A customer&amp;#146;s request to a company that they provide a quotation or sales information without obligation. Doc Type: IN, Trans Code to Create inquiry: VA11. The standard item category for inquiry is AFN.&lt;/P&gt;&lt;P&gt;QUOTATION: A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. Doc Type: QT, Trans Code to Create Quotation: VA21. The standard item category used in quotation is AGN.&lt;/P&gt;&lt;P&gt;SCHEDULING AGREEMENTS: A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. Trans Code: VA31. Doc Types: DS- Scheduling Agreements, COB- Sch Agreements BR, BL- Sch Agreement w/del schedule&lt;/P&gt;&lt;P&gt;TYPES OF SALES DOCUMENTS: VOV8&lt;/P&gt;&lt;P&gt;OR Standard order RO Rush order&lt;/P&gt;&lt;P&gt;CS Cash sales IN Inquiry&lt;/P&gt;&lt;P&gt;QT Quotation DS Scheduling agreements&lt;/P&gt;&lt;P&gt;B1 Rebate credit memo request B2 Rebate correction request&lt;/P&gt;&lt;P&gt;CD Free of charge delivery SDF Subsequent free of charge del&lt;/P&gt;&lt;P&gt;CF Consignment fill up CI Consignment issue&lt;/P&gt;&lt;P&gt;CR Consignment return CP Consignment pick up&lt;/P&gt;&lt;P&gt;VOV8 DETAILS:&lt;/P&gt;&lt;P&gt;Item No. Increment: how line item&amp;#146;s no should increase in documents.&lt;/P&gt;&lt;P&gt;Check Division: how system reacts when div at item &amp;amp; header level differ.&lt;/P&gt;&lt;P&gt;Probability: IN: 30%, QT: 70% and Order: 100%&lt;/P&gt;&lt;P&gt;Check Credit Limit: how system should respond to check during order processing&lt;/P&gt;&lt;P&gt;Item Division: check this field and at item level div is proposed from MMR.&lt;/P&gt;&lt;P&gt;Read Info Record&lt;/P&gt;&lt;P&gt;DoPP: the key that specifies the pricing proc for this type of sales doc.&lt;/P&gt;&lt;P&gt;Display Criteria: should system display only main or sub items or all items in sales doc&lt;/P&gt;&lt;P&gt;F.Code Overview Screen: after you enter the data in the initial sales doc screen, which overview screen the customer wants.&lt;/P&gt;&lt;P&gt;Quotation Messages:&lt;/P&gt;&lt;P&gt;Incompletion Message: check this field &amp;amp; u can&amp;#146;t save an incomplete doc.&lt;/P&gt;&lt;P&gt;Delivery Type: LF for OR and RO. BV for CS&lt;/P&gt;&lt;P&gt;Delivery Block&lt;/P&gt;&lt;P&gt;Shipping Conditions: specify a value here and the value in CMD is not taken.&lt;/P&gt;&lt;P&gt;Delivery Related Billing Type &amp;amp; Order Related Billing Type&lt;/P&gt;&lt;P&gt;Billing Block&lt;/P&gt;&lt;P&gt;Propose Del Date: Indicates whether the system automatically proposes the current date as the delivery date.&lt;/P&gt;&lt;P&gt;Lead Time In Days: specify the number of days after the current date that the proposal for the requested delivery date in the sales doc should be.&lt;/P&gt;&lt;P&gt;Immediate Delivery.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Oct 2007 05:05:23 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-19T05:05:23Z</dc:date>
    <item>
      <title>so</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959638#M698217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create sales order, can any body send me the screen shots pls.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Oct 2007 05:03:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959638#M698217</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-19T05:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: so</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959639#M698218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi.,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PLease go through the doccument&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SALES DOCUMENTS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sales related business transactions are recorded in the system as sales documents. These are grouped in to 4 categories:&lt;/P&gt;&lt;P&gt;Pre-sales document: Inquires &amp;amp; Quotations.&lt;/P&gt;&lt;P&gt;Sales Orders: OR/ RO/ CS.&lt;/P&gt;&lt;P&gt;Outline Agreements- Contracts &amp;amp; Scheduling Agreements.&lt;/P&gt;&lt;P&gt;Customer Complaints- Free of Charge Delivery (CD), Free of Charge Subsequent Delivery (SDF), Credit Memo (G2), Debit Memo (L2), Returns (RE).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DOCUMENT FLOW OR SALES ORDER CYCLE:&lt;/P&gt;&lt;P&gt;Sales Order Cycle starts with:&lt;/P&gt;&lt;P&gt;Inquiry- Quotation- Sales Order- Delivery- Invoice- Debit or Credit memo followed by SDF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STRUCTURE OF SALES DOCUMENT:&lt;/P&gt;&lt;P&gt;Header Data:(VBAK): no of the sold to party, no of the ship to party &amp;amp; payer, document currency &amp;amp; exchange rate, pricing elements for the entire document, delivery date and shipping point.&lt;/P&gt;&lt;P&gt;Item Data:(VBAP): material no, order qty, no of the ship to party &amp;amp; payer (an alternative ship to party or payer can be defined for a particular item), plant &amp;amp; storage location specifications and pricing elements for the individual item. This is controlled by sales item category, such as TAN.&lt;/P&gt;&lt;P&gt;Schedule Line Data:(VBEP): is responsible for delivery dates &amp;amp; delivery quantities. (It includes: schedule line qty, delivery date &amp;amp; confirmed qty). This is controlled by schedule line category, such as CP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FUNCTIONS OF SALES DOCUMENT:&lt;/P&gt;&lt;P&gt;Availability check&lt;/P&gt;&lt;P&gt;Delivery scheduling&lt;/P&gt;&lt;P&gt;Transfer of Requirements: to mat planning i.e. MRP&lt;/P&gt;&lt;P&gt;Calculating pricing and taxes&lt;/P&gt;&lt;P&gt;Checking credit limits&lt;/P&gt;&lt;P&gt;Output&lt;/P&gt;&lt;P&gt;Text&lt;/P&gt;&lt;P&gt;Sales information system.&lt;/P&gt;&lt;P&gt;INQUIRIES: A customer&amp;#146;s request to a company that they provide a quotation or sales information without obligation. Doc Type: IN, Trans Code to Create inquiry: VA11. The standard item category for inquiry is AFN.&lt;/P&gt;&lt;P&gt;QUOTATION: A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. Doc Type: QT, Trans Code to Create Quotation: VA21. The standard item category used in quotation is AGN.&lt;/P&gt;&lt;P&gt;SCHEDULING AGREEMENTS: A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. Trans Code: VA31. Doc Types: DS- Scheduling Agreements, COB- Sch Agreements BR, BL- Sch Agreement w/del schedule&lt;/P&gt;&lt;P&gt;TYPES OF SALES DOCUMENTS: VOV8&lt;/P&gt;&lt;P&gt;OR Standard order RO Rush order&lt;/P&gt;&lt;P&gt;CS Cash sales IN Inquiry&lt;/P&gt;&lt;P&gt;QT Quotation DS Scheduling agreements&lt;/P&gt;&lt;P&gt;B1 Rebate credit memo request B2 Rebate correction request&lt;/P&gt;&lt;P&gt;CD Free of charge delivery SDF Subsequent free of charge del&lt;/P&gt;&lt;P&gt;CF Consignment fill up CI Consignment issue&lt;/P&gt;&lt;P&gt;CR Consignment return CP Consignment pick up&lt;/P&gt;&lt;P&gt;VOV8 DETAILS:&lt;/P&gt;&lt;P&gt;Item No. Increment: how line item&amp;#146;s no should increase in documents.&lt;/P&gt;&lt;P&gt;Check Division: how system reacts when div at item &amp;amp; header level differ.&lt;/P&gt;&lt;P&gt;Probability: IN: 30%, QT: 70% and Order: 100%&lt;/P&gt;&lt;P&gt;Check Credit Limit: how system should respond to check during order processing&lt;/P&gt;&lt;P&gt;Item Division: check this field and at item level div is proposed from MMR.&lt;/P&gt;&lt;P&gt;Read Info Record&lt;/P&gt;&lt;P&gt;DoPP: the key that specifies the pricing proc for this type of sales doc.&lt;/P&gt;&lt;P&gt;Display Criteria: should system display only main or sub items or all items in sales doc&lt;/P&gt;&lt;P&gt;F.Code Overview Screen: after you enter the data in the initial sales doc screen, which overview screen the customer wants.&lt;/P&gt;&lt;P&gt;Quotation Messages:&lt;/P&gt;&lt;P&gt;Incompletion Message: check this field &amp;amp; u can&amp;#146;t save an incomplete doc.&lt;/P&gt;&lt;P&gt;Delivery Type: LF for OR and RO. BV for CS&lt;/P&gt;&lt;P&gt;Delivery Block&lt;/P&gt;&lt;P&gt;Shipping Conditions: specify a value here and the value in CMD is not taken.&lt;/P&gt;&lt;P&gt;Delivery Related Billing Type &amp;amp; Order Related Billing Type&lt;/P&gt;&lt;P&gt;Billing Block&lt;/P&gt;&lt;P&gt;Propose Del Date: Indicates whether the system automatically proposes the current date as the delivery date.&lt;/P&gt;&lt;P&gt;Lead Time In Days: specify the number of days after the current date that the proposal for the requested delivery date in the sales doc should be.&lt;/P&gt;&lt;P&gt;Immediate Delivery.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Oct 2007 05:05:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959639#M698218</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-19T05:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: so</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959640#M698219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;goto VA01 Tcode&lt;/P&gt;&lt;P&gt;enter Order type, sales orgn dis channel etc&lt;/P&gt;&lt;P&gt;enter SOLD to and SHiptot party, ref Po no and date on header and at item level enter Materilano, qty, unit, plant etc and enter some other fields which it asks then save&lt;/P&gt;&lt;P&gt;better take the sample data from the existing database tables VBAK and VBAP and create&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Oct 2007 05:06:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/so/m-p/2959640#M698219</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-19T05:06:20Z</dc:date>
    </item>
  </channel>
</rss>

