MSS: customizing standard toolbar - repainting of screen - other issues

Hello,
1) In the System and Menu drop down menus there is a Print button. Is there any way of moving that button so it appears on the tool bar by itself?
2)When you display an ALV report in the web browser it, the report expands only as big as the browser initially opens. Before we upgraded to integrated ITS7 the previous version had the standard sap gui with the green check mark and an input field beside where you could enter a transaction. Our users would simply expand the browser and hit the check mark which would refresh the screen and the ALV report would expand to the size of the browser. I read you can not go back to previous themes. Is there any other logical solution anyone can think of
3)MSS -> HR Reports
For some of the reports if there is nothing to display (say because the user did not pick a proper date range) a sap screen in the brower states "No entry found for your selection"(so there is a meaningful message) but for some reports it does not do anything. Is there a way to get at the code to change that? Also for some of the reports if no criteria is put in the Seleted Objects table it goes to the report criteria selection screen in sap as if you launched it throught a transaction. Is there any way of blocking that and displaying a message to the user?
I'm just having a real hard time figuring out where and how all this is put together and where the source code is.
Thanks
Preston Sampson

Hi Preston,
1.) it is unfortunately not possible to move the button from the menu to the top. What should be possible is to catch Ctrl-P in webgui as in SAP GUI if the print entry in the menu is available. We (ITS development team) will check this.
2.) With current SP from NW2004s webgui automatically sends a resize event to the backend. Therefore the ALV will use the full screen area after maximizing the browser window.
3.) if the report works this way there is no chance to change this on ITS/webgui level.
Best regards,
Klaus

Similar Messages

I am having problems rebooting my mid 2009 macbook pro (grey screen other issues), need help!

I am having problems rebooting, I have experienced the same problem as others with the grey screen but my case is a little different, It started with my mid 2009 macbook pro acting a little slower than normal, the screen would freeze, mouse wouldnt move and i'd be forced to "force reboot" this went on for a couple of days until i was tinkering with the wifi connection and it froze again. I had to reboot and this time i noticed that it took a long time to get to the login screen. i put in my password and it went into infinite load (i also tried the guest account and other accounts with same result). i tried rebooting again and the same thing would happen. after several reboots, the screen just stayed grey, sometimes with the apple logo and gear sometimes without it. Since its a 2009, (and for the most part, still works like a champ) i decided test the ram, i took one stick of ram out at a time to see if i could notice anything wrong with them. when i stuck just one in, the mac was still having the same problem rebooting. i pulled that ram and and stuck in the other and i noticed that this time the apple logo never appeard and a big crossed out circle appeared. figuring that the ram must be the problem, i ordered new ram and installed it. i noticed that when i rebooted for the first time with the new ram it was rather quick and took me straight to the login screen and i was able to log in with no problem. at this point i thought the problem was solved, but i noticed the macbook still acting funny. at first, none of my files appeared on my desktop or in the finder window. after about 20 minutes, everything magically popped up. i also noticed long pauses/freezes with the colored pin wheel spinnig. i closed the laptop and opened it again and the screen just stayed black. i tried rebooting again, and again i got the grey screen with no signs of being able to log in... i waited about 20 minutes and tried to reboot again and again i was able to log in, however the macbook is still acting slow and will freeze with no signs of unfreezing without a reboot.
my macbook is 5 years old and has plenty of miles on it, so i understand if the thing needs to be replaced alltogether but does anyone know what could be the issue? could the bad ram have corrupted the hard drive in anyway? would re-installing the OS fix it?? and if so, how would i do that if i downloaded mavericks from the app store? are there any other solutions to this problem?
all my files and what not are backed up on an external HD so theres nothing on it that i'd miss desperately if i had to whipe the hard drive but id really like to get her working again without any whiping of the HD. if anyone can help me out, it'd be greatly appreciated

It is very difficult to offer troubleshooting suggestions when the "os version" you are using is unknown as each os has their own troubleshooting solutions.
How large is your hard drive and how much hard drive space do you have left?

Set up Oracle Customer Standard (R12) in JDeveloper

We need to add some extensions to the Customer Standard > Site Details OAF screen. I am trying to get it up and running on my local client PC in JDeveloper but i am missing the parameters needed to launch it directly. I can launch the Customer Standard > Search form, search for a user, and click on the results to get to the customer overview screen. When I click on a specific address details icon I get an error so I'm hoping to jump direct to the site details screen if possible.
### Steps to Reproduce ###
Set up Oracle Customer Standard (R12) in JDeveloper. Rebuild and run the oracle.apps.ar.cusstd.srch.webui.ArPrtySrchPG.xml. Search for a user (person). Select the user to go to the overview screen. Scroll down and click a details link for an address. The following error is displayed.
The OA passivation framework coding standard has been violated. Web bean properties cannot be modified in the controller processFormData or processFormRequest method. Web bean properties should be modified in the processRequest method only. An attempt to modify a web bean has been made in the following call stack: java.lang.Throwable at oracle.apps.fnd.framework.OACommonUtils.getCallStack...

