SAP BUS2012 Rejection Stop not getting triggered

Hi experts,
I am facing one particular problem. When I am rejecting a PO, by default , REJECTION_START event of BUS2012 is getting triggered, I can see it in SWEL. But when I am cancelling the Rejection REJECTION_STOP event of BUS2012 is not getting triggered. Its not even coming in SWEL(Event trace).What could be the reason as every thing is standard, no custom work.

Hi,
That's strange. Where did you get this idea that this event should be created? (Well, I can see it also in SAP documentation.) And are you sure you are doing the rejection cancellation correctly (well, I don't know how many ways there could possibly be..) - the status of PO is changed, etc.?
SWETYPV should not have anything to do with this problem. The event is either created or not. SWETYPV is about how to react to events after they are created.
Are you sure that there is no filter set up in SWELS for the events. Perhaps the event is created but you cannot see it in SWEL due to a filter.
Regards,
Karri

Similar Messages

/BDL/TASK_PROCESSOR not getting triggered in satellite system from Solman

Hi,
We have scheduled EWA report in Solution Manager for one of the satellite system.
Solution Manager has sudddenly stopped creating of job /BDL/TASK_PROCESSOR0000002218 (ie job which is created immediately as EWA is scheduled in Solution Manager)
/BDL/TASK_PROCESSOR is running correctly and on hourly basis in satellite.
The EWA report is getting generated in Solution Manager after long time and without job /BDL/TASK_PROCESSOR0000002218 (is sessin specific job) being triggered.
Kindly help.
Regards,
Trupti M

Hi Paul,
My problem is solved.
Actually the Task: EarlyWatch Alert for Solution Manager under 'To Do' view of sdccn of satellite system was somehow getting scheduled as Back dated(ie instead of 30.04.2020 it was getting scheduled at 28.04.2010)
Due to this when we would do 'Start now' for the Task 'EarlyWatch Alert for Solution Manage' it was not getting triggered.
So I manually did refresh session which was mentioned under steps for manully sending data to SolMan under solution_mamanger tcode.
Due to this job BDL/TASK_PROCESSOR0000002237 got created.After this job got completed Task ''EarlyWatch Alert for Solution Manager ' got automatically generated.
I back dated the date for Task ''EarlyWatch Alert for Solution Manager" and started it.
Due to this the job /BDL/TASK_PROCESSOR0000002238 got created in satellite system for sending data to SolMan (This was not happening earlier.)
Extract from Solution_Manager tcode when scheduling:
When the Session Refresh task has been processed, a new task with the appropriate session type and session number appears in the To do view. This task collects and sends the data for your session. If a new task does not appear, search in the task-specific log for errors that ocurred during the Session Refresh task and make any necessary corrections.
To start the task immediately, select it and right-click to call up the context menu.
Choose Start Now. When the task has been processed successfully, it appears in the Done view. The data has been sent to your SAP Solution Manager system. You can check this in the task-specific log.
Thanks for all your help. Hoping my post will also be helpful for others.
Regards,
Trupti M

Alert is not getting triggered in QA

Hai Experts!
i have transported the Alert Classification and Alert Category from development system to Quality system and i created the alert rule in QA. Now alerts mails are not tiggering. In se30 i have excecuted the RSALERTTEST that time i am getting a mail in the alert inbox and also to my mail box but for a real time data alert is not getting triggered.
Pls help me to solve this issue.
Regard's
Preethi

Hi
Schedule send job
please see as
help.sap says
Send Job
E-mails sent from an SAP application are first stored in a queue. A periodical background process, the SAPconnect send job, gets the e-mails from this queue and sends them over the Internet. To schedule this job in SAPconnect: Administration, proceed as follows:
i.         Choose View ® Jobs.
ii.       If no other job has been scheduled, choose Job ® Create.
iii.      Enter a job name and confirm it.
iv.      Select the variant SAP&CONNECTALL by positioning the cursor on it.
v.        Choose Schedule Job.
vi.      Choose Schedule periodically.
vii.     Select the interval you require, such as 10 minutes.
viii.   Choose Create.
Refer this.
http://help.sap.com/saphelp_nw04/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm

Due to MODIF ID, SELECT query in START-OF-SELECTION not getting triggered

