SAP ABAP IMG Activity SIMG_PSM_GTE_CONSIST (BAdI: Budget Document Consistency Check)
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_PSM_GTE_CONSIST | BAdI: Budget Document Consistency Check |
Transaction Code | S_P7U_18000002 | (empty) |
Created on | 20051024 | |
Customizing Attributes | SIMG_PSM_GTE_CONSIST | BAdI: Budget Document Consistency Check |
Customizing Activity | SIMG_PSM_GTE_CONSIST | BAdI: Budget Document Consistency Check |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_PSM_GTE_CONSIST |
Use
Use this step to implement the enhancement for non-standard budget document validations to be carried out before you post a budget document in Grantee Management (GM-GTE). The sample code for this BAdI illustrates how you can include messages in the standard log of the budget workbench. If an error then occurs, an appropriate message describes the problem.
The parameters of the BAdI method are as follows:
- I_F_HEADER: Importing parameter with data of the header document
- I_T_LINES: Importing parameter with GM-GTE detail data
- I_T_FYD_LINES: Importing parameter with Funds Management (FM) detail data if there is any (if FM integration is active in the award phase)
- I_REF_LOG:Changing parameter to append messages to the budget workbench log
- This BAdI is designed to code any number of validations that will be executed sequentially, allowing you to structure a series of validations.
Import parameters are "read only" so that the implementations do not change any value.
Requirements
Standard settings
Activities
After you call up the IMG activity, a dialog box appears:
- In the dialog box, enter a name for the enhancement implementation, Short Text and Composite Enhancement Implementation. If no Composite exists, create a new one by choosing Create button.
- Save your entries, and assign the implementation to a development class.
- Click on BAdI tab and choose the Create BAdI button.
- In the dialog box, enter BAdI Definition, BAdI Implementation, Implementation Class and description, then press Enter.
- In the left panel on the next screen, expand implementation node and double-click on entry 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> and endmethod. Note that sample implementation is copied automatically.
- Save and activate all the objects.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_PSM_GTE_CONSIST | 0 | ALN0000199 | Budgeting and Availability Control |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20051024 |
SAP Release Created in |