851741 - System measurement: Standard user type

Symptom
The measurement terminates because a standard user type is not preassigned for non-classified users.


Other Terms
LAW, License-Admin, USMM


Reason and Prerequisites
When you select several price lists, or when you select the individual solution price list, a standard user type cannot be determined.


Solution
A solution is provided in the relevant Support Package or correction instructions.


The following Support Packages:

SAPKB46C54
SAPKB62063
SAPKB64020
SAPKB70012

implement a function that allows you to select a standard user type if a standard user type cannot be determined automatically. This selection option is available on the "Price Lists" tab in transaction "USMM".

As of Support Packages:

SAPKB46B61
SAPKB46C53
SAPKB46D44
SAPKB61047
SAPKB62060
SAPKB64018
SAPKB70010

the implementation contained in this note is already implemented. You then only have to maintain the TUCON entry (see below).


Implement the release-dependent objects and then make the program changes in accordance with the correction instructions.

You must also make an entry in the "TUCON" table.

Caution: Consider upper case/lower case letters
  • Call transaction SE16, enter table: "TUCON" -> choose F8, table entry-> Create

    • SYM_GRP    SYM_KEY      SYM_VAL
    Usertypes  Def UType    <ID>

In the SYM_VAL field, enter the 2-digit ID for the required standard user type.
The identification of the standard user type to be entered depends on the contract layout and it must be selected from the following "Professional users":
  • 52 (mySAP Professional) for a mySAP Business Suite contract
  • AX (mySAP ERP Professional) for a mySAP ERP contract
  • AA (mySAP CRM Professional) for a mySAP CRM contract
  • AC (mySAP SCM Professional) for a mySAP SCM contract
  • AE (mySAP SRM Professional) for a mySAP SRM contract
  • AH (mySAP PLM Professional) for a mySAP PLM contract

Create the maintenance report for table TUCON
If maintenance is not possible due to the table settings, you can also enter the values using a report.
For that, call transaction SE38 and create an "Executable program" with the name "Z_DFLT_UTYPE". Save the report as a Local Object.
In the editor, transfer (cut and paste) the following lines:
***********************************************************
parameters: utyp type usertypen.
TABLES: TUCON.
delete from tucon where sym_grp = 'Usertypes'
       and sym_key = 'Def UType'.
tucon-sym_grp = 'Usertypes'.
tucon-sym_key = 'Def UType'.
tucon-sym_val = <ID>.

insert tucon.
***********************************************************
Then activate the report.
Manual activities
Due to the complexity of the enhancement, manual activities are required in lower releases.
  • 7.00 No manual activities required
  • 6.40 No manual activities required
  • 6.20 No manual activities required
  • 6.10
  • Create DDIC structure DUT_STATUS.
                    Transaction SE11->: Data type "DUT_STATUS" -> create
                      Attributes: Package "SLIM"
                      Components:
Component    Component type
STATUS       MSGNR
COUNTER      NUMC05

  • Create DDIC structure DUT_LIST.
                    Transaction SE11->: Data type "DUT_LIST" -> Create.
                      Attributes: Package "SLIM"
                      Components:
Component    Component type
CLIENT       MANDT
DE_UTYPE     USERTYPEN
P_FLAG       CHAR1

  • Create function group "SLIM_USER_TYPES".
                    Transaction SE37 ->Go to ->Function Groups ->Create group.
                    Save:  Package "SLIM"
  • Create function module "SLIM_GET_DEFAULT_USER_TYPES".
                    SE37: Function module "SLIM_GET_DEFAULT_USER_TYPES" ->Create.
                    Function group: "SLIM_USER_TYPES"
                    Package: "SLIM"
                     Export parameter:
Parameter name  Type spec  Associated type
DFTL_USR_STATUS TYPE       DUT_STATUS
                     Tables:
Parameter name  Type spec  Associated type
DFTL_USR_TYPES  LIKE       DUT_LIST

  • 4.6D and 4.6C:
  • Create DDIC structure DUT_STATUS.
  • Create DDIC structure DUT_LIST.
  • Create function module "SLIM_GET_DEFAULT_USER_TYPES".
                    Transaction SE37: Function module "SLIM_GET_DEFAULT_USER_TYPES" ->Create.
                    Function group: "SLIC"
                    Package: "SLIM"
                     Export parameter:
Parameter name  Type spec  Associated type
DFTL_USR_STATUS TYPE       DUT_STATUS
                     Tables:
Parameter name  Type spec  Assoicated type
DFTL_USR_TYPES  LIKE       DUT_LIST
Note:
If you cannot implement this note automatically, you can simply insert the source code in the split-screen editor, since it is new source code.



Header Data
Released On 09.01.2008 14:36:52
Release Status Released for Customer
Component XX-SER-LAS License Auditing Services
Priority Correction with medium priority
Category Program error


Validity
Software Component
From Rel.
To Rel.
And Subsequent
SAP_BASIS
46B
46D
 
610
640
 
700
700
 


Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46C
46C
46D
46D
610
610
620
620
640
640
700
700


Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
610
46C
46B
46D
640
620
46C
640
700
620


References
This document refers to:
SAP Notes
896872   System measurement: Additional default user category
982708   LAW: ABAP runtime error when downloading
862182   System measurement: Standard user type
This document is referenced by:
SAP Notes (3)
982708   LAW: ABAP runtime error when downloading
862182   System measurement: Standard user type
896872   System measurement: Additional default user category
Posted by

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)