Dear SAP Gurus,
I'm stuck with this program, where, my program is not being executed, as in, my SELECT query in my event START-OF-SELECTION is not getting triggered. Since i hav used MODIF ID, for SELECT-OPTIONS, even after putting the entries in select-options...................when i click on the execute button, or press F8, the program still goes into the AT SELECTION-SCREEN OUTPUT event..........but i want it to goto START-OF-SELECTION event where my SELECT query is........what should i do??????????????
Please find the notepad file having the code, n exucse me for any selection-texts absence.
Need help from u in this issue.
Thanks in advance.
REPORT ZPPR_CONVSTAT NO STANDARD PAGE HEADING.
INCLUDE ZPPR_CONVSTAT_TOP.               " data declaration
INCLUDE ZPPR_CONVSTAT_SEL_CRITERIA.      " selection criteria
INCLUDE ZPPR_CONVSTAT_PBO.               " event at selection-screen output
INCLUDE ZPPR_CONVSTAT_START_SELECTION.   " event start-of-selection
INCLUDE ZPPR_CONVSTAT_F_START_OF_SEL.
*& Include           ZPPR_CONVSTAT_TOP
TABLES : VBUK,
          VBUP,
          VBAK,
          VBAP,
          VBEP,
          VBPA,
          TVAK,
          EKUB,
          LIKP,
          LIPS,
          MARA,
          MAKT,
          MARC,
          PLAF,
          AUFK,
          AFKO,
          AFPO,
          AFVC,
          AFVV,
          CRHD,
          PBIM,
          KNA1,
          T134,
          IOHEADER,
          IOITEM.
TYPE-POOLS : slis.
TYPES : BEGIN OF ty_final,
        werks   TYPE vbap-werks, "Plant
        auart   TYPE vbak-auart, "Sales Order Doc. type
        erdat   TYPE vbak-erdat, "Sales Order Creation date
        vbeln   TYPE vbak-vbeln, "Sales Order No.
        posnr   TYPE vbap-posnr, "Sales Order Item No.
        aedat   TYPE vbak-aedat, "Sales Order Change Date
        kwmeng TYPE vbap-kwmeng, "Sales Order qty.
        vdatu   TYPE vbak-vdatu, "Requested Delivery Date
        lfimg   TYPE lips-lfimg, "Sales Order Delivered Qty.
        matnr   TYPE vbap-matnr, "Material ID
        arktx   TYPE vbap-arktx, "Material Description
        strgr   TYPE marc-strgr, "Planning Strategy
        vrkme   TYPE vbap-vrkme, "UOM
        plnum   TYPE plaf-plnum, "Plan Order No.
        gsmng   TYPE plaf-gsmng, "Plan Order Qty.
        auffx   TYPE plaf-auffx, "Plan Order Firming Indicator u2013 Qty.
        stlfx   TYPE plaf-stlfx, "Plan Order Firming Indicator - Component
        erdat2 TYPE aufk-erdat, "Production Order Creation Date
        aufnr   TYPE aufk-aufnr, "Production Order No.
        prdqty TYPE afko-gamng, "Production Order qty.
        pckqty TYPE lips-lfimg, "Packed Delivered Qty.
        psamg   TYPE afpo-psamg, "Allotted scrap
        igmng   TYPE afko-igmng, "Confirmed Yield Qty.
        iasmg   TYPE afko-iasmg, "Confirmed Scrap Qty
        iamng   TYPE afpo-iamng, "Expected Yield
        wemng   TYPE afpo-wemng, "Delivered Qty.
        altscrp TYPE c LENGTH 6, "Allotted Scrap %
        actscrp TYPE c LENGTH 6, "Actual Scrap %
        umrez   TYPE afvv-umrez, "Ups (from Prd. ORD)
        ups     TYPE clobjdat-ausp1, "Ups (from Material Master)
        crtnstl TYPE clobjdat-ausp1, "Carton Style
        ppopr   TYPE clobjdat-ausp1, "Pre-Printing Operation
        brdtyp TYPE clobjdat-ausp1, "Board Type
        lsdim1 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 1
        lsdim2 TYPE clobjdat-ausp1, "Layout Size u2013 Dim 2
        lsgsm   TYPE clobjdat-ausp1, "GSM
        inktyp TYPE clobjdat-ausp1, "Ink Type
        foiltyp TYPE clobjdat-ausp1, "Foiling
        wintyp TYPE clobjdat-ausp1, "Window Type
        lamin   TYPE clobjdat-ausp1, "Lamination
        fsvrnsh TYPE clobjdat-ausp1, "Front Side Varnish
        bsvrnsh TYPE clobjdat-ausp1, "Back Side Varnish
        emboss TYPE clobjdat-ausp1, "Embossing
        punch   TYPE clobjdat-ausp1, "Punching
        paste   TYPE clobjdat-ausp1, "Pasting
        oprno   TYPE afvc-vornr,      "Operation No.
        wrkcntr TYPE crhd-arbpl,      "Work Centre
        oprtxt TYPE afvc-ltxa1,      "Operation Text
        oprqty TYPE afvv-mgvrg,      "Operation qty.
        yield   TYPE afvv-lmnga,      "Yield
        scrap   TYPE afvv-xmnga,      "Scrap
        jobtyp TYPE vbak-augru,      "Job Type
        prordst TYPE bsvx-sttxt,      "Production Order Status
        solinst TYPE vbup-lfsta,      "Sales Order Line Item Status
        sldprty TYPE kna1-name1,      "Sold to Party Name
        shpprty TYPE kna1-name1,      "Ship to Party Name
        shpcity TYPE kna1-ort01,      "Ship to party - City
        END OF ty_final.
