A company needs to set expectations around what is being expected from a consultant according to the experience level being hired for during an interview. Also,if a candidate answers 8/10 questions correctly, he/she should be cleared 99% of the time. Moreover, if the 2 questions that he/she answered incorrectly were tough questions, further consideration should be given to this fact. When interviewing a candidate for the role of a SD consultant, he/she should be EXPECTED to know the basics of SD. Knowledge of advanced topics and rare scenarios should be a GOOD TO KNOW, but NOT A MUST KNOW. In my case this did not happen. After calling me for the interview at 11 AM at the DLF office in Gachibowli, I was made to wait for an hour before my interview took place. The company's phone was not working and so, the recruiter asked me to dial the conference number from my mobile phone. The interview started and the recruiter asked me questions around SD. I answered most of them correctly (the interview questions that I can recollect are mentioned below). One of the questions that the interviewer asked me was how is the Customer Returns from third party sales mapped in SAP? I replied that we will first create a return sales order (RE) and then create a return delivery (LR) with reference to the return order so that we can receive the inventory into stock. Once the inventory is received, we create a credit memo and issue it to the customer. In MM, we will create a return purchase order and then create an outbound delivery to send the material to the vendor. This will remove the inventory from our stock. Finally, a debit memo must be created in MM against the original MIRO invoice. This is a rare scenario and after reaching home, I tried to find the answer to this question. On SCN, I found threads which said that this scenario is not supported by SAP (SAP note 751609). The entire discussion can be viewed on SCN: One of the questions I was asked was if I knew anything about Idoc's. I replied that I have not worked on Idocs. The Idoc topic falls into ABAP and functional consultants know this IF they have worked on this topic. Like debugging, function modules, user exits, BAPI's, BADI's, alv grids, SQVI queries, LSMW, these topics are a GOOD TO KNOW, but NOT A MUST KNOW for a functional consultant. Questions: Explain the controls in the sales document type definition? Explain the controls in the item category definition? In which scenario do you use item division and check division in the sales document type controls How can we make an item relevant for delivery? Explain how a revenue account is determined? How does the system perform an availability check? How is the shipping point determined? How is the plant determined? how is the item category determined? What is the significance of the usage field in the item category determination? When do we use the fields Billing relevance and pricing relevance in the item category controls? Explain the significance of the in completion procedure. At what times can we perform an in completion check? In the copy controls, what is the relevance of the update document flow control? Explain a gap that you faced in one of your projects? If a credit memo is created for the entire quantity with reference to an invoice, the does not allow the creation of a second credit memo. What configuration controls this? Have you worked on rebates? have you worked on STO's? I will update this review with more questions as I recollect them.