Hierarchy

⤷

⤷

IMG Activity
ID | _ISPSFM_N_BCS_BADI04 | BAdI: Enhance Budget Line Items |
Transaction Code | S_ALN_01000572 | (empty) |
Created on | 20020115 | |
Customizing Attributes | _ISPSFM_N_BCS_BADI04 | BAdI: Enhance Budget Line Items |
Customizing Activity | _ISPSFM_N_BCS_BADI04 | BAdI: Enhance Budget Line Items |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FMKU_BUDGET_LINES |
Note:
The settings affected here are exclusively reserved for the use of the Budget Control System (BCS).
Title
Budgeting Interface : Add Lines / Substitute Data
Use
With this Business Add-In you can :
- Create additional lines in budget entry documents
- Substitute fields contained in the original lines
The corresponding methods are called in the kernel of the Budget Control System (BCS).
Standard settings
SAP offers a default implementation using the CO-PA derivation tool:
For both implementations use the CO-PA derivation tool. Source fields are derived to create target fields. Source fields and target fields are part of the fields contained in a line. For each methode you have to define your derivation strategy in the IMG activities:
Define Derivation Strategy for Additional Budget Line Items
Define Substitution for Entry Documents
Implementation of the method ADD_LINES:
The target fields are initialized with the values of the source fields. After this, processing depends on the derivation strategy involved. If the commitment item category has changed (for example, from expenditures to revenues), the signs of the values are reversed. If a target field is ultimately empty, but the corresponding source field is not "blank", a message is generated in the application log to warn the user.
Implementation of the method SUBSTITUTE_DATA:
The target fields are initialized with the values of the source fields. After this, processing depends on the derivation strategy involved. If a target field is ultimately empty, but the corresponding source field is not "blank", a message is generated in the application log to warn the user.
Activities
This is a single-use BAdI, meaning that only one implementation can be activated.
Now implement the BAdI applying the following steps:
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.
Further information
For further information on each method, see:
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
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 | 20030707 |
SAP Release Created in | 110 |