TYPES : BEGIN OF ty_vbak,
        auart   TYPE vbak-auart,
        erdat   TYPE vbak-erdat, "Doc creation date
        vbeln   TYPE vbak-vbeln,
        aedat   TYPE vbak-aedat, "Doc change date
        vdatu   TYPE vbak-vdatu, "Requested delivery date
        kunnr   TYPE vbak-kunnr,
        augru   TYPE vbak-augru, "Job Type
        END OF ty_vbak.
TYPES : BEGIN OF ty_vbap,
        vbeln   TYPE vbap-vbeln,
        posnr   TYPE vbap-posnr,
        werks   TYPE vbap-werks,
        matnr   TYPE vbap-matnr,
        arktx   TYPE vbap-arktx,
        kwmeng TYPE vbap-kwmeng,
        vrkme   TYPE vbap-vrkme,
        END OF ty_vbap.
TYPES : BEGIN OF ty_pbim,
        pbdnr TYPE pbim-pbdnr, "Requirements Plan Number
        bdzei TYPE pbim-bdzei, "Independent requirements pointer
        matnr TYPE pbim-matnr,
        werks TYPE pbim-werks,
        END OF ty_pbim.
TYPES : BEGIN OF ty_pbhi,
        bdzei TYPE pbhi-bdzei, "Independent requirements pointer
        pdatu TYPE pbhi-pdatu, "Requirement date
        laeda TYPE pbhi-laeda, "Date of Last Change
        END OF ty_pbhi.
TYPES : BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "STO doc no
        bsart TYPE ekko-bsart,
        reswk TYPE ekko-reswk, "Supplying plant
        aedat TYPE ekko-aedat, "Doc creation date
        END OF ty_ekko.
TYPES : BEGIN OF ty_ekpo,
        ebeln TYPE ekpo-ebeln,
        ebelp TYPE ekpo-ebelp,
        aedat TYPE ekpo-aedat, "Doc change date
        menge TYPE ekpo-menge,
        meins TYPE ekpo-meins,
        matnr TYPE ekpo-matnr,
        txz01 TYPE ekpo-txz01,
        END OF ty_ekpo.
TYPES : BEGIN OF ty_eket,
        ebeln TYPE eket-ebeln,
        ebelp TYPE eket-ebelp,
        eindt TYPE eket-eindt, "Requested delivery date
        END OF ty_eket.
TYPES : BEGIN OF ty_lips,
        vbeln TYPE lips-vbeln,
        posnr TYPE lips-posnr,
        vgbel TYPE lips-vgbel,
        vgpos TYPE lips-vgpos,
        lfimg TYPE lips-lfimg,
        END OF ty_lips.
TYPES : BEGIN OF ty_plaf,
        plnum TYPE plaf-plnum,
        matnr TYPE plaf-matnr,
        gsmng TYPE plaf-gsmng,
        auffx TYPE plaf-auffx,
        stlfx TYPE plaf-stlfx,
        kdauf TYPE plaf-kdauf,
        kdpos TYPE plaf-kdpos,
        pbdnr TYPE plaf-pbdnr,
        END OF ty_plaf.
TYPES : BEGIN OF ty_aufk,
        aufnr TYPE aufk-aufnr,
        erdat TYPE aufk-erdat,
        objnr TYPE aufk-objnr,
        END OF ty_aufk.
TYPES : BEGIN OF ty_afko,
        aufnr TYPE afko-aufnr,
        gamng TYPE afko-gamng, "Total order quantity
        gasmg TYPE afko-gasmg, "Total scrap quantity in the order
        igmng TYPE afko-igmng, "Confirmed Yield Qty
        iasmg TYPE afko-iasmg, "Confirmed Scrap Qty
        aufpl TYPE afko-aufpl, "Routing number of operations in the order
        END OF ty_afko.