I have not modified any code yet or added any extensions. I have now turned of the OADiagnostic run option but still get the same error.
Error
Please make sure you have passed all the events and parameters required for the component.
HzPuiAccountSiteMode,

Should Standard Toolbar FIND work on an ALV within a custom container ?

I have an ALV in a custom container on a screen.
The FIND and FIND NEXT of the ALV toolbar work fine against the grid.
Should the FIND and FIND NEXT of the standard toolbar also work against the ALV if they are "activate" in the GUI status?
If so, what do I call/execute in response to the "FIND" ok-code?
I've tried calling the function ALV_POPUP_TO_SEARCH2 and the popup comes up, but it doesn't do anything.
Please advise at your earliest convenience.
Thanks
djh

Hi Rich,
Absolutely. Especially as they can paint the picture, and then blame the techies when their fiction is exposed.
Similarly, we had a situation where the Expense Report WD was failing, and the functional person ensured that everyone knew it was a technical problem and therefore my fault (with SAP as the popular co-conspirator).
Sadly the message above the Java stack messages was "No entry in table T706Z for argument ' '". Had the functional check their config and all was well. No one apologised though......
Last week at a different site the same thing happened (this time with TA20C) but the funky took one look at it and reviewed their config to solve - so they're not ALL the same.
Cheers
Gareth

Custom Button in ALV Grid standard toolbar

Hello Experts,
I am working on the program in which i have to add custom button to standard toolbar in ALV. I have created the button using the method as below
     data: lr_functions type ref to cl_salv_functions_list.
     lr_functions = gr_table->get_functions( ).
     lr_functions->set_default( abap_true ).
     data: l_text       type string,
           l_icon       type string.
*    l_text = text-b01.
     l_icon = icon_complete.
     try.
       lr_functions->add_function(
         name     = 'Update Equipment Cost'
         icon     = l_icon
         text     = l_text
         tooltip = 'Update Equipment Cost'
         position = if_salv_c_function_position=>right_of_salv_functions ).
       catch cx_salv_existing cx_salv_wrong_call.
     endtry.
I don't understand how to add functionality to this button. I want to design the functionality as when user press button then corresponding values on the screen will be automatically get updated in the table.
Thanks,
Avadhut

Hi Avadhut,
When you want to add a custom button on ALV - better copy the GUI Status of the standard ALV to your program. So all the function codes are copied , now you can go to the GUI_STATUS which is copied and you can mention your own function code or you can let the standard function codes as it is. You can copy the GUI of standard ALV from SE80 transaction. Let me know if you need any assistance in doing it.
Now, if you want to write the code for any of the button on ALV - then you need to handle it is the class.
I used CL_SALV_TABLE - if you are using same then the below code gives you an idea of it.
1. Create a local class in your program
*       CLASS lcl_alv_events DEFINITION
CLASS lcl_alv_events DEFINITION FINAL.
   PUBLIC SECTION.
     METHODS: on_user_command FOR EVENT added_function OF cl_salv_events
                              IMPORTING e_salv_function.
ENDCLASS.                    "lcl_alv_events DEFINITION
DATA: gv_event_handler TYPE REF TO lcl_alv_events.
CREATE OBJECT gv_event_handler.
* Header object
CREATE OBJECT gr_header.
2. Class Implementation
   CLASS lcl_alv_events IMPLEMENTATION.
      METHOD on_user_command.
     CASE e_salv_function.
     **When PROCESS Button is selected
       WHEN '&PROC'.    ***> In my program I added Process button and fcode for it - &PROC
      ***********Write your code here ******************
    ENDCASE.
   ENDMETHOD.
ENDCLASS.                    "lcl_alv_events IMPLEMENTATION
3. Calling events
   data: gr_events    TYPE REF TO cl_salv_events_table,
           gr_alv       TYPE REF TO cl_salv_table.
   TRY.
       CALL METHOD cl_salv_table=>factory
         IMPORTING
           r_salv_table = gr_alv
         CHANGING
           t_table      = p_in_tab[].    ***This is my internal table data.
      gr_events = gr_alv->get_event( ).
         SET HANDLER gv_event_handler->on_user_command FOR gr_events.
     CATCH cx_salv_msg INTO lv_msg.                      "#EC NO_HANDLER
     CATCH cx_salv_not_found INTO lv_excep.              "#EC NO_HANDLER
     CATCH cx_salv_data_error.                           "#EC NO_HANDLER
   ENDTRY.
Regards,
Rafi

ALV List Standard toolbar

How to display standard toolbar buttons in ALV which are not displayed in REUSE_ALV_GRID_DISPLAY

