Do you have any question about this t-code?
Transaction Code: ACO_ADMIN_OTYPE
Description: Object Category for Auth. Admin.
Release: S/4HANA and ECC 6
Program:
Screen: 0
Authorization Object:
Development Package: ACO_BSP
Package Description: BSPs for Access Control Lists from Package ACO
Parent Package: DEVELOPMENT_PROJECTS_UI
Module/Component: PPM-PRO
Description: Project Management
Overview: The SAP transaction code ACO_ADMIN_OTYPE is used to define the object category for authorization administration. This code is used to assign authorization objects to authorization profiles and roles. It is also used to define the authorization checks for a particular object type. Functionality: The ACO_ADMIN_OTYPE transaction code allows users to define the object categories for authorization administration. This includes assigning authorization objects to authorization profiles and roles, as well as defining the authorization checks for a particular object type. The object categories are used to group similar objects together, making it easier to manage and maintain the authorization system. Step-by-step How to Use: 1. Enter the transaction code ACO_ADMIN_OTYPE in the command field of the SAP GUI. 2. Select the “Object Category” tab in the main window. 3. Enter the name of the object category you want to create in the “Object Category” field. 4. Enter a description of the object category in the “Description” field. 5. Select the “Authorization Objects” tab and enter the authorization objects that should be assigned to this object category. 6. Select the “Authorization Profiles” tab and enter the authorization profiles that should be assigned to this object category. 7. Select the “Roles” tab and enter the roles that should be assigned to this object category. 8. Select the “Authorization Checks” tab and enter any additional authorization checks that should be performed for this object category. 9. Save your changes by selecting “Save” from the menu bar or pressing Ctrl+S on your keyboard. Other Recommendations: It is important to ensure that all of your changes are properly saved before exiting out of this transaction code, as any unsaved changes will be lost when you exit out of it. Additionally, it is recommended that you test out any changes you make before implementing them in a production environment, as any errors could cause serious issues with your system's security and performance.