Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

The ALV has to keep two context nodes in sync:

  • the context node from the application that is passed to the ALV
      and that contains the internal table to be displayed
      (in your case you are passing the internal table to POWL and POWL
      is passing it to the ALV)
  • and the ALV owned context node which contains the data displayed
      in the table control.

The ALV owned context is necessary to have additional information
added, like e.g. summary information which is then displayed by the
table.
Having two context nodes means that both always need to be kept in
sync from application to ALV and vice versa:

  • data
  • lead selection
  • selections
  • nullCells
  • messages (for the context attributes)
  • etc.

In the NullCell scenario it means that whenever the enduser types
in a value, the null cell information needs to be mapped to the
context node of the application embedding the ALV (which is POWL in
your case) and whenever POWL is updating the null cell information,
it needs to be mapped to the ALV.

When a sort is executed, the ALV takes the data of the application
context node and sorts the application data and binds it back again.
This process is invalidating the context node and all null cell
information is lost.

Therefore after a the sort service has been executed the null cell
information has to be recreated.
To be able to do so, the ALV requires a field called
SALV_WD_TABLE_INDEX which needs to be part of you data table you pass
to POWL (and which is passing it to the ALV).

Field SALV_WD_TABLE_INDEX needs to be of type sytabix and should
contain the values from 1 to n, which is the row index number.
The ALV has to keep two context nodes in sync:- the context node from the application that is passed to the ALV  and that contains the internal table to be displayed  (in your case you are passing the internal table to POWL and POWL  is passing it to the ALV)- and the ALV owned context node which contains the data displayed  in the table control.
The ALV owned context is necessary to have additional informationadded, like e.g. summary information which is then displayed by thetable.Having two context nodes means that both always need to be kept insync from application to ALV and vice versa:- data- lead selection- selections- nullCells- messages (for the context attributes)- etc.
In the NullCell scenario it means that whenever the enduser typesin a value, the null cell information needs to be mapped to thecontext node of the application embedding the ALV (which is POWL inyour case) and whenever POWL is updating the null cell information,it needs to be mapped to the ALV.
When a sort is executed, the ALV takes the data of the applicationcontext node and sorts the application data and binds it back again.This process is invalidating the context node and all null cellinformation is lost.
Therefore after a the sort service has been executed the null cellinformation has to be recreated.To be able to do so, the ALV requires a field calledSALV_WD_TABLE_INDEX which needs to be part of you data table you passto POWL (and which is passing it to the ALV).
Field SALV_WD_TABLE_INDEX needs to be of type sytabix and shouldcontain the values from 1 to n, which is the row index number.

  • No labels