HI
GOOD
GO THROUGH THIS REPORT
TYPE-POOLS: SLIS.
DATA: FIELDCAT           TYPE SLIS_T_FIELDCAT_ALV,
      FIELDCAT_LN        LIKE LINE OF FIELDCAT,
      SORTCAT            TYPE SLIS_T_SORTINFO_ALV,
      SORTCAT_LN         LIKE LINE OF SORTCAT,
      EVENTCAT           TYPE SLIS_T_EVENT,
      EVENTCAT_LN        LIKE LINE OF EVENTCAT,
      LAYOUT             TYPE SLIS_LAYOUT_ALV,
      C_TOP_OF_PAGE      TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
      W_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: COL_POS TYPE I,
      P_LIGNAM TYPE SLIS_FIELDNAME VALUE 'STATUS'.
******Declare Data Areas for List Viewer (End)**************
Other Variables
DATA: W_DATUM(10) TYPE C. "Convert system Date for Output
******Declare Internal Table to Store Selected Data (Begin)*
DATA: BEGIN OF IREPO OCCURS   0,
        EQUNR LIKE EQUI-EQUNR,
        EQKTX LIKE EQKT-EQKTX, "description
        ERDAT LIKE EQUI-ERDAT,
        ERNAM LIKE EQUI-ERNAM,
        AEDAT LIKE EQUI-AEDAT,
        AENAM LIKE EQUI-AENAM,
        EQART LIKE EQUI-EQART,
        INBDT LIKE EQUI-INBDT,
        ZZ_DESPATCH LIKE EQUI-ZZ_DESPATCH,
        ( ten million other Z fields)
        VKBUR LIKE ILOA-VKBUR, "Sales Office
        SWERK LIKE ILOA-SWERK, "Base Plant
        KOSTL LIKE ILOA-KOSTL, "Cost Centre
        ANLNR LIKE ITOB-ANLNR, "Asset Number
        NAME1 LIKE LFA1-NAME1, "Haulier name
        STATUS TYPE C,         "Is it flagged for deletion?
      END OF IREPO.
Table for descriptions
DATA: BEGIN OF IEQKT OCCURS 0,
        EQUNR LIKE EQKT-EQUNR,
        EQKTX LIKE EQKT-EQKTX,
      END OF IEQKT.
LOD Names - Internal Buffering
DATA: BEGIN OF VENDLIST OCCURS 0,
         LIFNR LIKE LFA1-LIFNR, "Vendor Number
         NAME1 LIKE LFA1-NAME1, "Vendor Name
      END OF VENDLIST.
******Declare Internal Table to Store Selected Data (End)**
TABLES: EQUI,ILOA.
*******Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS: P_EQUNR FOR EQUI-EQUNR,       "Fleet Number
                P_PLATE FOR EQUI-ZZ_PLATE_NO, "Registration
                P_EQART FOR EQUI-EQART.       "Truck Type
PARAMETER: EXCLUDE AS CHECKBOX.               "Exclude Deleted Trucks
SELECTION-SCREEN END OF BLOCK BLK1.
SELECTION-SCREEN BEGIN OF BLOCK BLK2 WITH FRAME TITLE TEXT-002.
SELECT-OPTIONS: P_DESPG    FOR EQUI-ZZ_DESPATCH, "Dgroup
                P_VKBUR    FOR ILOA-VKBUR,       "Sales Office
                P_SWERK    FOR ILOA-SWERK.       "Plant
SELECTION-SCREEN END OF BLOCK BLK2.
SELECTION-SCREEN BEGIN OF BLOCK BLK3 WITH FRAME TITLE TEXT-003.
SELECT-OPTIONS: P_HAULER FOR EQUI-ZZ_HAULER.    "Haulier Vendor
SELECTION-SCREEN END OF BLOCK BLK3.
*******Select Data into Internal Table (Begin) ***************
START-OF-SELECTION.
   CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
             TEXT       = 'Reading Truck Master Table' .
SELECT EQUIEQUNR EQUIEQART EQUIERNAM EQUIERDAT EQUI~AENAM
       EQUIAEDAT EQUIINBDT
        EQUI~ZZ_DESPATCH
        ( ten million custom Z fields )
        EQUI~ZZ_TIMEZONE
       ILOAVKBUR ILOASWERK ILOA~KOSTL
       INTO CORRESPONDING FIELDS OF TABLE IREPO
          FROM ( EQUI INNER JOIN EQUZ ON
                EQUIEQUNR = EQUZEQUNR )
              INNER JOIN ILOA ON
                EQUZILOAN = ILOAILOAN
       WHERE EQUI~EQUNR       IN P_EQUNR "Fleet Number
       AND   EQUI~EQART       IN P_EQART "Truck Type
       AND   EQUI~ZZ_PLATE_NO IN P_PLATE "Registration
       AND   EQUI~ZZ_DESPATCH IN P_DESPG "Despatch Group
       AND   EQUI~ZZ_HAULER   IN P_HAULER"Vendor
       AND   ILOA~SWERK       IN P_SWERK "Plant
       AND   ILOA~VKBUR       IN P_VKBUR."Sales Office