TYPES : BEGIN OF ty_afpo,
        aufnr TYPE afpo-aufnr,
        plnum TYPE afpo-plnum,
        matnr TYPE afpo-matnr,
        pgmng TYPE afpo-pgmng, "Plan Order Qty
        kdauf TYPE afpo-kdauf,
        kdpos TYPE afpo-kdpos,
        psamg TYPE afpo-psamg, "Allotted scrap
        iamng TYPE afpo-iamng, "Expected Yield Variance
        wemng TYPE afpo-wemng, "Delivered Qty
        END OF ty_afpo.
TYPES : BEGIN OF ty_afvc,
        vornr TYPE afvc-vornr,
        aufpl TYPE afvc-aufpl, "Routing number of operations in the order
        aplzl TYPE afvc-aplzl, "General counter for order
        arbid TYPE afvc-arbid, "Object ID of the resource
        ltxa1 TYPE afvc-ltxa1,
        END OF ty_afvc.
TYPES : BEGIN OF ty_afvv,
        aufpl TYPE afvv-aufpl, "Routing number of operations in the order
        aplzl TYPE afvv-aplzl, "General counter for order
        umrez TYPE afvv-umrez,
        mgvrg TYPE afvv-mgvrg,
        lmnga TYPE afvv-lmnga,
        xmnga TYPE afvv-xmnga,
        END OF ty_afvv.
TYPES : BEGIN OF ty_mdvm,
        mdkey TYPE mdvm-mdkey,
        disst TYPE mdkp-disst,
        matnr TYPE mdkp-matnr,
        plwrk TYPE mdkp-plwrk,
        END OF ty_mdvm.
DATA : it_final TYPE STANDARD TABLE OF ty_final,
        it_vbak   TYPE STANDARD TABLE OF ty_vbak,
        it_vbap   TYPE STANDARD TABLE OF ty_vbap,
        it_lips   TYPE STANDARD TABLE OF ty_lips,
        it_pbim   TYPE STANDARD TABLE OF ty_pbim,
        it_pbhi   TYPE STANDARD TABLE OF ty_pbhi,
        it_ekko   TYPE STANDARD TABLE OF ty_ekko,
        it_ekpo   TYPE STANDARD TABLE OF ty_ekpo,
        it_eket   TYPE STANDARD TABLE OF ty_eket,
        it_plaf   TYPE STANDARD TABLE OF ty_plaf,
        it_aufk   TYPE STANDARD TABLE OF ty_aufk,
        it_afko   TYPE STANDARD TABLE OF ty_afko,
        it_afpo   TYPE STANDARD TABLE OF ty_afpo,
        it_afvc   TYPE STANDARD TABLE OF ty_afvc,
        it_afvv   TYPE STANDARD TABLE OF ty_afvv,
        it_mdvm   TYPE STANDARD TABLE OF ty_mdvm.
DATA : wa_final TYPE ty_final,
        wa_vbak   TYPE ty_vbak,
        wa_vbap   TYPE ty_vbap,
        wa_lips   TYPE ty_lips,
        wa_pbim   TYPE ty_pbim,
        wa_pbhi   TYPE ty_pbhi,
        wa_ekko   TYPE ty_ekko,
        wa_ekpo   TYPE ty_ekpo,
        wa_eket   TYPE ty_eket,
        wa_plaf   TYPE ty_plaf,
        wa_aufk   TYPE ty_aufk,
        wa_afko   TYPE ty_afko,
        wa_afpo   TYPE ty_afpo,
        wa_afvc   TYPE ty_afvc,
        wa_afvv   TYPE ty_afvv,
        wa_mdvm   TYPE ty_mdvm.
DATA : it_object TYPE hum_object_t,
        wa_object TYPE hum_object,
        it_item   TYPE hum_hu_item_t,
        wa_item   TYPE vepovb,
        count1(6) TYPE n.
DATA : gv_objek TYPE ausp-objek.       "Put matnr for use in FM u2018CLAF_CLASSIFICATION_OF_OBJECTSu2019
DATA : BEGIN OF it_sclass OCCURS 0.
        INCLUDE STRUCTURE sclass.
DATA : END OF it_sclass.
DATA : BEGIN OF it_clobjdat OCCURS 0.
        INCLUDE STRUCTURE clobjdat.
DATA : END OF it_clobjdat.
*& Include           ZPPR_CONVSTAT_SEL_CRITERIA
SELECTION-SCREEN FOR 'PLANNING STAGE'
SELECTION-SCREEN BEGIN OF BLOCK main WITH FRAME TITLE text-001.
PARAMETERS: mrpntdn RADIOBUTTON GROUP sel                    DEFAULT 'X' user-command flag,
              pldord RADIOBUTTON GROUP sel,
              prdord RADIOBUTTON GROUP sel.
