OSS Note - Online Service System

OSS Note:

OSS means Online Service System - online SAP support notes. 

OSS notes are available online for solving critical problems in SAP system. We may use the already existing notes or may add our own queries. In order to apply any OSS note, company authorization is required and must be assigned an OSS ID and password.

OSS id is a SAP service logon which is needed for connecting to SAP marketplace and is related to company’s agreement with SAP and assigned to company’s installation numbers.

OSS id helps to:

- Create SAP systems under selected installation numbers - this allows you to request licenses and 

upgrade keys for the system 

- Register developers for SAP systems (developer key)

for Ex we  provide access to SAP Consultant in Q50-900 through OSS Message 104524/2015

1)       Open the OSS message with the message no. (as provided above 104524) from SAP Marketplace with the following link

https://websmp110.sap-ag.de/support

         

2)       Go to “Report a Product Error” tab.

3)       Go to “Search Message” option.

4)       Here provide the message number as shown: 104524

5)       Click on the Search button after which a link appears

6)       Once the link is clicked, click on “Maintain Access Data” button

7)       A screen for System Explorer appears Q50 Test System

8)       Here click on the system for which OSS ids are to be created. As per example taken, click on Q11 (Test system) which gives in turn the Logon data for Q50 system. Here note the expiration date for the OSS Ids as provided below. Here the expiration dates for two OSS ids are still valid, hence those ids cannot be provided to the user. If the IDs are not valid you can reuse them. Also please check in the message if anyone had already updated any id before. If you find any then please try to use that id only. But make sure you follow all the below process before using the id.

“Expiration date is within the Validity period” means Expiration date for the OSS id is less than or equal to present date.

In this scenario, it is required to find other OSS ids from the system which can be reused 

with expiration date = 9 days + ( sy-datum – 1), where sy-datum is present date.

9)       Once finding of proper OSS id is completed, Clicking on above Modify button will give a screen where details for client, user id, and password and expiration date are required. 

10)     So now in order to find OSS ids, logon to SAP GUI.

Now Go to SU01 in respective CUA. Here system is Q50, go to SA1 and give OSSQ50000* and press F4 (search help) and remove 900 from No. of Hits. 

11)     The first two ids cannot be chosen as the expiration date is within the validity period.

Hence select the third id and go to edit mode and check the Valid through date in LOGON tab. If the Valid through date has already expired, then that id can be reused.

12)     Go to Address tab.

Here this is previous data which is to be modified and reused.

13)     Put the OSS id in Last name and provide User full name followed by OSS message no and year.

14)     Go to LOGON tab again and change the Valid though date = 9 days + (present date – 1). Here the present date is 12/03/2015. Hence valid through date is 20/03/2015.

15)     Now go to Roles tab and verify if any Security / Basis / Debug / Configurator roles are assigned permanently. If any, then change the date from 31/12/9999 to any expired date as shown.

16)     Now logon to the child system individually and with given password as Welc0me1

Reset the new password to Spring01 and select the required system and cont

17)     Now in this screen, write the OSS message with OSS id details and system for which OSS id has been reused and click on “Send Message” button.

Regarding PRD OSS Ids

1. We must need ST Ticket and manager approval before providing OSS ID in production system. Requesting person can open ST Ticket and attach manager approval via email. If it is off hours, you still can give OSS ID providing requesting person will arrange for manager approval by next business days and attach it to ticket. You can send reminder email to verify next day

2. Once you have ST# Available, you can go to PA1 and find ANY available OSS ID for that system. You can identify OSS ID by naming convention

For example, OSSP50900-01 ID is for P50 900 System. If ID validity dates are expired, that means it is available to re-use. You need to update few things though like, requesting person name, OSS Message#, ST TICKET# . You can see these fields already mentioned for previous message. You can overwrite it for message you are working on it

3. Extend validity dates of OSS ID for 9 Business days (not including holidays) 

4. Remove old expired roles and assign new roles based on request. You can use general production end users roles/support team roles for same validity period . YOU CANNOT ASSIGN CUTOVER ROLES. If tcode is only available in FF ID roles, you can assign for max 48 hours

5. Go to child system and validate all changes you did in CUA is pushed there and roles updated. Reset password in child system. Try to login on your matching with OSS ID and initial password and change password to something like Welcome1234 or hello1234. Remember password you put. 

6. Go to OSS MESSAGE AREA and update OSS ID, PASSWORD, VALIDITY DATES in secure message area. Also put remarks in OSS Message and sent message back to SAP

7. Should we unlock (if it is locked) any of existing OSS id for reuse?

Yes. You should verify if validity dates of OSS ID already expired. If that's the  case, you can re-use ID by unlocking it and resetting password. We strongly suggest to re-use OSS ID rather than creating new one. We have around 6-7 OSS ID for each system which can be used repetitively.

8. What do we need to update in the star team ticket?

You can update ticket to inform requesting person that you have provide OSS ID and password details in secure message area. DO NOT PUT OSS ID PASSWORD IN starteam ticket. Also please do not email OSS ID password to Pepsico users. You should only save password in secure message area where SAP resources can check

9. What should be the final status of the ticket after providing the Oss id to the user?

We usually get OSS request as new issue or new special request. If it is new special request, you can put to special request assigned and assign back to requesting person. If it is new issue, you can just update ticket and assign back to requesting person. If no action required, he may close tickets

10. Also whom should we assign the ticket after we update the ticket?

You should put ticket back to requesting person unless it is specified in ticket whom to forward. You may check if OSS Connection is open or not. If OSS Connection is closed, you may forward ticket to SAP BASIS PRODUCTION team queue to open OSS Connection for 9 days or remind requesting person to follow up with BASIS team member to open OSS Connection. 

               

11. What roles to assign if not specified in ticket? 

You may ask to requesting person if he is available. If not and issue is urgent, you may copy all access of requesting person and put it in OSS ID. That could be starting point and SAP can request more access later if required for further analysis. 

12. Do we need approval to provide debug access (please advise the debug role also)?

Yes you need BASIS manager approval to provide debug access. Please see roles in OSS ID (OSSP70900-02) for example. If issue is urgent and manager is not available for example at midnight, you can provide access and strongly request user to collect manager approval by next business days. 

Important:

?        With recent changes, security team member will not have access to extend roles starting with ZPC-XXX*. We need to request FF ID if we need to assign these roles.

?        When you change validity date of role, also change valid from date