Hi Paul,
This may be helpfull for you.
list of the Business Add-Ins present in your system can be found either in the IMG or in the component hierarchy. The enhancements' names and corresponding documentation should help you decide which add-in you want to create an implementation for. During implementation creation, a class for implementing the enhancement's interface is also created. Implementations are discrete transport objects and lie within the namespace of the person or organization implementing them.
In order to create an implementation for the string conversion example, the add-in (in this case, the interface's method) needs to be filled with logic that converts the string. This logic will be run through every time the add-in is called from the application program.
To create an implementation, proceed as follows:
Choose ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE19) from the SAP menu or double-click on the corresponding activity in the Implementation Guide.
Enter a name for the implementation and choose Create.
Enter the name of the add-in you want to create an implementation for in the dialog box that appears.
Enter a short text describing your implementation on the following screen.
Choose the Interface tab.
Choose ABAP Code as the implementation type.
Besides ABAP Code, there is also the Formula option. If you choose Formula, the content of a method is determined using the Formula Builder. For more information on this, see Implementing Methods Using the Formula Builder.
Navigate to the Class Builder by double-clicking the method. You must first enter a package before the Class Builder is displayed.
Insert the desired source code for the implementation between the method if_ex_businessaddin~method. and endmethod. statements automatically provided to you by the system.
Enter the statement translate parameter to upper case. for the string conversion example.
Save your entries and return to the Change Implementation screen.
Choose Activate. You may now use this implementation when the application program is executed.
Numerous implementations may exist for a Business Add-In that cannot be used on a multiple basis. However, only one implementation can be active for these kinds of Business Add-Ins at any one time.
What is also important is that you must declare the instance generation of the implementing class (Attributes tab) as public and not as private or even abstract. If you do this, the system will return short dumps at runtime.
This Business Add-In (BAdI) is used in the SAP Business Information Warehouse in the component BW: Batch Reporting (BW-BEX-RSRB).
With the Business Add-In RSRA_ALERT, you can export BW alerts. This BAdI is a standardized interface for ABAP sources that enables partners and customers to enhance SAP-delivered programs in their namespace. Therefore, the SAP original objects from the customer-specific enhancements and the changes made in the SAP system (perhaps with Release changes) remain untouched.
You can implement the BAdI RSRA_ALERT several times and use a filter value for a certain InfoProvider to specifically define it.
Prerequisites
You have assigned the Export follow-up action to an exception.
You have specified a filter value where applicable.
You can find additional information under Editing the Follow-Up Action: Export.
Standard Settings
General data:
Package: RSRB
Name of the generated BAdI class from the enhancement management: CL_EX_RSRA_ALERT
The following standard settings are taken from SAP pages for the definition of the Business Add-In:
The BAdI RSRA_ALERT is useful in several ways, which means you can implement it in several ways.
The BAdI RSRA_ALERT is filter-dependent (filter type: RSRA_S_BADI_FILTER), which means that you define the BAdI by using a filter value specifically for a certain InfoProvider.
Activities
In the SAP menu, choose Tools ® ABAP Workbench ® Utilities ® Business Add-Ins ® Implementation (transaction SE19) or the respective activity in the IMG. You arrive at the screen BAdI-Builder: Implementation Maintenance Entry.
Create an implementation with regard to the BAdI definition.
You need an implementation for every filter value. In this way, several filter values can use the same implementation.
Program the interface methods in the class builder.
Activate the implementation.
In order for application developers to include Business Add-Ins in their programs, they must define an interface for the enhancement in the SAP menu under Tools ® ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE18) and call this interface at the appropriate point in their application program. Customers can then select the add-in and implement it according to their needs.
Example:
You want to be able to convert strings in your application program. You also want users to determine how their strings are converted themselves. As the application developer, you define an enhancement consisting of an interface with a method. A changing parameter is used to transfer strings.
To create an add-in like this, proceed as follows:
Choose Tools ® ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE18) from the SAP menu.
Enter a name for your Business Add-In containing a maximum of 20 characters.
Choose Create.
On the subsequent screen, enter a short description for your Business Add-In.
The option SAP internal is used when a developer at SAP provides a business add-in with implementations. If this flag is set, customers cannot create and use their own implementations for this business add-in. The possible entries help does not display business add-ins carrying this flag.
If this enhancement is going to be used multiple times or if you want its implementation to depend on a specific filter value, select the appropriate checkbox in the category Type. More information about multiple use and filter dependency can be found in the sections Multiple Use Business Add-Ins and Filter-Dependent Business Add-Ins .
This example only deals with basic enhancements, therefore neither of these checkboxes should be selected.
Choose the Interface tab.
The name of the interface, which is generated automatically, now appears. At this time, you can change the name of the interface if you so desire.
On the Fcodes tab you can create menu enhancements. For information on this, see Menu Enhancements.
On the Subscreens tab you can define screen enhancements. For information on this, see Screen Enhancements.
Double-click on the interface's name field. The system branches to the Class Builder.
Confirm that you want to save the entries you have made. Assign your add-in to a package.
Use the Class Builder to assign a method to the interface.
Now define a parameter with the following attributes:
Save and activate your changes. Use the pushbutton Back to navigate back to Business Add-In definition.
If you do not activate your attributes in the Class Builder, the system will not allow you to proceed with Business Add-In definition.
A table control now appears on the definition screen containing the method you have assigned to the interface.
Whenever you assign a method to an interface, the corresponding executing class is generated. The code generated cannot be altered in the initial expansion phase.
Save your entries and use the Def.-Docu. pushbutton to create a description for your new Business Add-In. Be aware that this documentation is of great importance in helping end users understand the purpose of your add-in.
Changes made to the interface and changes made to the Business-Add-In definition are always incompatible!
If implementations already exist for a Business-Add-In definition, they are invalidated if you make changes to the interface. This means that their syntax is no longer correct. No statements can be given on the runtime behavior. Try to absolutely avoid making changes to the interface or the Business-Add-In definition after the transport has taken place.
If changes to the interface are inevitable, clean up the method includes for all implementing classes, that is, all classes for which Business-Add-In implementations are used. To do this, in the Class Builder (using transaction SE19, tab Interface, field Name of implementing class) choose Utilities ® Clean up ® Method includes.
Default and Sample Code
In the BAdI Builder, you can choose the Goto menu entry to create, display, change and delete default or sample code.
The default implementation is only executed if no other active implementation is available. This applies also to filter-dependent Business Add-Ins.
It may usefull for you Paul.
Thanks,
Bhima Chandra Sekhar G
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.