cancel
Showing results for 
Search instead for 
Did you mean: 

Tools and Support Procedure.

Former Member
0 Kudos

Hi Experts,

What is the procedure for support.

How the tickets will come and after SD Consultants modify according to Users reqt, will there be any testing? and who will send back to the Users.(Testing team or SD Consultants itself)

Plz tell the procedure

2. How the tools differ from one another.

Ex: Remedy , one model.

Citrix. , other model. means how they looks like.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

ticket tracing is differs to comapany ot compant, generally end user raise the ticket for receving tickets ine person i sthere usualyy called MOD manager of the day he will collect all the tickets and sort out them and then distatch to the concern bucket(module), it the ticket is solved then the consultant will be updated in the ticket tracker toll like REMEDT, ONIX, OVSD

Former Member
0 Kudos

hi,

let me tell you an example of a credit card order. here the user doesnt enter the proper details of the card and tries to authorize the order.

he gets an error message of failed authorization and reports it to the support team through support management tools like remedy, cadre, perigrine, ovsd etc.

the consultants see the issue and provide an initial analysis reply to the user and start testing in the quality first. Now we simulate the error first in quality and see if any changes are required to made. If the error is because of incorrect data we tell the same to user. but if there is any config change required, we go to DEV and do it in the sandbox first. found good, we config that in golden client and test in the dev server test client. We now move it to quality and re test it. then ask user also to confirm if its working fine. Found good, we move the changes to PRD.

Now the user can close the issue or can approve that the issue can be closed, and we may also close it.

regards

sadhu kishore

Former Member
0 Kudos

Hi Sabina,

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.

Reward points pls.

Regards,

Govind.

Former Member
0 Kudos

Thnx for ur reply

The changes which have been done by the Support consultant, in DEV server

my doubt is that , will the consultants directly do the changes on DEV server. they will be different clients . right.

I think , u have understood my doubt

former_member1318783
Participant
0 Kudos

Yes, the consultant will do the required changes in dev server and later transported to quality by basis team ,then the enduser will check in quality system.if every thing is ok ,then again transportation will be done frirom quality to production.

hope ur doubt is cleared.

Reward points if useful.

cherukuri

Former Member
0 Kudos

Dear Sabina,

The changes are directly done in the dev server and then they are sent to the user for sign-off which means the user says that they are satisfied with the changes done. After the sign off the changes will be moved to higher systems.

The changes are moved through transports.

Do let me know in case of any queries.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh