Hierarchy
⤷ PSM-GM-GTE (Application Component) Grantee Management
⤷ GMBASIS_E (Package) Grants management (basis)
IMG Activity
ID | SIMG_GM_BADI_EXTCHK | BAdI: Extended Check for Object Mapper |
Transaction Code | S_AEN_10000379 | (empty) |
Created on | 20050207 | |
Customizing Attributes | SIMG_GM_BADI_EXTCHK | BAdI: Extended Check for Object Mapper |
Customizing Activity | SIMG_GM_BADI_EXTCHK | BAdI: Extended Check for Object Mapper |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | GM_OM_EXT_CHK |
Use
This Business Add-In (BAdI) enables you to specify additional validations of entered posting object mappings. The default is to check against budget and posting activity and disallow mappings in which individual postings overlap with mapped postings. With this BAdI, you can to alter the default as well as add additional verifications.
Requirements
You use passthrough funding and want to enhance (or reduce) the verifications on mapped Grants Management (GM) combinations.
Standard settings
Activate the additional checks for a certain checking view. The system contains a Master Data, Budget and Billing checking view for additional checks. The Posting Object Mapper is classified under the Master Data view. Enable the additional checks in BAdI method DO_CHECK. The actual checks are placed in the RUN_MORE_CHECKS method.
Activities
Create implementations to both methods as described below. The additional checks can be enabled with method DO_CHECK; method RUN_MORE_CHECKS then contains the coding for the additional verifications.
Form CHECK_TO_GRANT in function module GM_OM_CHECK_MAPPED_OBJECTS provides a coding reference for additional checks.
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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Example
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
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 | 20050207 |
SAP Release Created in | 600 |