Hierarchy

⤷

⤷

IMG Activity
ID | SIMG_BADIFMSG | BAdI: Control Postings Using Master Data Attributes |
Transaction Code | S_P2U_59000002 | (empty) |
Created on | 20030905 | |
Customizing Attributes | SIMG_BADIFMSG | BAdI: Control Postings Using Master Data Attributes |
Customizing Activity | SIMG_BADIFMSG | BAdI: Control Postings Using Master Data Attributes |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FMFG_FUNDMSG_DRV_DEF |
Use
Use this BAdI to perform additional validations in the posting process into Funds Management (FM). It is foreseen that additional authorization checks are carried-out depending on master data attributes like a fund or fund center status. With this BAdI you can set up the rules governing the nature and severity of messages when controlling specific postings.
The rules use source fields selected from the following:
- Fund
- Funds center
- Commitment item
- Funded program
- Grant
- User
- Fund's status
- Fund type
- GL account
- Commitment item
- Message variables
- Amount type
- Value type
The target fields for the rules are selected from the following:
- Message class
- Message severity
- Message number
Requirements
Standard settings
Activities
- Select the Create icon.
- In the dialog box, enter a name (Z_ABC_123) for the BAdI implementation in the Implementation Name field and press Enter.
- The screen for changing the BAdI implementations is now displayed.
- Enter a short text for the implementation in the Implementation Short text field.
- Choose the Interface tab.
- You can implement check rules as ABAP code, but implementation with the formula builder as described below is usually easier.
- Change the Implementation Type to Formula.
- Save your entries, and assign the implementation package to a customer development class .
- Provide transport information.
- Use the developer's key to proceed and save.
- Double click the method name to enter method processing.
- Choose the "Create Condition" icon.
- Enter a name for the first rule and press Enter.
- Change the "Show Me" fields to Parameters - Controlling Postings with Master Data Attributes
- Create the first rule # (Condition 1) and (Condition 2).
- Expand the subtree.
- Double click "True".
- Select "Create Exception"
- Enter the message number, message class, and message type. If you enter message type "Warning" or "Error" and leave the other fields empty, a default message of the specified type is issued.
- Repeat the above process for any additional rules and conditions.
- Choose Activate for this implementation.
The code you stored in the method will be run when the application program is executed.
Further notes
This BAdI can also be implemented with ABAP code. If there is the need to check authorizations for a given user under specific conditions for certain master data attributes, an authorization object should be created and evaluated at this calling point. SAP recommends the use of customer authorization objects to perform any detailed role-user dependent controls.
In previous releases, tables FMUSERGROUP and FMGROUP supported a grouping of users for specific checks within this BAdI. Although this functionality could still be used, the use of authorization objects is preferred and recommended.
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 | 20050623 |
SAP Release Created in | 200 |