SM62 & SM64

I'm trying to understand the concept of SM62. So if I want to manually trigger an event, lets say a process chain, so that means firrst I have to maintan an event for it in SM62? If yes, can anyone guide me through the process ? thanks in advance

Hi...
SM62 Display/Maintain events in SAP ie to create an event.....
also use function BP_EVENT_RAISE
An SAP event is a "flag" that is created in SAP (SM62). This event (or flag) can be triggered (from a Unix job to an incoming file), causing a job to execute in the background. This event (or flag) can be triggered within R/3 or can be done at the Unix level.
First, create an event in SM62. Itu2019s easy - just create it under "user event names" and "maintain". Youu2019ll find the create option from there.
Once created go to SM36 and create the job. Put in the job name you want to call it - fill in the ABAP/4 program youu2019ll want executed, but under "START DATE" select option AFTER EVENT. Then plug in your SAP event name you created. Fill in the remaining information on this screen and save.
Once saved, an entry is put in table BTCEVTJOB. The entry is the name of the event you raised. This is the systemu2019s way of keeping track of which jobs are in the queue waiting for an event to occur.
Now, once the event is triggered this newly created job will execute. The event can be triggered via sap (SM64)
If you want to trigger the event manually from within SAP, use transaction
SM64
or
Create an event in SM62
Call that event using BP_event raise fn module
Check this Link :
http://help.sap.com/saphelp_46c/helpdata/en/c5/e4aec8453d11d189430000e829fbbd/frameset.htm
Hope this helps you...
Regards,
Debjani...
Edited by: Debjani  Mukherjee on Sep 8, 2008 7:53 AM

