ALV -- sorting fields

hi there experts...
I´m doing an alv report and I want to know if it's possible to sort the alv like I'm going to explain:
WA_SORT-SPOS = 1.
WA_SORT-FIELDNAME = 'EKGRP'.
WA_SORT-TABNAME = 'T'.
WA_SORT-UP = 'X'.
APPEND WA_SORT TO IT_SORT.
CLEAR WA_SORT.
WA_SORT-SPOS = 2.
WA_SORT-FIELDNAME = 'EKNAM'.
WA_SORT-TABNAME = 'T'.
WA_SORT-UP = 'X'.
APPEND WA_SORT TO IT_SORT.
CLEAR WA_SORT.
I want to sort this two fields in order that, i just want to group the equal values of EKNAM that correspond to a single value of EKGRP nad not to group all equal values of EKNAM with diferent EKGRP values.
Output Example of what I want:
   EKGRP   |   EKNAM |   DESC
-----------|----------|-------------
       1   |   001    | blabla1
           |----------|-------------
           |   002    | blabla2
           |          |-------------
           |          | blabla3
-----------|----------|-------------
      2    |   002    | blabla4
           |          |-------------
           |          | blalba5
           |--------- |--------------
           |   012    | blabla6
With normal sort, value 002 for EKNAM field is grouped independently from the value of EKGRP field...
Is it possible to do??
Tanks
Edited by: Hermano.Andrade on Apr 8, 2009 5:59 PM

HI,
Refer to this link..https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/sortinALV
Opp's sorry it is not possible...if the value is same for the corresponding two values in the different sort column then the values are merged and displayed at first instead of showing once again if any change in the any of the values in other sort column.
Instead you can update the internal table in the same way as required and display as the output. The restriction on this you need to disable the sort buttons on the alv and no other operations to be performed.

Similar Messages

ALV print problems for reports with two sort fields and subtotal at each

When a report has two sort fields and subtotal at each of them, the print function is not working correctly. Please see the report below.
The second "" (single star) record (the 10 RL record) and the '*' (double star) record (the 12 RL record) are not printing.
This is happening for any standard SAP reports. Any resolution? Any OSS Notes?
     Material/Stock Code          Grade       Units Count     Unit Type     Set Position     LFT
     520085V000          7818     1     RL     A     19,682 LF
     520085V000          7818     1     RL     A     19,682 LF
*     520085V000               2     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000               1     RL
     599098V000          7717     1     RL     A     36,167 LF
*     599098V000               10     RL
**                    12     RL
***                    12
Thanks
Anand
Edited by: Anand Velayudhan on Feb 9, 2009 11:50 PM

Hi,
Check these OSS Notes..
Note 975777 - ALV total: Subtotals disappear from printout
Note 1039655 - ALV total: Subtotals disappear from printout II
Thanks
Naren

Sort field in action monitor

Dear Experts,
I'm trying to take bulk/mass printouts for CRM transactions, using t.code- CRMC_ACTION_JOB.here we have a field called SORT FIELD1.please tell me the significance of this.actually there is no furthur filteration criteria for this.like-user id,service organisation etc.
My requirement is to print the service order as per the service organisations,which is not possible in t.code-CRMC_ACTION_JOB.
please provide some input for this issue.

Hi,
You can use the sort fields to process a series of actions in a defined order during batch processing. For this, you have to assign an attribute of the application object to the sort field in the action Customizing. When the action is generated, the value of this attribute is then entered into the corresponding sort field. First, the sorting defines how the selected actions are displayed in the list. During the batch run, the actions are then also processed in this order.
For the sorting, you must create and specify a variant that orders the ALV according to the entries in the sort fields. The dialog allows you to check the correct sort sequence in the ALV.
For example, if the postal code of the document recipient is entered into one of the sort fields, documents can be printed sorted by their postal code.
Regards,
Madhu

Hotspot-clicking (Insert function) plus ALV Sorting

