SAP ABAP IMG Activity /MRSS/SQP_DEM_EXIT (BAdI: Extend requirements profiles)
Hierarchy
☛
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
⤷
PM-WOC-MO (Application Component) Maintenance Orders
⤷
/MRSS/SQP (Package) MRS Qualifications: Profiles

⤷

⤷

IMG Activity
ID | /MRSS/SQP_DEM_EXIT | BAdI: Extend requirements profiles |
Transaction Code | /MRSS/35000054 | IMG activity: /MRSS/SQP_DEM_EXIT |
Created on | 20061108 | |
Customizing Attributes | /MRSS/SQP_DEM_EXIT | BAdI: Extend requirements profiles |
Customizing Activity | /MRSS/SQP_DEM_EXIT | BAdI: Extend requirements profiles |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /MRSS/SQP_DEM_EXIT |
Use
You use this BAdI to enhance the functions of the requirements profiles.
Requirements
Customer include CI_REQ_ADDN_ATTR has to contain the necessary additional attribute fields for the following methods:
- ADDN_ATTR_INITIALIZE
- ADDN_ATTR_BEFORE_OUTPUT
- ADDN_ATTR_AFTER_INPUT
Standard settings
The BAdI is not active in the standard shipment. It is not filter-dependent and cannot be used more than once.
The BAdI provides the following methods:
- GET_WHEREUSED_DATA : With this method, you can modify the where-used list of a specific requirements profile.
- ADDN_ATTR_INITIALIZE, ADDN_ATTR_BEFORE_OUTPUT, ADDN_ATTR_AFTER_INPUT: With these methods, you can edit the additional attributes of the requirements profiles.
- ADDN_ATTR_INITIALIZE is used to initialize the additional attribute fields that are displayed on the interface, based on the context from which the profile is called.
- ADDN_ATTR_BEFORE_OUTPUT and ADDN_ATTR_AFTER_INPUT are used to specify which additional attribute data is to be displayed on the user interface (during PBO and PAI).
- ADDITIONAL_CHECKS: With this method, you can specify the conditions under which the system prevents a requirements profile from being saved.
- NOTIFY_PROFILE_CHANGE: With this method, you can send notifications about changes to requirements profiles if the requirements profiles are currently in use.
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.
Example
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 | /MRSS/SQP_DEM_EXIT | 0 | HLB0009110 | Cross-Application Components |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20090903 |
SAP Release Created in | 195 |