SAP ABAP IMG Activity SIMG_GM_BADI_GTCOPY (BAdI: Override Copied Data from Reference Grant)
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_GM_BADI_GTCOPY BAdI: Override Copied Data from Reference Grant  
Transaction Code S_ALN_01002614   (empty) 
Created on 20040115    
Customizing Attributes SIMG_GM_BADI_GTCOPY   BAdI: Override Copied Data from Reference Grant 
Customizing Activity SIMG_GM_BADI_GTCOPY   BAdI: Override Copied Data from Reference Grant 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GM_COPY_GRANT    

Use

When you create a grant as a copy of an existing grant, most, but not all data is transferred to the target grant. The following source grant data is not copied to the target grant:

  • Grant type
  • Sales order
  • Grant status
  • Modification and creation date
  • Workflow status
  • Application log data
  • Records Management linkage

The new grant gets the current date as creation date and source grant number as the copy_source. If this is inadequate for your purposes, you can use this BAdI to modify the defaults.

The importing parameters I_SOURCE_XXX represent all of the data contained in the source grant. The changing parameters C_TARGET_XXX represent all the data that has been proposed for the target grant. If you do nothing in the BAdI, you will retain the default behavior. Any changes to the changing parameters will be displayed in the newly created grant. Keep in mind that it is possible that some data will be changed again due to sponsor defaults.

Requirements

You are using Grants Management (GM) and want to create grants by copying from a reference grant. However, you want to modify the default copy behavior.

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

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  20040115 
SAP Release Created in 500