SAP ABAP IMG Activity RMPS_AUT_ORG_BADIKEY (BAdI: Implement Creation of Authorization Keys)
Hierarchy
☛ SAP_ABA (Software Component) Cross-Application Component
   ⤷ CA-GTF-RCM (Application Component) Records and Case Management
     ⤷ RMPS_CUSTOMIZING (Package) Customizing Records Management for Public Sector
IMG Activity
ID RMPS_AUT_ORG_BADIKEY BAdI: Implement Creation of Authorization Keys  
Transaction Code S_KRM_01000039   (empty) 
Created on 20021113    
Customizing Attributes RMPS_AUT_ORG_BADIKEY   Implement Creation of Authorization Keys 
Customizing Activity RMPS_AUT_ORG_BADIKEY   Implement Creation of Authorization Keys 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RMPS_AUT_KEY_GENSP    

Use

Using this Business Add In (BAdI), you can make entries in the field Authorization Key of the authorization objects RMPS: Access File, Process, Document Org. Assigment User (PS_RMPSORG) and RMPS: Access File, Process, Document Special Org.Units (PS_RMPSOEH).

You can define authorizations that are dependent on particular attributes or other information.

The system calls this BAdI for each authorization check and for searching for a record, document or incoming post item.

You can determine the attributes of objects you require for creating authorizations keys using the parameter IM_CALLER.

(see also: PSRM terminology)

Requirements

Standard settings

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

  1. You want to restrict access to old records.

    You first determine the start of the runtime of the records and then set the authorization keys dependent on "OLD".

    Then you have to assign the authorizations to the users who should have access to the records in role maintenance.

    To display sample coding, select Goto -> Sample Coding -> Display.

  2. A tax number is coded in the reference number of your records. The tax numbers are grouped in areas. You want to assign the authorization according to the area of the tax number.

    In this BAdI, you can use the reference number to determine the tax number and the area from the tax number. You put the area in the authorization key. You then have to assign the relevant authorizations in role maintenance.

Note

Note that this BAdI affects system performance because it is called up for each activity of an object. It is run particularly frequently in the search function. This can have a negative effect on the performance of a search if a large amount of objects is found. Then the authorization check is only carried out after the search and only for the objects found.

Business Attributes
ASAP Roadmap ID 209   Establish Authorization Management 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030404 
SAP Release Created in 110_620