Dynamic Select Query to get data

 TABLES: dd03l.

**********************************************************************

*                       Selection Screen

**********************************************************************

PARAMETERS:

  p_table TYPE tabname,

  p_row   TYPE sy-dbcnt.


SELECT-OPTIONS: s_field FOR dd03l-fieldname NO INTERVALS.

**********************************************************************

*                  Data Declaration

**********************************************************************


DATA:

  lo_dyn_data  TYPE REF TO data,

  lv_field     TYPE char24,

  lt_tab       TYPE TABLE OF char24,

  lv_success   TYPE abap_bool,

  lo_structure TYPE REF TO cl_abap_structdescr,

  lo_tabletype TYPE REF TO cl_abap_tabledescr,

  lt_comp      TYPE cl_abap_structdescr=>component_table,

  ls_comp      LIKE LINE OF lt_comp.



FIELD-SYMBOLS:

  <lt_tab>   TYPE ANY TABLE,

  <lt_table> TYPE ANY TABLE.


* Looping on select-options range and getting the low range to internal table.

LOOP AT s_field.

  SELECT tabname, fieldname FROM dd03l INTO TABLE @DATA(lt_field) WHERE tabname = @p_table AND fieldname = @s_field-low.

  IF sy-subrc = 0.

    lv_field = s_field-low.

    APPEND lv_field TO lt_tab.


    ls_comp-name = lv_field.

    ls_comp-type ?= cl_abap_datadescr=>describe_by_name( 'CHAR50' ).

    APPEND ls_comp TO lt_comp.


    CLEAR lv_field.

    CLEAR ls_comp.

  ENDIF.

ENDLOOP.


FIELD-SYMBOLS: <fs_table> TYPE ANY TABLE.



IF p_row < 0.

  MESSAGE s015(zin_message_cls) WITH p_row DISPLAY LIKE 'E'.

ELSE.


  DATA(lo_table) = NEW zin_cl_tab_data_fetch_dyn(  ).

  CALL METHOD lo_table->validate_table

    EXPORTING

      iv_tab = potable

    IMPORTING

      ev_val = lv_success.

  IF lv_success = abap_true.


    lo_structure = cl_abap_structdescr=>create( lt_comp ).

    lo_tabletype = cl_abap_tabledescr=>create( p_line_type = lo_structure ).


    CREATE DATA lo_dyn_data TYPE HANDLE lo_tabletype.

    ASSIGN lo_dyn_data->* TO <fs_table>.


    IF <fs_table> IS ASSIGNED.


      SELECT (lt_tab) FROM (p_table) INTO CORRESPONDING FIELDS OF TABLE <fs_table> UP TO p_row ROWS.


      IF sy-subrc = 0.


        cl_demo_output=>display_data(

          EXPORTING

            value   = <fs_table>

            name    = | Table : { p_table } |

        ).


      ENDIF.

    ENDIF.


  ENDIF.

ENDIF.

Comments

Post a Comment

Popular posts from this blog

MDG Derivation (BADI)

Image
In this blog, we will see how to derive MDG attributes using BADI. Derivations can be divided into two types.  Single-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from same entity. For this, we use 'USMD_RULE_SERVICE' BADI definition. Cross-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from another entity. For this, we use 'USMD_RULE_SERVICE_CROSS_ET' BADI definition. First, we will see a single entity derivation. Scenario:  We are going to make language English as the default if the user gives the country as India. Steps: 1. Go to SE18. 2. In 'USMD_RULE_SERVICE' BADI defination, create BADI Implementation.  3. For creating BADI Implementation, first we need to create Enhancement Implementation.  4. Give the properties as below. 5. Now, create BADI Implmentation and give following properties. 6. Maintain the filter values. H...
Read more

MDG Validation (Using BADI)

Image
In this blog, we will see how to validate the MDG attributes using the BADI implementation. So, we are taking the example of the 'BP Grouping' field to make it mandatory on the UI. For this, we should know the technical attribute name for the respective field. In our case, 'BU_GROUP' is the technical name for the BP grouping field. Steps for the Implementation of Validation BADI. 1.   Open T-code ‘MDGIMG’ –> General Setting -> Data Quality and Search -> Business Add-Ins -> Execute BADI: Define Validation/Derivation OR SE18 -> BADI name: 'USMD_RULE_SERVICE' -> Create BADI Implementation.  2. After execution, the following screen will appear. Go down, and there you will find the option to create enhancement implementation. Click on that button. 3. Provide the name and short description of the implementation, as follows:   4.  After that, we have to create the BADI Implementation and Implementation class. 5.  You will be directed to the Enha...
Read more

SAP MDG Process Modelling

Image
Overview In SAP MDG, every change to master data is initiated using a change request. After a change request is initiated, it needs to be processed before activation or rollback by applying governance rules and collaborations. The process model provides the required input (metadata) for change request creation and processing, e.g., workflow, CR steps, and objects that can be processes. Submit and activate/rollback are mandatory steps in a change request. MDG reuses the SAP Business Workflow component of an underlying SAP business suite. SAP MDG workflow is an instance of SAP Business Object BUS2250. If the request has parallel processing, then each parallel step of the change request will have one BUS2250 instance. Define Governance Scope: Here we can define governance scope on the entity as well as the attribute level. For example, we have kept ‘NO’ to the below custom entity. As a result of MDG UI, the UIBB for this entity will only be in read-only mode. Business Object An ...
Read more