SELECTION-SCREEN END OF BLOCK main.
SELECTION-SCREEN FOR 'SELECTION BY PLANT AND PLANT DATA'
SELECTION-SCREEN BEGIN OF BLOCK plant WITH FRAME TITLE text-002.
PARAMETERS      : p_werks   LIKE ioheader-werks OBLIGATORY DEFAULT '1100' MATCHCODE OBJECT H_T001W.
SELECT-OPTIONS : so_matnr FOR   ioitem-matnr                              MATCHCODE OBJECT MAT1.
PARAMETERS      : so_mtart TYPE t134-mtart     OBLIGATORY DEFAULT 'ZFIN' MATCHCODE OBJECT H_T134.
SELECT-OPTIONS : so_plnum FOR   ioitem-plnum                              MATCHCODE OBJECT plnum MODIF ID pld,
                    so_aufnr FOR   ioheader-aufnr                            MATCHCODE OBJECT orde   MODIF ID prd.
PARAMETERS      : p_prdsta LIKE tj02t-txt04                                                       MODIF ID prd.
SELECTION-SCREEN END OF BLOCK plant.
SELECTION-SCREEN FOR 'SELECTION BY REQUIREMENT TYPE'
SELECTION-SCREEN BEGIN OF BLOCK reqtyp WITH FRAME TITLE text-003.
PARAMETERS      : cb_so     TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_sto    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag,
                    cb_pir    TYPE AUSWL_EB AS CHECKBOX USER-COMMAND flag.
SELECTION-SCREEN END OF BLOCK reqtyp.
SELECTION-SCREEN FOR 'SELECTION BY DATE AND REQUIREMENT TYPE NOS'
SELECTION-SCREEN BEGIN OF BLOCK dtreqtypno WITH FRAME TITLE text-004.
SELECT-OPTIONS : so_crtdt FOR vbak-erdat                                                                MODIF ID gen,
                    so_vbeln FOR vbap-vbeln                                  MATCHCODE OBJECT WTY_F4_VBAP MODIF ID rso,
                    so_posnr FOR vbap-posnr                                                                MODIF ID rso,
                    so_ebeln FOR ekub-ebeln                                  MATCHCODE OBJECT MEKKM        MODIF ID rst,
                    so_ebelp FOR ekub-ebelp                                                                MODIF ID rst,
                    so_pbdnr FOR pbim-pbdnr                                                                MODIF ID rpi,
                    so_reqdt FOR vbep-edatu                                                                MODIF ID gen.
SELECTION-SCREEN END OF BLOCK dtreqtypno.
SELECTION-SCREEN FOR 'SELECTION BY OTHER PARAMETERS'
SELECTION-SCREEN BEGIN OF BLOCK othrparam WITH FRAME TITLE text-005.
SELECT-OPTIONS : so_kunnr FOR kna1-kunnr                                   MATCHCODE OBJECT debi   MODIF ID rso,
                    so_auart FOR tvak-auart                                   MATCHCODE OBJECT H_TVAK MODIF ID rso,
                    so_lfsta FOR vbup-lfsta                                                           MODIF ID rso.
SELECTION-SCREEN END OF BLOCK othrparam.
*& Include           ZPPR_CONVSTAT_PBO
*&   Event AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN OUTPUT.
IF mrpntdn = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF pldord = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'PLD'.
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
      IF screen-group1 = 'PRD'.
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ELSEIF prdord = 'X'.
    LOOP AT SCREEN.
      IF ( screen-group1 = 'PLD' OR screen-group1 = 'PRD' ).
        screen-intensified = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF ( cb_so = ' ' AND cb_sto = ' ' AND cb_pir = ' ' ).
    LOOP AT SCREEN.
      IF ( screen-group1 = 'GEN'
      OR screen-group1 = 'RSO'
      OR screen-group1 = 'RST'
      OR screen-group1 = 'RPI' ).
        screen-active = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
ENDIF.
IF cb_so = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'RSO'.
        screen-active = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_sto = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_pir = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RPI'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ELSEIF cb_pir = 'X'.
    IF cb_so = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RSO'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
    IF cb_sto = ' '.
      LOOP AT SCREEN.
        IF screen-group1 = 'RST'.
          screen-active = 0.
          MODIFY SCREEN.
        ENDIF.
      ENDLOOP.
    ENDIF.
