If you have a requirement to show some detailed data in an ALV Grid, there are two ways of doing it. You can create your dialog container and assign the grid to the dialog container.

SAP has made the job easier for us by giving a class

CL_RS_ALV_GRID_POPUP

However, the toolbar will NOT appear for this grid but you can have the layout and can chang the way you want it.

Here is the Class

The difference is, here you will have to pass the field catalog / structure which will have the column details, while creating the GRID object as against to doing it while displaying the data in the traditional CL_GUI_ALV_GRID class.

You can also specify the starting coordinates of the grid and width and height of the grid.

And here, while displaying the data, all you have to do is to pass the table, which has the data.

So, now we don't have to bother about creating a dialog container for showing a ALV grid as popup.

Here is a sample code for the same. I am calling this in the double click event of a MAIN ALV GRID.

-CARRID.

  ELSE.

    EXIT.

  ENDIF.

  CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'

   EXPORTING

•    I_BUFFER_ACTIVE              =

      I_STRUCTURE_NAME             = 'ALV_T_T2'

•    I_CLIENT_NEVER_DISPLAY       = 'X'

•    I_BYPASSING_BUFFER           =

•    I_INTERNAL_TABNAME           =

    CHANGING

      CT_FIELDCAT                  = T_FIELDCAT1

• EXCEPTIONS

•    INCONSISTENT_INTERFACE       = 1

•    PROGRAM_ERROR                = 2

•    OTHERS                       = 3

            .

  IF SY-SUBRC <> 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

•         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

  ENDIF.

  CREATE OBJECT W_POPUP_GRID

     EXPORTING

•    I_STRUCTURE_NAME =

       I_T_FIELDCATALOG = T_FIELDCAT1

•    I_S_LAYOUT =

•    I_CAPTION =

•    I_REPID =

•    I_DYNNR =

       I_LEFT = 10

       I_TOP  = 10

       I_HEIGHT = 300

       I_WIDTH = 300

      .

  CALL METHOD W_POPUP_GRID->SHOW_DATA

    EXPORTING

      I_T_DATA = T_DATA1.

  .

ENDFORM.                    " SHOW_DETAILS

</textarea>

Well, nothing exceptional, but definitely a handy one to reduce coding.

Have you scratched your head to do minor modifications (change the appearance of a column), add more fields to your output of an existing standard ALV report? I know most of us would have encountered this situation and finally ended up cloning the standard program and struggled with the changes to be done to get your requirements done.

Now, there is a way and the good thing is you do NOT have to copy the standard program. SAP has been kind of enough to provide a BADI which can be used just for this purpose. The BADI

ALV_GRID_XT

&----

*& Report  Y_RAVI_ALV_GRID_BADI

*&

&----

*&

*&

&----

REPORT  Y_RAVI_ALV_GRID_BADI.

DATA : T_DATA TYPE TABLE OF SFLIGHT,

       T_FIELDCAT TYPE LVC_T_FCAT.

DATA : W_CUSTOM_CONTAINER  TYPE REF TO CL_GUI_CUSTOM_CONTAINER,

       W_GRID TYPE REF TO cl_alv_grid_xt.

START-OF-SELECTION.

  SELECT * FROM SFLIGHT INTO TABLE T_DATA.

END-OF-SELECTION.

  CALL SCREEN 0100.

  INCLUDE Y_RAVI_ALV_GRID_BADI_STATUSO01.

  INCLUDE Y_RAVI_ALV_GRID_BADI_USER_CI01.

----

***INCLUDE Y_RAVI_ALV_GRID_BADI_STATUSO01 .

----

&----

*&      Module  STATUS_0100  OUTPUT

&----

•       text

----

MODULE STATUS_0100 OUTPUT.

  SET PF-STATUS 'ZALV_BADI'.

  SET TITLEBAR 'ZALV_BADI_TITLE'.

  IF CL_GUI_ALV_GRID=>OFFLINE( ) IS INITIAL.

    CREATE OBJECT W_CUSTOM_CONTAINER

           EXPORTING CONTAINER_NAME = 'ALV_BADI'.

    CREATE OBJECT W_GRID

        EXPORTING

          I_PARENT = W_CUSTOM_CONTAINER

I_GRID_ID = 'Y_RAVI_GRID_XT'.

  ENDIF.

  CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'

    EXPORTING

•     I_BUFFER_ACTIVE              =

      I_STRUCTURE_NAME             = 'SFLIGHT'

•     I_CLIENT_NEVER_DISPLAY       = 'X'

      I_BYPASSING_BUFFER           = 'X'

