Some imp points to remember in SAP – SD

1. Shipping point determination: Shipping conditions (sold to party)+Loading grp (mat. Master data)+Plant(from order item)= Shipping point 2.Route determination-automatic Departure Zone of Shipping point + Shipping condition(sold to party) + Transportation Group(material master data) + Transportation Zone/Receiving Zone of Ship to party = Route 3. Storage location or Picking location determination-Automatic Shipping point + plant + Storage condition(material master) = Storage Location Based on MALA Rule 4. Delivering Plant determination – Automatic a) Customer-material info record b) Customer master data c) Material master data 5. Partial delivery determination-automatic a) Customer-material info record. b) Customer master data. Also it can be changed in sales order (only in item data screen-shipping tab) 6. POD status determination-Automatic a. Customer Master data Also this can be changed in sales order (only in item data screen-shipping tab) 7. order combination-determination a. customer master data this can be changed in sales order (only in item data screen-shipping tab) 8. delivery priority-determination a) Customer-material info record b) Customer master data 9. customer master data –central customer data is created in XD01 for sales & distribution –master data is created in VD01. In XD01-customer is created with company code and sales area. In VD01-customer is created with Sales area only. 10. u can create separate master record for a. contact person-t.code-VAP1 b. competitors-t.code-V+23 c. sales partners-t-code-V+23 d. sales prospects-t.code-V+21 Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

11. Billing Blocks are given in Different documents. a. In sales documents types b. In sales document item categories. c. In sales orders-headers data d. In sales orders-item data e. In T-code=VD05 12. delivery blocks are given in different doc. a. In sales document types. b. In schedule line category c. In sales orders-Header data d. In sales order-Item data. 13. Proposing order data from customer master data: a. from Sold to Party • Incoterms • Pricing • Shipping Conditions b. From Bill to Party • Only Billing address c. From Payer • Terms of Payement • Invoice dates. • Relevent for Rebate • Account assignment group ( for Account determination) d. Ship to Party • Ship to Address • Taxes • Goods receiving hrs • Loading point. 14. Material master data is created with the following screens for S&D a. Basic Data 1 b. Sales: Sales org 1 c. Sales: Sales org 2 d. Sales: general/Plant data e. Sales Text. f. Accounting 1 Also the organizational details a. Plant b. Storage location c. Sales org d. Distribution channel 15. The highest organizational structure in Financial accounting is Company Code. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

16. The Highest organizational structure in Sales and Distribution is Sales Organization. 17. The Highest organizational structure in Shipping is Shipping Point. 18. The Highest organizational structure in Production planning is Plant. 19. The Highest organizational structure in Material Management is purchasing organization. 20. The Highest organizational structure in Transportation is Transportation planning point. 21. The Highest organizational structure in Controlling is Controlling Area. 22. A company code can have more than one business area. 23. A business area is defined by a. Sales Area b. Plant/Division 24. A client can have more than one company code. 25. A company code is uniquely assigned to one company code. 26. One business area can be assigned to several company codes. but it should have same descriptions in company codes. 27. Several company codes can be assigned to one company provided it should have a. same fiscal year b. same chart of accounts. But it can have different currencies. 28. A company code can have several sales organization. 29. A sales organization is uniquely assigned to one company code. 30. A distribution channel and division is assigned to sales organization. 31. A sales office is assigned to sales area. 32. when a plant is assigned to sales organization, then this plant becomes a delivering plant. 33. A company code can have several plants. But plant is uniquely assigned to company code. 34. A plant can be assigned to sales organization which belongs to another company code. 35. A text are always stored in objects in documents in R/3 system. Such as Customer master data, material master data, customer-material info record…….etc 36. a customer master data contains Central text, accounting text, sales distribution text and contact person text. 37. Material master data contains sales text and purchase order text. 38. all documents contains text in header and item text. 39. text can be entered in different languages 40. A text can be copied from one master data to another sales document. 41. A text can be copied in the language you require. 42. A standard text can also be copied to sales documents. 43. A text procedure is created for each text object. 44. A text procedure contains all text types. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