ENDIF.
*& Include           ZPPR_CONVSTAT_START_SELECTION
*&   Event START-OF-SELECTION
IF mrpntdn = 'X'.
PERFORM start_of_selection_mrpntdn.
ELSEIF pldord = 'X'.
PERFORM start_of_selection_pldord.
ELSEIF prdord = 'X'.
PERFORM start_of_selection_prdord.
ENDIF.
*& Include           ZPPR_CONVSTAT_F_START_OF_SEL
*&      Form START_OF_SELECTION
      Subroutine for MRP NOT DONE
FORM start_of_selection_mrpntdn.
    SELECT mdkey INTO TABLE it_mdvm FROM mdvm
                 WHERE GSAEN = 'X'
                   AND AKKEN = 'X'.
      IF sy-subrc = 0.
        LOOP AT it_mdvm INTO wa_mdvm.
          wa_mdvm-disst = wa_mdvm-mdkey(3).
          wa_mdvm-matnr = wa_mdvm-mdkey+3(18).
          wa_mdvm-plwrk = wa_mdvm-mdkey+21(4).
          MODIFY it_mdvm FROM wa_mdvm INDEX sy-index TRANSPORTING disst matnr plwrk.
        ENDLOOP.
      ENDIF.
ENDFORM.
*&      Form START_OF_SELECTION
      Subroutine for PLAN ORDER CREATED
FORM start_of_selection_pldord.
ENDFORM.
*&      Form START_OF_SELECTION for PRODUCTION ORDER CREATED
      Subroutine for PRODUCTION ORDER CREATED
FORM start_of_selection_prdord.
ENDFORM.

You need to mention START-OF-SELECTION explicitly in your code.
Change your code as below:
*& Event START-OF-SELECTION
START-OF-SELECTION.
IF mrpntdn = 'X'.

Escalation not getting triggered in Alert

Hi
I have triggered an alert from BPM which is successfully received both in my mail box as well as Alert inbox.
If the Alert is not confirmed, it should trigger an Escalation. In the Alert configuration I have maintained the recipient of the Escalation message, the tolerance limit and also have checked "Escalation Active"
But the Escalation is not getting triggered. Kindly advice...
Anup

Hi Anup,
Please go through these..
http://help.sap.com/saphelp_nw2004s/helpdata/en/96/f1033c128f4a7de10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/4a/2dc1e0778648afa9e69d9a44244def/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
cheers,
Prashanth

Urgent IDOC - EXIT_SAPLLMDE_002 not getting triggered.

I am doing an inbound idoc on message type WMMXY goods movement.
The idoc is sucessfully getting posted when tested through we19.
But the user exit EXIT_SAPLLMDE_002 where i am doing an enhancement is not getting triggered when the idoc is posted.
I have activated the exit functional module, the project in CMOD is also activated.
Some one pls help me .. if u have its document pls post it to me.