Hi,
I have a requirement where the ALV display has to be SORTED based on values entered/changed on a certain column. The sort works ok when used with a custom APPEND button for new records (always inserted at the bottom of the list).
However, it does not work correctly when used with the Hotspot-click (INSERT functionality). It looks like if you CLICK on a particular record onscreen, you are actually addressing the original record in that position before the SORT was effected.
Is the Hotspot-clicking (Insert functionality) possible with ALV sorting? The ideal solution would be to have the ALV sorted at PBO and also at PAI so that the user can change existing records and add new ones with the sorting being updated everytime ON_DATA_CHANGED is triggered.
Will appreciate any help on this.
Thanks!
Michael

Hello Michael
Thanks for further specifying your requirements. I have created the sample variant ZUS_SDN_ALVGRID_HOTSPOT_SORT_1 which contains two differences as compared to its template:
Replace table VBAK with VBAP (so we have two levels of sorting: VBELN, POSNR)
Move SET_TABLE_FOR_FIRST_DISPLAY method call into PBO
When I click on the hotspot (VBELN) a new row entry for the order number is created. The sorting (VBELN, POSNR) is kept even though the new row has been appended to the itab.
*& Report ZUS_SDN_ALVGRID_HOTSPOT_SORT
*& Thread: Hotspot-clicking (Insert function) plus ALV Sorting
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1159431"></a>
REPORT zus_sdn_alvgrid_hotspot_sort.
TYPES: BEGIN OF ty_s_outtab.
INCLUDE TYPE vbap.
TYPES: END OF ty_s_outtab.
TYPES: ty_t_outtab    TYPE STANDARD TABLE OF ty_s_outtab
                      WITH DEFAULT KEY.
DATA: gt_outtab    TYPE ty_t_outtab.
DATA:
gd_okcode        TYPE ui_func,
gd_repid         TYPE syrepid,
gt_sort          TYPE lvc_t_sort,
gt_fcat          TYPE lvc_t_fcat,
gs_layout        TYPE lvc_s_layo,
gs_variant       TYPE disvariant,
go_docking       TYPE REF TO cl_gui_docking_container,
go_grid          TYPE REF TO cl_gui_alv_grid.
*       CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
    CLASS-DATA:
      ms_sel_row    TYPE lvc_s_row. " selected row
    CLASS-METHODS:
      handle_data_changed FOR EVENT data_changed OF cl_gui_alv_grid
        IMPORTING
          er_data_changed
          e_onf4
          e_onf4_before
          e_onf4_after
          sender,
      handle_hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid
        IMPORTING
          e_row_id
          e_column_id
          es_row_no
          sender.
ENDCLASS.                    "lcl_eventhandler DEFINITION
*       CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_data_changed.
    FIELD-SYMBOLS: <lt_outtab> TYPE ty_t_outtab.
    BREAK-POINT.
ENDMETHOD.                    "handle_data_changed
METHOD handle_hotspot_click.
    " define local data
    DATA: ls_outtab    TYPE ty_s_outtab,
          ld_msg        TYPE bapi_msg.
    BREAK-POINT.
    CLEAR: lcl_eventhandler=>ms_sel_row.
    ms_sel_row = e_row_id.
    READ TABLE gt_outtab INTO ls_outtab INDEX e_row_id-index.
    CONCATENATE 'Selected Sales Order = ' ls_outtab-vbeln ' / '
                                          ls_outtab-posnr
      INTO ld_msg.
      message i398(00) with ld_msg.
    " Trigger PAI
    CALL METHOD cl_gui_cfw=>set_new_ok_code
      EXPORTING
        new_code = 'INSERT'
