Activation of the Standard Event

Hi All,
Can anyone help me, I am not able to activate the standard event, after giving the Object Category (BOR Object Type), Object Type (BUS2007) and Event (Created ) in Triggering Events and after selecting the row and when I am trying to activate it is not activating.Please help me .
Thanks in Advance,
Ram.

Hi Michal,
Thanks for your Response, Michal i had completed the activation, Now how can i test the workflow, Actually the thing is in transaction iw21 when ever i created a notification with m1 or m2 then i will be moving to the next screen and screen is Create Maintenance Notification : Maintenance Request in that screen i will be giving Notification and Functional location and the Reported by field after filling all these fields when i save the system autogenerates the notification Number with that when i go to iw22 and when i give name to the reported by field and when i click on the order button as the order created and system has to trigger a workflow to notify the person (Reported By) field that order has created.This is done through send mail option. Now can you help me in this .I had created the workflow with sendmail option and now i had activated also can you help me that how can i test my workflow.
Regards,
Ram.

Similar Messages

Custom Events are repeating with the standard events

Hello All,
I am facing a problem with the customization of standard OA Page.
We have modified the page by adding a new custom region with three buttons in it. We have also developed a controller for that region to handle the events. when a button is clicked, a new page opens up in a new window.
I have observed that the custom controller is called when any event occurs in the page irrespective of the region.
Now the actual problem is whenever any of the custom buttons are clicked, according to the requirement the new window opens up. But if we perform any other standard events in the page like clicking a standard LOV immediately after performing the custom event, then that most recent custom event is repeating with that standard event.
how to prevent this repetetion of custom event with standard event?
please help me solve this problem..
Thanks in advance.

For your page, are you setting the controller class for your various regions in the property inspector?

How can I make only the shape active for the mouse events, not the whole box around it?

I want to create mouse over events for different parts of an image (say of a hard disk drive), so when the user places their mouse over the spindle, say, it will change colour.
At the moment I have it working however the event is triggered when ever the mouse is in the bounding box of the spindle image. How can I get it to only be triggered when it is above the non transparent part of the image (or symbol)?

Thanks joris182, but that wont work when there are other objects within the bounding box of the transparent symbol. For example, if I want the sclera to highlight, if I use an invisible shape over it, it will be active even if someone has their mouse over the vitreous body.

While going to second approver the triggering event is changing