If successful go and get the descriptions
    IF SY-SUBRC EQ 0.
       CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
            EXPORTING
            TEXT       = 'Reading Descriptions' .
       SELECT EQUNR EQKTX FROM EQKT
              INTO CORRESPONDING FIELDS OF TABLE IEQKT
              FOR ALL ENTRIES IN IREPO
              WHERE EQUNR = IREPO-EQUNR
              AND   SPRAS = 'EN'.
        SORT IEQKT BY EQUNR.
    ENDIF.
   CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
             TEXT       = 'Check For Deletion Flags' .
DATA: L_EQUNR LIKE EQUI-EQUNR,
        L_OBJNR LIKE JEST-OBJNR.
LOOP AT IREPO.
    CONCATENATE 'IE' IREPO-EQUNR INTO L_OBJNR.
Start off by saying that the Truck is OK
    IREPO-STATUS = '3'.
Now see if the Truck has been flagged as Inactive e.g. under repair
    PERFORM STATUS_CHECK USING L_OBJNR 'I0320'.
    IF SY-SUBRC EQ 0.
       IREPO-STATUS = '2'. "It's inactive
    ENDIF.
Now see if the Truck has been flagged for deletion.
    PERFORM STATUS_CHECK USING L_OBJNR 'I0076'.
    IF SY-SUBRC EQ 0.
       IREPO-STATUS = '1'. "It's deleted
    ENDIF.
MODIFY IREPO.
CLEAR IREPO.
ENDLOOP.
If exclude is chosen lose deleted items
IF EXCLUDE = 'X'.
   DELETE IREPO WHERE STATUS = '1'.
ENDIF.
Final processing
   CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
        EXPORTING
             TEXT       = 'Prepare Data for Display' .
SORT IREPO BY EQUNR.
LOOP AT IREPO.
Get Description of Truck
    READ TABLE IEQKT WITH KEY EQUNR = IREPO-EQUNR BINARY SEARCH.
    IF SY-SUBRC EQ 0.
       IREPO-EQKTX = IEQKT-EQKTX.
    ELSE.
       IREPO-EQKTX = 'No Description in Truck Master'.
    ENDIF.
Get Name of Owner
    READ TABLE VENDLIST WITH KEY LIFNR = IREPO-ZZ_HAULER BINARY SEARCH.
    IF SY-SUBRC NE 0.
       SELECT SINGLE NAME1 FROM LFA1 INTO IREPO-NAME1
              WHERE LIFNR = IREPO-ZZ_HAULER.
       VENDLIST-LIFNR = IREPO-ZZ_HAULER.
       VENDLIST-NAME1 = IREPO-NAME1.
       APPEND VENDLIST.
       SORT VENDLIST BY LIFNR.
    ELSE.
       IREPO-NAME1 = VENDLIST-NAME1.
    ENDIF.
    MODIFY IREPO.
    CLEAR IREPO.
ENDLOOP.
END-OF-SELECTION.
Select Data into Internal Table (End) ****************
Build Field Catalogs (Begin)**************************
Fields with Standard Names
PERFORM RESETVALUES.
PERFORM ADDFIELD USING '1' 'EQUI' 'STATUS'. "Traffic Lights
FIELDCAT_LN-HOTSPOT = 'X'.
FIELDCAT_LN-KEY     = 'X'.
PERFORM ADDFIELD USING '2' 'EQUI' 'EQUNR'. "Fleet Number
PERFORM ADDFIELD USING '3' 'EQKT' 'EQKTX'. "Description
PERFORM ADDFIELD USING '4' 'EQUI' 'ZZ_PLATE_NO'.
PERFORM ADDFIELD USING '5' 'EQUI' 'EQART'.
PERFORM ADDFIELD USING '6' 'ILOA' 'SWERK'.
PERFORM ADDFIELD USING '8' 'ILOA' 'KOSTL'.
PERFORM ADDFIELD USING '9' 'EQUI' 'ZZ_MINLOADSIZE'.
PERFORM HIDFIELD USING '10' 'EQUI' 'ERNAM'.
PERFORM HIDFIELD USING '11' 'EQUI' 'AEDAT'.
PERFORM HIDFIELD USING '12' 'EQUI' 'AENAM'.
PERFORM HIDFIELD USING '13' 'EQUI' 'INBDT'.
( ten million custom Z fields )
PERFORM HIDFIELD USING '56' 'EQUI' 'ZZ_TIMEZONE'.
PERFORM HIDFIELD USING '57' 'ILOA' 'VKBUR'.
PERFORM HIDFIELD USING '58' 'EQUI' 'ZZ_HAULER'.
PERFORM HIDFIELD USING '59' 'EQUI' 'ERDAT'.
Fields with Custom Names
PERFORM NEWNAME USING 'Haulier Name'.
FIELDCAT_LN-OUTPUTLEN = '20'.
PERFORM ADDFIELD USING '7' 'LFA1' 'NAME1'. "Haulier Vendor Name
PERFORM NEWNAME USING 'Tare Time'.
PERFORM HIDFIELD USING '54' 'EQUI' 'ZZ_TARE_TIME'.
PERFORM NEWNAME USING 'Trailer 1'.
PERFORM HIDFIELD USING '19' 'EQUI' 'ZZ_TRAILER1'.
PERFORM NEWNAME USING 'Trailer 2'.
PERFORM HIDFIELD USING '20' 'EQUI' 'ZZ_TRAILER2'.
PERFORM NEWNAME USING 'Trailer 3'.
PERFORM HIDFIELD USING '21' 'EQUI' 'ZZ_TRAILER3'.
Sort Criteria
PERFORM BUILD_SORTCAT.
******Build Event Catalog (Begin)****************************
PERFORM BUILD_EVENTCAT.
Magic box for selection criteria & traffic lights for truck status
PERFORM BUILD_LAYOUT.
********Add a header at the top of the report            *******
PERFORM SET_REPORT_HEADER USING W_LIST_TOP_OF_PAGE[].
********Start List Viewer
PERFORM START_LIST_VIEWER.
******Start List Viewer (End)********************************
********FORM ROUTINES (Begin)********************************
Start Values for ALV Field Catalouge
FORM RESETVALUES.
FIELDCAT_LN-KEY = SPACE.
FIELDCAT_LN-DO_SUM = SPACE.
FIELDCAT_LN-NO_OUT = SPACE.
FIELDCAT_LN-QFIELDNAME = SPACE.
FIELDCAT_LN-HOTSPOT = SPACE.
FIELDCAT_LN-OUTPUTLEN = '0'.
CLEAR: fieldcat_ln-seltext_l, fieldcat_ln-seltext_m,
        fieldcat_ln-seltext_s, fieldcat_ln-reptext_ddic.
