Hierarchy
⤷ PPM-PFM (Application Component) Portfolio Management
⤷ RPM_IMG (Package) RPM IMG Objects
IMG Activity
ID | RPM_CREATEUSR_NAME | BAdI: Generate User Name |
Transaction Code | S_PCC_47000061 | (empty) |
Created on | 20060725 | |
Customizing Attributes | RPM_CREATEUSR_NAME | BAdI: Generate User Name |
Customizing Activity | RPM_CREATEUSR_NAME | BAdI: Generate User Name |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RPM_CREATEUSR_NAME |
Use
This Business Add-In (BAdI) is used in the Portfolio Management (PPM-PFM) component.
You can use this BAdI to generate a user name and a password for the R/3 user creation transaction RPMUSER, based on specific requirements.
Requirements
To use this BAdI, you have set the indicator value for Password assignment to Exit module for user name and password.
- You do this by choosing transaction RPMUSER.
- In the opening screen of this transaction, select Change user attributes/Key date. This opens the Attributes of users window.
- In this window select the Password Assignment as 'Exit module for user name and password''.
- To save the changes, choose Execute.
Standard settings
- In the standard system, there is no activated BAdI implementation.
- The BAdI is not designed for multiple use.
- The BAdI is not filter-dependent.
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:
- 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. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- 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.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - 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: - Choose Activate.
When the application program is executed, the code you created is run through.
See also
Method
Example
The sample implementation RPM_USER_NAME provided with the standard release has a sample code for name generation.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | RPM_CREATEUSR_NAME | 0 | /RPM/XSD0000011 | Portfolio Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20060725 |
SAP Release Created in | 400 |