SAP Authorization - Quiz For Pro

SUGR is the transaction code used to maintain user groups in SAP. This transaction allows users to create, modify, and delete user groups, which are used to assign specific authorizations and access rights to a group of users. By using SUGR, administrators can easily manage and organize users based on their roles and responsibilities within the system. This helps to streamline the authorization process and ensure that users have the appropriate level of access to perform their tasks efficiently.

צריך לוודא שוי מסומן כדי שיראה את הערכים של הפרמטרים של המערכת


login/accept_sso2_ticket 1 Accept SSO ticket logon for this (component) system
login/certificate_request_ca_url https://tcs.mySAP.com/invoke/tc/usercert URL of the certificate authority (for certificate requests)
login/certificate_request_subject CN=&UNAME, OU=&WPOU, O=mySAP.com User, C=DE Template for the subject of a certificate request
login/create_sso2_ticket 2 Create SSO tickets on this system
login/disable_cpic 0 Disable Incoming CPIC Communications
login/disable_multi_gui_login 1 disable multiple sapgui logons (for same SAP account)
login/disable_password_logon 0 login/disable_password_logon
login/failed_user_auto_unlock 0 Enable automatic unlock off locked user at midnight
login/fails_to_session_end 3 Number of invalid login attempts until session end
login/fails_to_user_lock 5 Number of invalid login attempts until user lock
login/isolate_rfc_system_calls 0 Number of invalid login attempts until user lock
login/min_password_diff 1 min. number of chars which differ between old and new password
login/min_password_digits 1 min. number of digits in passwords
login/min_password_letters 1 min. number of letters in passwords
login/min_password_lng 6 Minimum Password Length
login/min_password_lowercase 0 minimum number of lower-case characters in passwords
login/min_password_specials 0 min. number of special characters in passwords
login/min_password_uppercase 0 minimum number of upper-case characters in passwords
login/multi_login_users ULIEL,GBELLA,LJACOB,ZMARIZ,SRONEN,CELI,AYANIV,BMEIR,KZVIKA,K list of exceptional users: multiple logon allowed
login/no_automatic_user_sapstar 1 Control of the automatic login user SAP*
login/password_change_for_SSO 0 Handling of password change enforcements in Single Sign-On situations
login/password_change_waittime 1 Password change possible after # days (since last change)
login/password_charset 1 Zeichenmenge für Kennwörter
login/password_compliance_to_current_policy 0 Kennwort muß aktuellen Kennwortregeln genügen
login/password_downwards_compatibility 1 password downwards compatibility (8 / 40 characters, case-sensitivity)
login/password_expiration_time 90 Dates until password must be changed
login/password_history_size 5 Number of records to be stored in the password history
login/password_logon_usergroup users of this group can still logon with passwords
login/password_max_idle_initial 0 maximum #days a password (set by the admin) can be unused (idle)
login/password_max_idle_productive 0 maximum #days a password (set by the user) can be unused (idle)
login/system_client 400 System default client
login/ticket_expiration_time 8:00 login/ticket_expiration_time
login/ticket_only_by_https 0 generate ticket that will only be sent via https
login/ticket_only_to_host 0 generate ticket that will only be sent via https
login/ticketcache_entries_max 1000 generate ticket that will only be sent via https
login/ticketcache_off 0 generate ticket that will only be sent via https
login/update_logon_timestamp m update frequency / accuracy of logon timestamp

It is case sensitive,
"create" or "Create" are different searches

table SKB1 field: AUGR
auth. obj. F_BKPF_BES for documents
auth. obj. F_SKA1_BES for account header.

לזכור שהבדיקה מתבצעת לפי שרת אפליקציה, אפלקיישן סרוור, כך שחשוב לדעת באיזה סרוור בודקים.
אם רוצים לדעת לאן מחובר משתמש - AL08 או RSUSR000
אם רוצים להחליף שרת - SM51 מסמנים את השרת הרצוי ולוחצים על אייקון הברק.

SM49 is a transaction code in SAP that allows users to view and maintain the list of external OS commands. It provides a comprehensive list of all the external operating system commands that are available in the system. Users can use this transaction to view details about each command, such as the command name, description, and the program associated with it. They can also add, modify, or delete commands from the list as per their requirements. SM49 is a useful tool for system administrators and developers who need to manage and monitor the external OS commands in the SAP system.

חשוב לזכור שעובד לפי אפליקיישן סרוור,
אם רוצים לדעת לאיזה אפליקשיין סרוור המשתמש מחובר אפשר לעשות זאת עם
AL08, RSUSR000

אם רוצים להחליף שרת - SM51 מסמנים את השרת הרצוי ולוחצים על אייקון הברק.
אם רוצים לדעת לאן מחובר משתמש - AL08 או RSUSR000

The illegal password information is stored in the USR40 and usr40 tables.

הטרנזקציה מאפשר לסנן לפי סביבה, משתמש וכד'
פעולות שנתקעו אפשר להריץ שוב

The given statement is true. CUA stands for Central User Administration. It is a feature in SAP systems that allows for the centralized management and administration of user accounts across multiple systems. With CUA, user accounts can be created, modified, and deleted in a central system and then distributed to other connected systems, ensuring consistency and efficiency in user management.

כאן כדאי להוסיף את השדות הנוחים לחיפוש ולתוצאות

