Ansicht
Dokumentation

BW_BADI_BBS2 - BAdI: dynamic determination of jump targets at runtime

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

This BAdI interface allows you to dynamically enhance the context menu for the jump targets from a BEx report by adding jump targets to the ones defined in transaction RSBBS.

This means that the context menu cannot be enhanced until runtime, depending on the column, row, cell content (and key figure value), query or InfoProvider.

Create an implementing class.

Method IF_RS_BBS_BADI_DYNAMIC~GET_TYPES asks which instances of classes that use interface IF_RS_BBS_BADI_HANDLER_DYNAMIC need to be considered in order to build the dynamic context menu. You can further restrict the instances by filtering the query name and InfoProvider name.

If no instances are returned, the dynamic context menu will not be displayed during the scenario. The only jump targets added to the context menu will be ones from transaction RSBBS with checkbox #Dynamic Only# deselected.

Every time the dynamic context menu is called for any instance defined with IF_RS_BBS_BADI_DYNAMIC~GET_TYPES, method IF_RS_BBS_BADI_HANDLER_DYNAMIC~GET_TARGETS asks which jump targets need to be displayed. You can restrict the display by query name, InfoProvider name or mapping. For an example of possible restrictions, see example implementation class CL_RS_BBS_BADI_DYNAMIC_EXMPL.

Methods IF_RS_BBS_BADI_HANDLER_DYNAMIC~CALL_URL, IF_RS_BBS_BADI_HANDLER_DYNAMIC~CALL_BATCH and IF_RS_BBS_BADI_HANDLER_DYNAMIC~CALL_SAPGUI are called either by URL, batch or SAPGUI depending on the scenario when you select a jump target.

Program your jump logic here.

Example implementation class CL_RS_BBS_BADI_DYNAMIC_EXMPL.

Example implementation class CL_RS_BBS_BADI_DYNAMIC_EXMPL.

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 1856 Date: 20240524 Time: 015030     sap01-206 ( 40 ms )