Hi,
Please refer to this documentation of user-exit; may be of some help for you.
You can use this user exit to influence the processing of IDOCs of the
message type WMMBXY (goods movements) that are sent to SAP from external
systems via the MM-MOB or WM-LSR interfaces. You can also access
customer-specific processing in this case.
Call transaction and other important requirements
The user exit is performed in the function module that processes the
IDOCs of the message type WMMBXY, after the IDOC is withdrawn and
checked but before direct processing in the application has been
initiated. (That is, the data for the goods movement has already been
determined and edited, but the function module for updating this has not
yet been accessed. The standard function module for processing the
message type WMMBXY is called L_IDOC_INPUT_WMMBXY. The IDOC is processed
in an update task, which means that the source code is also executed in
the update.
If an error arises, then messages should not be issued since processing
is being carried out in the background and the result of processing must
always be returned to the ALE interface. For this reason language
elements such as MESSAGE, COMMIT WORK, LEAVE and the like should not be
used. If errors that should be passed on to the ALE interface or that
affect the result of processing are found in the user exit, you should
also use the user exit MWMIDI07(EXIT_SAPLLMDE_001) since it alone can be
used to take your errors into account (see documentation of the user
exit).
Parameters and options
The user exit in the program is the function module EXIT_SAPLLMDE_002.
In order to be able to use it, you must first create Include zxlidu10
and activate the enhancement by means of transaction CMOD. As
parameters, you can use the following data:
o   Goods movement data already determined from the received IDOC:
    -   Transaction code that is given along with the application
        function module (see interface description (import parameter
        X_TCODE).
    -   Indicator: post only if all items o.k. (import parameter X_XALLP
        ). This indicator must be set by default, to enable IDOC error
        processing.
    -   Indicator: Reset all tables (as primary call) (import parameter
        X_XALLR). This indicator is not set by default to enable the
        processing of several IDOCs. Normally you will not change these
        two indicators.
        -   Goods movement items table (table parameter T_IMSEG)
    o   Received IDOC data:
        -   IDOC control record (import parameter I_IDOC_CONTROL)
        -   IDOC data records (table parameter T_IDOC_DATA)
    This user exit can be used to:
    o   Influence the determined data for the goods movements. All data can
        be changed in this case.
    o   Analyze and process data that is transferred using customer-specific
        segments.
    o   Access additional activities.
    Examples
    A number of potential applications are described below.
A number of potential applications are described below.
o   You want to inform a user by mail when the goods movements of
     certain vendors or customers take place.
o   You want to start your own label printout, for example at goods
     receipt.
o   You want to update your own tables, for example statistical data.
o   You want to analyze a missing parts table at goods receipt and
     redirect the goods receipt correspondingly.
Reward points if helpful.
Regards,
Pankaj Sharma

Alerts not getting triggered from Adapter Framework

Hi,
I have done the following steps for the Alerting:-
1. In configuration of RWB, activated monitoring for XI integration server & XIAdapterFramework and set the monitoring level to 'HIGH'.
2. Scheduled the Report 'SXMSALERT_PROCESS_DATA_GET' on ABAP stack.
3. In the 'further settings' link in End-to-End monitoring, activated the monitoring and set the frequency.
4.Created an alert category using t-code 'ALRTCATDEF' and assigned fixed users(myself) to it.
5.Defined an alert rule with '*' in all conditions and 'No restrictions' for the question 'Where did the error occur'.
Finally after all the steps:-
I am able to receive the alerts in the inbox -
a) by running the test report 'RSALERTTEST'
b) from a control step in BPM.
<b>However, alerts are not getting triggered for an error in the Adapter Framework. (an exception in the Adapter Channel)</b>
When i debugged the SXMSALERT_PROCESS_DATA_GET report, there was step where it was looking for process instances in table 'SSPICSPRHD' which was empty and the alert error log said -
<i> No process instances found for process type ID: 26460B43EB934C4C9ABBE9627380A89E ( XIDomain: domain.00.hqdvsapxi01 )</i>
Any help/hint is welcome !!!
Thanks & Regards,
Renjith.

Hi,
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1382. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
I think this blog will be of help to you..
Cheers,
Divya

BBP... badi is not getting triggered

BBP... badi is not getting triggered... Set External breakpoint... PO getting created, but not stopping in the breakpoint. Does it mean that the badi is not getting fired?

Hi,
If you are trying to debug the badi which creates the backend document(Po/PR),then see the foll threads for more pointers:
Re: How can I debug BADI BBP_CREATE_BE_PO_NEW ??
Re: Debugging a BADI which is called in update task in background.
BR,
Disha.

Release strategy not getting triggered.

Hello,
As per the client request, new Purchase group had to be added to the existing release strategy.
I had added the purchase group in the edit characteristics and in the release strategies: classification.
But now the the release strategy is not getting triggerred.
In CL20n I see that the, status is marked 3 i.e incomplete. The reason to this is not known as customizing done is correct.
In OMGSCK i see that no errors are found with the release strategy.
Please suggest.
Regards,
Neetha

hi,
Sometimes the strategies are taken after restarting the sap system...there has been one same situation before also..at that time the same strategy started working after restarting the sap system...
pls check it may be the same issue with you also..
Regards
Priyanka.P

Treasury workflow not getting triggered .

I have done all as given in the SAP doc ...
The release procedure for the business partner has been set up using a Business Workflow, for
which SAP has defined the standard role 20000053 'TRLOAPPROVAL' and the Workflow
template WS20000263 'WSTRLOAPPROV'.
Procedure
In order to use the release workflow for the business partner, you are also required to make
settings in Customizing for the Basic Functions area in Treasury in the following IMG activities:
By choosing u2019Activate Releaseu2019, you can activate the release for the business partner.
By choosing u2018Maintain and Activate Release Parametersu2019, you can specify the number of
release steps you require for each role category.
By choosing 'Adjust/Copy Workflow Template', make the following settings:
By choosing 'Define Standard Roleu2019, you create the responsibilities for the standard roles
delivered with the system, to which you assign users, positions, organizational units,
work centers, jobs, or people. Using the settings you make here, the system determines
the Responsible Agent [Ext.] during the workflow run.
By choosing 'Adjust Workflow Template', you then have to activate the event linkage.
but its not getting triggered .. the event which is gettting triggered is not the one whcih is used in the workflow
Thanks for help .
Naval Bhatt

