DP - Upgrade - Process chain

All,
We are currently on SAP 4.1 Demand Planning. We would like to upgrade to SCM 2007 or SCM 7.0.
My question when we upgrade will the process chains be transported to the upgraded system.
Thank you
Regards
Sameep

Hi Sameep,
As I said, if it is a technical upgrade, then you can directly apply the upgrade patch and do an extensive testing(variants/selection profiles may create conflicts because of the enhanced/changed features of the new system).
Also, when you are creating process chain variants or selection profiles, you can attach those objects to a transport request and can send it to different systems.
I would suggest to do a test of one or two objects on a sandbox system and verify it again. It should work.
Alternatively, you apply the patch in the sandbox system and do the testing for different technical objects/business scenarios.
Regards
Manotosh

Similar Messages

  • Problem in process chain after upgrade

    Hi,
       We recently upgraded our sysetm to BI7.0 version.When I tried to run a process chain,it failed at the data load step.I tried to see  the  message but it is throwing an error like "object not persistent".so can somebody let me know what is the error here...
    Thanks
    Karthick

    Hi Karthik
    I assume variant(EXOR) has been used in another process chain which is inactive status, if we create Process Chain 'A' with variant (EXOR) and create another Process chain 'B 'with same variant(EXOR) and inactive status, PC 'A' doesn't execute though its in active status, it will work only when both process chains were in active status, please find in which process chain this variant has been used, remove/activate variant(EXOR) and execute your primary process chain, hope this will resolve your issue, please let me know if this doesn't resolve your issue
    -DU

  • Process Chain behavior changed after SP upgrade

    Hi all, we've recently updated SP from SAP_BW 700, SAPKW70016 to SAPKW70021.
    We realized about a particular process chain behavior:
    We have many process chains configured to execute the next step "Always" (whatever it happens with the previous process).
    This is the situation which changed:
    BEFORE the upgrade:
    If error raises on a process, this one remains "red" but the subsequent processes continues.
    Once repaired (repeat/repair from the PC) the "crashed" process it is updated to "Green" status.
    AFTER the upgrade:
    If error raises on a process, this one remains "red" but the subsequent processes continues.
    Once repaired (repeat/repair from the PC) the "crashed" process it is updated to "Green" status.
    The remaining processes are executed once again (a new branch is generated). <- This is different
    I want the "BEFORE the upgrade" behavior to keep working as always.
    Do you know if there's some OSS note or tips of configs available to set this as my needs? (we have found the OSS Note 1398868 and implemented it, but the "effect" is not as we should expect for this case in particular).
    I hope you can help. Thanks in advance and best regards,
    Bernardo

    I've found the OSS note: Note 1473491 - Chain not continued with termination and "ALWAYS" link; delivered with "SAPKW70025" corrections. It seems to be solving the issue I've originally mentioned. I'll perform some tests on this and update.
    Regards,
    Bernardo

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

  • Process chain is not triggering through event after BW Upgrade

    Many of our process chains are event based.
    After BW upgrade 7.0  to BW 7.31 we tried to trigger the event through  SM64 Tcode. But the process chains are not getting triggered.
    Could anyone please guide me what might be the issue.

    Hi Bharan,
    Can you please check once the start variant of process chain which are based on event.I think it should trigger after event is triggred.
    Regards,
    Ganesh Bothe

  • Updating an existing process chains created in 3.5 upgraded to 7.0

    I added DTP's to my process chain, see below process.
    1)  Load Inventory data to PSA (R3 to BI)
    2)  Run ODS DTP
    3)  Activate ODS
    4A)  Run DTP to Cube (If I add this, it works, but the Process Chain shows warning, must have Further processing before DTP to Cube.) Is a warning okay?
    4B)  Run Further Processing (Data Store object, ODS_BF).  The Process chain check shows no warning, no error.  But, when the process chain is executed, this last process executes DTP to the cube and also executes the Info Package from BI to BW (8ODS).  We are not using the Info Package of BI to BW at this time, we did not migrate this info package.
    Please help me understand how this should work.
    Thanks,
    Maximina Barry

    Warning is okay but its no harm to have " Further Processing " in ur chain.
    1. Start
    2. Execute Infopackage ( loads till psa )
    3.Execute DTP ( to load DSO frm PSA )
    4.Activate DSO
    5.Further Processing
    6.Delete Indexes for Cube
    7.Execute DTP ( to load Cube frm DSO )
    8.Create Indexes for Cube
    Infopackages n DTPs shud all be delta in update type.
    <b>Delete n Creating Indexes if preffered for performance.</b>
    Also look at : Further Processing Type In Process Chain

  • Delete Index in Process Chain Takes long time after SAP BI 7.0 SP 27

    After upgrading to SAP BI 7.0 SP 27 Delete index Process & Create index process in Process chain takes long time.
    For example : Delete index for 0SD_C03 takes around 55 minutes.
    Before SP upgrade it takes around 2 minutes to delete index from 0SD_C03.
    Regards
    Madhu P Menon

    Hi,
    Normally  index  creation or deletion can take long time in case  your database statistics are not updated properly, so can check  stat  after your data loading is completed and index generation is done,  Do creation of database statistics.
    Then try to recheck ...
    Regards,
    Satya

  • Invalid DataStore object name error when running process chain after EHP1

    Hello,
    We recently upgraded our BW Dev platform to NW7.01 EHP1 SP6. I noticed that the layout for "Delete PSA Request" process in the Process Chain has changed after the upgrade. We can no longer specify the actual PSA table to delete eg, /BIC/B0001645. Instead we need to specify the Datasource name and the Source System.
    Now after the upgrade when I run one of my process chains, it fails at "Delete PSA Request" step with error message "Invalid DataStore object name /BIC/B0001645: Reason: No  valid entry in table RSTS". This datasource is based on the flat file source system and the PSA table for this Datasource is /BIC/B0001653.
    Unfortunately the process chain is picking up an older PSA table for this datasource and there is no way for me to specify the current PSA table name after this change in layout with EHP1 upgrade. Any suggestions on how to resolve this issue.
    Many Thanks,
    Al

    Hi,
    Please implement OSS 1345331.
    If this does not help try the below steps:
    1.  Run the report 'RSAR_PSA_CLEANUP_DIRECTORY/_MS' in check mode for a 
           particular PSA table for finding the inconsistencies.
    2.   After that please analyze the logs and if there is any problems related to partition, you need to correct them using the report u2013
    3.  'SAP_PSA_PARTNO_CORRECT' in repair mode for the
          PSA tables.  Run the report again after this
    4.  'RSR_PSA_CLEANUP_DIRECTORY/_MS' in check mode to 
         double check that the invalid partitions are 
         corrected.
         Once this is done you can execute the report     
         'RSR_PSA_CLEANUP_DIRECTORY/_MS' in repair mode.
    -Vikram

  • ABAP process job ( BI_PROCESS_ABAP ) in process chain running for long time

    Dear Experts,
    We have an ABAP process job  BI_PROCESS_ABAP  in a process chain. This job is running for a very long time than previous run time.
    Recently we had an ORACLE database upgrade from 9.2 to 10g.
    From the very next day , we are having this problem.
    And also previously this process-chain was under control of BASIS guys . they were using a tool called CRONACLE to schedule it. At the time of upgrade this tool was crashed and they asked us to schedule it in BW system instead.
    Underlying program is using two custom tables.
    one is having both primary & secondary indexes but the other table is having only primary index.
    I am not sure whether we have secondary indexes on other table prior to upgrade or not.
    Where must be the problem?...
    At the time of upgrade BASIS has re-organized the table space along with database upgrade.
    please help me...
    Regards,
    SRIKANTH

    Please ask yr basis consultant to check the system parms.
    Below i have listed down SAP recommneded system parms .
    abap/heap_area_total 4000000000
    abap/heap_area_dia 2000000000
    abap/heap_area_nondia 2000000000
    Also check in SM37 if any other jobs are running for long time, peventing the your job running.
    Check the SM12 for locks or SM58

  • Process Chain issue-Needs urgent Help

    R/3 Master Data Main Chain
    Problem Description:
    When we trigger the process chain from SM64, the process chain fails at the step as shown below.
    There are no logs for the local chain i.e. the local chain fails without linking.
    If we manually schedule the local chain it runs successfully.
    The error message changed as and when we tried fixing the defects. Each of them with the solutions tried for them is explained below.
    ERROR 1:
    The error message which we got was as ‘Cannot Activate Job BI_PROCESS_LOADING (return code 8).
    Solution tried:
    1.     Replicating Data Sources and activating the transfer and communication structures by running the programs RS_COMSTRU_ACTIVATE_ALL and RS_TRANSTRU_ACTIVATE_ALL.
    ERROR 2:
    Later we found that the released job was missing for failed local chain.
    Solution tried:
    1.     We created a new job by copying a previous job.
    ERROR 3:
    When we re-scheduled the process chain, we got the error message as shown below.
    Solution tried:
    1.     Deleted all the logs which were in running status.
    ERROR 4:
    After re scheduling the process chain we are getting the error message as shown below. This is the error message we are getting now.
    Solutions Tried:
    1.    Saving the variant and reactivating the process chains.
    2.     Replicating Data Sources and activating the transfer and communication structures by running the programs RS_COMSTRU_ACTIVATE_ALL and RS_TRANSTRU_ACTIVATE_ALL.
    3.     Changing the scheduling options of the failed local chain to ‘Start using Meta Chain or API’ from ‘Direct Scheduling’.
    4.     We searched for locked entries in SM12. There are no locked entries.
    5.     We ran attribute change run with variant for info object ‘Profit Center’ from the following path
        RSA1-> Tools-> Apply Hierarchy/ Attribute Change Run. We created a new variant for the info object.
    We still could not find a solution. do let us know if you have any inputs.
    Thanks,
    Mayuri

    Hi All,
    Please reply ASAP. Its critical.
    We created a new process chain and when we do a check on it,we are getting a warning message.
    We just upgraded our Dev box from 3.5 to 7.0. Our master data process chains, which reflect samples delivered by SAP, are giving warnings saying "too many parallel processes" for chosen server. It refers us to note 621400.
    I am curious to know if others have run into this, and if they have changed their MD process chains to run in a serial fashion.
    Prior to the upgrade, we had no deadlocks with process chains.
    Thanks.

  • Process chain stops - previous processes are green

    Hi All,
    We have a process chain that loads our master data each night.  It chain is mostly made up of infopackages (mostly full loads) and the change run for those objects.  We recently upgraded from 3.5 to BI7, SP16. 
    Since the upgrade, this chain, and a few others just seem to stop.  They will start, and successfully complete some of the processes in the chain (all green), but then will not move on to the next process.  The next process will not be yellow, it just won't start. The overall status of the chain is yellow. 
    I am 100 percent sure there are no other chains running during this time frame.  This chain has been running for over 4 years in production, and we have never encountered this issue. 
    Last night, I removed the chain from the schedule, and then rescheduled.  I'm not sure if that is going to prevent us from having this issue.  I have also set the priority to high. 
    Should this prevent us from encountering this issue again?  I have searched OSS and found some related notes, but we are on a higher support pack than what is in the notes, so they are already applied.
    Any suggestions?
    Thanks!
    Charla

    The first thing that I'd recommend is to look at the Start Process Variants for the Process/Local Chains that are not starting. Specifically, I would check to see if the scheduling in those Start Process Variants are set to Direct Scheduling with Immediate Start or set to Start Using Meta Chain or API. It is possible that the conversion from BW 3.x to BW 7.x change the parameters of the scheduling withing the Start Process Variants, even though they were not physically changed and transported.
    My recollection is, when we upgraded Support Package Stacks, we had some Local Chains just change on their own where the Immediate Start checkbox mysteriously become unchecked.

  • BI Admin Cockpit process chains fail to install

    Hi All,
    I'm attempting to install and configure the BI Admin Cockpit on our BI Development system.
    I've followed the steps outlined in the collective note, 965386.
    When running transaction rstcc_inst_biac to install the Content for the BI Admin Cockpit, the background job RSTCC_ACTIVATE_ADMIN_COCKPIT cancelled with error message RS 062.
    Regarding this, instructions from note 1039381 were used to clear table entries and I re-ran the job, this time successfully.
    Checking slg1, the logs show no errors and only minor warnings and it can be seen via RSA1 that some Technical Content is in the Activated state.
    However, when entering transaction RSPC to schedule the process chains, the screen is blank and it appears that the associated chains have not been installed.
    Regarding this, note 1065249 has been checked:
    <i>'This note needs to be applied only if SP level of software component BI_CONT is less than SP7 and SAP_BW is greater than or equal to SP13.'</i>
    Our system is currently at the required SP levels, BW13 and BI_CONT SP7.
    Any ideas on how to install the process chains would be very welcome.
    Chris

    I was able to install BI Admin Cockpit recently after multiple attempts. All process chains installed properly. There are still some minor issues but in general I was able to see the BI Stats reports. Here is the steps that I did:
    System Info: SAP_BW     700     13, BI_CONT     703     5
    1. Note 934848: Select only myself system in the TX:RSOR Source System
    2. Note 834280: Installing technical BI Content after upgrade
    3. Apply OSS note: 1039381, 1065249, 1044792
    4. Note 965386: Activate tech content in IMG (SPRO) sequentially from Activate SAPI Data Sources ... to Activate Technical Content. Activating it sequentially will help identify which step is failing.
    5. Activate Process Chains using txn RSOR Technical Content (0TCT*).
    The process chains were installed but failed to be activated. Whe I double click on a process chain nothing was displayed but edit the process chain anyway and activate manually.
    Good luck.
    Tony

  • Process chain failing with error 8 in BI 7.0

    Hi ,
    we have upgrade the dev to BI 7.0 and I am trying to execute the process chains but it is failing with a error 8 due to the step of the job BI_PROCESS is in the name of a old user. So i have changed in process chain -Attrbutes--Execution user --- current user.So the chain has started but it has so many chains inside the Meta chain it looks i need to go to each of them and change as cyurrent user.
    But is there some place where I can change globally to a Batch user/current user for these process chain in BI 7.0.If so pl let me know.

    Hi,
    user SM37 to identify all BI_PROCESS jobs and change the User of the step in the jobs (they all should only have one step).
    bye
    Frank

  • Lock Problem while Broadcasting multiple reports using process chains

    Hi All,
    I am trying to broadcast 10 reports using the process chains using the program for RSRD_START and variants created in the Broadcaster..the Program jobs start fine.But I am facing the error that the RSRA_CA_LOG table is getting locked while trying to broadcast the Reports..Can any help me on how to run the jobs without the locking problem..Suggestions please.
    Thanks,
    Mike.

    Hi,
    Thanks for the Inputs and the SAP Notes.
    I am trying to broadcast the Reports from the the Bex Analyer and getting this ock error and not the workbooks.
    I am also trying to Broadcast the Workbooks also, but could not find the options to Broadcast them. we are in SAP -BW3.5 SP 12, Is it possible to broadcast the workbooks in this Patch level..or do we need to upgrade to achieve this.If so...can any one provide me the proceedure to  Broadcast the Workbooks.
    Thanks,
    Mike.

  • Process Chain Adhoc schedule

    Dear Experts,
    I have daily schedule of Process chains . At the time of month end due to offline backup or at the time patch upgradation we need to stop the schedule for that day and next day again put in schedule.
    Is there any way to define custom schedule like exclude certain days.
    Regards,
    Manish

    Hi Manish,
    1)You can make the process chain to be trigered by an event.
    You do so by having the Job that start the PC start after an Event.
    Then you define your set of job's (thru SM37) and make sure these jobs fire the event that starts the PC.
    There is an ABAP program you can use that fires events (FM -> BP_EVENT_RAISE).
    2)In the Start process of your process chain, select Direct Scheduling and then click the Change Selections icon. This will bring you to the Start Time window where you can put in the Date/Time you want to start your process chain. At the bottom of this window, click on the Periodic job box and you will notice another icon way at the bottom called Period Values. Click this to determine what frequency the job should be rescheduled (ie. daily, weekly, etc.).
    3)you can do this by right-clicking on the start process, selection "Maintain Variant", choose "Direct Scheduling". Next select "Change Selections", pick your date and time, set your period values and you're done.
    Hope this helps.
    ****Assign Points If Helpful****
    Regards,
    Ravikanth

Maybe you are looking for