ENDFORM.
Change key values for additional fields
FORM ADDFIELD USING POSITION TABLE_VALUE FIELD_VALUE.
     FIELDCAT_LN-REF_TABNAME = TABLE_VALUE .
     FIELDCAT_LN-FIELDNAME   = FIELD_VALUE.
     FIELDCAT_LN-COL_POS     = POSITION.
     APPEND FIELDCAT_LN TO FIELDCAT.
     PERFORM RESETVALUES.
ENDFORM.
FORM HIDFIELD USING POSITION TABLE_VALUE FIELD_VALUE.
     FIELDCAT_LN-NO_OUT = 'X'.
     FIELDCAT_LN-REF_TABNAME = TABLE_VALUE .
     FIELDCAT_LN-FIELDNAME   = FIELD_VALUE.
     FIELDCAT_LN-COL_POS     = POSITION.
     APPEND FIELDCAT_LN TO FIELDCAT.
     PERFORM RESETVALUES.
ENDFORM.
FORM NEWNAME USING NAME.
FIELDCAT_LN-SELTEXT_L = NAME..
FIELDCAT_LN-SELTEXT_M = NAME.
FIELDCAT_LN-SELTEXT_S = NAME.
FIELDCAT_LN-REPTEXT_DDIC = NAME.
FIELDCAT_LN-OUTPUTLEN = '10'.
ENDFORM.
Sort Criteria
FORM BUILD_SORTCAT.
SORTCAT_LN-SPOS = '1'.
SORTCAT_LN-FIELDNAME = 'EQUNR'. "Truck Number
SORTCAT_LN-UP = 'X'.
SORTCAT_LN-DOWN = SPACE.
SORTCAT_LN-SUBTOT = SPACE.
APPEND SORTCAT_LN TO SORTCAT.
ENDFORM.
FORM BUILD_EVENTCAT.
EVENTCAT_LN-NAME = C_TOP_OF_PAGE.
EVENTCAT_LN-FORM = C_TOP_OF_PAGE.
APPEND EVENTCAT_LN TO EVENTCAT.
ENDFORM.                               " BUILD_EVENTCAT
Add an extra button to get an extra button the user can press to
see what selection criteria they entered
This info will then appear when the report is printed
FORM BUILD_LAYOUT.
     LAYOUT-GET_SELINFOS = 'X'.
Now we want a traffic light to say if the Truck is deleted
the variable p_lignam contains the name in IREPO which stores the
value for the traffic light
     LAYOUT-LIGHTS_FIELDNAME = P_LIGNAM.
     LAYOUT-LIGHTS_CONDENSE = 'X'.
ENDFORM.
Invoke a custom status (toolbar) in case we want to add any extra
icons at a later date
FORM SET_PF_STATUS USING EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'STAND' EXCLUDING EXTAB.
ENDFORM.
FORM START_LIST_VIEWER.
DATA: PGM LIKE SY-REPID.
PGM = SY-REPID.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
     EXPORTING
          I_CALLBACK_PROGRAM       = PGM
          I_CALLBACK_PF_STATUS_SET = 'SET_PF_STATUS'
          I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
          IS_LAYOUT                = LAYOUT
          IT_FIELDCAT              = FIELDCAT
          IT_SORT                  = SORTCAT
          I_SAVE                   = 'A'
          IT_EVENTS                = EVENTCAT[]
      TABLES
           T_OUTTAB                 = IREPO
      EXCEPTIONS
           PROGRAM_ERROR            = 1
           OTHERS                   = 2.
