Hierarchy

⤷

⤷

IMG Activity
ID | /ISDFPS/FUNDC_DERIVE | BAdI: Define Funds Center Derivation |
Transaction Code | /ISDFPS/54000039 | (empty) |
Created on | 20040206 | |
Customizing Attributes | /ISDFPS/FUNDC_DERIVE | BAdI: Define Funds Center Derivation |
Customizing Activity | /ISDFPS/FUNDC_DERIVE | BAdI: Define Funds Center Derivation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /ISDFPS/FUNDC_DERIVE |
Use
With this Business Add-In (BAdI), you can define the procedure for deriving one or more funds centers from the force element attributes.
The funds center is used to:
- Display the funds center master record in the force element
- Display the funds center in the accounting check routines (status network of the Structures Workbench)
You can derive the procedure for your own implementation from the default code provided. The method provided requires the force element master record (type: /ISDFPS/FORCE) as an import parameter, a table is exported from /ISDFPS/FM_FUNDCENTER_KEY_T (financial management area and funds center).
Requirements
The BAdI is active in the standard system. If you do not create your own BAdI implementation, the BAdl definition default code is executed automatically.
The following functions are available:
- Determining the WBS element in the force element (if available)
- Determining the cost center in the force element (if no cost center has been assigned, the superior or inherited cost center is used)
- Transferring the WBS element and/or cost center to data structure FMDERIVE
- Determining a suitable funds center derivation using the R/3 standard function module FM_ACCOUNT_DERIVE. The funds center derived depends on the strategy sequence: WBS element -> cost center or cost center -> WBS element)
- Transferring the funds center to data structure COBL
- Transferring the financial management area and the funds center to the export parameter as a single record (table of type /ISDFPS/FM_FUNDCENTER_KEY_T).
In the present default code, only one funds center is determined. Several funds centers are possible.
You maintain the strategy in the force element on the Accounting tab page by navigating to transaction FMDERIVE (derivation strategy).
Standard settings
If you do not create an implementation, the default code is executed.
Activities
If you require a different function for deriving funds centers, create your own implementation.
Note:
You can also control the derivation function of your BAdI using the enhancement feature in transaction FMDERIVE. To do so, create an enhancement (EXIT_SAPLFMDT_001) that is executed in the BAdI when function module FM_ACCOUNT_DERIVE is executed.
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /ISDFPS/FUNDC_DERIVE | 0 | /ISDFPS/KL10000012 | Force Element |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040206 |
SAP Release Created in | 470 |