Hi Frds
Once the first approver is clicks the recommend to approve's button,then the work item goes to the second approver its all working fine.In the mean time the first approver got the workitem for the same Workflow.
I have checked in the SWEL (Event Trace's).
Can anyone give the solution for this problem.
Thanks
Pari

pari vedhan raj...
On looking into your issue two things i can suggest
First: goto SPRO Img>> Material management >> Purchasing >>Purchase Order >> Release procedure for purchase order >>
Define release procedure for purchase order >> select workflow.
here you can see all agents/approver for release strategy workflow, if same user maintained for different release code then he use to get same workitem with different release code.
sencond: check is there any other workflow is active for the same event.
regards,
Hari

Error while activating the copy of the standard module

Hi,
I wanted to create a copy of the module material_read_all and so I copied the entire function group.
Now when I am trying to activate it , I am getting syntax error saying that the field does not exist in the global declarations. When I double click on the field name it takes me to another modules of the same function group where the said field is an export parameter.
I cross checked with the standard module and there also no explicit declaration is given. I also tried declaraing the variable again and then activating.But on doing it I got different results from both the modules for the same input and so I had to delete and create it again.
The same thing is happening with other modules also which I am trying to copy.
Can anyone please help me with this.
For copying the function group I entered the main program name in se38 and clicked on copy. It then asked me to copy the modules so I just added 'Z' before the modules to make a duplicate copy.
It is very very urgent.
Thanks in advance
Edited by: Alvaro Tejada Galindo on Apr 28, 2008 11:50 AM

Hi,
I have tried activating all the includes individually and then the main program. But still I am getting the errors. While activating the includes on checking for the syntax error it showed error but on clicking on activating it got activated. But same thing sis not working for the main program.
I also tried with 'activate anyway' but even after that syntax errors are there with the field decalrations.

Error while Activating the Standard DSO

Hi,
I am getting the below error while Activating the Standard DSO.
Characteristic 0DPM_DCAS__0CSM_SPRO: DS object 0DPM_DCAS__0CSM_STAT (master data check) does not exist
I tried searching the forum , but didnt find any answer.
Any suggestions are welcome.
Thank you,
Adhvi.

Hi,
Are you getting the error while trying to activate the DSO data after loading or just while trying to activate the DSO itself.
If it is during the activation of a request,then please check if you have loaded some data in the DSO which doesnt have the corresponding Master Data loaded.For preventing this, you can check in Infopackage/DTP -"No Update without Master Data".
You can also go into RSRV and perform elementary tests for the DSO and check the SID table consistency.
Thanks,
Divya.

Which are the standard classes for events in ALV and explain each class pls

which are the standard classes for events in ALV and explain each class pls
POINTS WILL BE AWARDED,
REGARDS,
jagrut bharatkumar Shukla

hi,
some links.
www.sapgenie.com
www.abap4u.com
http://help.sap.com/saphelp_nw2004s/helpdata/en/5e/88d440e14f8431e10000000a1550b0/frameset.htm
download the PDF from following link.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVALV/BCSRVALV.pdf
The ALV object Grid methods allow the same functionality as ALV grid report function modules but are displayed within
a screen (dialog program). SAP has provided a suit of programs which demonstrate how to For examples see standard SAP
programs as detailed below:
BCALV_EDIT_01 This report illustrates the simplest case of using an editable/noneditable ALV Grid Control.
BCALV_EDIT_02 This report illustrates how to set chosen cells of an ALV Grid Control editable.
BCALV_EDIT_03 In this example the user may change values of fields SEATSOCC (occupied seats) and/or PLANETYPE.
The report checks the input value(s) semantically and provides protocol messages in case of error
BCALV_EDIT_04 This report illustrates how to add and remove lines to a table using the ALV Grid Control and how to
implement the saving of the new data.
BCALV_EDIT_05 This example shows how to use checkboxes within an ALV Grid Control. You learn:
     (1) how to define a column for editable checkboxes for an attribute of your list
     (2) how to evaluate the checked checkboxes
     (3) how to switch between editable and non-editable checkboxes
BCALV_EDIT_06 This example shows how to define a dropdown listbox for all cells of one column in an editable ALV
Grid Control.
BCALV_EDIT_07 This example shows how to define dropdown listboxes for particular cells of your output table.
BCALV_EDIT_08 This report implements an ALV Grid Control with an application specific F4 help. The following aspects
are dealt with:
     (1) how to replace the standard f4 help
     (2) how to pass the selected value to the ALV Grid Control
     (3) how to build an f4 help, whose value range depend on a value of another cell.
Rgds
Anversha

I have activated the standard datasource in r/3? how to identify active?

Hi All,
i have activated the standard datasource in r/3 ? and i have replicated the same in the bw system and in the source system of r/3 i have replicated it and i can find the data source there ? but how to identify whether the datasource is active in the bw system or not ?
i cant see a tick mark on the data source does it determine it is active?
Pls guide me on this?
thanks
Pooja

Hi all,
I am working on 3.5
And where can i find the datasource is green or not? it is not assigned to the source system i can identify it?
i am not able to rightclik on the datasource and see the active version.
When i right click on the data source i can see this option:
1. assign infosource
2. maintain datasource in the source system etc?
Thanks
Pooja

Error in Query View Saving -The standard transport system is active.You can

Hi,
I have a query in Dev system which is moved to production and i am able to edit the query in dev.But my problem is when i tried to create a view on that query and save the view, it is throwing me a error
"The standard transport system is active.You cannot save"
Any pointers on this.
Regards,
Pra

Hi
Did you get any feedback on this one?? Im facing the same message when saving a query view..
Thanks
Willem

Why can not catch the standard BACK event in ALV's USER_COMMAND event,

Hi expert, why i can not catch the standard BACK event in ALV's USER_COMMAND event,
Code:
DATA G_CON_UC_FORM   TYPE SLIS_FORMNAME VALUE 'F_USER_COMMAND',
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM      = SY-REPID
      I_CALLBACK_TOP_OF_PAGE = G_CON_FORM
      I_CALLBACK_USER_COMMAND = G_CON_UC_FORM
      IT_FIELDCAT             = G_TAB_FIELDCAT
      IT_SORT                 = G_TAB_SORT_INF
      I_SAVE                  = G_CON_U
*<<<Liang
    IT_EVENTS               = G_TAB_ALV_EVENTS
*<<<Liang
    TABLES
      T_OUTTAB                = G_TAB_OUTPUT_DATA
    EXCEPTIONS
      PROGRAM_ERROR           = 1
      OTHERS                  = 2.
*&      Form F_USER_COMMAND
      ALV USER COMMAND processing
FORM F_USER_COMMAND .
IF SY-UCOMM = '&FO3'.
    LEAVE TO SCREEN 0.
ENDIF.
ENDFORM.                    " F_USER_COMMAND
When I set breakpoint on this subrouting ,and try to click stardard BACK or CANCEL button, the callback form do not run, but if double click one of line of alv report, the callback form works well,
so why??

hi
good
check this report and change your code accordingly.
THESE LINES ARE FOR THE MAIN PROGRAM ***
SAP V40B ***
REPORT Z_PICK_LIST .
TABLES: RESB.
SELECTION-SCREEN BEGIN OF BLOCK BL1 WITH FRAME TITLE TEXT-BL1.
SELECT-OPTIONS: S_WERKS FOR RESB-WERKS," Plant
                S_AUFNR FOR RESB-AUFNR," Order number
                S_BDTER FOR RESB-BDTER." Req. date
SELECTION-SCREEN END OF BLOCK BL1.
PARAMETERS: P_VARI LIKE DISVARIANT-VARIANT DEFAULT '/STANDARD'.
DATA: BEGIN OF OUT OCCURS 10,
        AUFNR LIKE RESB-AUFNR,         " Order number
        MATNR LIKE RESB-MATNR,         " Material
        BDMNG LIKE RESB-BDMNG,         " Requirements in UM
        MEINS LIKE RESB-MEINS,         " Unit of Measure (UM)
        ERFMG LIKE RESB-ERFMG,         " Requirements in UE
        ERFME LIKE RESB-ERFME,         " Unit of Entry (UE)
        MAKTX LIKE MAKT-MAKTX,         " Mat. description
      END OF OUT.
INCLUDE Z_ALV_VARIABLES.
INITIALIZATION.
REPNAME = SY-REPID.
PERFORM INITIALIZE_FIELDCAT USING FIELDTAB[].
PERFORM BUILD_EVENTTAB USING EVENTS[].
PERFORM BUILD_COMMENT USING HEADING[].
PERFORM INITIALIZE_VARIANT.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM F4_FOR_VARIANT.
AT SELECTION-SCREEN.
PERFORM PAI_OF_SELECTION_SCREEN.
START-OF-SELECTION.
PERFORM GET_ORDERS.
PERFORM GET_MATERIAL_DESCRIPTION.
END-OF-SELECTION.
PERFORM BUILD_LAYOUT USING LAYOUT.
PERFORM BUILD_PRINT USING PRINTS.
PERFORM WRITE_USING_ALV.
      FORM INITIALIZE_FIELDCAT                               *
--> P_TAB                                                         *
FORM INITIALIZE_FIELDCAT USING P_TAB TYPE SLIS_T_FIELDCAT_ALV.
DATA: CAT TYPE SLIS_FIELDCAT_ALV.
CLEAR CAT.
ENDFORM.                               " INITIALIZE_FIELDCAT
*&      Form GET_ORDERS
      text
FORM GET_ORDERS.
SELECT AUFNR MATNR BDMNG MEINS ERFMG ERFME
         FROM RESB
         APPENDING TABLE OUT
         WHERE XLOEK EQ SPACE          " deletion indicator
         AND   XWAOK EQ 'X'            " goods movement indicator
         AND   WERKS IN S_WERKS        " plant
         AND   BDTER IN S_BDTER        " req. date
         AND   AUFNR IN S_AUFNR.       " pr. order
ENDFORM.                               " GET_ORDERS
*&      Form GET_MATERIAL_DESCRIPTION
      text
FORM GET_MATERIAL_DESCRIPTION.
SORT OUT BY MATNR.
LOOP AT OUT.
    SELECT SINGLE MAKTX
           INTO OUT-MAKTX
           FROM MAKT
           WHERE MATNR EQ OUT-MATNR
           AND   SPRAS EQ 'EN'.
    MODIFY OUT.
ENDLOOP.
SORT OUT BY AUFNR MATNR.
ENDFORM.                               " GET_MATERIAL_DESCRIPTION
      FORM TOP_OF_PAGE                                              *
FORM TOP_OF_PAGE.
DATA: L_POS TYPE P.
first line
WRITE:/ TEXT-001.                    " Plant:
IF S_WERKS-HIGH NE SPACE.
    WRITE: S_WERKS-LOW, TEXT-TO1, S_WERKS-HIGH.
ELSEIF S_WERKS-LOW NE SPACE.
    LOOP AT S_WERKS.
      WRITE: S_WERKS-LOW.
    ENDLOOP.
ELSEIF S_WERKS-LOW EQ SPACE.
    WRITE: TEXT-ALL.
ENDIF.
L_POS = ( SY-LINSZ DIV 2 ) - ( STRLEN( TEXT-TIT ) DIV 2 ).
POSITION L_POS. WRITE: TEXT-TIT.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-011, SY-UNAME RIGHT-JUSTIFIED. " User:
second line
WRITE:/ TEXT-002.                    " Order:
IF S_AUFNR-HIGH NE SPACE.
    WRITE: S_AUFNR-LOW, TEXT-TO1, S_AUFNR-HIGH.
ELSEIF S_AUFNR-LOW NE SPACE.
    LOOP AT S_AUFNR.
      WRITE: S_AUFNR-LOW.
    ENDLOOP.
ELSEIF S_AUFNR-LOW EQ SPACE.
    WRITE: TEXT-ALL.
ENDIF.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-012,SY-DATUM.      " Date:
third line
WRITE:/ TEXT-003.                    " Req. Date:
IF S_BDTER-HIGH(1) NE '0'.
    WRITE: S_BDTER-LOW, TEXT-TO1, S_BDTER-HIGH.
ELSEIF S_BDTER-LOW(1) NE '0'.
    LOOP AT S_BDTER.
      WRITE: S_BDTER-LOW.
    ENDLOOP.
ELSEIF S_BDTER-LOW(1) EQ '0'.
    WRITE: TEXT-ALL.
ENDIF.
L_POS = SY-LINSZ - 20.
POSITION L_POS. WRITE: TEXT-013, SY-PAGNO.   " Page:
ENDFORM.                               " TOP_OF_PAGE
      FORM END_OF_LIST                                              *
FORM END_OF_LIST.
DATA: L_POS TYPE P.
ULINE.
WRITE:/ '|', TEXT-021.      " Delivered by:
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|', TEXT-031.            " Received by:
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
WRITE:/ '|'.
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|'.
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
ULINE.
WRITE:/ '|', TEXT-012.      " Date:
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|', TEXT-012.            " Date:
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
WRITE:/ '|'.
L_POS = SY-LINSZ DIV 2.
POSITION L_POS. WRITE: '|'.
L_POS = SY-LINSZ.
POSITION L_POS. WRITE: '|'.
ULINE.
ENDFORM.                               " END_OF_LIST
*&      Form WRITE_USING_ALV
      text
FORM WRITE_USING_ALV.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
       EXPORTING
            I_PROGRAM_NAME     = REPNAME
            I_INTERNAL_TABNAME = 'OUT'
            I_INCLNAME         = REPNAME
       CHANGING
            CT_FIELDCAT        = FIELDTAB.
IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_FIELDCATALOG_MERGE'.
ENDIF.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM       = REPNAME
           i_callback_pf_status_set = 'PF_STATUS_SET'
           i_callback_user_command = 'USER_COMMAND'
            I_STRUCTURE_NAME         = 'OUT'
            IS_LAYOUT                = LAYOUT
            IT_FIELDCAT              = FIELDTAB
            I_DEFAULT                = 'A'
            I_SAVE                   = G_SAVE
            IS_VARIANT               = G_VARIANT
            IT_EVENTS                = EVENTS[]
            IS_PRINT                 = PRINTS
       TABLES
            T_OUTTAB                 = OUT.
IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC, 'REUSE_ALV_LIST_DISPLAY'.
ENDIF.
ENDFORM.                               " WRITE_USING_ALV
THESE LINES ARE FOR THE INCLUDE ***
***INCLUDE Z_ALV_VARIABLES .
TYPE-POOLS: SLIS.
DATA: FIELDTAB TYPE SLIS_T_FIELDCAT_ALV,
      HEADING TYPE SLIS_T_LISTHEADER,
      LAYOUT   TYPE SLIS_LAYOUT_ALV,
      EVENTS   TYPE SLIS_T_EVENT,
      REPNAME LIKE SY-REPID,
      F2CODE   LIKE SY-UCOMM VALUE '&ETA',
      PRINTS   TYPE SLIS_PRINT_ALV,
      TITLE(40) TYPE C,
      G_SAVE(1) TYPE C,
      G_EXIT(1) TYPE C,
      G_VARIANT LIKE DISVARIANT,
      GX_VARIANT LIKE DISVARIANT.
CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
           FORMNAME_END_OF_PAGE TYPE SLIS_FORMNAME VALUE 'END_OF_PAGE',
           FORMNAME_END_OF_LIST TYPE SLIS_FORMNAME VALUE 'END_OF_LIST',
           FORMNAME_BEFORE_LINE TYPE SLIS_FORMNAME VALUE 'BEFORE_LINE',
           FORMNAME_AFTER_LINE TYPE SLIS_FORMNAME VALUE 'AFTER_LINE'.
      FORM MAIN_STATEMENTS                                          *
THIS IS THE CODE THAT MUST BE INSERTED IN THE MAIN PROGRAM
FORM MAIN_STATEMENTS.
Declare the parameter P_VARI wherever you want it. If you don't
want it, hide it with NO-DISPLAY, but it must exist.
parameters: p_vari like disvariant-variant. " ALV Variant
You have to add the following line after the data and parameter
declaration:
include z_alv_variables.
Then, after the data/parameter declaration, add these lines:
*initialization.
repname = sy-repid.
perform initialize_fieldcat using fieldtab[].
perform build_eventtab using events[].
perform build_comment using heading[].
perform initialize_variant.
If you are using the variable P_VARI (ALV Variant), also add this:
*at selection-screen on value-request for p_vari.
perform f4_for_variant.
*at selection-screen.
perform pai_of_selection_screen.
After the "END-OF-SELECTION" statement, add these lines:
perform build_layout using layout.
perform build_print using prints.
perform write_using_alv.
You also have to create the following forms: (you can find samples
in this program)
INITIALIZE_FIELDCAT
USER_COMMAND     (only if you are creating a STATUS)
WRITE_USING_ALV
ENDFORM.
*&      Form INITIALIZE_FIELDCAT_SAMPLE
      THIS IS A SAMPLE, DO NOT USE THIS FORM IN YOUR PROGRAM
     -->P_FIELDTAB[] text                                           *
FORM INITIALIZE_FIELDCAT_SAMPLE USING P_TAB TYPE SLIS_T_FIELDCAT_ALV.
DATA: CAT TYPE SLIS_FIELDCAT_ALV.
CLEAR CAT.                           " Always clear before use
CAT-TABNAME = 'I'.                   " Your internal table
CAT-REF_TABNAME = 'ZCUSTMAS'. " The data dictionary reference table
CAT-FIELDNAME = 'KUNNR'.       " Name of your field in the itable.
CAT-COL_POS   = 1.                   " Output position
APPEND CAT TO P_TAB.
CAT-FIELDNAME = 'NAME1'.             " Next field
CAT-COL_POS   = 2.
APPEND CAT TO P_TAB.
CAT-FIELDNAME = 'STRAS'.             " and the next
CAT-COL_POS   = 3.
APPEND CAT TO P_TAB.
CAT-FIELDNAME = 'LOEVM'.
CAT-SELTEXT_S = 'Del'.         " You can always override the descrip-
CAT-SELTEXT_M = 'Delivery'.          " tion (short, medium, large)
CAT-SELTEXT_L = 'Delivery Num'.
CAT-COL_POS   = 4.
APPEND CAT TO P_TAB.
CAT-FIELDNAME = 'FKIMG'.
CAT-DO_SUM    = 'X'.                 " You want totals calculated.
CAT-NO_OUT    = 'X'.                 " and hidden.
APPEND CAT TO P_TAB.
ENDFORM.                               " INITIALIZE_FIELDCAT
*&      Form BUILD_EVENTTAB
      THIS IS THE SAME FOR ALL THE PROGRAMS
     -->P_EVENTS[] text                                             *
FORM BUILD_EVENTTAB USING P_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
            I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = P_EVENTS.
READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                           INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_EVENTS.
ENDIF.
CLEAR LS_EVENT.
READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_END_OF_LIST
                           INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_END_OF_LIST TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_EVENTS.
ENDIF.
CLEAR LS_EVENT.
READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_BEFORE_LINE_OUTPUT
                           INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_BEFORE_LINE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_EVENTS.
ENDIF.
CLEAR LS_EVENT.
READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_AFTER_LINE_OUTPUT
                           INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_AFTER_LINE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_EVENTS.
ENDIF.
CLEAR LS_EVENT.
READ TABLE P_EVENTS WITH KEY NAME = SLIS_EV_END_OF_PAGE
                           INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_END_OF_PAGE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_EVENTS.
ENDIF.
ENDFORM.                               " BUILD_EVENTTAB
*&      Form BUILD_COMMENT
NOT REALLY NEEDED, BUT I'LL LEAVE IT THERE, JUST IN CASE...
     -->P_HEADING[] text                                            *
FORM BUILD_COMMENT USING P_HEADING TYPE SLIS_T_LISTHEADER.
DATA: HLINE TYPE SLIS_LISTHEADER,
        TEXT(60) TYPE C,
        SEP(20) TYPE C.
CLEAR: HLINE, TEXT.
HLINE-TYP = 'H'.
write: text-101 to text+23.
HLINE-INFO = TEXT.
APPEND HLINE TO P_HEADING.
ENDFORM.                               " BUILD_COMMENT
*&      Form INITIALIZE_VARIANT
VERY IMPORTANT WHEN YOU USE VARIANTS!!!
FORM INITIALIZE_VARIANT.
G_SAVE = 'A'.
CLEAR G_VARIANT.
G_VARIANT-REPORT = REPNAME.
GX_VARIANT = G_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            I_SAVE     = G_SAVE
       CHANGING
            CS_VARIANT = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = GX_VARIANT-VARIANT.
ENDIF.
ENDFORM.                               " INITIALIZE_VARIANT
*&      Form PAI_OF_SELECTION_SCREEN
ALSO FOR VARIANTS
FORM PAI_OF_SELECTION_SCREEN.
IF NOT P_VARI IS INITIAL.
    MOVE G_VARIANT TO GX_VARIANT.
    MOVE P_VARI TO GX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
         EXPORTING
              I_SAVE     = G_SAVE
         CHANGING
              CS_VARIANT = GX_VARIANT
         EXCEPTIONS
              WRONG_INPUT   = 1
              NOT_FOUND     = 2
              PROGRAM_ERROR = 3.
    IF SY-SUBRC EQ 0.
      G_VARIANT = GX_VARIANT.
    ELSE.
      PERFORM INITIALIZE_VARIANT.
    ENDIF.
ELSE.
    PERFORM INITIALIZE_VARIANT.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN
*&      Form F4_FOR_VARIANT
      text
FORM F4_FOR_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
       EXPORTING
            IS_VARIANT = G_VARIANT
            I_SAVE     = G_SAVE
       IMPORTING
            E_EXIT     = G_EXIT
            ES_VARIANT = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 2.
    MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    IF G_EXIT = SPACE.
      P_VARI = GX_VARIANT-VARIANT.
    ENDIF.
ENDIF.
ENDFORM.                               " F4_FOR_VARIANT
*&      Form BUILD_LAYOUT
STANDARD LAYOUT
     -->P_LAYOUT text                                               *
FORM BUILD_LAYOUT USING P_LAYOUT TYPE SLIS_LAYOUT_ALV.
P_LAYOUT-F2CODE       = F2CODE.
P_LAYOUT-ZEBRA        = 'X'.
p_layout-detail_popup = 'X'.
P_LAYOUT-TOTALS_TEXT = SPACE.
P_LAYOUT-SUBTOTALS_TEXT = SPACE.
ENDFORM.                               " BUILD_LAYOUT
      FORM BUILD_PRINT                                              *
STANDARD PRINT OPTIONS                                             *
--> P_PRINT                                                       *
FORM BUILD_PRINT USING P_PRINT TYPE SLIS_PRINT_ALV.
P_PRINT-NO_PRINT_LISTINFOS = 'X'.
P_PRINT-NO_PRINT_SELINFOS = ' '.
ENDFORM.                               " BUILD_PRINT
      FORM PF_STATUS_SET                                            *
NAME YOUR STATUS ALV. IF YOU NEED IT..                             *
FORM PF_STATUS_SET USING EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'ALV' EXCLUDING EXTAB.
ENDFORM.                               " PF_STATUS_SET
      FORM USER_COMMAND_SAMPLE                                      *
--> UCOMM                                                         *
--> SELFIELD                                                      *
FORM USER_COMMAND_SAMPLE USING UCOMM    LIKE SY-UCOMM
                           SELFIELD TYPE SLIS_SELFIELD.
CASE UCOMM.
    WHEN 'MSXL'.                       " Export to Excel
     perform set_excel_export.
      CLEAR UCOMM.
    WHEN 'MM03'.
     set parameter id 'MAT' field selfield-value.
     call transaction 'MM03' and skip first screen.
      CLEAR UCOMM.
    WHEN 'BGR1'.
     perform fill_available.
     perform graph_available.
      CLEAR UCOMM.
    WHEN 'DOCU'.
     call function 'Z_HELP' exporting repname = repname.
ENDCASE.
ENDFORM.                               " USER_COMMAND
*&      Form WRITE_USING_ALV_SAMPLE
*THIS IS A SAMPLE AND MUST BE WRITTEN DIRECTLY IN THE MAIN PROGRAM
FORM WRITE_USING_ALV_SAMPLE.
YOU CAN MERGE WITH A DATA DICTIONARY TABLE USING THIS:
call function 'REUSE_ALV_FIELDCATALOG_MERGE'
      exporting
           i_program_name     = repname
           i_internal_tabname = 'I'
           i_inclname         = repname
      changing
           ct_fieldcat        = fieldtab.
if sy-subrc <> 0.
   write: 'SY-SUBRC: ', sy-subrc, 'REUSE_ALV_FIELDCATALOG_MERGE'.
endif.
OR JUST DISPLAY IT USING THIS:
call function 'REUSE_ALV_LIST_DISPLAY'
      exporting
           i_callback_program       = repname
           i_callback_pf_status_set = 'PF_STATUS_SET'
           i_callback_user_command = 'USER_COMMAND'
           i_structure_name         = 'I'
           is_layout                = layout
           it_fieldcat              = fieldtab
           i_default                = 'A'
           i_save                   = g_save
           is_variant               = g_variant
           it_events                = events[]
           is_print                 = prints
      tables
           t_outtab                 = i.
if sy-subrc <> 0.
   write: 'SY-SUBRC: ', sy-subrc, 'REUSE_ALV_LIST_DISPLAY'.
endif.
ENDFORM.                               " WRITE_USING_ALV
thanks
mrutyun^

Error in Portal: The Standard transport system is active.You cannot save

Hi Experts
In Portal,I am trying to save a BW Query as view in 'Favorites' or 'BEx Portfolio' or 'My Portfolio',I can't able to save it as i am getting
"The Standard transport system is active.You cannot save" msg
Please update me what is the reason and how to resolve this error
Thanks in advance

Hi,
SAP Note : 356018 might be handy.
Regards,
Sandeep Tudumu

For a given tcode how can we find out the available standard events

Hi Experts
For a given tcode how can we find out the available standard events?
Thanks in advance

Arghadip Kar wrote:>
>
> Or you can debug the Service for Generic Object button in the standard screens and there you will find which BO the Tcode is referencing to.
>
Wonder where you got that answer from, Arghadip!
You have neither acknowledged nor closed the 16 threads that you opened.

The standard transport system is active. BI querry on Poral

Hi All,
I am getting the error when saving the querry in BI ie when I click "Save As" button a dialog window opens and in "favourite" tab
i give description (any text ) and click Ok button. Then i get the following error :
The standard transport system is activeYou cannot save
This is carried out in portal.
Please help
Regards

Hi,
It's mentioned the activity of saving BI Query is carried out in Portal, so am assuming you might be using a BEx Web application for this.
If yes, then would suggest you to try once after switching off the standard transport. And instead use BEx transports in Admin workbench.
My understanding can be completely wrong, in which case request you to provide more details on the environment and the steps done.
Thanks,
Swapna Priya.

Activating the standard transport system in BI Dev system.

Hello All,
We have a debate going on like whether we need to activate the standard transport system or not in BW Development.
Our user is asking to enable some functionality from a Web Template using the
Save As command. This command enables a user to slice a report and
then save this view as a Portal Favorite. This functionality appears to be
blocked when the transport system is active(Switched on) but he is able to save it when transport system is switched off.
I know that it has to be switched on in order to collect the changes in transport requests in Dev other wise will be collected as Local obects in $TMP.
Also let me know the pros and crons of activating the transport system.
Appreciate if you could throw some light on this and solution to the above problem.
Regards,
Hari

Hi,
It's mentioned the activity of saving BI Query is carried out in Portal, so am assuming you might be using a BEx Web application for this.
If yes, then would suggest you to try once after switching off the standard transport. And instead use BEx transports in Admin workbench.
My understanding can be completely wrong, in which case request you to provide more details on the environment and the steps done.
Thanks,
Swapna Priya.

Add a custom event wihtout modifying the standard in a component controller

Hello,
We are currently working on an enhancement in the DPR_SEARCH component. We added through an enhancement a custom button, with a specific action. Then we would like to fire an event to other components (cross-controllers interface), but we are not able to add the event definition in the DPR_SEARCH component controller, wihout modifying the standard.
Does anyone know if it's possible?
Thank you.
Matthias

Seems not possible...

Activation of the Standard Event

Similar Messages

Maybe you are looking for