ENDFORM.
*******Process Call Back Events (Begin)**************************
FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM
                       SELFIELD TYPE SLIS_SELFIELD.
READ TABLE IREPO INDEX SELFIELD-TABINDEX.
CHECK SY-SUBRC = 0.
CASE UCOMM.
WHEN '&IC1'.
CASE SELFIELD-SEL_TAB_FIELD.
WHEN 'IREPO-EQUNR'.
Set Parameter ID and call ZTM3
Custom transaction to view Trucks
SET PARAMETER ID 'EQN' FIELD IREPO-EQUNR.
CALL TRANSACTION 'ZTM3' AND SKIP FIRST SCREEN.
ENDCASE.
ENDCASE.
ENDFORM.
*******Process Call Back Events (End)*****************************
Routine to print out user at the top
FORM SET_REPORT_HEADER USING LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
PERFORM CONVERT_DATE.
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'ZT01 : Truck Master Data Report'.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = 'Run On :'.
LS_LINE-INFO = W_DATUM.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
LS_LINE-KEY = 'User Name :'.
LS_LINE-INFO = SY-UNAME.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
ENDFORM.                               " SET_REPORT_HEADER
FORM CONVERT_DATE.
CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
            DATE_INTERNAL = SY-DATUM
       IMPORTING
            DATE_EXTERNAL = W_DATUM.
ENDFORM.                               " CONVERT_DATE
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
       EXPORTING
            IT_LIST_COMMENTARY = W_LIST_TOP_OF_PAGE.
ENDFORM.                               "TOP_OF_PAGE
FORM STATUS_CHECK USING OBJNR
                        STATUS.
This uses reverse logic i.e. subrc = 0 means the status being
checked (delete / inactive) is active.
e.g checking for I0076 and subrc = 0 means it's been flagged for
deletion
CALL FUNCTION 'STATUS_CHECK'
       EXPORTING
            BYPASS_BUFFER     = 'X'
            OBJNR             = OBJNR
            STATUS            = STATUS
       EXCEPTIONS
            OBJECT_NOT_FOUND = 1
            STATUS_NOT_ACTIVE = 2
            OTHERS            = 3.
ENDFORM.                               " STATUS_CHECK
**********FORM ROUTINES (END)*************************************
The other thing to note is that below I include a FORM to call a custom
status (toolbar). I define this in the repositry browser by copying the
STANDARD status from another ALV report, but you do not need to do this
unless you want to add some more buttons to the standard toolbar. I now do
this as a matter of course, as my users tend to want extra buttons e.g.
'REFRESH'.
How to add an extra button:-
Create a new status using the repository browser by copying an existing
one from an ALV program. Call it something like ZSTANDARD. Then change it by
adding a new button to the toolbar - give it an icon and a four digit name
like '&TMP' so the program knows what button the user has pressed.
(ii) Within your program include a FORM called something like SET_PF_STATUS
as in my example program below. Make sure the name of this FORM is included
in the call to the ALV function module, again as in the example below.
(iii) In the USER_COMMAND form, insert code to deal with the user pressing
the new button e.g.
Example of how to deal with users pressing new buttons
*******Process Call Back Events (Begin)**************************
FORM user_command USING ucomm LIKE sy-ucomm
                       selfield TYPE slis_selfield.
CASE ucomm.
WHEN '&IC1'.
READ TABLE irepo INDEX selfield-tabindex.
CHECK sy-subrc = 0.
CASE selfield-sel_tab_field.
WHEN 'IREPO-VBELN'.
     SET PARAMETER ID 'VL' FIELD irepo-vbeln.
     CALL TRANSACTION 'VL03' AND SKIP FIRST SCREEN. "Outbound
WHEN '&TMP'.
We are going to refresh the display so tell the ALV this
      selfield-refresh = 'X'.
Isn't that clever!
      PERFORM refresh. "Subroutine to refresh the screen (for example)
ENDCASE.
ENDFORM.
********Process Call Back Events (End) ****************************
THANKS
MRUTYUN

How to add fields in custom infotype and update its screens

