Kontakt

Ansicht
Dokumentation

CRM_ACE_IMPLEM_CUST - Prerequisites

CRM_ACE_IMPLEM_CUST - Prerequisites

PERFORM Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

If you want to use the Access Control Engine (ACE), ensure that you have authorizations for customizing your system and a development key.

  • The development key is a basic prerequisite for developing methods for the ACE.
  • In Customizing, you link the single parts of the ACE to form a functioning access control.

You have the following authorizations:

  • Authorization object S_TABU_DIS
To maintain the ACE tables, the administrator requires authorization object S_TABU_DIS.
The following tables are saved via the authorization object:
  • CRM_ACE_ACTS

  • CRM_ACE_ACTS_OTS

  • CRM_ACE_ACTTYP

  • CRM_ACE_AFO_CL

  • CRM_ACE_AFU_CL

  • CRM_ACE_ANGRP

  • CRM_ACE_ANGRPS

  • CRM_ACE_CUSTOM

  • CRM_ACE_INF_CL

  • CRM_ACE_OBF_CL

  • CRM_ACE_OTYPES

  • CRM_ACE_RIGHTS

  • CRM_ACE_RULES

  • CRM_ACE_ST_ACC

  • CRM_ACE_U_GRP

  • CRM_ACE_U_GRPS

  • CRM_ACE_WP

  • CRM_ACE_WP_OTS

  • Authorization object CRM_ACE_MD
  • The following applications are saved via the authorization object:
  • Activation Tool (transaction ACE_ACTIVATION)

  • Design Report (transaction ACE_DESIGN)

  • Update Tool (transaction ACE_UPDATE)

  • Runtime Report (Transaction ACE_RUNTIME)

The values of field ACTVT give the following authorizations:
  • 16 (Execute): Starts transactions

  • 63 (Activate): Activates rights and user groups

  • 66 (Refresh): Refreshes rights, user-, and object contexts

  • H1 (Deactivate): Deactivates rights and user groups

Job processing

You need to create a job in each system-client where ACE is active. Without this job, ACE will not be able to calculate authorization data. This job will be started by an event that is triggered by user activities mentioned in the documentation for Dispatcher and Trace Table for Background Processing.

To create this job, start transaction SM36. You can use the Job Wizard.

You need to specify the client using a parameter like the one shown below. Insert the current client when you create the job.

Job attributes:

  • Job name (proposal): ,,ACE_DISPATCHER
  • ABAP program name: ,,CRM_ACE_DISPATCHER
  • Event ID:,,,,,,SAP_CRM_ACE_DISPATCHER_REQUEST
  • Parameter ( example ):,,200
  • Indicator 'Periodic Jobs':,,activated

To check if the job will be executed by the event you can trigger this event manually in the transaction SM64 on the tab 'BckProcEvents'. Search for the event ID mentioned above and trigger the event using Trigger. Now you can see in the job overview ( transaction SM37 ) that a job with the name ACE_DISPATCHER is active or has just finished.

The job runtime depends on the number of objects to be processed and the Customizing parameters described in the section 'Parameters that control the calculation of authorization data in background processes' of the document Maintain General Parameters






Addresses (Business Address Services)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5120 Date: 20240606 Time: 042949     sap01-206 ( 53 ms )