Interrupt Process Chain

Hi,
I want to use the interrupt process in a process chain.
I have a number of process chains that the users can trigger themselves after inputting data and running planning sequences in BI-IP.  Due to system performance, I need to run the load jobs on the system only at night, when no users are running reports.
The problem I have is that there is no set time period for these inputs, the data depending on the KPI could be entered monthly, quarterly or yearly and on any day during the month.
I want to interrupt the process so that if it is triggered that day, it waits until 23:30 before it executes.
Can this be done using the interrupt process, I have tested it for a set day, so I can set it for today at 23:30 and the process will wait until then, but how to make the date dynamic?
Thanks
DJL

hi
check these links can help you.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70e59bef-3fe5-2b10-0bb5-c5c479b004f0?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30cb3053-98a0-2e10-aca3-dde5b649879a?QuickLink=index&overridelayout=true
process type in BI
Interrupt Process in Process chain.. pls help

Similar Messages

  • Interrupt process chain 2004s

    Hi,
    We are using three process chains which trigger events at the end of them those events triggered by them get collected in event collector in BI 3.5 (RSA1->Tools->Eventcollector).After collecting all the events event collector triggers the process chain.In 2004s this feature is not there.They have added the concept of interupt process.I don't know how to use it.Please help me
    Thanks in advance!

    Hi ,
    ebent collcetor is still in BI7.0 the feature is not there but you can check it thoruhg RSA1 OLD transactiona and program se38 >>> RSABW_NEW_START ..
    This Process type helps for interrupting the processing of a process chain up to the point at which a condition is filled.
    if a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
    The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
    interrupt is kind of a waiting time thing like we add in an infopackage or in  a process chain ..it can also be event based or time based ..
    Go to the display varaint of it .. you will find wether its event based or time based ..if the event is the check that event in se16 >> RSPCchain >>> put the event in process varaint .. you wil find from were the event is coming .. it will give you the porgram name also and the corressponding process chain too ..
    regards,
    shikha

  • Cleaning up obsolete interrupts in process chain

    Hi Everyone,
    We have just recently started using process chains to manage our forecasting solution. We use Interrupt Processes to wait for triggers from external systems. However, recently we've had a problem wherein certain interrupts no longer wait for the triggers and just continue to the next process.
    When we checked the table RSPCINTERRUPTLOG, we found several Interrupt entries do not have an associated LOG-ID and INSTANCE-ID. We suspect that this is what's causing those interrupts to just go through without waiting for the correct triggers.
    Would anyone know any standard program/report or process that can clean up / re-initialize this table?
    Thanks,
    Chasky Bolido

    Hi Im a coworker of the original poster,
    Our process chains are always scheduled and active daily but decision logic will end the chain for weekends. The interrupts are waiting for an external event and these are sent daily from another BI system. But it seems due to the reason that the chains are partially active in the weekends (ending with the decision logic before the interrupt process) and the external triggers are received daily, the events register and the next run of the interrupt process will not wait for the new event.
    Are there ways to clean up the registered events?
    Thanks,
    Ram G.

  • Frequest process chain issue - Database selection was interrupted

    hi experts,
    we are running master data meta chains daily, and we have PP,SD,MM,LO,FI,PS masterdata meta chains running daily, and everyday 2-3 process chains are failing, it is extracting only 50000 records and the requests becomes RED.
    if i check the long text of the error message, it is giving the below error message.
    Database selection was interrupted (see long text)
    Message no. RSBK072
    Diagnosis
    You are extracting data from a DataSource or an InfoProvider. The selection is made with an open database cursor. This cursor has been invalidated by one of the following ABAP statements:
    COMMIT WORK
    ROLLBACK WORK
    CALL TRANSACTION
    SUBMIT
    The ABAP statement responsible for termination probably ran in a transformation routine programmed by you.
    System Response
    Request processing has ended with errors.
    Procedure
    Change the code for the transformation in which one of the specified ABAP statements is executed. If you are using statement COMMIT WORK, replace it with:
    CALL FUNCTION 'DB_COMMIT'.
    again if i delete the request from the target and repeat it is working fine but taking lot of time. but there are no routines in the transformations.
    please provide us the solution to rectify the issues as it is causing lot of reporting issues.
    regards
    venuscm

    hi experts,
    here is the source 0MAT_PLANT_TEXT and the target is 0MAT_PLANT.
    info  package load is very fast, but DTP it is taking lot of time if i execute the DTP Manually.
    The data packets are processed very fast, but after that at the bottom
    Set technical status to green and
    set overall status to green in yellow very long time, due to this DTP Load for above master data is taking long time.
    how to resolve this?
    any solutionz pl.
    Regards
    venuscm
    Edited by: venu WAD on Oct 24, 2011 6:37 AM

  • Process Chain Interrupt Process

    Hi All,
    I have an interrupt process in one of my process chain. It will wait till one particular event is triggered. It was working fine until one day I manuallly triggered that event from SM64 for some other testing. I dont know how many times that event was triggered.
    Now, whenever the actual process chain is running, the job is not waiting at the interrupt process. It immediately passes control to the next process. How can we see the events which were triggered and which one is causing the interrupt to stop waiting?
    Thanks in advance,
    Regards,
    Bijesh

    It will not stop at the Interrupt process If the respective Events are already activated then PC will continue further immediately
    You will have to check all the Events , from which PC they are triggering on what time ... etc accordingly you can analyze
    You can check the process chain which is triggering this Event or check RSEVENTCHAIN and TBTCO both tables and using job name you can find in SM37 .. you will have to explore little bit to identify

  • INTERRUPT process types authorization in process chain

    Hi all ,
    I include INTERRUPT step in one of my process chains but I'm not able to change it on live system because of unsufficient authorization .  We have sufficient authorization just for START variant on process chains on production system however we also need to have schedule authorization for INTERRUPT process since I need to schedule it several times in live system. Does anyone know about the process to gather required authorization
    Thanks in advance ...

    .

  • Process Chain - Follow on dependencies to DSO Activation

    Hi, I have a Data Load Process where the start routine is dependent on DSO data that was just previously activated.  For some reason it looks like the the time before the load and the time after the DSO activation are close by just seconds. 
    The Data Load Routine will drop records if the activated DSO data is not available and this seems like what I am witnessing.  I thought there was a way to configure the chain or job to wait until the previous is completely done.  or did that go away with 7.0...
    Is there a way to make sure the loading process doesn't start until the previous DSO activation is completed and the data is available?
    Thanks!

    Hi,
    Interuppt concept :
    If a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
    The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
    The interrupt process schedules an additional background job that starts based on the relevant condition. Therefore the interrupt process is not really active during the interrupt phase; it does not use any resources during this time.
    If the interrupt processes are filled before the start process condition, the chain starts as soon as the start condition is filled; the interrupt process no longer interupts the chain because its condition has already been filled. If the interrupt process condition is is filled again before the start condition of the chain is filled, this does not influence the chain. It is not stopped by the interrupt process..
    so basically your interrupt will wait for an event like ex:..YABAP_YGTRFCEVENTRAISE_0035 ... so you can raise that event eother by some job or some program..bUt for you i think adding the waiting timw will be better option ..
    hope i cleared  you ..
    Regards,
    Shikha

  • ABAP Program using Selection Screen in Process Chain

    Hi,
    I have included an ABAP Program in the Process Chain.
    The ABAP Program takes a selection screen value from user before execution.
    I have created a variant for both the ABAP Process (YPV_ABC) and a variant for the Selection Screen (YPV_XYZ).
    The ABAP Program executes perfectly well in SE 38.
    I get the following message when I execute the Process Chain.
    "Status Change of Process ABAP YPV_ABC.
    Save Status and Trigger Events if Appropriate "
    When I click Yes, the ABAP Process becomes red.
    These are error messages in the log
    516 -  Job started     
    550 -  Step 001 started (program RSPROCESS, variant &0000000012961, user ID ALEREMOTE)
    25 -    Could not ascertain code page     
    546 -  Job cancelled after system exception ERROR_MESSAGE     
    My questions are:
    1) Is it possible to use an  ABAP Program which has a user input screen in Process Chain?
    2) Could you please help  with the above error?

    1) Is it possible to use an ABAP Program which has a user input screen in Process Chain?
    ABAP programs, with variants established for selection screens, are possible. We use them quite extensively for setting triggers to allow Process Chain to continue after an Interrupt Process has been hit.
    2) Could you please help with the above error?
    I'm not quite sure what could be causing this. When you tested this program in SE38, did you test it with the same variant for the selection screen and did you execute it in background?

  • Step by Step method to create a process chain in SAP BI

    HI There,
    I'm new to SAP BI, can anyone pleas explain me why we need to use Process Chains in a simpler way?
    Also it would be great if someone can give me step by step description for creating process chain. I've seen couple of PDF files but they confusing me more then clearing my doubts. Appreciate your time and thanks in advance.
    Vandana
    Please search the forum before posting a thread
    Edited by: Pravender on May 4, 2011 3:57 PM

    Hi Vandana,
    1.Go to RSPC tcode ->(F5) create ->It will ask for process chain name ->then it will ask for start variant
    2.If you have no start variant pre created then create new one (at right side there will be a paper symbol for that ).Every process chain has one and only one start variant that is to set scheduling option etc .When you will create a new one you will go to a screen where you have scheduling option .
    3.a) Direct scheduling ->to start execution immediately 
       b) start using meta chain or API ->chains which run at specific time (day ,month etc or after some specific event ). save your settings and go back .click check symbol for final creation of start variant.
    4.Now at left screen you  have chain symbol (process types) .when you will click on that you will have all the process lists .
    5.You can select process as per your requirement and connect different processes together.Each process is a different event (ex : load DTP ,Infopackage ,ABAP program ,AND ,Interrupt ).You cna do detailed study for that .
    6.After adding all processes activate (ctrl+F3) and execute .
    7.After that you can check logs (shift+F1) .you can see todays log ,yesterday and today etc .For details of every process execution right click on process and see display variant .
    Hope this will be helpful for basic startup.you can further read thoroughly on each process .
    Regards,
    Jaya

  • Process Chain Ended with Errors - cause unknown

    I have had several instances of process chains stopping for no apparent reason.  The stops occur between 2 master data infopackage loads.  The last step is green and the next is grey.  The PSA table has been updated successfully for the last step.  All IDocs are in green status in both systems.  The monitor for the last successful step does say "Ended with Errors" although no errors are evident.  The process chain starts back up via Repeat at the next (grey) step and continues successfully.  There were no system problems or connection interruptions that occurred during the time the process chains failed.  There were no changes in the remote user profile.
    This exact problem has occurred a half dozen times since our application of ECC Support Packs several months ago and had not occurred before.  The infopackages are different each time. Two different process chains have had this problem.  I have re-activated and re-scheduled the process chains without solving the problem.
    Thanks for any ideas on why this may be occurring or what I can do to prevent it.
    Patty Moffatt

    Hi Des,
    Here's my BW release info:
    SAP_ABA        640       0019 SAPKA64019     Cross-Application
    SAP_BASIS      640       0019 SAPKB64019     SAP Basis          
    PI_BASIS       2005_1_6400009 SAPKIPYJ69     Basis Plug-In
    ST-PI          2005_1_6400008 SAPKITLQH8     SAP Solution Tools Plug-
    SAP_BW         350       0019 SAPKW35019   SAP_BW                      
    ECC SPs 13-21 were applied before the BW problem started:
    SAP_BASIS      640       0021 SAPKB64021    
    SAP_ABA        640       0021 SAPKA64021    
    PI_BASIS       2005_1_6400012 SAPKIPYJ6C   
    ST-PI          2005_1_6400008 SAPKITLQH8    
    SAP_BW         350       0021 SAPKW35021   
    PI             2004_1_5000016 SAPKIPZI6G    
    The process chain step and the monitor load both are green.  The Details tab shows all the processing is green, but the Process Chain itself is red with "Errors Occurred.  There have been no runtime dumps.
    Patty

  • Interrupt process and Debug loop

    Hi,
    What is the difference between Interrupt process and Debug Loop in the process chain if both are used to delay the a process
    Thanks
    krish

    hi,
    Interrupt is a process type which is used in the process chains to trigger the chain after completion of specific steps in another process chains or to pass the process chain up to specified certain time is reached based on the requirement.
    Debug loop can be used to debug a process chain,you will have to specify here the gap between one event been triggered and the next subsequent process also you have to Enter a wait time
    regards
    laksh

  • Process chain - ODS Activation error

    Hello All,
    I have a process chain which has the following data load sequences:
    Load data to ODS
    Activate ODS
    Load data to ODS2
    Activate data ODS2
    Load data to ODS3
    Activate ODS3.
    Used the Program to RSPC_SYNCHRONOUS_RUN to schedule the process chain in Background.
    When the process chain is executed in background it loads the data to ODS1 and Activation process is not happening. It registers short dump like shown below at the end. But when i execute the same process chain in RSPC, Schedule option with Start variant set to immediate, it is activating the ODS Data and completes the process chain Succesfully.
    Help me to solve this problem.
    ABAP Short dump information:
    Invalid interruption of a database selection.
    t happened?
    Error in ABAP application program.
    The current ABAP program "GP4BRKGANFKJY5K2A3ACVGAPTN4" had to be terminated
      because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    Unable to perform database selection fully.
    record.
    t can you do?
    If the error occurs in debugging mode, you should first run the process
    without debugging activated.
    If the error persists outside debugging, you must check the application
    program more closely.
    No error requiring recovery has occurred.
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletiondate.
    is especially useful if you want to keep a particular message
    Error analysis
        An exception occurred. This exception is dealt with in more detail below
        . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
         neither
        caught nor passed along using a RAISING clause, in the procedure "ACTIVATE_ODS"
         "(FORM)"
        Since the caller of the procedure could not have expected this exception
         to occur, the running program was terminated.
        The reason for the exception is:
        One of the database selections included a database commit.
        The selection was then supposed to continue. Before a
        database commit, however, all outstanding database selections must be
        concluded.
        Possible causes in the application program:
        Within a loop (SELECT/LOOP/EXEC SQL), one of the following
        statements is used:
        - MESSAGE (apart from MESSAGE S...)
        - COMMIT WORK
        - ROLLBACK WORK
        - CALL SCREEN
        - CALL DIALOG
        - CALL TRANSACTION
        - SUBMIT
        - BREAK-POINT
        - WAIT
        In debugging mode, a program sometimes triggers
        a "COMMIT WORK" during the database selection. As a result
        this termination may also occur in debugging mode with a correct
        program.
    A "COMMIT WORK" during debugging may be due to the following reasons:
    1. A program or screen was regenerated
        and updated in the database.
    2. Each user needs a private process in debugging mode, but
        the number of available processes is restricted. If this
        limit is exceeded, each debugging step then requires a
        "COMMIT WORK".
    The error occurred in a statement that accesses the table "/BIC/AZXOQMATR40 ".
    Thanks in Advance.
    Points will be assigned.
    Regards
    M.A

    Hi,
    If it is a daily process chain u define it on a periodic basis in the variant and it'll run successfully.
    I guess the DUMP may be due to less processes at the time u run...It is gving the same in the dump also..
    So when u run the chain immediate in the BKGD the ODS will be automatically getting the required processes dailog and bkgd to run according to ur settings and it was successful..
    U try to execute the chain using FM: RSPC_API_CHAIN_START and give the tecnical name of the chain under I_CHAIN filed and conitinue...It'll scedule the chain in the BKGD only and if it is a periodic one the chain will be automatically ready for the next run also...
    rgds,

  • Process Chain - triggering sub chains at set time interval

    Hi all,
    Scenario:
    I want to setup multiple process chains during the day (hourly intervals).  I would like to have a main chain which would then trigger subsequent chains.  the problem is that when i tried to setup the sub-chains to run at say, 10am. 11am etc, they don't fire off at those specified times (because they are part of the meta chain?).  I currently have the individual chains running independently (i.e. first chain at 10am, 2nd chain at 11am...) - but i need to be able to stop the 2nd chain from running if there is a problem on the 1st chain (which is why i want to run them as part of a Meta chain).
    Hope this makes sense - and any help/assistance is much appreciated!  Thanks
    M.

    Do you know how long 1st PC will run ? will it finish before 11 am ?
    If so,  try following proess
    Add Abap Program process(under General Services) to the end of the 1st PC  and use program BTC_EVENT_RAISE and Enter Program variant = event  and activate the PC
    Now go to 2nd PC and schedule at 11 am periodically
    Add another step Interrupt Process (u can find under General Services ) just after start process and enter event and schedule the pc
    When 1st Pc completes sucessfully it will activate the event to trigger 2nd PC , though the event is activated the 2nd pc will start at 11am
    Hope it's clear!

  • How to Stop the process chain if it in the middle of the process?

    Hi,
    Is there anyway that i can stop the process chain if it is in the middle of the process already?
    Raj

    "Hi,
    First and foremost let me advice you to be very careful while doing this.
    You can start from SM37, find the process WID/PID then go to SM50 or SM51 and kill it. Once its done come back to RSMO and check the request, it should be red but again manually force to red and save by clicking on the total status button in the status tab. This shuld ensure that the process is killed properly.
    The next step will be to go to targets that you were loading and remove the red requests from those targets.
    Note: For source system loads you may have to check if the request is running in the source system and kill if needed and pull it again.
    But for BW datamart delta loads u may have reset the datamarts in case u are going to pull the delta again.
    Different Ways to stop process chain
    1)SM37 -->Kill Job
    2)SM50/sm66- ->Kill process
    3)RSPC>Job Log>Make the process RED forecefully.
    4)RSPC>Process chain> main Menu"Remove from Scheduling" OR
    5)se37-->RSPC_API_CHAIN_INTERRUPT
    give RFC BW system name(technical) and process chain name(technical)
    Steps 1 -3 stops the chain running in process
    Steps 4-5 stops the chain AFTER the current job which is running is completed as sucessful or Failure by nature.
    Rationale - 4-5
    This function will only remove the jobs from schedule, which did not yet run. It will not kill running jobs, as this may leave the system in an inconsistent state, moreover killing processes is possible for synchronous processes only anyhow. This means, that there will be no errors with interrupted chains, which on the other
    hand means an interrupted chain is not restartable. So for a running chain this function is intended to be an emergency break only. You can use it, however, to remove a scheduled chain from schedule, such that it does not start except by your product.
    Re: Kill a Job
    Re: Killing a process chain.
    How to stop a process in a process chain?
    Regards,
    JituK

  • Adding BAPI jobs in Process Chain

    Hi All,
    I want to add BAPIs in process chain in BW 3.5.Can anybody help me in this???????

    Hi,
    There will be no impact on the work processes but the main concern here is for all jobs that run in dialog/fore ground there will be some specific time limit defined...so if a job/process crosses that limit it'll go to ABAP dump....
    At a max there'll be no timelimit for the bkgd processes so a job can run for a long time without any interruption...
    To know the time limit for foreground processes u can chk wit ur BASIS team or use Tcode- RZ11...
    Now If any of the job in ur process chain takes long time it may go thru dump, so it depends on the step howmuch it is taking....(Eg: Attribute change runs take long time sometimes)
    rgds,

Maybe you are looking for