Hierarchy
⤷ PSM-FM (Application Component) Funds Management
⤷ FMBS_ADDON (Package) FIFM: Basis (Add-On Objects)
IMG Activity
ID | _ISPSFM_FILTER_ITEMS | BAdI: Filter for Closing Open Items for Fiscal Year Change |
Transaction Code | S_ALN_01000503 | (empty) |
Created on | 20020103 | |
Customizing Attributes | _ISPSFM_OBLIGOVORTR | BADIs Commitment Carryforward |
Customizing Activity | _ISPSFM_FILTER_ITEMS | Filter for Closing Open Items with Fiscal Year Change |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FM_CCL_FILTER_ITEMS |
Use
With this Business Add-In you can include your own rules with the closing operations in Funds Management when closing open commitment, through which the quantity of document items that can be closed automatically is restricted even further. The program Closing Operations: Closing Open Items (RFFMCCLS) then only offers the document items to be closed that correspond to these rules.
Requirements
In the Customizing of Funds Management Government a valid update profile was assigned to the FM area and the commitment update in Funds Management is active.
Standard settings
In the standard, the Business Add-In is active, provided that you use update profile 000600 (budgetary ledger e.g. US Government). The default coding is carried out automatically and has the following effect:
When you execute program RFFMCCLS, the rules consulted for closing commitment are those that you defined in the Customizing of Funds Management Government, in step "Define Rules for Closing Commitment ". If a rule is defined for the fund type and the status of the fund, to which the document item is assigned, the affected document item can be closed by using program RFFMCCLS.
The Business Add-In is filter-dependent. Create the implementation for your update profile.
Activities
Create an implementation of the Business Add-In for your update profile provided that update profile 000600 is not assigned to your FM area. You do this as follows:
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
Notes
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 3 | Nonrequired 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 | 20020325 |
SAP Release Created in | 110 |