SAP SD Interview Questions

Following are some SD Interview questions that might be asked. 1. What is the purpose of text determination, account determination, partner determination, output determination, storage location determination? Text determination: For transferring information from material or customer to order/delivery or invoice (and anything in between) Account determination: For transferring financial and costing information to proper financial docs Partner determination: For determining who is is legally responsible for A/r, who the goods are going to and whatever else you waana drive through this functionality. Output determination: What kind a output does a sales/delivery/billing document create and who gets it, where?. For example A partner might get an EDI notification for a sales order just confirmed, whereas a financial/leasing company gets the invoice! 2. What are the five imp fields to be maintained in account determination (2) Account Determination: Sales View, Sales Organization, Distribution Chanel, Chart of Accounts, Account Assignment Group for Customer and Material and Account Keys. 3. How to create excise invoice and what is it As per Indian tax system, Excise duty (16%) is payable by each manufacturing unit on the value of manufactured goods / on the value added. The manufacturing plant is supposed to submit an excise duty report on fortnightly / monthly basis. Various registers (RG1, RG23A, RG23C, PLA) are maintained for that purpose, which record all the transactions including movement of goods, cenvat credit available and cash balance available. In SAP, we use transaction j1id for configuration and j1iin, j2i7, j1i5, j2i5, j2i6, j1ip for creating, extracting and printing excise invoice. 4. What is meant by transfer of data from legacy code to sap ? Ans: It should be legacy data to SAP. What it means is you want to transfer all the customer and materials and all other information from Older (legacy system) to new SAP system. You can do it using many tools, most noticeably MDMs. (or) Before installation of SAP, Data maintained by Company is called Legacy Data. At the time of installation, it is required to transfer Data from Legacy to SAP like Masters (Material/Customer, etc). It can be done in various ways like BDC, LSMW, etc. 5. What do you do really in pricing determination, and what are the main differences between one pricing procedure determination to the others, which data control these differences ? Ans: The main differences between pricing procedures would be the differences as I mentioned above, from the point of view of field entries. Coming to the output and the procedure, I suppose the condition types used will be different and hence the following whole procedure. Pricing is determined by combination of Sales Organization, Distribution Channel, Division, Customer Pricing Procedure and Document Pricing Procedure.

6. What type of reports generally a support consultant maintain and report Depends on Customer requirements. 7. What are interfaces used generally an indian organization which is in retail business and which is in banking business and oil business. ? 8. What is the purpose of shipping point determination not menu path ? 9. What and where types of copy controls we change? Ans: Copy Control: is basically meant so that Data is copied from preceding Document to subsequent one. What subsequent Document is required is to some extent determined by Customer Requirements as well as Document Types. e.g. In general case of Standard Order, it will be Copy Control (Order to Delivery) from OR to LF . 10. How to and where to maintain copy controls 11. What is purpose of maintaining common distribution channels and common divisions Ans: Common Distribution Channel and Common Divison are maintained so that if any master data like customer or material maintained with respect to one distribution channel can be used in other DCh. It prevents the multiplication of master records. Eg: A customer is created for say sales area 1000/20/00 then the same customer can be used in sales area 1000/30/00 if we maintain 20 as common distribution channel. Hence no need for extending the customers...the same for materials also. 1. (a) Text Determination: Any Texts in Material Master/Material Determination/ Order/ Delivery , etc is meant to convey messages to the subsequent documents for compliance. e.g. "Give Top Priority" message mentioned in Order is meant for Production Dept. (b) Account Determination: is integration between Finance and SD. The A/P along with Account Keys need to be allocated accordingly with combination of Account Determination Group for Customer and Material if required. (c) Partner Determination: To identify which type of Partner it is so that if required for same Customer different Partner Functions may be required e.g Only One Sold To Party per Customer. More than One Ship to Party/ Bill to Party/ Payer possible. Accordingly different Masters will have to be created. Useful for dispatch of Material in case of Ship to Party, sending Bill in case of Bill to Party and payment follow up/Dunning in case of Payer. (d) Output Determination: What type of Output (Fax/Mail, etc) is required, where and in what Format(ABAP Customization may be required in some cases especially Invoices). (e) Storage Location Determination: depends on Plant, Shipping Point and Storage Conditions. What is the difference between the Avaialbility check 01 (Daily requirement) and 02 (Individual Requirement) in material master? 01 and 02 are the checking group. Availability check is carried out with the help of these checking group and checking rule. Checking group 01 and 02 are maintained on the material master. 01 - Individual requirement -For this system generates transfers the requirement for each order to the MRP .So that MM can either produce or procure. 02- Collective requirement.-In this all the requirements in a day or in a week are processed at a time. System stores all req and passes on to the MRP in MRP run. In this system performance is high however you can not do the backorder processing whereas in other you can do.