Naval,
Either you can check SAP notes for the same or you can customize the workflow. If the event being triggered is different then copy the workflow and change the workflow start condition.

Release procedure with classification not getting triggered

Hi,
I have configured the new release procedure for the PR release of type with classification, but its not getting triggered. Earlier my SAP system had without classification in place, but I wanted to have with classification. Can any one suggest how do I switch between two.
Ideally once I create the release group in with classification procedure that procedure gets activated and gets triggered. Unfortunately its not happening in my case. I tried deleting the entries from the without classification side too, but still it doesnt respond. Is there in patch or note missing.
Your suggestion would be highly appreciated.
sachin

Hi Jurgen,
I am configuring it for PR and with classification method. Well for simplification I am using just purchase group as characteristics, but still its not working. Earlier system had without classification in place, as its there in a default system and used to get triggered. When I created new procedure its not getting triggered. To be assured I deleted the data from witout classification, but still its not working.
Where as I did the same setting for PO, its working and giving me correct releaes strategy.
My characteristic is PRGRP using the communication structure CEBAN and field as EKGRP
Please suggest me on this.
sahcin
Edited by: sachin sagane on May 18, 2010 6:32 PM

Outbound IDOC not getting triggered while new master data is created

Hi Experts,
I am trying to trigger an outbound idoc for Cost Center master data when ever cost center is being created or cost center is being changed. (Usinf COSMAS)
I have successfully made use of change pointers and now able to trigger the idoc when ever Cost Center is getting changed. But while creating new Cost center, IDOC is not getting triggered.
I used the function module MASTERIDOC_CREATE_SMD_COSMAS for triggering the idoc.
Could one of you please let me what would have gone wrong? Since IDOC is getting triggered while changing the master data but not getting triggered while creating new master data.
Thanks in Advance,
Vinoth

Hello,
when you activate BD21 for a message type, it creates a entry in the SAP tables. that these Cost Centers have been sent already and any susequent changes to this will trigger a IDoc.
As for BD16, scheduling it wont help as, you need to specify the selection criteria, and i do not see how you will be able to dynamically get the selection criteria.
Try BD95, and BD59 to create a change pointer for a field, so when ever this fields is modified (new/updated) an idoc will be triggered.
regards,
Abhishek

Exit Class for Inbound Mail not getting triggered

Hi Gurus,
I have created an exit class for processing the Inbound Mail that comes to SAP Inbox (SOIN).
I have set up the Inbound processing rule in transaction SO50 and set it to all recipients.
If i send a mail from any external id to the id configured in SAP then it is coming in SAP Inbox (SOIN) but the exit class for processing the email is not getting triggered.
I have made all the settings for SMTP.
Kindly guide me with the steps needed to be followed for triggering the Exit Class.

Hi
Check u have maintained ur outgoing mail server IP in SCOT transation.
Check link step to configure PO mail.
http://architectsap.com/blog/sap/sap-mm-purchasing-send-purchase-order-by-mail-to-vendor-in-sap/

BDCP_BEFORE_WRITE not getting triggered

Hi all,
I have created an implementation for badi BDCP_BEFORE_WRITE for message type MATMAS. I have also included a break sy-uname statement in the method FILTER_BDCPV_BEFORE_WRITE.
But when I run MM02 and save the material changes, neither the badi is triggered and nor does the control land into the debug mode. I have also executed RBDMIDOC but the badi is still not triggered.
Can anyone tell me how to trigger this badi.I have done all the settings required for change pointers and idocs are getting generated. But the badi is not getting triggered.I am working in SAP version ECC6.0
Any help is highly appreciated.
Thanks in advance.
Shoma

Hi Shoma,
No. You don't require anything else. Please check everything one by one. I am sure you might be missing something.
Check change pointer is active or not
Check with the break-point, where did you put.
Delete the second implementation which you created ..etc
Regards,
Atish

Print program is not getting triggered when saving the application

Hi all,
My requirement is when i save the invoice using VF01 the print program should get triggered.
The print program is not getting triggered when saving the application even when i have configured the outtype and have attached the print program.
The setting "send immediately (when saving application)" is also checked.
I need to configure it for VF01 transaction.
The error message displayed was " please maintain output device in master data".
Regards,
Umesh

Hi Umesh
Please check if you have missed any of the following:
1. Defining Access Sequence(can use existing).
2. Defining Output Condition Type(can use existing). - Assigning the Driver Program and Form in processing routine.
3. Output Determination Procedure
4. Assign Output Procedure to Billing Types
Kind Regards
Eswar

SAP BUS2012 Rejection Stop not getting triggered

Similar Messages

Maybe you are looking for