45. A text object has to be assigned to one of the defined text procedure. 46. A access sequences contains text object and which Id’s to be copied. 47. U can make text as a obligatory or not. If it is obligatory, then it will get automatically included in incompletion log. 48. Always a text type is created for an text object. 49. you can store specific requirement for each access to restrict the search. a. For certain partner functions. b. For Certain languages c. For any requirements( routines) 50. A text can be referenced or copied. 51. For copying you have to use Routines in access sequence. 52. For reference you can check box in text procedure. 53. while copying changes can be done to the text. 54. If you are using a sales document as reference document and the text in that document should be seen in another document, then this can be done. 55. also any changes made to first document, changes can be seen in another document. 56. all documents will have output types. 57. Output is determined using condition technique. 58. a condition record can also be maintained for output type. 59. output types is assigned to partner functions, transmission media and the time. 60. for every transmission media there is processing program is defined and it is linked to FORM(layouts) for printouts. 61. assignment of different important functionalities. a. Pricing Procedure is assigned to Sales Area + Document pric. Procedure + Customer Pricing Procedure. b. Free Goods procedure is assigned to Sales Area + Document pric. Procedure + Customer Pricing Procedure. c. Listing/Exclusion is assigned to Sales Document types. d. Material Determination is assigned to Sales Document types. e. Output Determination-Sales document header is assigned to Sales Document type. f. Output Determination-Sales document item is assigned to Sales Document-item category. g. Output Determination-Delivery document- header is assigned to Delivery type. h. Output Determination-Delivery document-item is assigned to Delivery Item category. i. Output Determination-Billing document- header is assigned to Billing type. j. Output Determination-Billing document-Item is assigned to Billing type. k. Account determination is assigned to Billing Types.

Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

l. General Ledger Account is assigned to Sales Organization + Chart of accounts + Condition Types + Application + Account keys. m. Partner Determination Procedure for Customer master data is assigned to Customer Account Groups. n. Partner Determination Procedure for Sales document Header is assigned to Sales document types . o. Partner Determination Procedure for Sales Document Item Category is assigned to Sales document item category. p. Partner Determination Procedure for Delivery header is assigned to Delivery Type. q. Partner Determination Procedure for shipment header is assigned to Shipment Type. r. Partner Determination Procedure for Billing Header is assigned to Billing Type. s. Partner Determination Procedure for Billing item is assigned to Billing Type. 62. Incompletion Log procedure is defined for and assigned a. Sales Document Types. b. Sales document-item Category c. Scheduline line category. d. Partner functions. e. Delivery types f. Delivery item. 63. Taxes determination in SAP is defined by a. Departure Country( delivering Plant ) b. Destination Ship to Party. c. Customer Master data Tax Classification. d. Material master data Tax Classification. 64. In Customer Master data tax classification is maintained whether it is liable or not liable for tax. It is not maintained in Currency nor in Percentage. 65. Delivery due list for sales order is maintained by(VL10A) a. by shipping point b. By delivery priority c. Ship to party. d. Route 66. Billing Due List is Maintained by (VF04) a. Billing date b. Sales organization. c. Distribution Channel. d. Division. e. Shipping Point. f. Sold to party. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

67.Several Shipping points can be assigned to a Plant. One Shipping point can be assigned to several plants. 67. Plant can have several Storage Locations and one storage location can be assigned to several plants. 68. Plant and storage location is uniquely assigned to Lean warehouse number. 69. Availability Check is always done at Plant Level. 70. Availability Check is done on material Availability Date. 71. While creating order system does first Backward scheduling, if material is not available on material available date then System goes for Forward Scheduling. 72. Using Standard Analysis and Flexible Analysis we create sales information system. 73. In both the Analysis Characteristic data and Key Figures is the important component. 74. In standard analysis key figures are fixed and characteristic data are Flexible. 75. In Flexible analysis both are fixed but u can permuation and combinations for both of them. 76. condition type refers to characteristic of conditions or represents the properties of the pricing conditions. 77. The pricing procedure contains REQUIREMENTS ROUTINES AND FORMULAE’S which are used to meet user requiorements. 78. Using pricing reports user can analyze what condition records are created for a particular condition types . 79. the pricing reports contains a. Page header b. Group header c. Item 80.Condition records has two maintenance interface. a. VK31 (New) b. VK11 (Old) The new one i.e vk31 allows mass maintainance of records based on characteristic ( customers).that means condition records can be maintained across all condition types and condition tables. 81.we can maintain new tables or combinations for new condition records by using Area menu’s 82.Multiple condition records can be created by copying existing condition records. 83.Text is not copied when you create condition records with reference another record. 84.Text cannot be copied from condition records to sales documents. 85.Scales are always maintained in condition records. 86. Condition supplements are activated in condition types by assigning Condition supplements pricing procedure e.g pr0000,ka0000, k0007 87. Mass change data is allowed in Sales order for following a. Plant b. Reason for Rejection. c. Delivery priority. d. Delivery date. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

