Repairing/Repeating Terminated Processes - Process Chains

Hi,
Can any one please explain me with a simple example about repeat and repair in case of process chain.
I’ve referred http://help.sap.com/saphelp_nw04s/helpdata/en/f3/0d4a975f450443be900e89a47ad48e/content.htm but yet I am not very clear about the two.
Which option do we use under what circumstances?
Thank you,
sam

Hi Sam,
Normally with Repeat option next processes automatically trigger. But after manual update u should do them manually.
Check this Function module.
Look into this FM - RSPC_PROCESS_FINISH and execute with G(complete) this will start the next process automatically without doing anything manually.
or
Go to the plan view of that chain, in trasaction field enter '=copy', it asks for the name and description, then u remove the processes which r already ran, connect a start process to which r yet to run ( means to the first process in that). select the immediate option in maintain variant for start process then trigger it.
Hope the following links will give u a clear idea about process chains and clear ur doubts.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-03/using%20process%20chains%20in%20sap%20business%20information%20warehouse
Business Intelligence Old Forum (Read Only Archive)
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Siggi's weblogs for data load error and how to restart process chain
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
Hope this helps.
Regrads,
Ravikanth

Similar Messages

  • Repairing/Repeating Terminated Processes

    hello
    when do you go for repairing or repeating a load..
    pls do furnish with some example.
    points for sure
    thanks
    GVS

    Hi Venkat subramaniyam,
    When you are using Delta type of update method and also when it fails ,We use the Repeat Delta option to make sure
    it get only Delta records
    When you are using Full update and when it got failed,you use
    Repair Full Request .
    We can change full update request into Repair full request by
    runing rssm_SET_REPAIR_FULLREQUEST
    we use this because there may be scenario where we cannot use delta and Full update in same ODS
    Please go through the links
    [Full repair request|I have a little confusion regarding Full Repair request scenario.;
    [Difference between Reconstruction and Repet|Difference between reconstruction and repeat delta;
    [Repeat Delta|repeat delta ...;
    Hope i have answered your question

  • Process Chain fails - ABAP dump

    Hi Everyone,
    Some of the process chains in our system keep failing at random intervals and end with an ABAP dump (MESSAGE_TYPE_X). The short text error message in the log says: 'The current application triggered a termination with a short dump'.
    Long Text:
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    Code Extract:
      14   select single * from rsmdatastate  bypassing buffer
      15                   into l_s_datastate
      16                   where infocube = i_infocube.
      17   if sy-subrc ne 0.
      18     message x051(rsar) with 'infocube_not_found' i_infoc
      19     raise infocube_not_found.
      20   endif.
      21
      22 * nur weitere Tests, falls Request kleiner als qualok
      23   if i_rnsid <= l_s_datastate-qualok.
    >>>>     message x051(rsar) with 'sid_too_low' i_rnsid
      25                             l_s_datastate-qualok.
      26   else.
      27
      28     if   i_rnsid <= l_s_datastate-compr
      29       or i_rnsid <= l_s_datastate-rollup_rsvd_dual
      30       or i_rnsid <= l_s_datastate-dmall.
      31
      32       message x051(rsar) with i_rnsid
      33                               l_s_datastate-compr
      34                               l_s_datastate-rollup_rsvd_
      35                               l_s_datastate-dmall.
      36       raise write_not_allowed.
      37
      38     elseif l_s_datastate-rollup_rsvd_dual = 0.
      39 *   es sind noch keine Aggregate vorhanden
      40 *   check, ob ein Aggregat gefüllt wird
    We have been getting this error in different PCs with no specific pattern. When I re-generate the program and repeat the process chain, it executes successfully.
    What could be the cause of this repeated failure?
    Thanks,
    Ram

    To recognize this error early on, the attached corrections check whether the references are correct. If they are not, the following termination occurs:
    "System error in program SAPLRRSI and form INITIALIZE-1- (see long text)".
    The content version of the characteristic 0REQUEST is usually correct. You can see this in transaction RSD5 (dropdown content). If this is the case, you can transfer the InfoObject from the content again:
    Transaction RSOR -> BI Content -> Object Types -> under InfoObjects select 0REQUEST and transfer it to the right (note the following settings: "Only Necessary Objects"; collection mode: "Collect Automatically").

  • Process chain problems

    Hi guys
    yesterday I got problem with process chain(PC),....its master data loading into characteristic attribute with everyday deltas.....
    I have three infopackages
    1.first IP for deltas(used in process chain)
    2.second IP for full repair
    3.third IP for delta initialisation.
    Process chain(having IP for deltas) stopped yesterday and the errors are:
    Repeat delta mode not supported by extraction API
    pROBLEM in source system
    I got advice yesterday...to solve this problem like this
    1.check if your failed delta request has any records...if it donot have any...go to IP for initialisation and do Delta initialisation without datatransfer.....if failed delta request has any data....then do delta initialisation with data transfer.
    2.Select repeat in process chain.
    Today...I checked delta queue...there are no records  for my request...then went into IP for Initialisation and choose option 'Delta Initialisation without data transfer'....and tried to schedule it.....it shows message:
    Delta Initialisation already done...cannot be done again....
    how can I solve this problem.....
    thanx for your inputs
    NR

    Hi.....
    Today...I checked delta queue...there are no records for my request...then went into IP for Initialisation and choose option 'Delta Initialisation without data transfer'....and tried to schedule it.....it shows message:
    Delta Initialisation already done...cannot be done again....
    Your delta queue is showing 0 records......may be there is no new records.......whatever delta s was there you have already send it..............
    Why you want to do re-init again..........I did'nt get you......
    Anyways............before doing re-init...always you have to delete the init flag.........because init flag is like a pointer.........you are doing re-init means you are again setting the init flag...........when already init flag is set...........how can you set it again without deleting the previous one.............due to this you are getting this error message..........
    Regards,
    Debjani.......

  • Error while transfer from DP to SNP in process chain

    Hello All,
    I am gettting a error message as below
    6875  characteristics combinations processed
    3606  characteristics combinations successfully saved
    0  characteristics combination not saved
    3269  characteristics combination contained errors
    and strangely when I repeat the process chain its actually comleted are the times series not attached?.
    Thanks in advance,
    Kumar

    Hi Kumar,
    Could you please elaborate on the error for the 3269 by looking
    at the job log.  Also check livecache connectivity was proper
    at the initial run
    Regards
    R. Senthil Mareeswaran.

  • Loadihng from ODS to Cube failed in process chain

    Hi All,
    I have a process chain for SD loads scheduled every night. It gave me an error while loading data from Billing ODS to Billing Cube(via Further Processing, and the data is not available in PSA).
    The error it gave is as follows:
    Error while updating data from DataStore object ZSD_O03
    Error 7 when sending an IDoc
    Time limit exceeded. 3
    Time limit exceeded.     
    Errors in source system
    Now the request is loaded in Cube(YELLOW status) with transfered records 87125 and added 62245. But there is no way by which we can check if the complete data has come to the cube.
    i did not delete the previous request from the cube  and tried to repeat the process chain from the same point...it then gave me the following error:
    -Last delta incorrect. A repeat must be requested. This is not possible.
    Please tell me now what should I do...i don't have to miss the delta records in the cube.
    1)Should I delete the prevous loaded request in cube and repeat the process chain from the same point...will it get all the delta records in that case???
    2)Should I delete the request from cube and manually repeat the last delta for the cube. and then manually load the remaining process chain.
    please help me out soon..
    Thanks and Regards,

    Hello Niyati
    you can use 2nd option
    Your error message is comming because of lack of BGD process and memory....just set the status of request in cube to red, delete it, and run a repeat load from infopackage.....
    If no. of records are high than just go for the option of "load data in PSA and than subsequently in data target"
    in infopackage
    Thanks
    Tripple k

  • Process Chain background jobs

    Hi All,
    we got a typical issue in Process Chain,  every day process chain triggers in the midnight, and yesterday morning It got failed while activating DSO for HR data,  and we observed that the jobs are running in the background for longer time (there are 3 jobs related to HR still running since around 24 hours). In order to run the following processes which are no way related to HR, we made turning red to Finish (to skip this process - using Function module RSPC_PROCESS_FINISH) to make sure other reports work perfectly. yesterday PC ran successful expect HR data.
    Today morning we observed that the jobs are still running and also PC gets stopped in deleting contents of HR (after this we are loading HR DSO) . the process neither failed nor success. we checked in Sm37 and observed that job related to Delete content of HR data is also still running and in active status.
    it is not allowing us to skip the process as we did for the HR DSO. So we thought to kill the job and Killed the JOB of delete content of HR data, and tried refreshing in Process Chain. But the variant is empty now and process stopped at before the Delete contents (which are another deleting cubes) now the process is at delete contents of CUbe (which is before step to the delete HR DSO), if we right click and check the options it is showing display variant and display messages.
    We repeated the Process chain again it stopped at delete content HR DSO(back ground job running again and running longer time), the process is at delete contents DSO HR, (showing the box half filled).
    how to skip this delete contents of HR data DSO, because we don't want to stop all the following processes(which are not related to HR) and how to make my PC ran successful (expect HR) to make my report working perfectly expect HR reports
    Thanks in advance,
    Teena
    Edited by: Teenab on Feb 10, 2011 10:42 AM
    Edited by: Teenab on Feb 10, 2011 10:43 AM
    Edited by: Teenab on Feb 10, 2011 10:45 AM
    Edited by: Teenab on Feb 10, 2011 10:50 AM

    Thank you for the reply,
    Yes we can create PC for HR seperately.
    Presently the thing is yesterday we din't loaded the HR data (as we skipped the process by forcefully finished the process using FM -RSPC_PROCESS_FINISH) , As the jobs are still running morethan 26 hours. Now DSO HR doesn't have any data, but the process has been stopped at the deleting the content of HR data (our assumption since the HR loading jobs running longertime causing this, job delete content HR is also active and running (while loading it is trying to delete it, so it might be locked)
    But we need to skip the process of HR delete content now, inorder to run other process successful, (we can create other HR PC  later) but can you suggest the solution for now.
    Thank you,
    Teena
    Edited by: Teenab on Feb 10, 2011 11:03 AM

  • Process chain - How to  correct?

    Hi friends,
    i have a process chain which failed at process LOAD INFOPACKAGE . subsequent to this process is  UPDATE FROM PSA. .
    we loaded the infopackage manually  and tried to repeat the Update from PSA , but it got failed.
      I have done any mistake in repeating the process update from PSA.??
    plz tell me what should i do in this case.
    regards,
    Pavan

    Dear Pavan,
    When you repeated the process chain from update PSA step, it will take the failed instance of 'LOAD INFOPACKAGE' step. So it will fail only. Now what you can do is you can manually make this update PSA step green.
    Follow these steps:
    > GO to failed step, right click say maintain variant.
    > go to tab chain
    > open se11, table-rspcprocesslog, display list
    > copy variant, instance, date from chain to respective fields of this table
    > execute
    > open se38, Program-rspc_process_finish
    > copy everything (variant, log-id, instance, date) which has copied earlier and write status as G.
    > execute
    > Refresh the chain
    After doing this your update PSA will become green and process chain will continue further.
    Hope this helps.
    Thanks,
    Nabha

  • PSA Deletion Process failed in Process Chain

    Hi..I have a bizzarre issue...
    I have created one process step in Process chain for deletion of PSA data of a particulur data source(o days).Every setting is fine.
    Except for it fails and gives message:
    Data inconsistency; Partition /BIC/B0001723000 not deleted
    Then I do the repeat in Process Chain and it completes successfully.
    Can anybody throw some light??

    Hi,
    Go to se14 and adjust it - /BIC/B0001723000
    thats it,
    Best regards,
    dushyant.

  • Process Chain Failed for Master Data

    Hi All,
    Process Chain has failed for vendor attributes, when i checked the error no message has shown, and when i check the vendor attribute , there request in RED which is loaded on sunday(it got failed on sunday) again failed today.
    I repeated the Process Chain again failed, and i deleted the request which in generated yesterday (sunday) and deleted request from PSA (delta) also (which is RED) trying to Load again It is saying that Last delta update was Incorrect There no new update is possible
    It seems there is no load in (sunday) that is why it is giving that message.
    Could you please let me know how this problem will be solved.
    Thank you,
    Teena

    Hi,
    You need to mark the failed request as "red". Then go to the infopackage and rerun. If it still fails, check the error message in the monitor. In the monitor, click on the failed load, go to the status tab and then click on the error message button. It will tell you the exact error.
    Most probably, the error is datasource does not support mode R. (Repeat of last delta). In which case, you need to reinitialiize the datasource. Most master data datasources do not support repeat of last deltas. Hence if the delta's fail, then you need to do a reinitialization.
    Hope this helps.
    Regards.

  • Process chain failed at COLLAPSE PROCESS TYPE ?

    HI all ,
    we have one process chain , in that  we have used oe process type collapse  for the cube .
    it got failed , but in the manage screen , under request status , it is showing tick mark i.e collapse successfully .
    give me some solution..
    regards ,
    Srinivas .

    Hi Venkatesh,
    thank you,  i have resolved this issue.
    i have checked in SM12 and there is no lock on the particular info cube then i repeated the process.
    the process chain failed at the stage of rolling up infocubes and the next triggred process was successfull even though i repeated the process chain.
    my concern is how the next process triggrred and it was successful when rollup process failed.
    can you please explain me
    thanks

  • Process chain load failure

    Hi experts,
    A delta process chain which schedules the data to a dso
    through infopackge daily failed.
    Load was unsuccesfull.
    The error message is:
    Transfer (IDocs and TRFC): Errors occurred
    Data Package 000001 : sent, not arrived
    Info IDoc 3 : sent, not arrived ; Data passed to port OK
    Info IDoc 4 : sent, not arrived ; Data passed to port OK
    How to rectify this error.
    And also how to repeat a process chain for which the delta load was failed. This is first time i am handling a process chain.
    Regards,
    Bhadri M.

    Hi......
    Is it failing everyday.......no one has taken any action........I mean no one has rectify the failed previous failed loads......
    Or you mean to say that...........first time it is failing.........then after repeating...it is getting successfull.........I think all the previous failed loads are already rectified........check the log..........
    Actually this error means TRFC are stucked.........check in SM58...........may be everyday it is due to the same issue since.....at this particular point of time.........no of jobs is huge.......due to which system performance is getting effected......and TRFC is getting stucked.............
    If all the previous loads are already rectified.............then for today's load..........delete the request from the target after making the QM status red...........then repeat the load from IP scheduler............
    But as per my knowledge..........previous loads are rectified.........otherwise next delta load will not star.........it will give a pop up Last delta was incorrect...........
    Hope this helps.........
    Regards,
    Debjani........

  • Process Chain-Repair & Repeat

    Dear Experts,
    Could plz elaborate difference between Process Chain-Repair & Repeat. After the PC error(red status), when we go for Repair & when we go for Repeat.
    Thanks in advance.
    Regards,
    RR

    Hi Raghu ,
    Depending on the process type, there are two possibilities:
    ·        You can repair a process. In this case the terminated instance is executed again.
    This enables you to restart processes that cannot be repeated with a new instance because the data to be edited is attached to the instance, as for example with a data transfer process. A data transfer process, for example, cannot be repeated with a new request number because the data itself is attached to the request.
    ·        You can repeat a process. In this case a new instance is created.
    Hope this helps you..pls go through this link : http://help.sap.com/saphelp_nw04s/helpdata/en/f3/0d4a975f450443be900e89a47ad48e/frameset.htm
    Thanks Regards
    Santosh Deepak

  • Process Types in Process Chains - Loading - Repeatable/repairable

    Hi,
    I know SAP recommends that we do not change the properties of the Process Types for Process Chains. I want to know if any one has ever changed the property of "LOADING" process type to "repeatable" or "repairable". We are keen to change this attribute of "LOADING" process to repeatable. Any experiences, good or bad, would be highly useful to us to take a decision and would be highly appreciated.
    regards
    Uday

    Hi Simon,
    So far, I have not come across any documents that explain the difference between the two options. But, I believe the 'repairable" would start from where it has stopped in the program calles, while "repeatable" will restart the current job (not the whole process chain) from the start. Please remember to post it here, if you ever come across any documentation on these options.
    Uday

  • Process Chain error after Enpk1(7.01) upgrade - "Termination discovered"

    Hello We have upgraded our BW from 7.0 to  Enhpk1 (7.01) with latest stack.
    After our upgrade I'm seeing our Process chain when a step errors out and there is a next step to continue with always link inspite of the error in prev step, but  the Process chain does not continue and hangs and when checking the log it gives a prompt of "Termination discovered"
    Gives a prompt something like this
    "The analysis of chain ZP_MD_OTHER_CUST showed that process
    ODSACTIVAT ZP_MD_OTHER_CUST_ACTV was terminated However the
    occur) or a metachain Run 4KFMOYW9CGL10CGCQV2ZL691R could
    not be ended due to the termination. It may be the case that
    a metachain was not informed about the error Continue run
    for chain ZP_MD_OTHER_CUST and any corresponding metachain?"
    with yes or No prompt
    So the chain hangs and does continue only after we enter Yes to the prompt.
    We are in Q testing the upgrade this can be big issue when we dont our chain to hang for something that we want to continue always.
    Opened a msg with SAP, they got back say its because of note 1398868 in the support pack, asked us to implement the manual update on RSADMIN and apply another note 1473491 - Chain not continued with termination and "ALWAYS" link.
    But this has not fixed the issue, Have notified back to them and waiting.
    If any of you have encountered this and resolved . pl let me know.
    Thanks
    Mayil

    Since you just upgraded the source SAP system, it's likely that the delta queue doesn't exist for the data and has to be re-initialized. I'd suggest doing an Init w/o Data Transfer and do a Full Repair extraction to catch up on any missed data. From then on, you shouldn't have an issue with your Delta mode extraction from the source system.

Maybe you are looking for