•     I_INTERNAL_TABNAME           =

    CHANGING

      CT_FIELDCAT                  = T_FIELDCAT

    EXCEPTIONS

      INCONSISTENT_INTERFACE       = 1

      PROGRAM_ERROR                = 2

      OTHERS                       = 3

            .

  IF SY-SUBRC <> 0.

    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

  ENDIF.

  CALL METHOD W_GRID->SET_TABLE_FOR_FIRST_DISPLAY

• EXPORTING

•    I_BUFFER_ACTIVE               =

•    I_BYPASSING_BUFFER            =

•    I_CONSISTENCY_CHECK           =

•    I_STRUCTURE_NAME              =

•    IS_VARIANT                    =

•    I_SAVE                        =

•    I_DEFAULT                     = 'X'

•    IS_LAYOUT                     =

•    IS_PRINT                      =

•    IT_SPECIAL_GROUPS             =

•    IT_TOOLBAR_EXCLUDING          =

•    IT_HYPERLINK                  =

•    IT_ALV_GRAPHICS               =

•    IT_EXCEPT_QINFO               =

•    IR_SALV_ADAPTER               =

    CHANGING

       IT_OUTTAB                     = T_DATA

       IT_FIELDCATALOG               = T_FIELDCAT

•    IT_SORT                       =

•    IT_FILTER                     =

    EXCEPTIONS

      INVALID_PARAMETER_COMBINATION = 1

      PROGRAM_ERROR                 = 2

      TOO_MANY_LINES                = 3

      OTHERS                        = 4

          .

  IF SY-SUBRC <> 0.

    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

  ENDIF.

ENDMODULE.                 " STATUS_0100  OUTPUT

</textarea>

Here is the output of my report.

Now, let us create a implementation of the BADI in SE18 / SE19 transactions.