e. Delivery block. f. Billing block. 88. Net Price List is Created by Sales Area + customer + Plant + Material + Pricing date + Order Date. 89.Condition indices are mainly used to search condition records which are maintained for Condition types and Condition tables. 90.Condition types is assigned to access sequences ( exceptions are there). 91. Each condition type will tell you how the condition is a. calculated( calculation type) b. whether maintained in item data screen or header data screen of sales order. c. Whether it can be deleted, change the value, change the price. d. What is the scale basis. 92. Condition update is maintained in Condition types. 93. condition updates is checked , an extra fields is created in Condition records. U can use condition updates for giving discounts for first 100 sales orders or first 100 pcs etc. 94.Item Category of an material is defined by Sales document types + Item Category Group(Material Master) = Item Category 95. For text Item the item category is defined by Usage of the material. 96. Item category of the material defines whether it is relevant for billing or not. If revelant whether it is Order related or delivery related. 97. item revelant for delivery in item category is used in case if it is a text or service item. 98. for exploding BOM the structure scope and Application is to be defined in item category. 99. Item category TAD is a service item category. a. the item type is A(Value item) b. Order related Billing. c. Pricing is allowed. d. Business item is allowed. e. Schedule lines are allowed. f. Credit active. g. No Partner determination. 100. Lean Warehouse management is used for Picking the materials. To pick the materials transfer order is created. 101. Lean WM uses Fixed storage bins only. Materials are not stored in Several storage bins. 102.Lean WM is activated by Plant and Storage Location. 103.Packing is a optional Function in Delivery doc. 104.Automatic packing is controlled by Delivery type. 105. Packing function for an item is controlled by Delivery item category. 106. Whether storage location is mandatory is controlled in delivery item category. 107.Whether delivery doc is to be created with reference to sales or not is controlled in delivery doc. 108.output type, partner determination and text controls for delivery doc is controlled in delivery type. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

109.Picking for an material is mandatory or optional is controlled in delivery item category. 110.check for over delivery tolerance, minimum delivery qty and whether material number is zero is allowed is controlled in delivery item category. 111.the effects of Post Goods Issue(PGI) a. It updates the Inventory management. b. An inventory doc is created. c. A financial inventory doc is created. d. Updates in sales orders and delivery doc. e. Updates in controlling doc. f. Appears in Billing due list. 112.The output type for transfer order is WMTA. 113. The output type for Packing is PL00. 114. The output type for Sales Orders is BA00. 115. The output type for Cash sales is RD03. 116. The output type for Delivery Note is LD00. 117. The output type for Billing doc is Rd00. 118.all output type has access seq. 119. condition records can be created for output types. 120.batch management is activated in material master data in Purchasing view or Sales/general plant data. 121. Automatic batch determination is controlled on Sales document item category and delivery item category. 122.Serial numbers are activated in material master data by assigning Serial number Profile in Sales/General plant data screen or Plant data/ storage location 2 screen. 123.handling units are assigned for packaging materials. 124.Return order(RE), Credit memo Request(CR),Debit memo request(DR),Delivery free of charge(FD),quotation(QT) can be created directly without any reference to another document. 125.invoice correction request is always created with reference to Billing doc. 126. Subsequent delivery free of charge is always created with reference to Order(sales or return). 127.Scheduling agreements doc can be processed directly for creating delivery doc. 128. Quantity contracts and value contracts goes thru sales orders. 129.This above doc does not have schedule lines. also not relevant for credit check. 130.Scheduline line Category is defined by Item Category of the material + MRP type of the material = Schedule line category. 131.without MRP type we can define schedule line also. 132.Refence number always appears in header of accounting document. 133. Allocation number always appears in customer line number in accounting document. 134. Reference and Allocation numbers appears in Header of the Billing document in Header tab. 135.For creating invoice list the following things are activated. a. A factoring discounts RL00 and Tax MW15 is assigned in Pricing procedure and also the condition records for both are created. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

