Most often asked SAP SD Questions

 

1) How you will release change request in SD module? How often you release them?

2) How to create tasks. What are the maximum number of tasks you were created in you are previous project?

3) What is the difference between task and change request?

4) Is it possible to release change request, without releasing task.

5) Is functional module configuration comes under workbench request or customization request?

6) What is the tool you are using for testing purposes in your project?

7) What is the landscape you are following, which one you prefer to test functional module level changes?

8) Could you explain about sales deals?

9) Product attributes means?

10) What do you mean by drop shipment?

11) Can you explain about Higher-level item category and item usage?

12) What do you mean by condition index, how you configured in you project?

13) What do you mean by sort key(company code data in CMR) ?

14) What is the difference between ERB and ERU account keys?

15) What is the difference between general item category group and item category group ( sales org2 in MMR)?

16) What is the difference between alternative calculation type and alternative condition base value?

17) Is it possible to have different pricing procedure for sales order and invoice?

18) Consumption based planning?

19) Difference between billing and invoice?

20) How to stop PGI?

21) What do you mean by user specific parameters?

22) Explain about common distribution channels and common divisions and combined distribution channel and combined divisions, what is use?

23) How to extend material and customer to other sales areas?

24) Why does account group controls customer?

25) How can you use R/3 project management in implementation?

26) What are the Enhancements you done as a support team member and explain any two?

27) To get pricing in billing what are configuration you done in your project?

28) To extend material one plant to another plant what are the configuration you done in your project?

29) What do you mean by POD(proof of delivery) what is the use of pod? What are the con figuration you done in your project?

30) What is the significance of products under system application and products?

31) Why do you need project IMG?

32) What is the client specific data? Give two examples of client specific data?

33) What is the use of sales area?

34) How we assigned sales organization to delivering plant?

35) In system landscape where the sand box and golden box exists?

36) What are the challenges you faced in your previous implementation project?

37) What are the inter faces do you know?

38) Explain about smart forms?

39) From where system picks VAT registration number?

40) What is condition update? Can you give condition update for product, which is already given condition update?

41) What is the difference between customization and configuration?

42) While I am creating a customer in ship to party account group you have shipping and billing partner function tab pages, client wants to shift all important fields in billing like payment terms, incoterms , and tax classification into shipping tab page. He wants only shipping partner function only, how does you customize?

43) In material determination how you configure the system should propose when product A is not available then only system substitute with product B. If A is available 60% quantity. How do you do in the situation?

44) In which phase you transfer data into SAP R/3?

45) Explain EDI and its usage?

46) Sales order is created 1st November for 200 tooth pastes 100 brushes free of goods(2+1 free goods).At the time of delivery on 15th November you have shortage of brushes by 40. offer closed on 15th November . How do you solve in this scenario?

47) Can you assign one sales organization to multiple company codes? If yes how? If no why?

48) In real time what user name and password we use?

49) In real-time when we start system in first what screen we get and tell me process how to logon sap screen? I faced this question in IBM?

50) Where you worked with ABAPers?

51) How do you calculate net price on MRP based?

52) Have you worked on debugging? Explain any of one of the example?

53) How many user exists have you developed in your current project? Name at least 10 user exists you have developed and used in your current project?

54) Explain about SOP (service operating procedure) and your role in it?

55) Can you do account determination without account keys? And explain how?

56) Explain about minimum value surcharge calculated?

57) What you done business blue print, realization, final preparation, and go live support in your previous project?

58) How many SAP versions you know? And what is difference between them?

59) Without delivery can you do billing?

60) Is it possible to do delivery without shipping point?

61) Quotation has been created for product-D, 10 quantities, sales order is created with reference to the quotation, system copies 10 quantities in sales order. How do you restrict in sales order end user should not change quantities, system should not allow for changes by en user?

62) What are the business processes in your project?

63) How system picks up pricing while doing billing?

64) How SAP support to the client to know the customer requirements?

65) What are Z errors?

66) What are the training documents while giving training session for users?

67) What are the time bound deliveries?

68) What are the GAP analysis you identified in your project?

69) Can you explain about actual GI (gods issue) date and planned GI date? Can actual GI date differ from planned GI date?

70) Which module integration is required in output determination? 71) What are the two user exits you have used in your project?

72) What is the importance of release status and dynamic field check in condition table/condition record?

73) How sales document is structured?

74) What is the use of pricing date in condition type?

75) What is the use of condition type in pricing procedure determination?

76) In sales order how system does picks up plant?

77) What happens if inspection lot is rejected?

78) Can one have multiple packing for delivery?

79) What happens to the material listing/exclusion if the payer is different from the sold to party?

80) Can one create delivery with reference to the project?

81) An order item with different shipping point copied into the sales deliveries?

82) Can one specify user specific dates in delivery documents?

83) How does the rule MALA decide the picking location?

84) Why do I use condition indexes? How do you activate them?

85) How can we process out bound deliveries without shipping point?

86) Stock transfer?

87) What is the use of VPRS, EK01 and Ek02? For material cost we are using VPRS why we need EK01 and EK02?

88) When I am saving customer master (internal number range), system generating number range like 5000211,500216and 500221 instead of giving 500211,500212 and 500213.why system generating like this?

