Standard workflow is not getting triggered

Dear all,
   I have activated standard worflow for QM module for notification, but after saving notification workflow item is not getting diaplayed in Inbox.
Thanx & regards,
Harish.

Hi,
1) Check that workflow triggered or not in SWEL or in the Creator's (SBWP) Outbox --> Started workflows
2) If it was triggered, the agent determination might be failed
3) Also check whether you maintained that task as a General Task.
Regards,
Surjith

Similar Messages

  • ISR Process object - Workflow is not getting triggered -

    Hi
    I am facing some strange problem, in my project we are using the new HCM concept using Process Object and not the Notification type,
    I have take standard scenario SBC1 - child birth, done the config and checked the form and also process its not giving any error.
    But when i tried test process execution "HRASR_TEST_PROCESS", getts error message " Work Item Not Found; Workflow Not Started" and "Process Object Not Created",
    when i check the log in SLG1 tcode for Object: HRASR, Subobject: POBJ. "Case 46CC2D7604BB275EE1000000995893A9 does not exist. No administration authorization in Change and Transport System", this error message only consfuse me more.
    Can you help me on this, if you required i will send the screen shot of the error message
    Regards
    Anand KS

    In most cases, this means that the 'Start Process' is not configured correctly. Take a look at the following:
    1. make sure that the Wf assigned to your start process is active
    2. make sure that reference numbers are configured and assigned to your process
    3. assign a user to receive error messages when an error occurs
    Thanks,
    Derrick Banks

  • Workflow not getting triggered on status change

    Hiii Everyone
    Workflow is not getting triggered whenever I change the status of the Order (Lead).  When we create a lead a workflow is triggered.
    1. If the status is Open a mail is sent.
    2. Then the status is checked for in process. And whenever the  status is changed to inprocess it is assigned to the agent by   the  rule attached to the workflow.
    3. And again when the status is changed to sanctioned a mail is sent.
    Now problem is if I create a lead and change its status to inprocess and then save , then the mail is sent and it is assigned to the agent properly. But when I change the status to sanctioned , then the mail is not sent for sanctioned(i.e. no worklfow step is shown in swel).
    If I open the lead and save it then the mail is sent properly. But then after that when I change the status to inprocess, the workflow is not showing agent assignment (jn swel).
    Summary: Whenever I cahnge the status after saving the order , the workflow is not showing any further step .
    Please suggest the solution.
    Regards
    Shafali

    Hi,
    Your workflow has been triggered when the status is open and then when change the status to in process,it is not sending mail as there is no agent assignment.
    That means, workflow triggered, but it is not going to the next step.
    Is it a standard or custom one?
    Can you post the workflow log screenshot over here?
    Cheers,
    Raja.D

  • Workflow not getting triggered from Z inbound FM

    Hi
    I have created a simple workflow with start events
    Object Type IDOCAPPL EVENT - INPUTERROROCCURRED
    activated the binding and activate the linkage
    also in the idoc inbdound FM i put workflow_result = 99999 also added the object and the start and end event in process code link
    however the workflow is not getting triggered do i need to trigger it manually using swe_event_create....
    what is the miostake

    Hello,
    Even if the event linkage is configured correctly, you have to trigger an event with the FM swe_event_create to run your workflow.
    You have a transaction SWU0 that can simulate an event => then you can check if your event linkage is correct.
    Please reward if useful.
    René

  • OIM 11gR2 Approval workflow not getting triggered

    I created an approval workflow by following the 11gR2 developer's guide and deployed it. then created an app instance and also an approval policy for operational level which is auto approved and for request level with this composite. when i raise a request for this app instance in the catalog the SOA composite is not getting triggered. I am able to see a task in pending approval of system admin whenever i raise request for any user and if i complete that pending approval the app gets provisioned directly. Also i do not see any request ID also. please help to find out whats going wrong

    Now i tried raising a request from another user who is not a member of SYSADMIN role. This time the request id is generated and a task 'Manual Task for Provision operation for Beneficiary X' is generated in pending approvals of xelsysadm user. When completed the app instance gets provisioned. So this means operational level approval task is triggered? and it has auto-provisioning?
    why my custom approval workflow is not getting triggered?
    I have created 2 approval policies, one for request level which is auto approval and other for operational level where i have selected the deployed composite name.In both the approval policies i have selected the request type as Provision ApplicationInstance. There is no error also while deploying the composite. Am i missing any step? please help.
    Edited by: 955932 on Jan 10, 2013 10:19 PM

  • Issue in workflow workitem that gets triggered to two users at one time.

    Hi All,
    Below are the query  details:
    Module:  HR
    Area:      Workflow
    Process: Hiring
    There is an workflow in HR module that is triggered when an hiring action is run against an candidate.
    There are two or three maximum approvers  which is based on the position to which the candidate is hired.
    Issue:
    During the hiring process some times the workitem is getting triggered to two users at once.
    One is the actual approver who should receive the workitem in his UWL and other is the user of our service center who is no where involved in the approval process.
    Analysis Done:
    We checked the workflow log and found that the actual approver's ID is getting displayed under agent and workflow is complete. But the other user's ID is no where shown in the log but he has received an workitem in his UWL that makes the issue still confusing.
    Awaiting for experts suggestions.

    Reply to Susan Questions:
    You say that 'the workitem is getting triggered to two users at once' - do you mean that there are two workflow instances that are being kicked off at the same time when the hiring action is performed? Or is it that the workflow is generating two tasks that go to these different users?
    Ans : There is a single task attached to the activity.
    Is this a custom workflow?
    Ans : Yes.
    Are you certain that the erroneous task is only going to the user in the service center, or is it perhaps going to everybody (marked as a general task)?
    Ans : The task is marked as general but the workitem is received by only one user of the service center at a time.
             As this issue has taken place 4 times in the past year all the 4 receiver were different belonging to different position.
    Reply to Pavan Questions:
    1. Did you try to check the SPRO settings with respect to Hiring Process ,is there any where based on the position does workflow is forwarding the workitem to the other user.
    2. Check the other user Roles and in the Org Structure where he is located , there could be a possibility of wrong position holding.
    Ans : We checked the org structure, but org structure of both the centers are different and independent there is no linkage    between the two.
    *3. IF you are using custom workflow then check if any standard workflow is also getting triggered. Check *
    Ans : Yes this is a custom workflow, but no other Standard workflow is being called.
    4. Check in the SWEHR3 is any custom entries maintained.
    Ans : No, entries are maintained in SWEHR3.
    Additional Info :
    The task that triggers the workitem has an send mail step before it.
    The send mail activity is to notify receiver that there is an workitem lying in the UWL.This mail is received by the actual user and not by the other one.The next step is the task that creates workitem which gets triggered totwo different IDs.
    This scenarios mostly has come up when the number of approver is 1. If the approver is more than 1 the  workflow runs fine without  deviating the workitem to any worng user.

  • Event not getting triggered for a few users in production

    Hi Experts!!
    We have a workflow that gets triggered on the event REQUESTCREATED of BUS2089. In production, we see that for a few users the event is getting triggered and even the workflow is. But for a few users, the workflow is not getting triggered. However, we didn't check SWEQADM yet and are waiting to get auth to check the same. But before that, I need your valuable suggestions on this.
    When I check SWEL, I cannot see any entries at all. Not even for the successfully processed ones.
    Auth objects cannot be a reason, as all the users have same auth. Please suggest me on what else can be the reasons.
    Your help is highly appreciable.

    Hello Srinivas !
                  Check in SWEQADM to know whether the event is on queue.If so, redeliver it.
                  If there is no event on queue, check the RFC queue( transaction SWU2 ) and ST22 for possible ABAP dumps.
                  Call work item list report (transaction SWI1) and check event linkages (transaction SWETYPV )of the users for whom the event is not triggered.Are you using BAdI or user- exit to trigger the workflow ? If so, check whether those are in active state.
                 Refresh the workflow buffers(transaction SWU_OBUF).Check either of the workflow versions are in active state.
    Regards,
    S.Suresh

  • 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.

  • Workflow not getting triggered from MM01

    Hi,
    I understand there is a similar post but the solution is not so clear there.
    I wish to trigger a workflow whenever a material is created using tcode MM01.
    For which i am using BUS1001. (In the header data > start events tab > BO/BUS1001/CREATED binding exists and activated)
    whenever i am creating a material using MM01, and check the trace in SWEL i am getting the following info:
    BUS1001006     VIEWCREATED     25.03.2011     13:00:12          @AI@     No receiver entered
    BUS1001006     CREATED     25.03.2011     13:00:12     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    Can someone please help where to enter the receiver.
    regards
    abhishek

    Hi sanju,
    I have created the event as per your suggestions but the workflow is not yet triggered from mm01.
    the event stack trace is as follows :-
    BUS1001     CREATED     28.03.2011     08:28:42     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
    BUS1001006     VIEWCREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
    BUS1001006     CREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
    BUS1001     CREATED     28.03.2011     08:33:03     WS99900237     @5B@     SWW_WI_CREATE_VIA_EVENT
    Linkage is activated in SWE2 and the receiver  FM is SWW_WI_CREATE_VIA_EVENT.
    still unable to get the workflow triggered.
    Secondly as per SAP suggestion the BO BUS1001006 should be used for std material master. But while i enter BUS1001006 no such methods are available in F4. (refer atttachment)
    I have checked in the BOR and i see that BUS1001006 is released and active.

  • Workflow not getting triggered from Action definition in CRMD_ORDER

    Hello Experts,
    I have created a workflow which should send mail to partner team in a Change Request.This workflow should be triggered when a particular Zaction is performed on the CR.Zaction is created properly and my workflow is also assigned to it.I have also followed OSS note-733675 and created a workflow container with name "BUSINESSOBJECT" to get the application data into my workflow when the action is performed.My workflow is a background processing one.
    I have tested it separately by providing GUID foreground and it works perfectly fine and mail is sent to partner team.But when i perform the action,mails are not getting triggered nor the workflow.I am not even able to check the logs.I am not even able to know if all the action has triggered my workflow.Kindly help.Would appreciate your contribution.
    Regds
    VLP

    Please check in SWI2_FREQ whether the Workflow is really getting triggered.
    Thanks
    Arghadip

  • Issue in Production for Workflow not getting Triggered .

    Hi Guys,
    I have a workflow, which is properly triggering in the development and Quality but not getting triggered in the Production. Can't get the Exaact reason because by using T-code PFTC when i test the workflow independantly its working properly and even BOR does not have any problem. Please Help me guys as this is a issue in Production.
    The workflow is a customized one, It getting triggered throught the funtion call in User Exit of MM01.
    Thanks

    It getting triggered throught the funtion call in User Exit of MM01.
    1. I hope the workflow customization is done properly in production system, as you stated that if you are trying to trigger from PFTC then it is working fine, can you please try to Refresh Organizational Environment  from SBWP ---> On MEnu  ---> Settings  --> Workflow Settings  ---> Refresh Organizational Environment and  secondly try to refresh the buffer from txn SWU_OBUF
    2. Make sure the user exit is transported to Production.
    3. Check the workflow log from the txn SWIA  if you have proper authorizations for the userid.

  • If standard Workflows are not available what to do?

    Hi,
    Can anyone please tell me if any standard workflow is not available how to go for our own workflows???

    Hi Chaterjee,
    I really did not understand the query in FULL, but i am expecting that you are trying to trigger a WF when a particular action takes place in a Standard SAP transaction.
    There will be a Business Object (Trn: SWO1)and a corresponding Event that would be triggered whenever an action takes place in a Standard Transaction scenario. There could be a Standard WF that could get triggered whenever this event occurs.
    But it may not suit our customer requirement. There could be a case where the Standard has not delivered a WF itself. Then we go for creation of new WF based on the Business Object EVENT that is triggered by the standard. The WF will have the Event of the Business Object in the Triggering Events Tab. Creation of WF is done using Trn: SWDD or PFTC.
    Now if there is no business object and an event then you need to create one and trigger it explicitly in an user-exit/BADI whenever that action in the standard transaction occurs.
    This description may not solve your problem but might give you a picture what you may be looking for. Please let me know if further details are required from my side.
    Thanks & Regards,
    Goutham.

  • User command is not getting triggered in interactive ALV with LIST display

    Hi experts,
    I have developed an interactive ALV report with LIST display. Here, the issue is, when i double click a record in the primary ALV list, the control must go to the USER COMMAND event which i have written in my report. But the user command event is not getting triggered at all when i double click any record.
    It gives the following information instead.
    "Choose a valid function".
    (My user command name and its respective form name are same.)
    Here is my code..
    START-OF-SELECTION.
      CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
        EXPORTING
          i_callback_program       = sy-repid
          i_structure_name         = p_table
          i_callback_user_command  = 'TST1'
          i_callback_pf_status_set = 'SET_PF_STATUS'
        TABLES
          t_outtab                 = <dyn_table>
        EXCEPTIONS
          program_error            = 1
          OTHERS                   = 2.
      IF sy-subrc <> 0.
      ENDIF.
    FORM tst1 USING r_ucomm LIKE sy-ucomm
                    rs_selfield TYPE slis_selfield.
    * Local data declaration
      DATA: li_tab TYPE REF TO data,
            l_line TYPE REF TO data.
    * Local field-symbols
      FIELD-SYMBOLS:<l_tab> TYPE table,
                    <l_wa>  TYPE ANY.
    * Create table
      CREATE DATA li_tab TYPE STANDARD TABLE OF (p_table).
      ASSIGN li_tab->* TO <l_tab>.
    * Create workarea
      CREATE DATA l_line LIKE LINE OF <l_tab>.
      ASSIGN l_line->* TO <l_wa>.  CASE r_ucomm.
    *   When a record is selected
        WHEN '&IC1'.
    *     Read the selected record
          READ TABLE <dyn_table> ASSIGNING <dyn_wa> INDEX
          rs_selfield-tabindex.      IF sy-subrc = 0.
    *       Store the record in an internal table
            APPEND <dyn_wa> TO <l_tab>.
    *       Fetch the field catalog info
            CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
              EXPORTING
                i_program_name         = 'Z_DEMO_PDF_JG'
                i_structure_name       = p_table
              CHANGING
                ct_fieldcat            = i_fieldcat
              EXCEPTIONS
                inconsistent_interface = 1
                program_error          = 2
                OTHERS                 = 3.
    Please advice what is the msitake i have done here..

    Read the following code:
    pass the  i_callback_user_command = g_user_command to the ALV function module and write the FORM user_command USING ucomm    LIKE sy-ucomm
                            selfield TYPE slis_selfield.
    as shown below.
    thanx
    Data for ALV display
    DATA  : gt_fieldcat TYPE slis_t_fieldcat_alv,
            gt_events           TYPE slis_t_event,
            g_variant LIKE disvariant,
            g_user_command      TYPE slis_formname VALUE 'USER_COMMAND',
            g_status            TYPE slis_formname VALUE 'SET_PF_STATUS',
            gt_list_top_of_page TYPE slis_t_listheader,
            g_repid LIKE sy-repid,
            gf_pos TYPE i
    Data for ALV display
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
               EXPORTING
              i_callback_program      = g_repid
                 i_callback_program      = sy-repid
                 it_fieldcat             = gt_fieldcat[]
           it_events               = gt_events[]
              i_callback_user_command = g_user_command
                 i_save                  = 'A'
                 is_variant              = g_variant
               TABLES
                 t_outtab                = it_print.
    FORM user_command USING ucomm    LIKE sy-ucomm
                            selfield TYPE slis_selfield.
      CASE ucomm.
        WHEN '&IC1'.
          CASE selfield-sel_tab_field.
            WHEN '1-KUNNR'.
              READ TABLE it_print INTO wa_print INDEX selfield-tabindex.
              IF sy-subrc = 0.
                SET PARAMETER ID 'BPA' FIELD wa_print-kunnr.
                CALL TRANSACTION 'BP'.
              ENDIF.
            WHEN '1-MATNR'.
              READ TABLE it_print INTO wa_print INDEX selfield-tabindex.
              IF sy-subrc = 0.
                SET PARAMETER ID 'JP_ISS' FIELD wa_print-matnr.
                CALL TRANSACTION 'JP29' AND SKIP FIRST SCREEN..
               GET PARAMETER ID 'WRK' FIELD wa_zprint-werks.
               SET PARAMETER ID 'VKO' FIELD wa_zprint-vkorg.
               SET PARAMETER ID 'VTW' FIELD wa_zprint-vtweg.
               CALL TRANSACTION 'JP29' AND SKIP FIRST SCREEN.
              ENDIF.
    Endcase.
    Endform.

  • 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'.

  • Events in USER objects type not getting triggered in PFCG

    Hi,
    We need to send some notifications to the concern person at the time of assiging roles to the user . There is an object type USER and has events like created,cloned, deleted, roles_changed. But these events not getting triggered.
    I need to trigger the workflow. How do we activate the events as the entry doesnot exits in SWE2 tooo . Is ther any other way?

    HI munish
    If the entry is not in swe2 Put the entry for the business object USER and use the receiver type as your workflow number.
    Regards
    vijay

Maybe you are looking for