Using Personalization Objects in the LAW

Use

You can use personalization objects, which have been available since SAP release 4.6C, to assign completely individual information to an SAP user. These personalization objects are also available through SAP Note 838736.

You can either maintain personalization objects manually in user maintenance or automatically using the ABAP class interface CL_PERS_ADMIN. To be able to assign special personalization objects to the users, you must register the associated data structure with transaction PERSREG once.

As of SAP NetWeaver '04, the LAW can assign personalization objects to the SAP users to be grouped and further process the personalization objects. The DDIC table structure LAW_T_PERS and the associated row structure LAW_S_PERS used by the LAW already exist in this release. The personalization object LAW_PERS is also already registered. In user maintenance, the following entry is in the table of existing personalization objects on the Personalization tab page:

Personalization object for license administration LAW_PERS

Double-click this entry to start the display or maintenance.

To use personalization objects for LAW consolidation in general, you must create these structures and register the personalization object LAW_PERS in all component systems with older releases. Since you must do this in the customer namespace, the original names must be renamed.

Process

1. In the ABAP Dictionary, create the following objects in succession, each with the relevant values listed below (see also Creating a Data Element):

   1. Data type LAW_PERS_VAR as ZLAW_PERS_VAR

      • Brief Description LAW: Name of a personalization variable

      • Domain: CHAR20

      • Field Description: Name of the Variable

   2. Data type LAW_PERS_VAL as ZLAW_PERS_VAL

      • Short description: LAW: Value of a personalization variable

      • Domain: TEXT128

      • Field Description: Value

   3. Row structure LAW_S_PERS, for example, as ZLAW_S_PERS

      • Short description: LAW: Row of a personalization variable

      • Component: Component type

      • NAME: ZLAW_PERS_VAR

      • VALUE: ZLAW_PERS_VAL

   4. Table type LAW_T_PERS, for example, as ZLAW_T_PERS

      • Short description: LAW: Personalization object

      • Row Type: ZLAW_S_PERS

2. Register the personalization object LAW_PERS, for example as ZLAW_PERS, with transaction PERSREG (see Registering Personalization Objects).

   The appearance of the transaction is different in release 4.6C from older releases.

   Release 4.6C

   The system may display the following warnings, which you can ignore: “Cross-client table” or “Do not make any changes (SAP data)”.

   1. Choose New Entries.

   2. Enter the following data, and set the following indicators:

      • Key: ZLAW_PERS

      • Description: Personalization object for license administration

      • Standard repository: X (set indicator)

      • FM for Dialog: LAW_PERS_DIALOG (more information: SAP Note 721694)

      • Access via user maintenance: X (set indicator)

      • Visible in user maintenance: X (set indicator)

   SAP Web Application Server 6.10 and 6.20

   1. Choose Create.

   2. Specify the value of the key as ZLAW_PERS.

   3. On the next screen, enter the following data, and set the following indicators:

   Description: Personalization object for license administration

   Generic Repository: X (set indicator)

   Dialog Function Module: SPERS_STANDARD_DIALOG

   Take into account when user changed: X (set indicator)

   Visible in user maintenance: X (set indicator)

   Type name: ZLAW_T_PERS

   You do not need to specify an application component and can ignore the warning “Application component is not active”.

3. Adjust the LAW plug-in (report RSLAW_PLUGIN) to the registered name, such as ZLAW_PERS, in the ABAP Editor.

               
   *----------------------------------------------------------------------*
               
   * Key of the LAW personalization object
               
   *
               
   * This key has to be adjusted when using the plugin in a release lower
               
   * than 6.40. Use the name that was registered using transaction PERSREG.
               
   DATA: g_pers_key TYPE ty_spers_obj-pers_key VALUE 'ZLAW_PERS'.
               
   *----------------------------------------------------------------------*