*      IMPORTING
*        rc       =
ENDMETHOD.                    "handle_hotspot_click
ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
PARAMETERS:
p_vkorg      TYPE vkorg DEFAULT '0001' OBLIGATORY.
START-OF-SELECTION.
** SELECT * FROM vbak INTO CORRESPONDING FIELDS OF TABLE gt_outtab
**    UP TO 200 ROWS
**         WHERE vkorg = p_vkorg.
SELECT * FROM vbap INTO CORRESPONDING FIELDS OF TABLE gt_outtab
    UP TO 100 ROWS.
PERFORM init_controls.
* Build fieldcatalog and set hotspot for field KUNNR
PERFORM build_fieldcatalog.
PERFORM set_layout_and_variant.
PERFORM set_sorting.
" Register EDIT event
CALL METHOD go_grid->register_edit_event
    EXPORTING
      i_event_id = cl_gui_alv_grid=>mc_evt_enter
    EXCEPTIONS
      error      = 1
      OTHERS     = 2.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SET HANDLER:
    lcl_eventhandler=>handle_data_changed FOR go_grid,
    lcl_eventhandler=>handle_hotspot_click FOR go_grid.
* Link the docking container to the target dynpro
gd_repid = syst-repid.
CALL METHOD go_docking->link
    EXPORTING
      repid                       = gd_repid
      dynnr                       = '0100'
*      CONTAINER                   =
    EXCEPTIONS
      OTHERS                      = 4.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* ok-code field = GD_OKCODE
CALL SCREEN '0100'.
END-OF-SELECTION.
*&      Module STATUS_0100 OUTPUT
*       text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'.
* SET TITLEBAR 'xxx'.
* Display data
CALL METHOD go_grid->set_table_for_first_display
    EXPORTING
      i_bypassing_buffer            = abap_true
      is_variant                    = gs_variant
      i_save                        = 'A'
*      i_default                     = 'X'
      is_layout                     = gs_layout
*      is_print                      =
*      it_special_groups             =
*      it_toolbar_excluding          =
*      it_hyperlink                  =
*      it_alv_graphics               =
*      it_except_qinfo               =
*      ir_salv_adapter               =
    CHANGING
      it_outtab                     = gt_outtab
      it_fieldcatalog               = gt_fcat
      it_sort                       = gt_sort
*      it_filter                     =
    EXCEPTIONS
      invalid_parameter_combination = 1
      program_error                 = 2
      too_many_lines                = 3
      OTHERS                        = 4.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
** CALL METHOD go_grid->refresh_table_display
***        EXPORTING
***          IS_STABLE      =
***          I_SOFT_REFRESH =
**    EXCEPTIONS
**      finished       = 1
**      OTHERS         = 2.
** IF sy-subrc ne 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
*&      Module USER_COMMAND_0100 INPUT
*       text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
    WHEN 'BACK' OR
         'EXIT' OR
         'CANC'.
      SET SCREEN 0. LEAVE SCREEN.
    WHEN 'INSERT'.
      PERFORM insert_row.
    WHEN OTHERS.
      " Check for changed data at the frontend (= grid control)
      CALL METHOD go_grid->check_changed_data( ).
ENDCASE.
CALL METHOD go_grid->refresh_table_display
*    EXPORTING
*      IS_STABLE      =
*      I_SOFT_REFRESH =
    EXCEPTIONS
      finished       = 1
      OTHERS         = 2.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR: gd_okcode.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
*&      Form INIT_CONTROLS
*       text
* --> p1        text
* <-- p2        text
FORM init_controls .
* Create docking container
CREATE OBJECT go_docking
    EXPORTING
      parent = cl_gui_container=>screen0
      ratio = 90
    EXCEPTIONS
      others = 6.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL METHOD go_docking->set_extension
    EXPORTING
      extension = 99999
    EXCEPTIONS
      cntl_error = 1
      OTHERS     = 2.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
* Create ALV grid
CREATE OBJECT go_grid
    EXPORTING
      i_parent = go_docking
    EXCEPTIONS
      others   = 5.
