Hierarchy
⤷ CRM-ISA (Application Component) Internet Sales
⤷ AD01 (Package) B2R: Bapi Structures
IMG Activity
ID | BADI_SAPLAD15_RRB_OP | BAdI: Resource Related Billing Optimization |
Transaction Code | S_EBJ_98000251 | (empty) |
Created on | 20130212 | |
Customizing Attributes | BADI_SAPLAD15_RRB_OP | BAdI: Resource Related Billing Optimization |
Customizing Activity | BADI_SAPLAD15_RRB_OP | BAdI: Resource Related Billing Optimization |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BADI_SAPLAD15_RRB_OPTIMIZATION |
Use
This Business Add-In (BAdI) is used in the Project System - Revenue and Billing (PS-REV) component. You can use this BAdI to achieve Resource Related Billing (RRB) optimization.
This optimization is applicable only for the source #Actual Costs # Line Items#. The optimization is used to group data by fields of the COVP table and aggregating them. Therefore, the level of optimization depends on the fields that are used for grouping (These fields are maintained in the DIP Profile as relevant characteristics). For example, if the fields Document Number and Posting row are relevant characteristics, the selected records are unique. Therefore, the grouping of data does not occur when Document Number and Posting row need to be fetched.
Since this optimization comes with a few restrictions, you need to explicitly maintain the DIP profiles for which optimization needs to be enabled. This is achieved by implementing the corresponding BAdI method CHECK_OPTIMIZATION.
Prior to optimization, the data was fetched from all fields of the COVP table. Post optimization, data will be fetched from few fields based on the profile maintained in the Dynamic Item Processor (DIP) Profile.
For RRB, there are three types of fields that can be fetched from the COVP table:
- Fields that can be used directly. For example, Object Number.
- Fields that need to be derived. For example, Period is derived from fields
PERIO
andGJAHR
. - Fields that require data from COVP as input for further processing. For example, Category ID, Business Area.
- For this category, you can use the corresponding BAdI method GET_COVP_FIELDS where you can provide the list of fields for which data needs to be fetched from the COVP table.
Performance improvements are expected to arise from:
- Aggregation of data on database level instead of ABAP server level.
- Reduced volume of data transferred from the database to the ABAP server.
Requirements
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
BAdI Definition
- BADI_SAPLAD15_RRB_OPTIMIZATION
Activities
Example
See also
BAdI method documentation:
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 |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20130212 |
SAP Release Created in |