1. What exactly is automatic posting can you explain? 1. Automatic posting could be, posting of accounting documents to FICO once invoice is created which can also be controlled manually. Automatically determine the freight while pricing in ship doc. and post to the relevant account to fico. usually automatic posting is posting of documents to FICO based on various account keys and account groups. 2. How many clients we will create in landscape (like in development server, quality server, production server) if we are creating more than one in each server what is exact use of that client. 2. Client landscape : Basic layout : dev -testing- production also - Sandbox env. for trial and error - Development env. for actually creating transports(CTS) - Global env. If you have global implementations at different client locations (eg; Canada, US, UK) (for testing purposes with actual master data as well) - Testing env.(for regression testing purposes before moving to production, integration etc..) - Prod. env. the actual production system The clients could be variable and could be created to a specific env. usually a dev. where abap, functional would mess around. say : client 100-functinal consultants client 300- abapers client 400- other users(like super etc) 3. How we will configure export sales in sd (respect to plants assign and sales process)? 4. How we can do invoice split depending on item category in which scenario we will use? 4. You first need to go for copying controls either from sales to billing (invoice) or delivery to billing or billing to billing ,use transactions (VTAA, VTAF, VTLA, VTFA, VTFL, VTFF) all possibilities for copy controls. this basically is flow of doc to doc. (may it be sales to billing, del to bill, or billing to billing etc..) -> this is where you see the Item category and you control whether split is possible or not with the indicator "B". eg: representing split in invoice based on item category. The field here "data VBRK/VBRP" (header/item)which actually is used for splits or combining different deliveries. create a splitting rule using VOFM (you need access key to get here). Here you define comparisons for the fields at header table and item tables and the comparison fields say SPART" division". "purchase order "BSTKD Instance: 5 sales orders combined into 2 deliveries and the split at the invoice would be 5 individual billing with respect to fields PO and DIv. of each sales order would let you create 5 billings. You need to define the exact "field" in the comparisons both at header and item level that could lead to invoice split. the key here is the field that is different from header to item will cause split at the item level. 5. Can any one explain how we will configure milestone billing , periodic billing and which scenario we will use? 5. Menu path: IMG->sales &distr->Billing->billing plans->define billing plan types. You set the start date and end dates if applicable to the type of billing you are using. What time

to be billed (end of month, start of month etc..) Milestone is a billing plan type where a customer is billed for the amount distributed between the dates until total value is reached eg: if the total billing amounts 1000 USD for a year. You will bill the customer in different amounts say 200, 500, 300 at different intervals as per customer agreement. On the other hand Periodic billing is billing the customer for the total amount(here 1000 USD) at regular intervals periodically until the customer agreement is reached. eg: 1000/12 for a 1 year agreement and say billed at the 1st day of every month. 6. What are some pricing routines and sd functional specs? 6. Form routines for pricing and various other functions can be maintained form routines are something to do with ABAP code. Go to (VOFM) where all requirements which are represented by form routines can be maintained. Requirements are available to be assigned where access sequences are used (for determination procedures, here pricing). Once the t code VOFM is accessed you will see requirements and go select "pricing" again you need access key to create your own or copy a routine. Say you want header price not to have effect the item pricing, you need to go to the program to change abap code to meet the requirement. this specific requirement you created will be assigned in the pricing proc. determination "requirements field" usually with a number beyond 600. Note: make sure you activate your routine for its effect to take place.