Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
While trying to understand the Authorization concept in SAP, I came across the stage where an Authorization is ‘generated’ resulting in a profile number.
Now I’ve the following questions:
Q1. What is the meaning of ‘generating’ an authorization. What new does the button actually do because we already have allocated an authorization object to a class. I think this only should serve the purpose of allocating this authorization to a user?
Q2. What is a profile?
Thanks!
“Profiles” are the technical stuff that the kernel reads to actually evaluate the permissions. In The Good (?) Old Days [TM], there were only profiles, maintained manually. Roles / Activity groups were built on top of this later on, adding functionality and more settings. They consequently generate profiles from the settings assembled there. This allowed for a gradual transition from manual profiles to generated profiles / roles without throwing away the kernel and user code that was known to work. You can still see this in the technical names: PRGN = profile generator…