SM12 לנעילות אפשר להשתמש

The correct answer is 105,0105. This answer suggests that the information type used to connect an employee and a username is a combination of two codes: 105 and 0105. These codes likely represent specific data fields or identifiers within an HR system that link an employee's personal information to their unique username.

SU24 is the transaction used to assign authorization objects to a transaction. It allows users to maintain and analyze the authorization objects that are relevant to a specific transaction. By using SU24, users can assign authorization objects to a transaction and define the necessary authorizations required to execute that transaction.

These are not twins but looks the same,
we find by using these transaction what every user activating right now,
We can see here which application server is used by the user without connect to the station.

remember: trace by ST01 must activate at the same appl. server where the user active.
you can change your appl. server by using SM51.

SMEN_BUFFC טבלה ראשית
SMEN_BUFFI טבלה נוספת שמכילה קישורים

Table USR02
Report RSUSR200

To assign a HR Structure authorization to a user, the transaction to be used is OOSB or oosb. This transaction allows the user to assign the necessary authorization to access and manage the HR Structure. This authorization is crucial for the user to perform tasks related to HR management and organizational structure within the system.

not-available-via-ai

בודקים האם יש איקס בשדה
COL_FLAG - Assignment comes from composite role
ORG_FLAG - HR Organization Management - יש כאן גם שדה לשיוך עקיף ממבנה ארגוני

The SAP menu option "AUTH" or "auth" is dedicated to authorization issues. This menu provides access to various authorization-related functions and settings, allowing users to manage and control user access and permissions within the SAP system. By navigating to this menu, users can handle tasks such as creating and maintaining authorization roles, assigning authorizations to users, and troubleshooting authorization-related problems.

The table AGR_1252 and agr_1252 both contain the "Organizational Level" values in roles. The question does not specify which one is the correct answer, so both options are valid.

The evaluation path for HR Structure authorization is defined in the transaction OOAW or ooaw.

The correct answer is USR01 or usr01. These are the tables where you can find user default values like language or printer.

ST22 is the transaction code in SAP that allows users to view ABAP runtime errors, also known as dumps. When a program encounters an error during runtime, it creates a dump, which contains information about the error and the program's state at the time of the error. By using the ST22 transaction, users can access and analyze these dumps to identify the cause of the error and take appropriate actions to resolve it.

not-available-via-ai

יבוא לידי ביטוי רק אחרי שיפעילו אותו,
S_TABU_DIS כמו כן, יבוא לידי ביטוי רק כאשר הבדיקה לא עברה את הבדיקה הרגילה

מידע מגוון מאוד
כמה ימים מאז הכניסה האחרונה
כמה ימים מאז שינוי סיסמה
משתמשים בתוקף או לא בתוקף
משתמשים נעולים או שאינם נעולים
מספר טעיות בהקשת סיסמה
מה הסטטוס של הסיסמה, מי לא החליף סיסמה ראשונית

לבהירות בדוח, כדאי להוריד את הוי של
Display Profile Parameters

not-available-via-ai

use transaction FS00 to change authorization groups for G/L accounts.
table SKB1 field: AUGR
auth. obj. F_BKPF_BES for documents
auth. obj. F_SKA1_BES for account header.

not-available-via-ai

Use SE38, or SA30 to run:
PFCG_ORGFIELD_CREATE - Create New Org. Level Field
PFCG_ORGFIELD_DELETE - Delete New Org. Level Field
Relevant Tables: USVAR, USORG , USVART

Delete New Org. Level Field

not-available-via-ai

כדאי להשתמש בכוכבית כדי לחפש שמות

יצירת הרשאה מבנית או תחזוקה שלה עושים עם
OOSP

To view the System Log, you can use the transaction code SM21. This transaction allows you to access and analyze the system log records. The system log contains important information about system events, errors, and warnings that occur in the SAP system. By accessing the System Log using SM21, you can troubleshoot issues, monitor system activities, and identify any potential problems or errors that may have occurred.

for query of changes use these fields:
CHANGE_USR
CHANGE_DAT
CHANGE_TIM

not-available-via-ai

SE54 is the transaction code used to maintain authorization groups.

The AUTH. Object "s_cts_admi" with values "IMPA" and "IMPAS" are relevant for Change Requests.

actvt 08 - Display change documents
actvt 09 - Display prices
M_BEST_BSA Document Type in Purchase Order
M_BEST_EKG Purchasing Group in Purchase Order
M_BEST_EKO Purchasing Organization in Purchase Order
M_BEST_WRK Plant in Purchase Order

The table "USER_ADDR" provides good information about a user's names. It likely contains columns such as "first_name" and "last_name" that store the names of users. By querying this table, one can retrieve accurate and relevant information regarding the names of users.

בדובר רק בפרטים שמוזנים לפרופיל המשתמש
החיפוש כאן הוא לפי כל השדות האפשריים
table AGR_ADDR will help too.

not-available-via-ai

USR05 - Users Parameters Id
TPARA - Main Parametes table
TPARAT - Texts

SU2, SU3, SU01 - Transaction to change user parameters

Use transation FS00 to change authorization gruop for G/L accounts.
table SKB1 field: AUGR
auth. obj. F_BKPF_BES for documents
auth. obj. F_SKA1_BES for account header.