Table of contents
Scope
ERP
References
Attachments
INTRODUCTION
Objectives and scope of this procedure
This OP explains how to check any modifications made to the users of structure in SRM7.
Freshdesk ticket handling
When a ticket arrives to the PTP D&A SRM Freshdesk Group, the ticket is pick up by a team member.
The ticket needs to be updated (if needed) to the correct classification "PTP Request ", PTP-Process "Data & Analysis, PTP-Subprocess "SRM7" and PTP-Category "Approval structures maintenance".
- Make analysis of the request to see the person responsible to validate the request.
- Check if the ticket requester is the Site Application manager /WW Controller/Purchaser Key User or was validated by Site Application manager/WW Controller/Purchaser Key User. To check the person responsible to validate see the link below:
{+}https://docs.google.com/spreadsheets/d/1_5H3sPBO7bN3HJvOcx_hRUsmujwLHhYKoTXEpmRxU3M/edit#gid=2051071738+
If not an approved requester, the team contact the Site Application manager (AM)/WW Controller/Purchaser Key User to validate the request. (1)
§ Change the status of the ticket to "Need for more information"
If yes, proceed with the changes
- Make the necessary changes
- After the modifications are done the team member Inform all involved parties in the loop of the changes made.
The ticket can now be closed.
§ Change the Ticket status to "Closed".
(1) When an email is sent asking for more details (requester) or some kind of approval (AM + WW Controller), always put all involved parties in the loop (Requester + AM/WW Controller);
- If no feedback was provided, after 3 days we send the 1st reminder asking for feedback;
- If no feedback was provided, after 3 days we send the 2nd reminder asking for feedback;
- Finally if no feedback was provided, after 3 days we send a 3rd message with the following text:
*Dear xxxx,
As we didn't received any feedback for our question/s it's not possible to our Team proceed with your request.
Please be informed that we need your site Application Manager/ WW Controller/Purchaser Key User approval to proceed with your account creation as requested (for example).
Dear Application Manager, we will proceed with the closure of this ticket.
If you can provide us the requested feedback please just reply to this message and the ticket will automatically re-open in order to our Team proceed with requested actions.
Always at your disposal,
SRM Team*
STEPS OF THE PROCESS
Changes in the user
Go to BP2 – Tcode SU01
#1#3#2
#4#5
#6
# | Main activities | Tips / Best practices | Key points |
1 | Enter the user ID |
|
|
2 | Click on the icon " |
|
|
3 | Select "Change Documents for Users" |
|
|
4 | Click on the icon " |
|
|
5 | Click on the icon " |
|
|
6 | Check the changes made |
|
|
Changes in the structure
Check the changes made
Go to BP2 – Tcode PPOSA_BBP
#1#2#3#4
#5
# | Main activities | Tips / Best practices | Key points |
1 | Select the Department or position to check |
|
|
2 | Click on the icon " |
|
|
3 | Enter a date previously to the change |
|
|
4 | Click on the icon " |
|
|
5 | Check the changes |
| The changes will appear with arrows. The green ones correspond to entries and the red ones to removals. |
Check who made the changes
Go to BP2 – Tcode PP02
#1#2#3#4
#5#6
#9#7#8
#10#11
# | Main activities | Tips / Best practices | Key points |
1 | Select the Object type |
|
|
2 | Select the Object ID |
|
|
3 | Select the Infotype | If you don't know the infotype select 1000. You will be able to see all the infotypes that have changes. | Most used 1000 (Object), 1001 (Relationships), 1222 (General Attribute Maint.) and 5503 (EBP Order Value Limits) |
4 | Click on the icon " |
|
|
5 | Select the line of the change |
|
|
6 | Click on the icon " |
|
|
7 | Click on "Change information" |
|
|
8 | Check the user that made the change |
|
|
9 | Click on the icon " | To see all infotypes with changes |
|
10 | Select the infotype line |
| The line with changes appear |
11 | Click on the icon " |
|
|
REFERENCES
ATTACHMENTS
No document attached.
End of document