Hi Experts
I want to enhance a custom infotype ( Add some new fields, and add special function on its screen). This custom infotype is created in previous release. is there any way to add fields in infotype? and let system automatcailly modify corresponding screens to add new fields

Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the u2018Employee Infotypeu2019 radio button.
4) Select the u2018PS Structure Infotypeu2019.
5) Click on Createu2026 A separate table maintenance window appearsu2026
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on u2018Allu2019 push button. It takes a few moments.
10) Click on u2018Technical Characteristicsu2019. Infotype list screen appears
11) Click on u2018Changeu2019(pencil) button
12) Select your Infotype and click on u2018Detailu2019 (magnifying glass) button
13) Give u2018T591Au2019 as subtype table
14) Give u2018T591Su2019 as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on u2018Infotype Characteristicsu2019 u2026 Infotype list screen appears
18) Click on u2018Changeu2019 (pencil) button
19) Click on u2018New Entriesu2019
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotypeu2019s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirementu2026
25) In the PM01 initial screenu2026Select u2018Screenu2019 radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select u2018Layout Editoru2019 and click u2018Changeu2019.
27) Screen default layout appearsu2026here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Donu2019t forget to u2018Activate at every level
i think u have to select CI_INCLUDE while enhanceing the Standrad Infotype

How to deactivate the standard toolbar 'print' button

Dear Expert,
I want to deactivate the standard toolbar print's button in the smartform print preview screen.
Could you explain and give me some sample code ? Thanks !

For details of how to restore it, see the [[menu bar is missing]] article.

Zoom Control not appearing in Standard Toolbar (CR2008 - SP1)

In Crystal XI (and prior versions), the Zoom control would appear in the standard toolbar. I was able to either select (from the drop down list) or type in the level of zoom. Now this control is no longer showing on the toolbar. Is there a setting somewhere I need to set?
I checked help, and this is what it says under 'using the zoom feature' (so it sounds like the zoom control should still be on the standard toolbar).:
You can easily zoom in on a report. You can choose any magnification from 25% to 400%. This feature is active in both the Design and Preview tabs.
To zoom the report in or out, set the zoom level in the Zoom Control box found on the Standard toolbar.
It is helpful to view reports at low magnifications in order to get an overall picture of the layout of your report. Views at higher magnifications focus attention on the details of the report.

Yes, but I don't want to have to go into a menu every time...that's extra work.
Needless to say, I did find it. It is in the lower right corner of the screen (to the
right of the status bar).
You can zoom there, so you do not have to go into a menu pick.
I could not find in the documentation where the zoom had moved to.

BDT custom SFCs not shown on screen

We have to set up some custom SFC categories, and I have to create new screens for them so that they are included in claims. According to OSS Note 704333, the following needs to be done (this is copied directly from the note):
Enter a new category in the IMG under Claims Management -> Structuring Business Processes -> Structured Facts Capture -> Enhance Facts Capture Categories. Also refer to the documentation for this IMGnode.
Create a BDT view. You have to enter different subscreens and function modules in the view, depending on whether it is a quick question sequence or standard question sequence (dialog box). As examples, you can use view ICLQ08 for the quick question sequence and ICLQ03 for the standard question sequence.
With the standard question sequence you must also assign field groups 50 and 51 to the view.
For a standard question sequence, use screen 300 in SAPLICL_SFC_BDT, for a quick question sequence, on the other hand, use 112 (depending on the desired size).
For the PBO and PAI modules, you have to enter the function modules mentioned for the above views (depending on the category). The PBC module has to be created specifically for your view; the modules entered with the above views can also serve as a template.
In the PBC you have to fill the following fields of structure ICL_SFC:
FACTSCAT: Your new SFC category
DSTSUBCLAIM: Subclaim to which the SFC refers
SUBOBJECT: The key by which the object is clearing identified in the claim, e.g. the number of the damaged object
XREADONLY: To be set in the display mode of the claim
You can fill PBTEXT and VIEW using function module ICL_TBSFC004_GET.
You use function module ICL_SFC_ACTINST_SET to set the values in function group ICL_SFC_BDT. Add the newly created BDT view to the provided screen sequence.
Create a question sequence for your SFC category and assign this to the corresponding internal claim type.
I followed the instructions and created new views for the new SFC's (this is so that I could use my own Function modules in the PBC events. This is the only thing I changed - the PAI and PBO both call standard SAP modules, and all the other stuff, i.e. application etc. I left the same as the standard). I assigned the views to sections --> screens etc. The screen where the SFC should appear, is there but it is blank, i.e. it doesn't show any buttons or anything.
I also hard-coded break points into my PBC modules but these never seem to be called either, because the processing never gets there, evidently. So this leads me to believe that I've missed something out in setting up the funtionality. Any ideas? Also, do I need to do anything in the BDT events to populate the new SFC's or does the system do this automatically?
Thanks for your help.