b. Factory calendar is assigned in Customer master data in Billing document Tab in invoice list dates field. c. In the billing type Invoice list type has to assigned. d. Output type LR00 should be created. 136. A sales organization can sell products, which belong to plant of another company code. 137. A shipping point can be assigned to plant which belongs to another company code. 138.In billing plan-Periodic Billing plan u have a start date and end date and also Billing date. 139. In billing plan-Milestone Billing plan u have a start date only and Billing date only. 140.Billing plan are assigned to sales document types and item category. 141.In rebate agreements a. The Proposed Valid date from and Proposed valid to is assigned. b. Condition type groups is assigned. c. For settlements, sales document type i.e. credit memo request is assigned. d. Text determination procedure is also assigned. 142. For rebates to be active a. In sales organization rebate relevant should be checked. b. In Billing type rebate relevant should be checked. c. In Payer master data rebate relevant should be checked. 143.If a sales order is generated and also delivery doc. Should be created immediately, activate the immediately delivery field in sales document type. 144. Shipping condition can also be set in sales document type. 145. while creating sales order, system gives top priority for sales document type information. 146.A schedule category is created only for one line item. 147. Shipping point, Plant, Route and Storage location are always seen in item condition screen in sales order. 148. The Pricing procedure in a sales order can be seen in Sales Tab in header screen of sales order. 149.After generating Accounting document only information travels to Controlling areaprofitability analysis. 150.Serial numbers are always assigned in delivery document. 151. Packing proposal can be given in sales order also. 152. In determining delivery item category, the usage is used for only Packing materials, for batch split materials, for product selection and for inbound deliveries. 153. A shipping point can also be set as a GOODS RECIEPT POINT for Inbound Deliveries. 154.A warehouse can have different storage types. 155.Planned goods movement date or Planned GI date is depended on these factors A. Requested delivery date. B. Pick/pack time C. Loading time. D. Transit time. 156.Picking date is determined based on the Material Availability date. on this date the picking activity should start. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

157.Loading date is determined based on Shipping point, loading group and Route. On this date picking and packing should be completed. 158.The Scheduling activity takes into account a. transit time b. loading time c. pick/pack time d. transportation planning time. Transit time and transportation planning time is taken from Route and Loading time and Pick/Pack time is taken from Shipping Point. 159.Transfer order Contains a. Material number b. Quantity to be moved c. Source and Destination bins. 160. Some of the WM functions not included in Lean WM are: a. Storage sections b. Reserve storage bins. c. Strategies for put away and picking d. Replenishment e. Inventory at storage bin level 161. Packing Instructions consists of: a. Packing materials b. Materials to be packed c. Text items d. Subordinate packing instructions e. Rules concerning rounding, minimum quantities, and so on f. Definition of a check profile. 162. Material is assigned to one division only. A material cannot be assigned to several divisions. 163. a material can belong to several distribution channel. 164. Common Distribution Channels – Advantage a. Common Customer Master data b. Common Material Master data c. Common Pricing Condition Master data 165. Common Divisions-Advantage a. Common Customer master data b. Common pricing Condition Master Data. 166. The effects of Post Goods Issue (PGI) a. the stock is reduced from Warehouse b. The value of the stock is reduced and posting is made in Financial Inventory doc. c. The delivery requirements will be changed. d. The information will be updated in Sales order and delivery doc. e. In the Billing due list, the delivery doc is listed. f. Information is updated in SIS. 167. If staging Areas are different in delivery doc, then there is a split in transfer order. 168. The service item Category ( TAD) has these controls. a. It is a value item. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

b. It is relevant for Pricing. c. Not relevant for weight/volume d. Not relevant for cost. 169. Billing plan consists of Date descriptions +Date categories + Date proposals + billing plan rule. 170. Price list field can be seen in customer master data –sales area data screen-sales tab. This field can be seen in sales order doc in header data screen – sales tab and in item data screen sales b tab. 171. Authorization groups can be set for a. Customer master data b. Material master data c. Bill of materials d. Sales doc types. 172. Bill of materials is always exploded in Item categories. 173.Promotion and sales deal doc number will appear in billing document. 174.a contract profile consists of a. start date rule and end date rule of the contract b. validity period c. activities( action and action date rule) d. cancellation procedure. 175.Partner release functions is given in Quantity contract and Value contract. 176.A Partner function is assigned to Partner types. 177.A scheduling agreement has a validity period. 178. it has a target quantity and order quantity. 179.order quantity can be seen in schedule line lines tab in scheduling agreements. 180. A scheduling agreement has a fixed delivery dates and quantity. 181.if a business item is de-checked in item category, then the business data in the header and as well as in the item data in the sales order remains same. if it is checked, then it can be different. 182.list in LIS or SIS means where no activities are done based on that list. For Eg. List of inquires, list of quotation,list of sales orders. 183. a worklist means, based on the list a activity is carried out. For Eg. Delivery due list, Billing due list. 184.in standard analysis , characteristic data is not constant. whereas key figures are constant. 185.In pricing agreements, we have Promotion and Sales Deals. 186. A promotion is like promotional activities e.g summer promotion. Diwali promotion etc. 187.every promotion contains a. Validity dates (from& to) b. Application. c. Agreement category (promotion, sales deal, rebates….) d. Overview screen. e. Text determination procedure. A number ranges can be created for each promotion type. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

