SAP ABAP IMG Activity SIMG_BADI_GMDERIVE (BAdI: GM Derivation Tool)

Hierarchy

☛ EA-PS (Software Component) SAP Enterprise Extension Public Services
   ⤷ PSM-GM-GTE (Application Component) Grantee Management
     ⤷ GMBASIS_E (Package) Grants management (basis)

IMG Activity

ID	SIMG_BADI_GMDERIVE	BAdI: GM Derivation Tool
Transaction Code	S_ALN_01002365	(empty)
Created on	20031103
Customizing Attributes	SIMG_BADI_GMDERIVE	BAdI: GM Derivation Tool
Customizing Activity	SIMG_BADI_GMDERIVE	BAdI: GM Derivation Tool

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	BADI_GMDERIVE

Use

SAP provides methods that enable further customize the behavior of the Grants Management (GM) derivation tool. You must create an implementation using the following predefined methods:

• CHECK_DRULE_BEFORE_SAVE
• CHECK_DRULE_ENTRY
• GET_STRATEGY
• STEP_ACTIVITY_CHECK
• STEP_CHECK_ON_ENTER
• STEP_CHECK_ON_EXIT
• SET_DISPLAY_MODE
• STEP_DRULE_ACTIVITY_CHECK
• SET_STRATEGY_BUTTONS
• Derive

Requirements

Standard settings

We do not deliver any standard settings.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

   The screen for creating BAdI implementations is now displayed.

2. Enter a short text for the implementation in the Short text for implementation field.
3. From the tab index, choose Interface.

   The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

4. Save your entries, and assign the implementation to a development class.
5. Place the cursor on the method, and double-click to enter method processing.
6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your code. Return to the Edit Implementation screen.
8. Save the entries on the Edit Implementation screen.

   Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

9. Choose Activate

   The code you stored in the method will be run when the application program is executed.

Example

(1) You use the method CHECK_DRULE_BEFORE_SAVE to prevent users from deleting assignments.

*---- Check if table is initial

DESCRIBE TABLE I_TAB_DELETED_ENTRIES lines sy-tfill.

IF NOT sy-tfill is initial.

* Raise MESSAGE not allowed to delete entries

e_reject = 'X".

ENDIF.

(2) You use the method CHECK_DRULE_BEFORE_SAVE to check specific rule IDs.

CASE i_stepid

WHEN 'AAA'.

* Specific Check for Step ID 'AAA'

WHEN OTHERS.

ENDCASE.

Business Attributes

ASAP Roadmap ID	204	Establish Functions and Processes
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	20081219
SAP Release Created in	500