1.  Which agreement type I should consider, is this custmer rebate(0003), material rebate(0002) or Rebate on the basis of sales volume(0005), because here client is not offering rebate on Sales volume in rupees or dollar. He is only concerned with totat sales in kiloleter(Quantity). As per rebate agreement concern rebate is offered in percentage. Please guide me for  my scenario.

If your distributors are fewer (far less than 900 materials) then you should go for only customer rebate.

2. Guide me for conditions types and scale basis for maintaining condition records.

When creating customer rebates (T:VB01) select customer rebate, there you will see a header tab: Conditions , click it add how many customers you want. For each customer you can create scale based conditions (under the heading tab :Scales).

3. Is it necesary to maintain condition record for every material and every customer defining the scale? Because in this scennario client is going for incentives scheme for each material and each customer (distrbutor).

No need to create condition record for every material if you create customer rebate.

Customer Master

How to create the customer master?

The following are the T-codes for central creation of customer master.

        XD01    Create Customer (Centrally)
        XD02    Change Customer (Centrally)
        XD03    Display Customer (Centrally)
        XD04    Customer Changes (Centrally)
        XD05    Block customer (centrally)
        XD06    Mark customer for deletion (centr.)
        XD07    Change Customer Account Group
        XD99    Customer master mass maintenance
        XDN1    Maintain Number Ranges (Customer)

You need to identify various parameters within each Account group based on which the reco account is identified within the customer master.

Customer master is basically divided into 3 tabs.
- General - General master details, Juristiction codes, Region, Transportation zone, export data,  etc.
- Company data - payment terms, account management, reco account, insurance etc.
- Sales data -  Sales product attributes, sales office, sales group, customer pricing procedure, Cust. Statistical grp, 
   - Shipping data 
   - Billing data
   - Partner functions.

You can create a customer based on 3 views:
1. For Account purpose
FD01/FD02/FD03 etc
2. Sales purpose
XD01/XD02/XD03 etc.
3. Centrally 
VD01/VD02/VD03 etc.

What is the Function of item category and item category group?
Item Category determines the processing of any Item/material that we enter in a sales order and in this way it also effects the procesing of any sales doc in which it is used.

Item Category Group is one of the component which along with the Sales Doc Type, The Item Usage and Higher Level Item Category decide about the Item Category in a sales doc.

 

What is "alt cal type" & "alt base value" & "Requirement field" in the Pricing Procedure

The alternate base value is used as the calculation basis only, while the alternate calculation is used to modify the final value. 

For example, imagine you have a condition type ZZ01, with a condition record maintained (master data) for $100.  Now, condition ZZ02 also exists lower in the schema, but with a rate of 10%.  The standard calculation would result in a final value of $110. 

The alternate base value could say, "don't use $100 as the basis -- use the original price PR00 only, which was $90."  Then, the final value would be $100 + (10% of $90) = $109. 

The alternate calculation routine says, "ignore the 10% altogether. Instead, use an externally calculated 20%."  Then, you end up with a final value of $100 + (20% of $100) = $120. 

Put them both together, and you could end up with $100 + (20% of $90) = $118. 

Now once again,

Alternative Calculation Type:

Normally if you want to calculate a value you have to use a calculation type for determination the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.  

Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10  % in the condition record. Then this percentage is taken as the calculation type  and the condition value is determined.

In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material. it depends on so many criteria like, the weight, volume  and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.

Alternative Condition Base value: If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the  discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the  condition value of the base price of the material to calculate the value.

Now you don't want to take the base value and take other values as base value which are derived on some formulae. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type.

Requirement:
A factor in the condition technique that restricts access to a condition table.   The system only accesses a condition table to determine the price if the requirement specified has been met. 

Example:
The system uses an access sequence to determine the price of a material. One of the accesses in the sequence contains the requirement "in foreign currency." The system only uses the table behind this access if the sales order for which the price must be calculated is in a foreign currency.

======================

Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customer’s requested delivery date to determine if this date can be met.

The transit time, loading time, and pick/pack time are subtracted from the customer’s requested delivery date to calculate the required material availability date.

The system calculates backward scheduling as follows:

· Requested delivery date minus transit time  = Goods issue date

· Goods issue date minus loading time = Loading date

· Loading date minus transportation lead time = Transportation scheduling date

· Loading date minus pick/pack time = Material availability date

By default, the system will calculate delivery dates the closest day, taking into consideration the working days of the shipping point and a rounding profile. In this case the system assumes a 24 hour work day and lead times can be entered in days up to 2 decimal points.  This is referred to as daily scheduling.

Precise scheduling calculated down to the day, hour and minute is supported.  This allows the scheduling of a delivery within a single day.  It is activated by maintaining the working hours for a particular shipping point.

Backward scheduling is always carried out first.  If the material availability date or transportation scheduling date is calculated to be in the past, the system must then use forward scheduling.

Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities.  The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.

The above said is right, there are two more important factors comes. One is "Replenishment lead time" - this is the time gap between ordering and receing the goods (Inward movement).If we set RLT while customising, system will take this consideration from the present date onwards.If the RLT is low, then delivery confirmation date will be optimal.
The second this is delivery type, ie partial or complete delivery.
These two factors make a great change in the delivery date and time, which is key of forward and backward scheduling.