IF sy-subrc NE 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " INIT_CONTROLS
*&      Form BUILD_FIELDCATALOG
*       text
* --> p1        text
* <-- p2        text
FORM build_fieldcatalog.
* define local data
DATA:
    ls_fcat        TYPE lvc_s_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
    EXPORTING
*     I_BUFFER_ACTIVE              =
      i_structure_name             = 'VBAP' " 'VBAK'
*     I_CLIENT_NEVER_DISPLAY       = 'X'
*     I_BYPASSING_BUFFER           =
*     I_INTERNAL_TABNAME           =
    CHANGING
      ct_fieldcat                  = gt_fcat
    EXCEPTIONS
      inconsistent_interface       = 1
      program_error                = 2
      OTHERS                       = 3.
IF sy-subrc NE 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
** LOOP AT gt_fcat INTO ls_fcat.
**    CASE ls_fcat-fieldname.
**      WHEN 'VBELN' OR
**           'ERDAT' OR
**           'ERZET' OR
**           'ERNAM' OR
**           'AUART' OR
**           'NETWR' OR
**           'WAERK'.
**        CONTINUE.
**      WHEN OTHERS.
**        ls_fcat-no_out = abap_true.
**    ENDCASE.
**    MODIFY gt_fcat FROM ls_fcat INDEX syst-tabix.
** ENDLOOP.
* Only non-key fields are editable
** ls_fcat-edit = 'X'.
** MODIFY gt_fcat FROM ls_fcat
**    TRANSPORTING edit
**    WHERE ( fieldname NE space ).
ls_fcat-hotspot = abap_true.
MODIFY gt_fcat FROM ls_fcat
    TRANSPORTING hotspot
    WHERE ( fieldname = 'AUART'   OR
            fieldname = 'VBELN' ).
** DELETE gt_fcat FROM 15 TO 99.
ENDFORM.                    " BUILD_FIELDCATALOG_KNB1
*&      Form SET_LAYOUT_AND_VARIANT
*       text
* --> p1        text
* <-- p2        text
FORM set_layout_and_variant .
CLEAR: gs_layout,
         gs_variant.
gs_layout-cwidth_opt = abap_true.
gs_variant-report = syst-repid.
gs_variant-handle = 'GRID'.
ENDFORM.                    " SET_LAYOUT_AND_VARIANT
*&      Form SET_SORTING
*       text
* --> p1        text
* <-- p2        text
FORM set_sorting .
* define local data
DATA: ls_sort   TYPE lvc_s_sort.
REFRESH: gt_sort.
CLEAR: ls_sort.
ls_sort-spos = 1.
ls_sort-fieldname = 'VBELN'.
ls_sort-up = abap_true.
APPEND ls_sort TO gt_sort.
CLEAR: ls_sort.
ls_sort-spos = 1.
ls_sort-fieldname = 'POSNR'.
ls_sort-up = abap_true.
APPEND ls_sort TO gt_sort.
ENDFORM.                    " SET_SORTING
*&      Form INSERT_ROW
*       text
* --> p1        text
* <-- p2        text
FORM insert_row .
* define local data
DATA: ls_outtab   TYPE ty_s_outtab,
        ld_order    TYPE vbeln.
READ TABLE gt_outtab INTO ls_outtab
                       INDEX lcl_eventhandler=>ms_sel_row-index.
ld_order = ls_outtab-vbeln.
" Find last item of sales order
LOOP AT gt_outtab INTO ls_outtab
                    WHERE ( vbeln = ld_order ).
ENDLOOP.
" Create next item:
add 10 to ls_outtab-posnr.
" NOTE: added at the end of the list
APPEND ls_outtab TO gt_outtab.
" NOTE: insert new row AFTER selected row => works, too
** INSERT ls_outtab INTO gt_outtab
**                   INDEX lcl_eventhandler=>ms_sel_row-index.
ENDFORM.                    " INSERT_ROW

Sort field in VF31

