SD Questions Please Send The Answers

[Former Member]

Hai

Here i have attached some SD Interview Questions .Please Send the Answers .

Awaiting For Ur Replay - Please Mail Me ssivadkn@gmail.com, And sksap12@gmail.com

Thanks

S.Siva

1. Five steps of implementation with full details.

2. What is ticket? Process flow ticket?

3. What is ticketing tool? What is SODA?

4. How to stop PGI?

5. Details about SLS.

6. Details about the Gap analysis. (What are the gaps you have faced?)

7. What is meant by landscape? (Landscape of your project for example)

8. In which scenario we go for different pricing procedure at orders and billing?

9. Cut over activity means what?

10. In real-time project, how many pricing procedures to be used?

11. What are the tools used to communicate with the client?

12. Any three major issues faced in the support project?

13. Difference between SD account key and FI account key?

14. How to post goods receipt from storage location to warehouse? What is the movement type?

15. Tcode for listing blocked documents?

16. What is the advantage of using the text as reference instead of duplicating it?

17. Have you ever applied BPR (Business Process Reengineering) in an implementation project?

18. To perform material configuration, which system one has to use in landscape?

19. What is the tcode for creating number range for a sales order type?

20. Difference between centralized credit mgmt and decentralized credit management.

21. Where do u configure in development server or application server or in testing server?

22. Details about clients.

23. What is an abap query? Why it is used?

24. What are the steps for end user training in sap SD module?

25. Difference between discount and rebate.

26. When is material determination got triggered?

27. A customer wants to buy two materials / one is 3rd party material (Item category: TAS) / another one is normal material (Item category: TAN). His requirement is he wants a single invoice for both items without splitting? How can we do this?

28. In consignment fill up, we deliver goods to customer site, is there any agreement with customer? If yes means, what type of agreement relating price?

29. Details about VAT configuration.

30. What is the use of pricing date in condition type?

31. In R/3, we represent a company’s structure by defining and assigning corporate structure elements. What is the purpose of doing that?

32. What are the different partner functions can a customer master record serve?

33. What is the difference between condition type EK01 and EK02?

34. What is retroactive billing? Who will create that?

35. In your functional role, how you gather technical specifications for your technical team members from your client?

36. Is it possible to change existing item categories?

37. For cash sale, how will availability check be done?

38. How is the access sequence controlled?

39. User specific parameter means what? How to create that one?

40. What is the difference between listing and exclusion?

41. Difference between customization and configuration.

42. How to customize rebate processing in sap sd?

43. LSMW important step is what?

44. What is the extract used in condition technique of pricing?

45. Can we create credit management separately for two different materials?

46. Work center means what?

47. If the client logon screen deleted while requirement is urgent, then what to do?

48. What is meant by time bond deliveries?

49. After implementing sap in production environment, while creating sales order, client wants to give discount for first 10 sales orders? How to do this?

50. What are the Three different kinds of messages? What is the difference between them?

51. Details about testing at sap sd.

52. What is the access sequence for header conditions?

53. Details about actual GI date and planned GI date .Can actual GI dt differ from planned GI dt?

54. Influencing factors for account determination for invoices.

55. Details about sap best practices.

56. To start a transaction, how many ways are there? And what are they?

57. Who will create transportation request?

58. In realization phase, what will be doing?

59. Is it possible to release change request without releasing task?

60. Details about lean warehouse management.

61. How to customize excise duty, insurance and cess condition type in pricing procedure?

62. How to stop PGI?

63. Data dictionary or repository means what?

64. How do you transfer request from development instance to production or quality instance?

65. What is the importance of release status in condition table?

66. Why does account group controls customer?

67. What are the deliverables in your blue print?

68. If you generate bill more than credit limit, then what will happen?

69. What is the value class used for material creation?

70. Why do we maintain sales office?

71. Is it possible to substitute one product for another? If so, how it can be achieved?

72. What is the difference between ATP check and availability check? How these reflect in sales order?( Which check system considers) what are the img steps for the same?

73. Explain process and steps involved in returns third party order processing.

74. What is the client specific data? Give 2 examples of client specific data.

75. What is the most critical field in delivery document?

76. What is the relation between sap sd and ABAP?

77. What is the functionality of negative posting in billing document?

78. In real time, when we start system in first, what screen we get and tell me the process how to log on screen? (IBM question)

79. How can you check in sap system, how, when and by whom, which fields in the customer master record were changed?

80. What is variant and its configuration?

81. After logging into R/3 system, if you want an end user to see a specific menu…. How could you do that?

82. Is it possible to automate output processing?

83. Which data is relevant for crediting credit and debit memos?

84. In system landscape, where the sandbox and golden box client exists?

85. What is the user exists? /how can we create user exists? What is the purpose of that?

86. Details about value sap.

87. Is there any difference between product selection and material determination?

88. How do you transfer request from development instance to production or development instance?

89.What part of the company is responsible for the type of shipping, the necessary shipping materials and the means of transport?

[Former Member]

What is ticketing tool? What is SODA?

ticket tool means which software ur using for handling the

ticket.

generally, RADIX and REMEDY tools using for handling the

ticket.

How to stop PGI?

You can control it by:

1.Authorization control

2.User status

3.Credit control settings which prevents PGI, if it is applicable.

Details about the Gap analysis.

Gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.

Actual gap analysis is time consuming and it plays vital role in blue print stage.

The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.

Examples

In customer master data the client requirement needs legacy customer number which can be solved with User exit.

In sales order we need customer Phone number, we can use user exit

If client want new field in customer master like nearest fire station.

GAP analysis is done in Blue Print stage. It aims to understand what can be done with the standard SAP and how the client actually wants a particular scenario to be processed.

It’s an understanding of the GAP between the actual & required scenarios.

Tthe difference between agreed work and completed work is GAP Analysis.

E.g.: To Fill This Gap, We Use The Enhancements,These Enhancements Divided Into Exits, Like User exits, Field Exits Screen Exits & Menu Exits.These Enhancements are used to update the standard program in its Respective Business Transactions, Used as a Gateway to Meet the Client Requirements.

REgards.

[Former Member]

What is ticket? Process flow ticket

Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.

The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.

The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.

The work process in support projects are given below for your reference.

1. The customer or the end user logs a call through any tool or by mail (RADIX).

2. Each one of the support team is a part of support group.

3. Whenever a customer logs a call he /she has to mention to which work group (by name).

4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)

5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)

6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.

These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.

An example:

Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

To begin with , we should give "TICKET" to you for not knowing it.

Here is an eg of a ticket raise:

End user is not able to

1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

He raises a ticket and the priority is set in one of the below:

1. Low 2. Medium 3. High.

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.

Regards.

[Former Member]

Five steps of implementation with full details

ASAP Methodology:

Project Preparation:

The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.

Blue Print Preparation:

This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.

Realisation:

In this step actual development is taken place. The ABAPer is responsible for this step.

Testing:

In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).

GO live and Support:

This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.

Rewards if useful.

[Former Member]

Hi Siva,

Thank you for your posting , The questions u have posted are too big It consumes valuable time of the consultant and Its very hard for any one to answer no of questions at a time so please post your questions separately .

Wish you Good Luck