Hierarchy

⤷

⤷

IMG Activity
ID | MYOBJ_CATS_CMOD001 | CATS Worklist: Enhancement for Determining SY-UNAME |
Transaction Code | S_AXA_22000004 | (empty) |
Created on | 20020416 | |
Customizing Attributes | MYOBJ_CATS_CMOD001 | CATS Worklist: Enhancement for Determining SY-UNAME |
Customizing Activity | MYOBJ_CATS_CMOD001 | CATS Worklist: Enhancement for Determining SY-UNAME |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | MYOBJ_CATS_UNAME |
Use
myObjects uses the user name (SY-NAME) to personalize data. HR, however, uses the personnel number (PERNR). For this reason, the standard system determines the user name through info type 105 of the current personnel number. If no user name is defined in info type 105, the system uses the current user name.
Since it may not be sufficient in some cases to determine the user name through the personnel number, the BAdI MYOBJ_CATS_UNAME is provided for this purpose. This BAdI (SE18) provides method AT_UNAME_DETERMINE and enables you to determine the user name yourself. If the user name determined does not exist, the user name is determined in the standard way (see above).
Requirements
The BAdI method is implemented and the BAdI is activated.
Standard settings
The BAdI method has the following parameters:
- Import SAP_IMP_USER_NAME (user name from HR info type as per PERNR)
- Import SAP_IMP_PERNR (PERNR with which CATS was started)
- Import SAP_IMP_SY_UNAME (cur. SY-UNAME indep. of PERNR + HR-UNAME)
- Export SAP_EXP_SY_UNAME (deviating UNAME determined in the BAdI method)
Activities
Example
Business Attributes
ASAP Roadmap ID | 151 | Design interfaces |
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 | 20020503 |
SAP Release Created in |