Similar Messages

  • Object level checking for some of the basis tcodes(internal audit)

    Hi masters,
    in our company every month we check access controls for some of basis tcodes,i am giving it below,is the selection for Tcode and object level values combinations are correct or is there any modifications please notify.
    Tcodes     Imp Auth Objects     Auth fields     Auth  values
    SCC1     S_CLNT_IMP     Actvt     21,60
         S_TABU_CLI     CLIIDMAINT     X
    SCC4     S_TABU_CLI     CLIIDMAINT     X
         S_TABU_DIS     Authorization Group     *
              Actvt     01,02
    SCC5     S_CLNT_IMP     Actvt     21,60
         S_TABU_CLI     CLIIDMAINT     X
    SCC7     S_TRANSPRT     Request type     *
              Actvt     43,60,75
         S_CLNT_IMP     Actvt     21,60
    SCC8     S_DATASET     PROGRAM     *
              Actvt     06,34,A7
         S_TRANSPRT     Request type     *
              Actvt     43,60,75
    SCC9     S_TABU_CLI     CLIIDMAINT     X
         S_CLNT_IMP     Actvt     21,60
    SCCL     S_TABU_CLI     CLIIDMAINT     X
         S_CLNT_IMP     Actvt     21,60
    SCU0     S_TABU_DIS     Authorization Group     SS
              Actvt     01,02
         S_TABU_RFC     Actvt     3
    OBR1               
    SM01     S_ADMI_FCD          TLCK
    SM04     S_ADMI_FCD          PADM
    SM12     S_ENQUE     S_ENQ_ACT     DPFU,DLOU
    SM13     S_ADMI_FCD          UADM,UMON
    SM50     S_ADMI_FCD          PADM
    SM54     S_ADMI_FCD          NADM
    SM55     S_ADMI_FCD          NADM
    SM56               
    SM59     S_ADMI_FCD          NADM
                   RFCA
    SMLT     S_LANG_ADM     Actvt     02,16,61
              Table     *
    SPAD     S_SPO_DEV     SPODEVICE     *
    SP01     S_SPO_DEV     SPODEVICE     *
         S_ADMI_FCD          SP01,SP0R
    ST01     S_ADMI_FCD          ST0M,ST0R
    ST05     S_ADMI_FCD          ST0M,ST0R
    RZ04     S_RZL_ADM     Actvt     1
    RZ06     S_RZL_ADM     Actvt     1
    RZ10     S_RZL_ADM     Actvt     1
    RZ21     S_RZL_ADM     Actvt     1
         S_BTCH_JOB     JOBGROUP     *
              JOBACTION     DELE,RELE
    SM49     S_LOG_COM     Command     *
              Opsystem     *
              Host     *
         S_RZL_ADM     Actvt     1
    SM69     S_RZL_ADM     Actvt     1
    SM63     S_RZL_ADM     Actvt     1
    SMLG     S_RZL_ADM     Actvt     1
    SE16     S_TABU_DIS     Authorization Group     *
              Actvt     01,02
    SM30     S_TABU_DIS     Authorization Group     *
              Actvt     01,02
    SM31     S_TABU_DIS     Authorization Group     *
              Actvt     01,02
    SPRO     S_PROJECT     PROJECT_ID     *
              APPL_COMP     *
              PROJ_CONF     *
              Actvt     02,06
         S_DOKU_AUT     DOKU_ACT     MAINTAIN
              DOKU_DEVCL     *
              DOKU_MODE     *
    SPRO_ADMIN     S_PROJECTS     APPL_COMP     *
              PRCLASS     *
              Actvt     01,70
         S_PROJECT     PROJECT_ID     *
              APPL_COMP     *
              PROJ_CONF     *
              Actvt     02,06
    PFCG     S_USER_AGR     ACT_GROUP     *
              Actvt     01,02
         S_USER_PRO     Actvt     01,02
              PROFILE     *
    SM19     S_ADMI_FCD          AUDA,AUDD
    SU01     S_USER_AGR          *
                   01,02
         S_USER_GRP     Class     *
              Actvt     01,02
    SU02     S_USER_PRO     Profile     *
              Actvt     01,02
    SU03     S_USER_AUT     OBJECT     *
              AUTH     *
              Actvt     01,02
         S_USER_PRO     Profile     *
              Actvt     01,02
    SU05               
    SU10     S_USER_GRP     Class     *
              Actvt     01,02
    SU12     S_USER_GRP     Class     *
              Actvt     01,02
    SU20     S_DEVELOP     DevClass     *
              ObjectType     SUSO
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SU21     S_DEVELOP     DevClass     *
              ObjectType     SUSO
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SU22     S_DEVELOP     DevClass     *
              ObjectType     SUST
              ObjectName     *
              P_Group     *
              Actvt     01,02
    CMOD     S_DEVELOP     DevClass     *
              ObjectType     CMOD
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SA38     S_PROGRAM     P_Action     SUBMIT,BTCSUBMIT
              P_Group     *
    SD11     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     UDMO,UENO
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE11     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     DOMA,DTEL.ENQU
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE12     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     DOMA,DTEL.ENQU
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE13               
    SE14     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     INDX.MCID,TABL
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE15     S_DEVELOP     DevClass     *
              ObjectType     *
              ObjectName     *
              P_Group     *
              Actvt     3
    SE37               
    SE38     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     FUGR,PROG
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE93     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     TRAN
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE41     S_DEVELOP     DevClass     *
              ObjectType     *
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE43     S_DEVELOP     DevClass     *
              ObjectType     *
              ObjectName     *
              P_Group     *
              Actvt     3
    SE43N     S_DEVELOP     DevClass      '
              ObjectType      '
              ObjectName      '
              P_Group      '
              Actvt     01,02
    SE51     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     FUGR,PROG,DYNP
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE80     S_DEVELOP     DevClass     T,Y,Z*
              ObjectType     *
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE81     S_DEVELOP     DevClass     *
              ObjectType     *
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE82     S_DEVELOP     DevClass     Y,Z
              ObjectType     APPLTREE
              ObjectName     *
              P_Group     *
              Actvt     01,02
    SE91               
    SE92               
    SE92N               
    SNRO     S_NUMBER     NROBJ     *
              Actvt     02,17,11
    SQ00     S_QUERY     Actvt     02,23
    SQ01     S_QUERY     Actvt     02,23
    SQ02     S_QUERY     Actvt     02,23
    SQ03     S_QUERY     Actvt     23
    SQVI               
    SM35     S_BDC_MONI     BDCAKTI     ABTC,AONL,DELE
    SM35P     S_BDC_MONI     BDCAKTI     ANAL
    SM36     S_BTCH_ADM     BTCADMIN     Y
    SM37     S_BTCH_JOB     Jobaction     PROT,SHOW
              Jobgroup     *
    SM39               
    SM62               
    SM64     S_BTCH_ADM     BTCADMIN     Y
    SE01     S_CTS_ADMI     CTS_ADMFCT     EPS1,EPS2,PROJ
         S_TRANSPRT     Actvt     *
              Ttype     *
    SE06     S_C_FUNCT     PROGRAM     SAPLSTRF,SAPLSTRI
              CFUNCNAME     SYSTEM
              ACTVT     16
         S_TRANSPRT     Actvt     43,60,65
              Ttype     *
    SE09     S_TRANSPRT     Actvt     43,60,65
              Ttype     *
         S_CTS_ADMI     CTS_ADMFCT     EPS1,EPS2,PROJ
    SE10     S_TRANSPRT     Actvt     43,60,65
              Ttype     *
         S_CTS_ADMI     CTS_ADMFCT     *
    SPAM     S_CTS_ADMI     CTS_ADMFCT     IMPA,IMPS
         S_TRANSPRT     Actvt     43,60,65
              Ttype     PATC,PIEC
    STMS     S_CTS_ADMI     CTS_ADMFCT     *
         S_RFC     Actvt     16
              RFC_NAME     EPSF,STPA
              RFC_TYPE     FUGR
    Edited by: rameshbabu muddana on Mar 2, 2009 10:56 AM

    hi,thanks for reply "you should not care about the transaction start s_tcode at all - only check the object required"
    It has made manditory policy to check for users and roles every month with given criteria of Tcode and object,now i have been given the task to check the combination of Tcode and object value combination are correct or not,please validate the combinations and suggest,we are using ECC 5.0,i had gone through wild card use (#) when we check in SUIM,i am getting confused that when i give # followed by value, data i am getting different from without #.please provide an example for SE16 with S_TABU_DIS
    how to check?
    i am checking in this way
    S_TCODE       SE16
    S_TABU_DIS
    Activity                   
    Value  01or 02
    Authorization Group
    Value  #&NC&

  • SM64 & SM62

    Why doesnt my process chain appear in SM62 ? i'm trying to trigger the even manually through SM64 but the process chain I want to trigger is not recognized. wht could be the problem

    Hi Farhan,
    You have to trigget your event manually in sm64. You cannot see your process chain there. You have to enter your Event name in sm64 (start process->after event) and trigger it. you have to maintain your event name in sm62 before you trigger the event.
    Hope that helps.
    Thanks.

  • Event History SM62 - doesn't show the events raised

    Hello,
    I definded an event within SM64 and raised the event during a perodical job. Now I thought to see the events with SM62, but there are only old events listed. I checked the selection criteria and changed them that all events should be listed.
    Has anyone an idea?
    Regards Geert

    Hi Juan.
    I have the authorization and I'm also able to list "old" events. Could it have something to do that I raised the events with the report BTC_EVENT_RAISE?
    Regards Geert
    P.S. Thanks for the first reply

  • SM64 doesn't work

    Hi All!
      I've created an user event in SM62 to use in a process chain. I've declared the event at "Start" in my process chain without a parameter and checked "periodic job".
       When I try to trigger this event in transaction SM64, my process chain doesn't start.
       Does anybody can help me? Did I miss any step?
    Thank you!!
    Aline

    Did you activate and schedule your process chain?  Go into your process chain using RSPC.  Right-click on the Start variant and select "Displaying Scheduled Job(s)...  You should see a job called BI_PROCESS_TRIGGER.  This is the job that starts your process chain.  Check the start conditions of this job.
    Hope this helps.

  • Whats is the use of SM64 Tcode?? and about Trigger Event???

    Hi
    Whats is the use of SM64 Tcode?? and about Trigger Event???
    Can anyone tell me??
    Thanks & Regards
    Senthil

    Hi,
    When scheduling a background job, you can specify it to start "after event".
    If you do so, you'll have to create an event in SM62.
    If a job is scheduled after event event and you trigger the event with SM64, the job will start.
    Events can be raised by external systems in SAP by sending a command to a SAP application server. You can also raise event in any program using function mosule BP_EVENT_RAISE.
    hope this helps....
    Olivier.

  • What does SM64 Do , BDC...

    Hi,
    I want to know hat does t-code SM64 do?
    It triggers an event. I want to know what sort of event does it trigger, I am making a BDC for that but am not sure for all of its functionality.I also want to know when exactly does it create an event manually...
    Also in the program if the bdc executes then under which circumstances does an entry be present in SM35 and not present in Sm35 if SY-SUBRC =0, i.e no error.
    Regards
    Arnab.

    Hope this will help.
    Events let you start background jobs when particular changes in the SAP system take place. When an event occurs, the background processing system starts all jobs that were scheduled to wait for that event.
    http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
    Events have meaning only in the background processing system. You can use events only to start background jobs.
    Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
    http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e37543b11d1898e0000e8322d00/frameset.htm
    Use function module BP_EVENT_RAISE to trigger an event from an ABAP program.
    Example
    Report processing before triggering event...
    Trigger event to start background jobs waiting for the event.
    DATA: EVENTID LIKE TBTCJOB-EVENTID.
    DATA: EVENTPARM LIKE TBTCJOB-EVENTPARM.
    EVENTID = 'SP_TEST_EVENT'. " Event name must be defined
    " with transaction SM62.
    EVENTPARM = 'EVENT1'. " Optional: a job can be
    " scheduled to wait for an
    " EVENTID or combination of
    " EVENTID and EVENTPARM.
    CALL FUNCTION 'BP_EVENT_RAISE' " Event is triggered. Jobs
    EXPORTING " waiting for event will be
    EVENTID = EVENTID " started.
    EVENTPARM = EVENTPARM
    TARGET_INSTANCE = ‘ ‘ " Instance at which an event
    " should be processed. Can
    " generally be omitted.
    EXCEPTIONS OTHERS = 1. " Exceptions include event not
    " defined, no EVENTID
    " exported, etc.
    Regards,
    anver

  • What is SM62 Tcode is used for? and the consequence's for executing it?

    What is SM62 Tcode is used for? and the consequence's for executing it?
    Thank you,
    York

    Hi Les,
    You can goto this URL to understand more about events :
    http://help.sap.com/saphelp_nw2004s/helpdata/en/44/c079239d3756a2e10000000a1553f6/frameset.htm
    http://www.sapfans.com/sapfans/sapfaq/robert.htm
    About my experience working with events:
    In one of my BW Project: we were using AutoSys to do job scheduling (to run InfoPackages).
    To automate the loading process we created events for  each infopackage. Then in that Infopackage we used to select option "Start later in Background" and then select option "After Event". Then specified the event name and parameter.
    Then in the same infopackage we selected button "Subsequent Process" the in that seelct option "Trigger Events" Here you can have options to specify if this event is successful then what next event to trigger and if this event fails what next event to trigger.
    So this way we used to automate data loads.
    This was dont caz there was no process chains concept during that time. So good example of events and event based process are PROCESS CHAINS.
    Hope this helps !!
    Assign points if helps !!
    Regards,
    Naveen Rao Kattela

  • Want to add event created through SM62 in transport request?

    Hi Guys,
    i have created one Event in SM62 but it did not ask for any transport while creation.
    So to add this event to transport so that it can be made available in other systems?
    Thanks,
    GURU

    Hi Guru
    Have you checked if the events are directly maintainable in respective servers?
    Kind Regards
    Eswar

  • Event SM62 - Is it possible to pass some parameters ?

    Hello,
    with SM62 transaction is possible to create an event.
    there's the possibility to manage the parameters ?
    I mean, I call the event X for material number Y.
    The program or job (for exemple) that is triggered can read that the parameters is article N° y ? How do it ?
    Thank you,
    Roberto

    Hi,
    I don't think you can pass any parameters while triggering an event.
    However, If you are raising the event through ABAP, you can update the material number to a Ztable and make use of it in the background job. May be you can use a flag in the Ztable to set once the background job process a particular material.
    Regards,
    Karthik D

  • Event in SM62...urgent

    I know the event maintained in SM62. I want to check where it is triggering in which program.
    How to find that????
    Thanks.

    Hi,
      Refer
    https://forums.sdn.sap.com/click.jspa?searchID=10281667&messageID=3305610
    Regards
    Kiran Sure

  • How to trigger event from SM64

    Hi Experts
    I have an interrupt variant in my process chain, it is still not proceeding even if data load is complete for which it is waiting for.
    my friend suggested me to trigger that event in SM64.
    but i  know nothing about that. can you help.

    Hi
    Goto SM64 --> search for your event.
    select the event --> click on extent trigger
    check the below document
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/c079239d3756a2e10000000a1553f6/frameset.htm
    Regards,
    Venkatesh

  • Event handling through SM62 in 6.0

    Hi All
    How can I create Background process event in 6.0? As when I am saving it after putting the event name and description it is not showing the name in the Background Process list.

    Solved

  • How can I trigger an event from an ABAP Program

    Hi everyone,
    I have a requirement, where I have to create an ABAP program, that has to execute (trigger) an event which belongs to a Process Chain. when I run the program, the Process Chain has to run.
    So, how can I do it?
    Thanks for your help, Federico

    HI ,
    The program can call function module BP_EVENT_RAISE to raise the event. you can create vent in sm64 and sm62 .There you give the parameter of the event same as what you will define in the event of start variant of your process chian ..
    Regards,
    shikha

  • How to stop a process chain tempararly

    Hi
    we have a process chain BI (7.0) which extracts data from R/3
    scheduled everyday at 6AM. However, our basis team is
    shutting down the R/3 server around this time for maintenance.
    I want stop the process cain for this day and start regular
    schedule the next day. Can some body please tell me the
    steps involved in this process. we are using BI7
    Thanks

    hi srigant...
         schedule your start process to run periodically (every day, hour, week...) at a particular time. If this schedule shall not be possible with the standard SAP scheduling, then schedule your start process to be fired "after event". Create an event in SM62. Then write an ABAP report raising this event with function module BP_ENVENT_RAISE. You can as well test this by raising your event manually in SM64.
    so you need to write ABAP program for triggering an event based on the time and check condition...
    hope it helps..
    regards
    ram'n

Maybe you are looking for