And here is the code in my implementation. Once I do this I activate the BADI. Here I am taking a simple case of just changing the colour of o`e singli column

.

While creating the BADI implemenation make sure you mention the filter conditions so that the implementation works only for your report and for everyone else's.

This BADI fires just before the

SET_TABLE_FOR_FIRST_DISPLAY

SAP XI IN ACTION-I

Please read the blog SAP XI IN ACTION before continuing further. I actually planned to depict the implementation of entire approach in this blog but we are stuck up with the XI server issues and due to which I cannot take good snapshots. In this blog , I just want to share a generic mapping object which is used extensively in the design. We have used generic mapping object for converting any flat file structure to any hierarchical idoc structure. It is required because file adapter has the generic interface structure as specified in the previous blog and sample xml file generated for MRI interface would look like this:

It has to be converted to the hierarchical structure of MRI Idoc as shown below. It cannot be done at the file adapter CC due to the limitation of adapter. I have taken a simple Idoc structure for ease of demonstration.

It is very complex to design the mapping in graphical editor so I went for java mapping. Even in this case we have to develop mapping programs for every interface and each developer has to put his own logic for his interface. Instead I thought of an approach, which would make the code generic, and each developer just specifies the Idoc structure in his interface specific code and generic code will convert any file structure to hierarchical structure .It cuts down the development efforts as each individual has to just specify the structure and the generic code transforms the input Idoc structure as specified in the interface. It worked out really fantastic in the project.

Interface Specific Code :

MRIGenToHierMap.java

/*****************************************************************************************************

• Mapping Program to Convert NOM IDOC Master Structure to the Generic structure Expected by

• the FTP Receiver adapter

******************************************************************************************************/

import com.sap.aii.mapping.api.*;

import java.io.*;

import java.util.Map;

import java.util.Vector;

import javax.xml.parsers.*;

import javax.xml.transform.*;

import javax.xml.transform.dom.DOMSource;

import javax.xml.transform.stream.StreamResult;

import org.w3c.dom.*;

import org.xml.sax.*;

//Specify the Hirearchial Structure

class MRIGenToHierMap implements StreamTransformation

{

     public Vector v;

    private Map map;

    /** * method setParamters is required, but we do not anything with it */

     public void setParameter(Map param)

     {

          map = param;

     } /** * method execute is called by the XI mapping program */

public void buildXsd()

{

  Relation  mriRel ;

  v = new Vector();

  mriRel = new Relation();

  mriRel.parents = new String[1];

  mriRel.elements = new String[6];

  mriRel.node =  "A00" ;

  mriRel.parents[0] =   "NULL" ;

  mriRel.elements[0] =  "TRANSACTION_TYPE" ;

  mriRel.elements[1] =  "ORGANISATION_ID" ;

  mriRel.elements[2] =  "FILE_TYPE" ;

  mriRel.elements[3] =  "CREATION_DATE" ;

  mriRel.elements[4] =  "CREATION_TIME" ;

  mriRel.elements[5] =  "GENERATION_NUMBER" ;

  v.add(mriRel) ;

  mriRel = new Relation();

  mriRel.parents = new String[1];

  mriRel.elements = new String[39];

  mriRel.node = "N90";

  mriRel.parents[0] =   "NULL" ;

  mriRel.elements[0] =  "TRANSACTION_TYPE" ;

  mriRel.elements[1] =  "CONFIRMATION_REFERENCE" ;

  mriRel.elements[2] =  "METER_POINT_REFERENCE" ;

  mriRel.elements[3] =  "EFFECTIVE_DATE" ;

  mriRel.elements[4] =  "METER_LOCATION_CODE" ;

  mriRel.elements[5] =  "METER_LOCATION_DESCRIPTION" ;

  mriRel.elements[6] =  "METER_INSTRUCTIONS" ;

  mriRel.elements[7] =  "BUILDING_NUMBER" ;

  mriRel.elements[8] =  "BUILDING_NAME" ;

  mriRel.elements[9] =  "DEPENDENT_STREET" ;

  mriRel.elements[10] =  "PRINCIPAL_STREET" ;

  mriRel.elements[11] =  "DEPENDENT_LOCALITY" ;

  mriRel.elements[12] =  "POST_TOWN" ;

  mriRel.elements[13] =  "COUNTY" ;

  mriRel.elements[14] =  "METERING_SET_REFERENCE" ;

  mriRel.elements[15] =  "BYPASS_FITTED_INDICATOR" ;

  mriRel.elements[16] =  "METER_SERIAL_NUMBER" ;

  mriRel.elements[17] =  "METER_MODEL_NAME" ;

  mriRel.elements[18] =  "IMPERIAL_METER_INDICATOR" ;

  mriRel.elements[19] =  "METER_NO_OF_DIGITS_OR_DIALS" ;

  mriRel.elements[20] =  "METER_MECHANISM" ;

  mriRel.elements[21] =  "METER_STATUS" ;

  mriRel.elements[22] =  "METER_COLLAR_FITTED_INDICATOR" ;

  mriRel.elements[23] =  "METER_PULSE_VALUE" ;

  mriRel.elements[24] =  "METER_READING_FACTOR" ;

  mriRel.elements[25] =  "CORRECTOR_SERIAL_NUMBER" ;

  mriRel.elements[26] =  "NO_OF_CORRECTED_DIALS" ;

  mriRel.elements[27] =  "NO_OF_UNCORRECTED_DIALS" ;

  mriRel.elements[28] =  "CORRECTION_FACTOR" ;

  mriRel.elements[29] =  "LAST_READ_DATE" ;

  mriRel.elements[30] =  "LAST_INSPECTION_DATE" ;

  mriRel.elements[31] =  "GAS_ACT_OWNERSHIP_TYPE" ;

  mriRel.elements[32] =  "METER_MANUFACTURER_CODE" ;

  mriRel.elements[33] =  "METER_MANUFACTURED_YEAR" ;

  mriRel.elements[34] =  "CONVERTER_MANUFACTURER" ;

  mriRel.elements[35] =  "CONVERTER_MODEL" ;

  mriRel.elements[36] =  "CONVERTER_MANUFACTURED_YEAR" ;

  mriRel.elements[37] =  "CONVERTER_READING_UNITS" ;

  mriRel.elements[38] =  "CORRECTOR_CORRECTION_FACTOR" ;

  v.add(mriRel) ;

  mriRel = new Relation();

  mriRel.parents = new String[1];

  mriRel.elements = new String[39];

  mriRel.node = "U06";

  mriRel.parents[0] =   "NULL" ;

  mriRel.elements[0] =  "TRANSACTION_TYPE" ;

  mriRel.elements[1] =  "CONFIRMATION_REFERENCE" ;

  mriRel.elements[2] =  "METER_POINT_REFERENCE" ;

  mriRel.elements[3] =  "EFFECTIVE_DATE" ;

  mriRel.elements[4] =  "METER_LOCATION_CODE" ;

  mriRel.elements[5] =  "METER_LOCATION_DESCRIPTION" ;

  mriRel.elements[6] =  "METER_INSTRUCTIONS" ;

  mriRel.elements[7] =  "BUILDING_NUMBER" ;

  mriRel.elements[8] =  "BUILDING_NAME" ;

  mriRel.elements[9] =  "DEPENDENT_STREET" ;

  mriRel.elements[10] =  "PRINCIPAL_STREET" ;

  mriRel.elements[11] =  "DEPENDENT_LOCALITY" ;

  mriRel.elements[12] =  "POST_TOWN" ;

  mriRel.elements[13] =  "COUNTY" ;

  mriRel.elements[14] =  "METERING_SET_REFERENCE" ;

  mriRel.elements[15] =  "BYPASS_FITTED_INDICATOR" ;

  mriRel.elements[16] =  "METER_SERIAL_NUMBER" ;

  mriRel.elements[17] =  "METER_MODEL_NAME" ;

  mriRel.elements[18] =  "IMPERIAL_METER_INDICATOR" ;

  mriRel.elements[19] =  "METER_NO_OF_DIGITS_OR_DIALS" ;

  mriRel.elements[20] =  "METER_MECHANISM" ;

  mriRel.elements[21] =  "METER_STATUS" ;

  mriRel.elements[22] =  "METER_COLLAR_FITTED_INDICATOR" ;

  mriRel.elements[23] =  "METER_PULSE_VALUE" ;

  mriRel.elements[24] =  "METER_READING_FACTOR" ;

  mriRel.elements[25] =  "CORRECTOR_SERIAL_NUMBER" ;

  mriRel.elements[26] =  "NO_OF_CORRECTED_DIALS" ;

  mriRel.elements[27] =  "NO_OF_UNCORRECTED_DIALS" ;

  mriRel.elements[28] =  "CORRECTION_FACTOR" ;

  mriRel.elements[29] =  "LAST_READ_DATE" ;

  mriRel.elements[30] =  "LAST_INSPECTION_DATE" ;

  mriRel.elements[31] =  "GAS_ACT_OWNERSHIP_TYPE" ;

  mriRel.elements[32] =  "METER_MANUFACTURER_CODE" ;

  mriRel.elements[33] =  "METER_MANUFACTURED_YEAR";

  mriRel.elements[34] =  "CONVERTER_MANUFACTURER" ;

  mriRel.elements[35] =  "CONVERTER_MODEL" ;

  mriRel.elements[36] =  "CONVERTER_MANUFACTURED_YEAR" ;

  mriRel.elements[37] =  "CONVERTER_READING_UNITS" ;

  mriRel.elements[38] =  "CORRECTOR_CORRECTION_FACTOR" ;

  v.add(mriRel) ;

  mriRel = new Relation();

  mriRel.parents = new String[2];

  mriRel.elements = new String[6];

  mriRel.node =  "K15" ;

  mriRel.parents[0] =   "N90" ;

  mriRel.parents[1] = "U06";

  mriRel.elements[0] =  "TRANSACTION_TYPE" ;

  mriRel.elements[1] =  "METER_INSTALLATION_DATE" ;

  mriRel.elements[2] =  "METER_LINK_CODE" ;

  mriRel.elements[3] =  "GAS_NOMINATION_TYPE_CODE" ;

  mriRel.elements[4] =  "DATA_LOGGER_SERIAL_NUMBER" ;

  mriRel.elements[5] =  "DATA_LOGGER_UNIQUE_NUMBER" ;

  v.add(mriRel) ;

}

public void execute(InputStream in, OutputStream out) throws com.sap.aii.mapping.api.StreamTransformationException

{

     MRIGenToHierMap rel = new MRIGenToHierMap();

     rel.buildXsd();

     new GenToHierMap(in,out,rel.v,"MRI_ABSTRACT","urn:horzon:MRI");

}

public static void main (String[] args) throws Exception

     {

          try

          {

               MRIGenToHierMap rel = new MRIGenToHierMap();

               FileInputStream in = new FileInputStream ("H:/j2sdk1.4.2_07/bin/DOM_IN.xml");

               FileOutputStream out = new FileOutputStream ("H:/j2sdk1.4.2_07/bin/DOM_OUT.xml");

               rel.buildXsd();

               new GenToHierMap(in,out,rel.v,"MRI_ABSTRACT","urn:horzon:MRI");

          }catch(Exception e) {e.printStackTrace();}

     }

}

//Transformation of flat structure to hirearchial structure

All the 3 files have to be kept in the same directory and the generic java files should be compiled. Input XML has to be kept in the folder specified in the generic code. I would blog more details about the code depending on the demand for the same.

In this weblog we will see how to give access in a controlled manner to the user to change or create new layouts for the reports. We will also see how the user can select a layout on the selection screen, i.e., even before executing the report

How to restrict the user from creating new layout / changing existing layouts.

Before going into the details we need to understand that there 2 different types layouts available &#150; Global layout and User-Defined layouts. As the name suggests global layouts will be available for all the users, where as the user-defined layouts will be available for only those users who have created it.

Normally this is what the user sees, when an ALV report is displayed.

Here the user has got access to do everything with the layouts.

Not sure if you have observed in the last weblog when the SET_TABLE_FOR_FIRST_DISPLAY method was called, there was a parameter called I_SAVE and we passed a value &#145;A&#146; to it. This implies that the user will have all kinds of access to the layouts. Now if we do NOT pass anything to this parameter, the user will loose the privileges to delete / create new layouts. However he will still be able to select a different layout and change an existing one, however he will not be able to save the changed one.

Next variation - I_SAVE = &#145;X&#146;.

This is where the trick happens. When you pass &#145;X&#146;, although you see all the options for the layouts, the user will not be able save User-Defined Layouts.

Next variation - I_SAVE = &#145;U&#148;.

This is exactly opposite to the previous one. The user will be able save only user-define layouts.

So, here is the summary.

I_SAVE = SPACE (Default)- Layouts cannot be saved

I_SAVE = &#145;U&#146; - Only User-Define Layouts can be saved

I_SAVE = &#145;X&#146; - Only Global Layouts can be saved

I_SAVE = &#145;A&#146; - Both user-defined and global layouts can be saved.

In addition to these we will see how to remove some of the standard functionality given the standard ALV toolbar.

Now, that we have seen how to control the layouts, we will now see how to access them on the selection screen.

Define a parameters on the selection &#150; screen (Eg: P_LAYOUT LIKE DISVARIANT-VARIANT)

Invoke the following subroutine on value request for the parameter

This subroutine will throw a message if there are no layouts

Or, show the list of layouts if available

You can select one of the layouts and the name will be populated in the parameter field. Now the question is how to you make sure that this layout is used while showing the grid.

If you have observed there was one more parameter that we passed to SET_TABLE_FOR_FIRST_DISPLAY called IS_VARIANT and the variable that we passed to this was WA_VARIANT. Fill the variable as shown below and the layout tha was selected on the selection will be used to display the grid.

WA_VARIANT-REPORT = SY-REPID.
WA_VARIANT-USERNAME = SY-UNAME.
WA_VARIANT-VARIANT = P_LAYOUT.

Now we know all the options to play with Layouts. However the combination the IS_VARIANT and I_SAVE also play a crucial role. So, use them according to your requirements.

In the next weblog we will see how to restrict the user from using some standard features of the ALV toolbar by not displaying them. Also, we will see how to add custom functions to the toolbar and respond to the events.

We all know about ALV reports and the flexibility and user friendliness that ALV offers to users and ease of development for the technical consultants.

However, off late I have seen requirements where the users want dynamically add or remove columns depending on the data selected. For example, there is a report which compares the same set of fields for a given dimension. To be more precise if for a vendor / RFQ, you want to compare a list of fields and the user wants the comparison to be displayed vertically, that means more number of vendors / RFQ&#146;s, more number of fields need to be added to the output.

Now to the field catalog you can add more fields at runtime depending on the data coming in. However, how to add more columns to the internal table that will be used to display the data on the ALV grid. One crude of way doing is declare an internal table big enough to handle maximum fields and depending on the actual fields coming in at runtime, build the field catalog only for those field required so that the extra fields will not be visible. However, this is not the efficient way doing the same and more over you have every chance that the code might short dump as the field catalog and the structure of the output internal table are in sync.

So the elegant solution for this is to create a table dynamically, with the list of the fields that we have determined at run time. The question is how do we do that. Here is a quick solution.

1. Create your field catalog either manually or automatically using the function module, LVC_FIELDCATALOG_MERGE. Add more rows to the field catalog table (T_FIELDCAT) at run time.

2. Use the field catalog to create a table dynamically using the method below.

DATA: T_OUTPUT TYPE REF TO DATA

FIELD-SYMBOLS: &LT;T_OUTPUT&GT; TYPE TABLE

Call Method CL_ALV_TABLE_CREATE->CREATE_DYNAMIC_TABLE

Exporting

IT_FIELDCATALOG = T_FIELDCAT

Importing

EP_TABLE = T_OUTPUT

ASSIGN T_OUTPUT->* TO &LT;T_OUTPUT&GT;.

Now the field symbol &LT;T_OUTPUT&GT; is pointing to an output table of the structure that contains the fields which were determined at runtime. Now fill this table with the data and pass &LT;T_OUTPUT&GT; to the method SET_TABLE_FOR_FIRST_DISPLAY and the ALV grid should show the data properly.

However, if you want to access or modify or fill in the data for specific columns, you have to use the ASSIGN COMPONENT statement for the specific field name and do it.