What is badi implementation

Now all fields are accessible via their corresponding field-symbols. All kinds of calculations and manipulations can be executed using these field-symbols. Data disaggregation is a perfect example for this. In BPC data can be entered at parent level and then this data can be distributed across its children prorated to the existing data.

This makes most sense for dimensions like entity and time. The following code retrieves the hierarchy information for entity and is also repeated for the time component. Data is disaggregated pro rata to existing data. So we need to look up the existing data that corresponds to the data coming from the BPC application. This is achieved by launching a RSDRI query, which requires a list of dimensions to be returned and the list of filters to be applied.

First step is to retrieve the cube metadata. If the processed line is a parent, we need to get its children to be able to distribute the data across the children afterwards. Remember, as mentioned earlier this is not a multiple use BADI?

This basically just means that you can only have one implementation active at any one time. Then try activating this, you would get the error message that there are implementations already active. Ignore the fact that it says active at the top of the screen. Please enter the name of the enhancement implementation and a short description before you press Enter. Now, within the extension implementation that has just been set up, a BAdI implementation can be created.

Please enter the name of the BAdI implementation and the name of respective class, which carries the logic. Depending on your operation area, you can select one of the BAdI definitions described above. Your business logic is to be implemented inside methods of the class. The structure of methods is inherited from the BAdI definition you selected. However, the business logic is not executed until the filter criteria are met.

In the Filter Values section you can define criteria to ensure the class is executed for a specific table name and table type only.

This is because implementing the taxes for different countries most probably belongs to different projects and because the structure of the simple enhancement implementations must mirror the project structure. When instantiating a single-use BAdI, you have to make sure that only one implementation comes into effect at runtime.

What you need now is a way to select among different BAdI implementations. That can be easily done with filters. For more information, see How to Use Filters. Create a Container for the Implementation. To create a container that is uniquely assigned to the enhancement spot to which your BAdI belongs, proceed as follows: In the Object Navigator transaction SE80 , open the enhancement spot you have already created and choose the Create Enhancement Implementation pushbutton.

In the new dialog that appears, create an enhancement implementation: The following new window opens: What are you asked to enter here? Note Select the property Implementation is active in the Runtime Behavior pane in the figure above. Now that you have a BAdI implementation, you need an implementing class.

Choose the triangle in front of the name of the BAdI implementation in the tree.