Hi,
Pls anybody let me know what is the functionality of field "Sort order" in VF31 screen?
what is the meaning of this feild and for what purpose we use this field?
thanks & Regards,
Srikanth.P

Hi,
We have 5 options in this field "SORT ORDER"...
01 Billing document/Item/Output type
02 Output type/Billing document/Item
03 Partner function/Partner no./Output type
04 Sort fields 1-3
05 Output type/Sort fields 1-3
Let me know why we use these options?
Regards,
Srikky

Sort field in maint.plan&in ip30

hi
does some one implementd sort field use in img of maint plan
and does dead line monitoring in ip3o
whar are the benifits or scope
ponts will be rewarded

Hi,
The sort field is used to 'sort' plans according to different criteria that you need to configure.
For e.g. If a company has 200 Maintenance plans and you want to know all the plans valid for a certain division of the company. You can have these plans sorted as per company division.
You will need to configure the sort fields in IMG. If company name is COMP, then sort fields may be
COMPDIV1, COMPDIV2 etc (just an example).
For scheduling maintenance plans indvidually IP10 may be used. However in real scenarios. the transaction IP30 is used to do a scheduling of all the maintenance plans together.
Thanks,
KF

Sort field in maintenace plan

hi
does some one implementd sort field use in img of maint plan
and does dead line monitoring in ip3o
whar are the benifits or scope

Hi,
The sort field is used to 'sort' plans according to different criteria that you need to configure.
For e.g. If a company has 200 Maintenance plans and you want to know all the plans valid for a certain division of the company. You can have these plans sorted as per company division.
You will need to configure the sort fields in IMG. If company name is COMP, then sort fields may be
COMPDIV1, COMPDIV2 etc (just an example).
For scheduling maintenance plans indvidually IP10 may be used. However in real scenarios. the transaction IP30 is used to do a scheduling of all the maintenance plans together.
Thanks,
KF

Sort field in equipment main screen

We have an equipment having some validity dates(Valid from: 20.11.2009 & valid to: 31.12.9999) . Whenever we enter sort field in the Location tab the validity start date changes to todays date (Valid from:10.06.2009). How we can avoid this changes of dates. What is relation of sort field with valid from date ?

Hi,
It appears you have the sort field marked as relevant for equipment usage period. This will cause a new usage period with valid from date to be set each time the value of this field is changed.
You can check customizing as follows:
Plant Maintenance and Customer Service
Master Data in Plant Maintenance and Customer Service
Technical Objects
   Equipment
   Equipment Usage Period
   Define History-Related Fields
The field to look for is EQFNR.
-Paul

Sort field in maintenance order

Hello;
I want to make sort field in maintenance order as a mandatory field. But if I make it as a mandatory field, system still allows me to save the order as long as I have not clicked 'Location' tab. So there is no positive control over this field. May I know, how do I achieve this? I have even tried to put order type as the influencing field but it does not help.
Points assured.
Regards
Hemant