188. A sales deal contains a. Validity dates ( from & to) b. Application c. Agreement category. d. Overview screen e. Text determination procedure. f. Release status. g. Different validity period( condition records dates differ from agreement types dates) h. Condition type groups. i. Agreement hierarchy( whether with reference to promotion is mandatory or optional). A sales can have different number ranges. 189. a condition types groups are created and it is linked to condition types for creating condition records. 190. finally condition type groups are assigned to Sales deals. 191. A rebate Agreements type contains a. validity dates. b. Application category. c. Default status. d. Condition types groups. e. Verification levels. f. Different validity period. g. Manually accruals are allowed. h. If allowed, what is the document type. i. Under manual payments, what is the payment procedure. j. Partial settlement document types. k. Final settlement doc type. l. Text determination procedure. 192.All rebates condition types are calculated based on Rebate Basis. 193. Rebate condition should be created separately and separate access sequence should be assigned. 194. while creating rebate access sequence, we have to choose a category called rebates. then this access sequence will be activated for Rebates. 195. The Rebate Basis should be assigned to Sub-Total 7 in pricing procedure. 196.All rebate condition types in the pricing procedure should have Account keys ERB and ERU. 197.A retro active Rebate Agreements means previous months sales volume are taken into consideration. 198.In Rebate agreements the agreements date is changed or we have to run a program called SDBONT06 to update billing documents into Rebate agreements. 198.Prerequisites for Rebate to be active. a. In sales organization the rebate should be set as active. b. In billing types the rebate should be set as active. c. In payer master data the rebate should be set as active. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

199.In rebate agreements type called 0003,0004 and 0005 only customer will be the recipient of rebates. Here materials are not considered. 200.once u create a billing document and a account document is created, the sales volume is updated in rebate agreements. 201. In Taxes we can set a rule whether tax number and tax classification should be taken from sold to party, payer and ship to party. 202.A billing document contains Header and item data screens. 203. The header screen consists of tabs. they are a. header details b. header partner c. conditions d. foreign trade. e. Text. 204. Item screen of billing document consists of Tabs. They are. a. item details. b. Item partner c. Conditions. d. Foreign trade. e. Text and f. P.O. data. 205.Account determination of Sales revenue accounts are determined according to the following criteria. a. Chart of Accounts. b. Sales organization. c. Account assignment group for Payer. d. Account assignment group for Materials. e. Account keys. 206. Installment plans are assigned in customer master data-in payment terms field.(payer master data) or u can change in sales order. System will generate only one billing document.in the invoice it will list of dates and exact amounts to be paid on which dates as per the agreed installment plan. 207.in the accounting document of installment plant, customer account will show the list of installment dates and amounts. but in revenue account it will show only single amount. 208.Down payment are used in projects. The down payment request in SD is automatically posted in Financial accounting as a Down payment request(posted as Noted Item).the item has special General Ledger account. 209.once actual billing starts, u can make partial or full settlement of down payment. 210. Down payment always carried out in billing Plan. 211. The Value of Down payment can be entered as percentage or fixed amount.this control is in customizing screen via the Rule. 212. down payment uses a Billing type called FAZ. 213. A special condition type AZWR is used for Down payment items in slaes documents. 214. In order to activate Invoice List, the following customizing settings has to be made. Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

a. b. c. d. e.

invoice list type has to be assigned to a billing type. A factory calendar has to be assigned to payer master data. Payer has to be same. Output type LR00 has to be assigned to Invoice list type (LR). A factoring tax(RL00) is assigned in pricing procedure, which can be seen in Invoice list.(optional) f. A tax condition type(MW15) is assigned in pricing procedure, which can be seen in the invoice list type.(optional)

Abhishek Parihar SAP SD Certified Consultant E-Mail: abhishekparihar@rediffmail.com

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.