No error in the Process Chain

HI
  I am Working In production support
   Recently I am Facing a Problem in the Process chains
   Actual Process chain consist of Local Chains(many)
   Some times one Local chain does not trigger even the previous Local chain gets completed Sucessfully.
   It does not rigger automatically.
   I am repeating the Local chain
  Why this error is Occuring..., Can any body please help me out

Hi Priya,
Try this post:
How-to trigger a process chain using ABAP?
Check these links:
Docs in sdn
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
Process Chains
Steps for Creating Process chain!
http://help.sap.com/saphelp_nw04/helpdata/en/67/13843b74f7be0fe10000000a114084/frameset.htm
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
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
Hope the following links will give u a clear idea about process chains and clear ur doubts.
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
****Assign Points If Helpful****
Regards,
Ravikanth

Similar Messages

  • Error in the Process Chain

    Hi,
    Im getting following error in the Monthly Process Chain :
    "A type "Attribute Change Run" process has to follow process "Execute InfoPackage" var.ZPAK_D3VOS4BQNK1QJ98G29CU8EWFE in the chain"
    Please advise...
    Regards,
    Anuja

    Hi,
    You need to add the "Attribute Change Run" process type after the infopackage load in the PC.
    I assume the infopackage loads Master Data.
    Thanks.

  • How to identify what are all the errors appears in process chain,

    Hi all,
    i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
    thanks
    pooja

    Hi Pooja,
    Errors in monitoring:
    SID error
    Reason: If the corresponding master data is missing for the particular transaction data.
             1. Check for the load timing for the respective master data, if it less than an hour  then make the request red and repeat the ip.
             2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
             3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with ‘Single as postfix’.
             4. Goto ‘data selection’ tab and change the range.
    Tip: change the last 4 digits for from to ‘0000’and the last 4 digit for to     ‘9999’.
            5. Repeat the ip.
             6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
    Note: IF PSA is present never make the request red rather delete it.
    Replication error
    Reason: Data source replication Failed.
             1. In order to handle this error you should be known to IP, info source and source system.
             2. Goto RSA1, find the data source in the source sys tab.
             3. Right click on the data source and replicate it.
             4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
             5. Delete the ‘red’ request from the target.
    Update R not supported
    Reason: The corresponding initialization flag for the ip is lost.
             1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
             2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
             3. Goto update tab and select ‘Initialize delta process’ try going for ‘with data transfer’.
             4. Reschedule the IP.
    Duplicate Record Error
    Reason: Duplicate error records for the loaded master data.
             1. Goto info package via header or via RSA1.
             2. Goto ‘processing tab’ and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
             3. Do remember to change the ip settings back to the original once after the second step.
    ODS activation failure
    Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
             1. Goto ‘maintain variant’.
             2. Check for the ‘QM’ status of the requests in the target they should be green.
             3. Then click the ODS activation tab.
             4. In the screen which appears put the requests for which ODS activation failed.
             5. Activate these and keep on refreshing them until status reverts from green,
    Remember to refresh these requests one at a time.
             6. If requests are red then delete them from target.
             7. Reschedule the IP.
    Note: Never Try activating ODS manually if it is Y1.
    Aggregate Rollup error
    Reason: No aggregate found for the respective rollup.
             1. Click on the variant in which the error occurred.
             2. Goto chain tab and copy the variant and instance.
             3. Run the nestle provided program YBW05.
             4. Put in info in there and put the status as g – ‘green’.
             5. Execute and refresh the status.
    Lock issue
    Reason: The same ip is been locked by other user or may be used by other process chain.
             1. We can see the locked entries and in the transaction SM12.
             2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
             3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
             4. In the box appears select update in the background.
             5. And the manually update the failed IP’s by selecting manual update in the context menu.
    Alfa confirming value error, Time conversion error, Chain didn’t start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
    Reasons:
      Alfa confirming error: Data format mismatch.
      Time conversion error: Date, time format mismatch.
      Chain didn’t start: A scheduled chain didn’t triggered at the prescribed timing.
    -For all the above error we have to raise a ticket.
    Idoc or TRFC error
    Reason: An Idoc is been stuck somewhere.
             1. Reload the Master Data manually again from Info-package at RSA1.
             2. Release the Idoc.
             3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
             4. In the Screen if the status is ‘Transaction Recorded’ it means its stuck goto edit and click Execute LUW or press F6.
             5. If status is ‘Transaction executing’ then it means its fine wait.
             6. Or raise ticket.
    Error Due to short Dump
    Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
    Process terminated in the Source system.
               Reason: Sometimes we face that a load has failed due to job Termination at Source System.             
          This happens due to unavailability of the source system or some connectivity problem between source and target systems.
    1.      Make the request red.
    2.      Delete the request from the data target.
    3.      Reschedule the ip.
    4.      If still the job fails raise the ticket.
    And also check in following links:
    Process Chain Errors
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Common Process chain errors
    For Data Load Errors check this blog:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Pls assign points if it helps u,
    Thanks & Regards,
    Madhu

  • How to delete the error stack in process chain?

    Hi all,
    we just want to do the following:
    - we are loading in FULL daily to our datatarget (data is versionized by 0calday)
    - we want to use the error-stack in order to analyze wrong data
    --> but we now encounter the problem that, if data has once been added to the error stack and has not been handled yet, all data from the next daily load will be sorted out as records with this key do already exist in the error-stack. But that's exactly what we want to avoid.
    with other words: how can we delete the records in the error stack by a report by e.g. using this in a process chain?
    Thanks in advance,
    Best regards,
    bivision
    Edited by: bivision2009 on Jul 6, 2010 12:25 PM

    Dbl click that DTP.... From menu... Extras -> Setting for Error Stack
    Here U can see error stack table name /BIC/B0001234000.
    Using SE38, create simple program "Delete from /BIC/B0001234000"
    In the process chain, add process type "ABAP Program" to add above deletion statement.

  • Error while running the process chain

    Hi, I am getting following error while running the process chain.
    "Lock NOT set for: Deleting the data completely from a data target"
    Please suggest.
    amit

    hi,
    This is due to a lock on the objects which is being used by ur load.
    Even if master data used by this would be in a lock by an attribute change run. wait till that attribute change run finishes and then repeat.
    If this target itself is locked by someother process like rollup , compression , this error would appear. In this case also repeat the step after those locking process finish.
    some general locks during loading:
    Sometimes parallel processing in DTP might lead to this, its better set the DTP and infopackage in serial processing. In this case change the settings and then repeat the process.
    There is a specific case in which the Serial DTP gets locked by itself, in this case repeat it untill it succeeds.
    You can identify the above scenario as below. This is applicable only if the DTPs processing mode is serial.
    if u see in SM 37 this load would have three DTP processes running.
    it should have only two.
    In this case cancel the process and repeat it untill u get it right.
    hope this helps u
    regard,
    ranjith
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:44 AM
    Edited by: Ranjith  Kumar Murugesan on Sep 12, 2008 10:46 AM

  • Error while designing the Process Chains

    Hi All,
    I have a issue on Process Chains.
    In my Project there are 2 ODS.
    ODS 1 : Status Header ODS (ZODS)
    ODS 2 : Service Order Header. (0CRM_PROH)
    In CRM, if any Service Order is created, it is available in delta Queue(RSA7) immediately.
    While loading the data to ODS 2(Service Order),it is checking the data from status ODS 1(Status ODS)
    For Example, I am loading the data of service Order 80001 to ODS 2(0CRM_PROH). Before loading to ODS 2, i am checking whether this service Order Number(80001) is available in ODS 1.
    If the service Order 80001 is there in ODS 1, it will update the data to ODS 2.
    If the service order 80001 is not there in ODS 1, it will not Update the data to ODS 2.
    Problem i am facing :
    1. First i am loading the data to ODS 1 (Status ODS). Early Morning 2.30AM and it completes the data load at 2.40AM. And document posting is happening on 2.37AM and ODS 1 doesnt pull the data of document posted.
    2. Once the ODS 1 is completed, by 2.41AM, the data loading will happen for ODS 2 (Service Order Header).It brings all the data including the document posted on 2.37AM.
    3.While loading all the data is available, and while loading to ODS 2, it is checking the status ODS. And it is checking for the document posted on 2.37AM and this document is not there in Status ODS 1 and the data(posted on 2.37AM) will not update in ODS 2.
    Because of this, some records are missing in ODS 2. And while loading, we cant stop the document posting also.
    How can i achieve this using the process Chain.
    Design i have tried in Process Chain :
    1. Start Variant.
    2. Load Infopackage to PSA only for ODS 2.
    3. Load Infopackage to PSA and activate ODS for ODS 1 (Status ODS)
    4. Read PSA (of ODS 2) to Load data to ODS 2.
    5. Activate the ODS.
    I tried, but i got a error message while designing the process Chains.
    No type "Activate DataStore Object Data" process can be in front of process "Read PSA and Update Data Target" variable PSA_SERVICE_ORDER in the chain
    Pls suggest how to recify this according to my design.
    Thanks & Regards,
    Ram.

    Hi,
    You can try this..
      .......................................... Start  ...................................................
    Load data to PSA (ODS 2) ..................................... Load data to PSA (ODS 1)         
    ..................................................................................Load data to ODS 1
    ...................................................................................Activate ODS 1
      ........................................... AND ..........................................................
      ........................................ Load data to ODS 2 .............................................
       .......................................... Activate ODS 2 ...........................................
    Regards,
    Anup.
    Edited by: Anup ShankarBS on Sep 3, 2009 4:56 PM

  • Error while collecting the process chain in a transport request

    Hi Gurus,
    I am getting an error while collecting my process chain in a tranpsort request.I have to transport the request from DEV to QA system.
    When in RSA1--->transport connection i drag & drop the chain from left to right side pane then the Error occurs.
    1.Object 'REQUDELZPAK_48RZW8GZX87CNEH7S897TFQSD' (RSPV) of type 'Process Variants' is not available in version 'A'
    Sap help given
    You wanted to generate an object with the name 'ZPAK_48RZW8GZX87CNEH7S897TFQSD' (in transport request RSPT) of type 'Process Chain Starter' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
    2.Object 'ZPAK_48RZW8GZX87CNEH7S897TFQSD' (RSPT) of type 'Process Chain Starter' is not available in version 'A'
    Sap help given
    You wanted to generate an object with the name 'REQUDEL   ZPAK_48RZW8GZX87CNEH7S897TFQSD' (in transport request RSPV) of type 'Process Variants' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
    From one of the threads:
    (https://forums.sdn.sap.com/click.jspasearchID=10081153&messageID=4623856)
    i though it was the problem of patch level sap note(966131).
    Accordingly i tried collecting process chain in the request where the patch level is high(24).But same error is seen.
    I have activated chain again & then tried collecting the request i the process chain.But did not solve the error.
    I have to collect Process chain in a transport request.Can you help me out to solve the problem?
    Thanks in advance!
    Regards,
    Pallavi

    Hi,
    take a look:
    Data Warehousing
    "Errors occurred during post-handling RS_AFTER_IMPORT for MPRO L "
    Errors occurred during post-handling RS_AFTER_IMPORT for ROUT L
    Try to set the Process Chain Start to Immediate(background jobs) in the schedule, because this will trigger the process chain once tranported and may cause similar errors.
    Regards
    Andreas

  • Error while executing the Process chain

    Hi Friends,
    The process chain that I scheduled is getting failed at the Infopackage loading stage.
    On checking the diplay message, I found the following log:
    Cannot stage requested data for datasource
    Error in source system
    I activated the datasource in source system, then replicated the same and tried to load data.
    But the issue remains the same.
    I checked in RSA7. The status corresponding to this datasource is in yellow status.
    Can I delete this entry and try again?
    Please suggest.
    Thanks in advance.
    Surjit P

    Hi,
    /people/mona.kapur/blog/2008/01/14/process-chain-errors
    Deadlock
    http://help.sap.com/saphelp_nw04s/helpdata/en/2e/44934257a5c86ae10000000a155106/frameset.htm
    Dead Locks
    2. Error in unit conversion
    Units of measure
    3.Error 1 in update
    When Src file is already open or not accessible.
    4.Processing no data
    theres no data selected after extraction
    5.Caller 70 missing
    "• This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
    1) Whenever we are loading the Master Data for the first time, it creates SID’s. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
    2) If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
    3)Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
    4) If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
    5) It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
    6) It is a system error which can be seen under
    the “Status” tab in the Job Over View.
    solution:
    "• If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
    • If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
    • If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SID’s and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
    • If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
    • If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
    • Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
    • Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
    6.Idoc not processed completely.
    Here the request remains yellow (in process) and with the same details (as seen in the details tab of the monitor) for an abnormally long time. Many-a-times, the port for communication is not open and re-starting the load helps. For long running jobs, it may not be advisable to restart the extraction
    Contact the BASIS administrator to push the IDOC.
    look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Majority of the issues will be based on these things only..
    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.
    pls award me some points
    thanks.
    Thanks

  • Error while designing the process Chain.

    Hi All,
    I have created the Process Chain.
    1. Start Variant.
    2. Load data to PSA for ODS 1.
    3. Load data to ODS 2
    4. Activate the ODS 2
    5. Read PSA and load data target to ODS 1.
    6. Activate the ODS 1.
    While checking the process Chain, i am getting the error message as
    "No Type "Activate Datastore Object data" process can be in front of process "Read PSA and data target" Variable PSA_CONFIRM_ITEM in the chain.
    Can u pls help on this issue.
    Thanks,
    Jelina.

    Hi,
    You can try this..
    ..................................................... Start ...................................................
    Load data to PSA for ODS 1 ..................................Load data to ODS 2
    ...................................................................................Activate ODS 2
    .............................................. AND ..........................................................
    ........................ Read PSA and load data To ODS 1 .............................................
    .......................................... Activate ODS 1 ............................................
    Regards,
    Anup.
    Edited by: Anup ShankarBS on Sep 4, 2009 10:47 AM

  • SET CURRENT DEGREE = 1..error when run the process chain..

    Hi Experts,
    when i run the process chain ,  i got the following error..
    SET CURRENT DEGREE = 1..
    what is this error?
    Kindly help ..

    hi,
    As BW reporting queries are often CPU-intensive and geneally executed in parallel.
    Parallel processing is activated dynamically in the SAP BW system for every reporting query CURRENT DEGREE = ANY and itsdefault value is 1.
      you can limit the maximum number of parallel tasks using ZPARM PARAMDEG(maximum number of parallel tasks ) for the no. of parallel processors for its usuage and this should match no. of processors you can get touch with your basis team
    check SAP Note:390016 -DB2/390: BW: Database settings and performance ; in that look at query parallelism it explain about this
    hope it helps
    regards
    laksh

  • What are some of the process chain errors one comes across?

    hi friends
    What are some of the process chain errors one comes across?

    Hello Kiran,
    Here are some of the errors that come across...
    -> Rollup not possible, no filled aggregates available
    -> Error when starting the extraction program
    -> The process step locked by another changerun
    -> Info objet does not contain alpha confirming values
    -> Errors due to non activated objects
    -> Errors due to duplicate records
    -> Errors due to locking
    -> Problems because of connection problem between source and bw systems
    -> Problems due to RFC
    Hope this helps you
    Cheers
    SRS

  • Error in delta run in the process chain

    Hello Experts,
    I have a delta infopackge that runs everyday , since many days the process chain is giving error at the IP.
    The IP is red everyday and the following objects does not start, however when I check in the monitor the ip is completed successfully without any errors.
    I checked the logs which is in greeen in the batch job , please find the details below.
    Job started
    Step 001 started (program RSPROCESS, variant &0000000111903, user ID ALEREMOTE)
    Last delta upload not yet completed. Cancel
    Data saved successfully
    Start InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7
    Last delta upload not yet completed. Cancel
    Last delta upload not yet completed. Cancel
    InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 created request
    Request REQU_4L001XOSR2IQQ14M90QLO1CTA could not be generated with InfoPackage REQU_4L001XOSR2IQQ14M90QLO1CTA without errors
    Last delta upload not yet completed. Cancel
    Error After Starting InfoPackage ZPAK_4EH1CYBST65PTYCQVFAQY6ZI7 in Process Chain ZIM_INT_ORDER
    Entire chain now has status 'A'
    Job finished
    Could you please suggest.

    Hello
    Thanks for your reply
    the problem was with the way it was schudled, the chian was ticket at periodic run , as a result it as running automatically, and causing problem.
    I have removed the periodic n saved it again ...the error stopped appearing !
    The issue is resolved now.
    Thanks for your help.

  • Warning Error message while scheduling the Process Chain

    Dear All,
    I have created the meta Chain, which contains 7 Local Chains. I have tested this chain in BI Development and Quality. It was working fine. I have moved this Meta Chain to production. While i am trying to schedule this chain, i got the warning message.
    Too many parallel processes for chosen server BICI
    Message no. RSPC118
    Diagnosis
    On the server TVSBICI you have chosen, there are only 0 batch processes available. The process chain has been designed in such as way that 3 processes must be processed parallel.
    System Response
    Only 0 processes can be processed parallel. Note also that to be able to start sub-chains, AT LEAST TWO free batch processes must be available. Otherwise a lock situation may arise.
    For more information, see SAP Note 621400.
    Procedure
    Reduce the number of parallel processes in the chain or include sub- chains. This warning applies to all relevant processes.
    Procedure for System Administration
    Increase the number of batch processes available. You should note however that it makes no sense to set up more batch processes than there are CPUs on server BICI.
    Pls help on this issue.
    Thanks,
    Siva.
    Edited by: Siva Kumar on Jun 15, 2009 9:16 AM

    I have Ignored this warning and now process Chain is working fine.
    Thanks,
    Siva.

  • Error while activating Process Chains

    Hi all,
    while activating the Process Chains, i am getting the following error "Job BI_PROCESS_PSAPROCESS could not be scheduled. Termination with returncode 8"
    when i double click on the error msg, i got the following help msg: "
    <i>Message no. RSPC065
    Diagnosis
    Program RSPROCESS is to be scheduled as job BI_PROCESS_PSAPROCESS under user ALEREMOTE.</i>
    Can any one please show some way to solve this problem? please do this favor, i have been suffering with error for a long time.
    Points will be given
    Thanks
    Ganesh

    Hi,
    Just analyze the error message that you get while activating the PC, don't give any server name.If you are trying to run process chain using Flat file, it won't work,
    and you should have source system R/3 or you have own datasources in BW system itself at that toime you can use PC to extract data. If your source system is Flat ile, it won't work. other wise you should place your flat file in application server, using AL11 tcode.
    <b>OSS : 511475</b>
    <b>Symptom</b>
    You cannot schedule or perform any batch jobs with the BW or source system background user.
    The error RSPC 065 occurs in the process chains:"Job could not be scheduled, termination with return code 8"
    <b>Other terms</b>
    RSPC065
    <b>Reason and Prerequisites</b>
    The user type is
    "CPIC" up to 4.6B
    "Communication" as of 4.6C
    This user type may not execute or start any batch jobs, irrespective of the user authorizations.
    <b>Solution</b>
    Set the type of background user to
    "Background" up to 4.6B
    "System" as of 4.6C
    This user type corresponds to the "Communication" type and may also perform background functions.
    Through the Customizing, the BW user is automatically created by mistake as a communication user.Depending on your BW system release, you can solve this problem as follows:
    BW 2.0B
               Import Support Package 24 for 2.0B (BW2.0B patch24 or SAPKW20B24) into your BW system. The Support Package is available once note 456551 with the short text "SAPBWNews BW 2.0B Support Package 24", which describes this Support Package in more detail, has been released for customers.
    BW 2.1C
               Import Support Package 16 for 2.1C (BW2.1C patch16 or SAPKW21C16) into your BW system. The Support Package is available once note 456566 with the short text "SAPBWNews BW 2.1C Support Package 16" has been released for customers.
    BW 3.0A
               Import Support Package 8 for 3.0A (BW3.0A patch08 or SAPKW30A08) into your BW system. The Support Package is available once note 452632 with the short text "SAPBWNews BW 3.0A Support Package 08" has been released for customers.
    <b></b>

  • Regarding "Delete Index" process in the process chain.

    Hi Gurus
    In the process chain, I have Delete Index -> Load Info pacakge -> Create Index process in the above order.
    I am loading few records, so no need to delete indexes everytime. Can i remove the "Delete Index" process from the Chain without deleting the Create Index process. Or do I have to delete both.
    Could you please clarify my doubt if possible in detail.
    Thanks,
    Regards,
    aarthi

    With the numbers you provided, you probably don't need to have the steps.  With Oracle (not sure about all the other DB flavors) there are some other considerations:
    Not having the indexes when loading the data can improve the load time since the bitmap indexes are not very efficient with respect to inserts/updates. The more dimensions you have, the more indexes there will be and the more noticable the impact of having the indexes present when loading.
    The drop index process only drops the F fact table indexes.  If you compress your cubes regularly so that you don't have many uncompressed requests, the index rebuild time will remain small, but if you have many uncompressed requests in your cube, the index rebuild time can begin to exceed whatever time you might save on the load with indexes deleted.
    With bitmap indexes present, you can also occasionally receive a ORA-0600 deadlock error during the load process, and that can be prevented by dropping the indexes before loading or chose the load option packet by packet so that two packets are not trying to update the same index block at the same time.
    Another concern in shops where reporting on the cube might occur during the load process - if you drop indexes prior to a load, any one trying to run a query on teh cube could have poor query performance since all the indexes will be missing onthe F fact table, this agina becomes more apparent the more data you have in the uncompressed fact table.
    So it really comes down to your environment, but certainly drop the indexes any time you have large loads.

Maybe you are looking for