Hierarchy
⤷ BW-BCT-ISR-AA (Application Component) Analytical Applications
⤷ RS_BCT_RETAIL_TLOG_MINING (Package) Affinity Analysis
IMG Activity
ID | RSBCT_TLOGM_TASK | Implement Single Task for Postprocessing |
Transaction Code | S_B73_57000047 | (empty) |
Created on | 20080128 | |
Customizing Attributes | RSBCT_TLOGM_TASK | Implement Single Task for Postprocessing |
Customizing Activity | RSBCT_TLOGM_TASK | Implement Single Task for Postprocessing |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RSBCT_TLOGM_TASK |
Use
This Business Add-In (BAdI) is used in the component BW-BCT-ISR-AA (Retail Analytical Applications).
Using this BAdI, you have the facility to carry out postprocessing of the results of the affinity analysis. In particular, you have the opportunity to extend the rules with further characteristics and further key figures.
Requirements
This BAdI can only be used if you simultaneously implement the BAdIRSBCT_TLOGM_TASKLIST. Whereas the BAdI RSBCT_TLOGM_TASKLIST is responsible for the assignment of allowed tasks to analysis configurations, you use this BAdI to store the program logic for executing a single postprocessing task.
Standard settings
The BAdI is filter-dependent and is not multiple-use. As BAdI filter, the code of the task is used in each case.
There is no default implementation. No postprocessing of the analysis results is carried out.
Activities
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 | 257 | Create User Exits |
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 | RSBCT_TLOGM_TASK | 0 | B520000055 | Retail and Consumer Goods |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20080128 |
SAP Release Created in | 703 |