tickets?

[Former Member]

hi,

i'm new to ABAP.

please can anyone specify any of the realtime tickets/issues resolved in brief.

Thx

[Former Member]

SAP Tickets - What Is That?

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.

Have a look at this link:

/thread/491170 [original link is broken]

In maintenance and Support projects what happens is if a customer is facing any problem while executing any particular transaction or report etc .

He calls up the Call center (help desk) and explains the problem and the help desk ppl will create a ticket based on the users requirement.these ticket are assigned to

1. User will encounter a error/problem

2. User will call up the Help desk.

3. Help desk will take the inputs from the user and routes it to the

concerned group (technical or functional).

4. Technical guys will accept the ticket taking the ownership and will work on that.

5. He solves the issue and sends a mail to the user for conmfirmation.

6. After users confimation the ticket will be closed by the technical or functional

consultant.

https://forums.sdn.sap.com/click.jspa?searchID=3145434&messageID=3229099

[Former Member]

Hi

Functional consultants they will send tickets to technical team leader, technical team leader will assign the tickets to the employers (Consultants).

there will some priority for that ticket

depends like high , low , mediam

depends up on the priority you need to deliver it , if it had high priority then time will be less around 3 hours etc..

in real time tickets will be like this

once i got one ticket like program is executing in quality server but not excuting in production

at that time i had taken basisi people and reduced the load of the paramater then it executed perfectly

so what ever the problems they faced in the production server the clients pass it to functional cunsultant then from them if there is any tech related then they assign to us

<b>Reward if usefull</b>