No I don't think you want ECSFO001 for ISUSDPART either. I recall implementing that last year to disable the create/change functions in the "Search and Display" component as they bypassed BDT field-group security.
I'm not sure where in CIC you want your custom field to display. Do you want to show it in the navigation area?
As for search results (ISUFINDER), I seem to recall that it was possible to configure the finder to show additional attributes of the BOR object type, such as ISUPARTNER. But I might be having myself on there as it's only a vague memory.
As standard, the finder displays columns for the the key and default attribute of the search object, in this case BOR object type ISUPARTNER. The default attribute in this case is name shorttext (can't recall what the attribute is called right now). You could implement a sub-type and override the implementation of this default attribute so that you also display an icon of some sort in the name text if your custom field is set.
Cheers,
Scott

Copying standard report transaction selection screen

Hi everybody,
How can we copy standard report transaction's VI05 selection screen to my custom report transaction's selection screen some zprogram . The problem is that when i am copying the selection screen into my programs screen, it is getting copied, but not as selection screen rather as normal screen. I have defined a transaction code for the same with the custom screen no as the selection screen but its giving a message that selection screen 9001 doesn't exist. However if i keep the selection screen as 1000 the screen in the standard transaction VI05 the transaction is executing fine.
But again the problem was that although it seems that the screen 1000 of the standard program for VI05 has been copied to my custom program but its not showing in the object list of my custom program. so I cannot do any changes which i require.
If anybody requires any clarification u can raise your doubts i will try to make it more clear.
Can any body help me with this?
Your help will be deeply appreciated.
Thanks a lot!
Best Wishes!
Regards
Prem

Hi Prem,
Even if the GUI Status is active, you cannot see two components of Standard Selection Screen.
1. All Selections - Push Button
2. Categories - Screen Block in the first with two options
2.1. OI_STAND
2.2. OI_BULK
This is becoz, there are enhancement spots included in the Standard program and the enhancement spots will not be copied, unless you copy them manually.
Check the same.
Regards,
-Syed.

Moving Custom fields to the main screen in CUP

Hi Gurus,
I am wondering if there is a way to move a custom field to the main screen like under general information instead of it being in the more section. We have a custom field which would be mandatory, So it would be nice to have it on the main screen.
Thanks,
Chinmaya
Edited by: chinmaya prakash on Nov 3, 2010 6:38 PM

Hi,
There is no way to achieve this. As per the desgin, CUP adds all the standard field to main screen and custom fields under more section.
Alpesh

Handling standard toolbar event in CL_SALV_TABLE

Hi Experts,
I have created a ALV report using class CL_SAL_TABLE. I have created some buttons in the application toolbar of ALV by which I can jump to other ALV views. Now my requirement is if I click on the Exit (Shift+F3) button on the standard toolbar at that time, I'd be taken back to the selection screen. Currently both the back and exit button behaves the same way (i.e. set screen 0. leave screen.). I want to change the behaviour for exit button.
Can anybody help me how to implement that?
Thanks,
Mainak

Hi Mainak,
Call the screen number that you wish to. (Selection-screen number).
CASE sy-ucomm.
WHEN EXIT.
CALL SCREEN 'xxxx'.

Pushbuttons on application toolbar in selection screen

Hi,
I have created 2 pushbuttons in the application tool bar of selection screen using pf-status.But the other icons in the standard toolbar were grayed out because of this.can anyone tell me why this is happening.

Hi
you need to define those other elements of the menubar in the PF-STATUS for example for back write -
> BACK
for cancel----->CANCEL for save
use these predefined function codes
PRI
List
CTRL-P
Print displayed list
%EX
List
Shift-F3
Exit processing
PICK
Edit
F2
Event AT LINE-SELECTION
RW
Edit
F12 , ESC
Cancel processing
%SC
Edit
CTRL-F
Find
%SC+
Edit
CTRL-G
Find next
BACK
Goto
F3
Back one level
P--
CTRL-PgUp
Scroll to first window page
P-
PgUp
Scroll to previous window page
P+
PgDn
Scroll to next window page
P++
Ctrl-PgDn
Scroll to last window page
Regards
Pavan
Edited by: Pavan Bhamidipati on Jul 11, 2008 6:40 AM

Standard Toolbar

Hi Friends,
The standard toolbar items are not working in my screen painter program. The code I have written is as follows.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
*&      Module USER_COMMAND_0100 INPUT
      text
MODULE USER_COMMAND_0100 INPUT.
   LOOP AT SCREEN.
       IF SY-UCOMM EQ 'EXIT'(001).
          LEAVE PROGRAM.
       ENDIF.
   ENDLOOP.
ENDMODULE.                 " USER_COMMAND_0100 INPUT
When I execute the program and click on the Exit icon, the program is not functioning.
Kindly guide me the solution.
TIA.
Regards,
Mark K

HI Mark,
Modify your code like this:-
PROCESS BEFORE OUPUT.
MODULE STATUS_0100 OUTPUT.
<b>MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'MAIN-100'.
SET TITLEBAR 'TITLE_100'.
ENDMODULE.</b>
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100 INPUT.
*& Module USER_COMMAND_0100 INPUT
text
MODULE USER_COMMAND_0100 INPUT.
IF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
ENDMODULE. " USER_COMMAND_0100 INPUT
After writing this code double click on 'MAIN-100'. This will take you to the toolbar screen. Select the option function keys from there and on top of the exit button write EXIT. Activate it and come back.
Now execute your program. Exit button will work.
Please reward points if this is what you required.
Regards,
Kirti.

MSS: customizing standard toolbar - repainting of screen - other issues

Similar Messages

Maybe you are looking for