Hierarchy
⤷ FIN-CGV-MIC (Application Component) Management of Internal Controls
⤷ FOPC_REPORTING (Package) Reporting
IMG Activity
ID | FOPC_REPORT_WEIGHT | BAdI: Weighting of a Report Line During Aggregation |
Transaction Code | S_QE6_02000007 | (empty) |
Created on | 20040616 | |
Customizing Attributes | FOPC_REPORT_WEIGHT | BAdI: Weighting of a Report Line During Aggregation |
Customizing Activity | FOPC_REPORT_WEIGHT | BAdI: Weighting of a Report Line During Aggregation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FOPC_REPORT_WEIGHT |
Use
This Business Add-In (BAdI) is used in reporting for the Management of Internal Controls (FIN-CGV-MIC) component.
You can use this BAdI to specify for hierarchical reports how the ratings should be aggregated. The BAdI enables you to give individual report lines greater weighting than others.
Requirements
Standard settings
The following implementations are delivered for this BAdI:
- Active: Calculate Weight from Control Significance (FOPC_REPORT_W_SIG)
- Inactive: Return Weight = 1 for Every Line (FOPC_REPORT_WEIGHT_1)
Activities
If you want to create your own implementation, proceed as follows:
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
The following example demonstrates another possible implementation other than the delivered implementations. In this example, all entries at control level are weighted with 1, and all other entries at higher levels are weighted with 0. This means that process design ratings and management control ratings are ignored and only the ratings for controls (control design ratings or control efficiency ratings) are included in the aggregation.
if is_report-s_key-control is initial.
e_weight = 0.
else.
e_weight = 1.
endif.
See also:
Method
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 | FOPC_REPORT_WEIGHT | 0 | XS40000002 | Management of Internal Controls |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20040617 |
SAP Release Created in | 100 |