Hello Hemant,
access to the SAP service marketplace via www.service.sap.com to create an OSS message. Choose link "product errors". Therefore you need an OSS user and you have to be authorized to create OSS messages.
To create an user-exit, you have to go to transaction CMOD. There you have to create a project and assign the enhancement you want to use (I'm not really sure, but I think IWO10009 is the correct one in your case - you can search the user-exits via transaction SMOD - search for IWO*).
After this you have to implement your coding and then you have to activate the project.
The implementation of the user-exit should be done by an ABAP developer.
By the way - I've had a look at the OSS. There's note 768576.
Reason and Prerequisites
The problem is caused by a missing function.
Influences set via field selection will only become effective if a screen with the corresponding fields is processed. You must also refer to the documentation defined in the corresponding Customizing area. For the location & account assignment data, no additional check is (such as with the general order header data) is realised during the saving.
Prerequisite
Via field selection you declared fields of the location & account assignment data as mandatory field, and no screen that contains these fields was passed.
Solution
By means of the example code, you must implement a corresponding mandatory field check via customer enhancement IWO10009 at the time of the order backup.
1. Create subroutine Z_IWO10009_GET_DATA_FOR_FAW in program SAPMILA0. It would be best if you create an own include ZMILA0F1 for this so that you will not have any unnecessary expenditure for future Support Packages (via Transaction SE80).
FORM Z_IWO10009_GET_DATA_FOR_FAW.
CALL FUNCTION 'CO_IH_GET_HEADER'
       IMPORTING
                 CAUFVD_IMP = CAUFVD.
CALL FUNCTION 'CO_IH_GET_ILOA'
       EXPORTING
                 CAUFVD_IMP = CAUFVD
       IMPORTING
                ILOA_WA    = ILOA.
ENDFORM.                    "Z_IWO10009_GET_DATA_FOR_FAW
2. Create the following source code in customer enhancement IWO10009:
STATICS: XTFAWF LIKE TFAWF OCCURS 0 WITH HEADER LINE.
tables: tfawf.
DATA: wa_screen    LIKE screen.
FIELD-SYMBOLS: 'A'.
perform Z_IWO10009_GET_DATA_FOR_FAW(SAPMILA0).
if xtfawf[] is initial.
    SELECT * FROM TFAWF INTO TABLE XTFAWF
             WHERE PROG = 'SAPMILA0'.
endif.
LOOP AT XTFAWF WHERE CUST_M = 'X'.
    CALL FUNCTION 'FIELD_SELECTION_INFLUENCE'
         EXPORTING
              dynprogruppe = '7   '
              mode        = 'C'
              modulpool    = 'SAPMILA0'
              fieldname    = XTFAWF-MFELD
         IMPORTING
              input        = wa_screen-input
              output      = wa_screen-output
              active      = wa_screen-active
              required    = wa_screen-required
              intensified = wa_screen-intensified
              invisible    = wa_screen-invisible
         EXCEPTIONS
              OTHERS      = 1.
    if wa_screen-required = 1.
      clear lv_mfeld.
      lv_mfeld = 'CAUFVD_IMP-'.
      case XTFAWF-MFELD.
        when 'ILOA-AUFNR'.
          lv_mfeld+11 = 'IAUFNR'.
        when 'ILOA-KOKRS'.
          lv_mfeld+11 = 'IKOKRS'.
        when 'ILOA-BUKRS'.
          lv_mfeld+11 = 'IBUKRS'.
        when 'ILOA-GSBER'.
          lv_mfeld+11 = 'IGSBER'.
        when 'RILA0-ARBPL'.
          lv_mfeld11 = xtfawf-mfeld6.
        when others.
          lv_mfeld11 = xtfawf-mfeld5.
      endcase.
      ASSIGN (lv_mfeld) TO IS INITIAL.
        Message E461(IW)
        with 'Mussfelder der Standort&Kontierungsdaten füllen'.
        EXIT.
      ENDIF.
    endif.
endloop.
endif.
3. Activate the changes
Correspondingly you can implement this solution also for the order release, for example, via customer enhancement IWO10002.
Bear in mind that this is a source code proposal. It might be useful or necessary to adjust this source code to special applications.
Best regards
Stephan
Edited by: Stephan Theis on Jan 5, 2008 11:20 AM

Sort Field to be made mandatory while creating maintenance plan(IP42)

Hi Experts,
Please suggest me the way by which i can make the field "Sort field" mandatory while creating maintenance plan (IP42).
Regards,
Vivek

Vivek,
There is no std config to acheive this. Please use IPRM0004 Maintenance plan/item: Customer check for "Save" to accomplish the same.
Mahee

Sort Fields Not Working Properly?

If I do Get Info on a track, and change the Sort Artist to anything, then I Right Click on the track in the library > Apply Sort Field > Same Artist it changes the Sort Artist of all tracks by that artist to what I entered.
However, I want to delete all the Sort Artist data. I do exactly the same thing, and change the Sort Artist data to nothing on a track. However when I try to apply the sort field to all tracks by the artist it leaves them alone! It doesn't change all the Sort Artists to nothing! It only does this when I enter no data. Any string at all and it works correctly.
How can I change all the Sort Artists to nothing i.e. delete the Sort Artist data?

Hi there.
How about, instead of leaving the Sort Artist field blank, entering a name that is identical to the actual Artist field instead and then use the Apply Sort Field > Same Artist option.
You can then go to the iTunes View menu > View Options command and uncheck Sort Artist so that it will no longer appear in your iTunes Library display.
Does that bring you anything in the way of satisfaction?

F4 help for ALV table field

Hi Experts,
I need to implement F4 help for ALV table field.
I my scenario, I am using two views. If we click on any record in fist view then it displays the popup window (second view) with relevant record details.
Here one of the columns having fieldnames corresponding values (old values), for correcting old values I have created new value editable column, we can enter new value for old value then we can save it. Till this functionality is ok.
Then I have included OVS help for new value field. Here I need to get f4 help for newvalue field relevant to fieldname.
For example: user clicks on f4 in cell (new value) then if corresponding fieldname is u2018WERKSu2019 then it shows the plant values
Here I can get fieldname, domain name and value table using method set_attribute ().
Same concept I have implemented in ALV using F4IF_FIELD_VALUE_REQUEST. It is working fine
Here I have little bit confusion. Please advise me how to implement in OVS.
Regards,
BBC

Hi,
you'll have to create a method for the OVS search help (define it in the "OVS component usage" field in the context).
Sample code (should work for WERKS):
method on_ovs .
declare data structures for the fields to be displayed and
for the table columns of the selection list, if necessary
types:
    begin of lty_stru_input,
add fields for the display of your search input here
      WERKS TYPE WERKS,
    end of lty_stru_input.
types:
    begin of lty_stru_list,
add fields for the selection list here
      WERKS TYPE WERKS_D,
      NAME1 type NAME1,
    end of lty_stru_list.
data: ls_search_input type lty_stru_input,
        lt_select_list   type standard table of lty_stru_list,
        ls_text          type wdr_name_value,
        lt_label_texts   type wdr_name_value_list,
        lt_column_texts type wdr_name_value_list,
        lv_window_title type string,
        lv_group_header type string,
        lv_table_header type string,
        lv_werks type werks_d.
field-symbols: <ls_query_params> type lty_stru_input,
                 <ls_selection>    type lty_stru_list.
case ovs_callback_object->phase_indicator.
    when if_wd_ovs=>co_phase_0. "configuration phase, may be omitted
in this phase you have the possibility to define the texts,
if you do not want to use the defaults (DDIC-texts)
Set label from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_label_texts.
Set col header from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_column_texts.
     lv_window_title = wd_assist->get_text( `003` ).
     lv_group_header = wd_assist->get_text( `004` ).
     lv_table_header = wd_assist->get_text( `005` ).
      ovs_callback_object->set_configuration(
                label_texts = lt_label_texts
                column_texts = lt_column_texts
                group_header = lv_group_header
                window_title = lv_window_title
                table_header = lv_table_header
                col_count    = 2
                row_count    = 20 ).
    when if_wd_ovs=>co_phase_1. "set search structure and defaults
In this phase you can set the structure and default values
of the search structure. If this phase is omitted, the search
fields will not be displayed, but the selection table is
displayed directly.
Read values of the original context (not necessary, but you
may set these as the defaults). A reference to the context
element is available in the callback object.
     ovs_callback_object->context_element->get_static_attributes(
         importing static_attributes = ls_search_input ).
    pass the values to the OVS component
     ovs_callback_object->set_input_structure(
         input = ls_search_input ).
    when if_wd_ovs=>co_phase_2.
If phase 1 is implemented, use the field input for the
selection of the table.
If phase 1 is omitted, use values from your own context.
      if ovs_callback_object->query_parameters is not bound.
      endif.
      assign ovs_callback_object->query_parameters->*
                              to <ls_query_params>.
      if not <ls_query_params> is assigned.
TODO exception handling
      endif.
        call method ovs_callback_object->context_element->get_attribute
          exporting
            name = 'WERKS'
          importing
            value = lv_werks.
        data: lv_subcat_text type rstxtmd.
        select werks
               name1
          into table lt_select_list
          from T001W.
        ovs_callback_object->set_output_table( output = lt_select_list ).
    when if_wd_ovs=>co_phase_3.
apply result
      if ovs_callback_object->selection is not bound.
      endif.
      assign ovs_callback_object->selection->* to <ls_selection>.
      if <ls_selection> is assigned.
        ovs_callback_object->context_element->set_attribute(
                               name = `WERKS`
                               value = <ls_selection>-werks ).
      endif.
endcase.
endmethod.

The sort field is not used when ordering multiple cds in one alumn folder, how do I correct this?

It is using the track number and not the sort order field. The reason I have multiple cds in one alumn is because they are books on cd.

Sorry for the typo my "b" key was not working correctly.
The sort field is not used when ordering multiple cds in one albumn folder, how do I correct this? It is using the track number and not the sort order field. The reason I have multiple cds in one albumn is because they are books on cd.

Use of Sort Field in equipment Master

Dear All
What is the use of SORT field in Equipment Master Record

Dear Kumar Sahoo,
This field is for identification purpose and generally give similar technical objects
example:if you have so motors like lathe and drilling and lifting and milling etc thease all motors are same motors and if you want see the list you can give sor name then see, otherwise you have to give each number and find out
some more benefit is you can list sorting and unic identification of similar objects
generally using internal purpose, i mean there is no relation of external procurement or warranty or any outside of company activiteis.
Hope this may helps you
Prem

ALV OUTPUT FIELD LEANTH

HI EXPERTS,
IN ALV OUTPUT FIELD LENTH IS MAX 128?
IN MY REQUIRMENT THE FIELD HAS 500 CHARTERS
Moderator Message: So where is the question? And why type in CAPITAL letters? Do some research before you post a question here. Also, please read the Rules of Engagement of this forum
Edited by: kishan P on Apr 1, 2011 10:10 AM

Hi,
Linking F4 Help to Fields
For the last section, we will deal with linking F4 help to fields. It is easy. As usual, define, implement and register the event onf4 at proper places in your code. For F4 help, you must register the fields whose F4 request will trigger the onf4 event. For this you must prepare a table of type LVC_T_F4 and register this table using the method register_f4_for_fields. While preparing table you must include a line for each field which will trigger F4 event. For each field in the structure;
Pass the fieldname to FIELDNAME
Set REGISTER to make the field registered,
Set GETBEFORE to provide field content transport before F4 in editable mode
Set CHNGEAFTER to make the data changed after F4 in editable mode.
Preparing table for the fields to be registered to trigger F4 event
DATA: lt_f4 TYPE lvc_t_f4 WITH HEADER LINE .
lt_f4-fieldname = 'PRICE'.
lt_f4-register = 'X' .
lt_f4-getbefore = 'X' .
APPEND lt_f4 .
CALL METHOD gr_alvgrid->register_f4_for_fields
EXPORTING
it_f4 = lt_f4[] .
A sample onf4 method implementation
METHOD handle_on_f1 .
PERFORM f4_help USING e_fieldname es_row_no .
er_event_data->m_event_handled = 'X' .
Again, we set the attribute er_event_data->m_event_handled to prevent further processing of standard F4 help.
Regards,
Ranjit Thakur.
<b>Please Mark The Helpful Answer.</b>
ENDMETHOD .

ALV -- sorting fields

Similar Messages

Maybe you are looking for