please send me a ticket sample view so that I understand , structure of tik

[Former Member]

please send me a ticket sample view so that I understand , structure of ticket,

Points will be awarded,

Jagrut Shukla

[Former Member]

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.

[Former Member]

Thank you for your valuable information ,

Another thing i want to know is the layout or how it look like e.g

ticket no --- but what format?

any sequence for ticket,

how does the priority differs in tickets,

Poits will be awarded

[Former Member]

depends on the tool used

say for cadre , it will be H123456_12345

for ITSM --- starts from 000000001 and increases

Priority can be Medium , SL5

SL5 in the sense it is for developments and takes about 20- 25 working days