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.

basically we are using ticketing tool for getting tickets, and resolve thos tickets.every company should be maintaind some tools like....Remedy and open hp view dif,dif types,internally or externally ex: application development, testing , production evnvironment ,our organigation become some problem effected in application or development environment or client will rise some problem like my system was not working or my application was not running ....how can u resolve, problem how can identified and how can u understand those problems,,,,,,thats way we can installed ticketing tools..... Knowledge in testing tools like ECATT ( Extended Computer Aided Test Tool)

QTP ( Quick Test Professional Tool)