How to migrate waiting stage workflows in ms crm 2015

Hi,
We are migrating the data from ms crm 2011 on-premise to ms crm 2015 on-line.
So how to migrate the ms crm 2011 on-premise waiting stage workflows to crm 2015 on-line?
Is there anyway to migrate these workflows or workaround? Please suggest
Its very urgent.
Thanks,
Yadav
Yadav

Hello Yadav,
If you want to migrate from CRM 2011 on premise to CRM 2015 online, unfortunately this is not possible in single step. You would have to first upgrade to CRM 2013 and then only you can upgarde to CRM 2015.
CRM 2011 -> CRM 2013 SP1 -> CRM 2015
Refer https://technet.microsoft.com/en-us/library/hh699673.aspx
For On Premise to Online migration, all customizations has to be exported through a solution. And if your database is big you need to plan your migration using a DM tool like scribe.
Now coming on to your original question, the answer is if you just migrate database, everything will be in same state as it was earlier in your old environment, and will continue the same way. The records for which workflow are in waiting state or in progress
will be resumed again automatically once the migration is completed, if you will stop "CRM Aynchronous Service" then all workflows will be in waiting state so when you will resume the service again then the system will resume those workflows again.
Regards, Abhishek Bakshi If you find this post helpful then please Vote as Helpful and Mark As Answer. Check my blog on https://mydynamicscrmblog.wordpress.com/

Similar Messages

  • How to migrate Trade Promotions, Funds, Fundsplans im CRM 7.0

    Hello all,
    we want to upload Trade promotions, Funds and Fundsplans to CRM 7.0, but we cannot find any functions moduls, bapi or Classes.
    Any suggestions for that ?
    Thank you
    Frank

    Frank, I would post this Question in CRM Web UI forum which  is very active. I'm sure there are many people who worked on TPM.
    Thanks
    --Prasad

  • How to re-start the workflow for Shopping carts in WAITING status

    Hi
    We are using 1-step approval work flow, and we get some strange issue. We can add approver in the workflow, but after we click order button and back to check status again, sometimes there will be "Ad-hoc agent not found" issue. Do you know how to solve?
    And one workaround for user is to re-add the approval, and sometimes the shopping cart back to normal. But sometimes, after we add the approver, the shopping cart are in waiting status:
    Workflow Item:
    Workitem-ID 000000714642
    Task WS10000276
    Text One-Step Approval: Value limit: Shopping Cart
    1000114698
    Status WAITING
    Statustext Waiting
    Date 13.06.2008
    Time 10:41:22
    So may I ask how to re-trigger the workflow?

    Hi,
    Thx for that. I need to trigger the Approval workflow to go the the approval manager.
    Can u give me the document on this? thx,  kerry.liu [at] ap.effem.com.
    Thx very much
    Kerry

  • How can we import 3 stage workflow in Office 365?

    Hi All,
    How can we import and create 3 stage workflow in Office 365?

    Hi Farhan,
    First of all you are in the wrong forum for Office 365 Discussions.
    Secondly, please go through the links provided below for the query..
    All about Approval workflows
    SharePoint 2013 / Office 365: How to develop an out of box Helpdesk Approval Workflow
    SharePoint 2013 Document Approval Work Flow With Visio 2013
    Indul Hassan
    http://www.indulhassan.com
    You Snooze.. You Lose !!
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Migration of 2010 workflow to 2013

    if we use leading 3rd party tool Quest for migration then how to migrate sequential workflows from 2010 to 2013? will all sequential workflows automatically migrate to 2013 with quest tool or we need to do any further steps? It will be helpful if you say
    about steps here.
    Do quest tools supports automatic migration of sequntial workflows to 2013 . I think it will run as 2010 workflow only. 2013 introduced stages, do we have to crate those stages?

    2010 workflows will still run the same way they did in 2013.  The 2010 workflow mode is backwards compatible.  If you want the workflows to run in the newer 2013 engine then you'll need to re-write the workflows.  There are actions that are
    available in 2010 that aren't available in the 2013 mode and vice versa so there is no automated conversion available.
    But the Quest migration tool should migrate the workflows with the rest of the site when you migrate it.  In general they continue to work, but I do recommend testing since I've seen a few workflows that had problems after upgrade.  But the migrated
    workflows will run as 2010 workflows in 2013.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • How to migrate Drop Ship PO and SO from 11.0.3 instance to R12?

    Hi Everyone,
    We are in process of migrating Drop Ship Orders from 11.0.3 system to R12 system?
    Can anyone help me in identifying how to migrate Drop Ship Orders?
    Is it possible to migrate Drop Ship PO and SO Separately and then link them through Drop ship sources table? How the reservation will work for this type of orders?
    Any guidelines will be really helpful.

    Hi,
    What I am currently planning to do is as follows:
    1) Migrate the Drop Ship SO
    2) Run the workflow background process which will progress the line (From Booked -> Awaiting Receipt) and insert the record in to Requisitions Interface and OE_DROP_SHIP_SOURCES Table
    3) Migrate the PO separately
    4) Update the record created through second step in Drop Ship Sources table with PO Header ID, Line ID and Line Location ID
    5) Receive against the PO
    6) OM Line is getting shipped at this stage once the receiving is done
    7) Delete the lines in Requisition interface table
    In this, the only custom thing we are doing is updating the DROP SHIP SOURCES Table with PO IDs.
    I am not able to think any other way to migrate Drop Ship SO.
    Please suggest, if anyone is foreseeing any problem in this approach or having any other approach.

  • Upgrade CF9 to CF11 w/IIS can't get to migration/configuration stage

    I finally go approval to do my upgrade not as a stand alone, side-by-side upgrade which was requiring me to do a major hack that wasn't working due to our funky coding and security twists we have implemented in the code.
    Unfortunately, when I do the upgrade/installation it installs, but I can't move on to the migration/configuration stage of the installation.  I can't see anything in the error logs.  Sometimes I'll get the 500.19 error message when I try to connect to the administrator myself, other times nothing.  When I get the HTTP Error 500.19 Internal Server Error it refers to the ApplicationHost.config or web.config file that contains malformed xml element.  When I look at the old web.config file it contains about 9 handlers that are using either jrun_iis6_wildcard.dll or jrun_iis6.dll.  I do have the IIS6 to IIS7 configuration selected in the new installation of CF11, but I can't move forward.  I want to just copy these 2 files from my CF9 installation, but I don't know where to put them.  I've even renamed the web.config file so that IIS would recreate it so it wouldn't be referring to the old CF9 web.config file and getting stuck there, which one error message once referred to these lines in the CF9 web.config file.  I understand that this question blurs the ColdFusion/IIS category boundaries.  I'm not sure where my error is lying, with IIS or CF11.  I want to just enter these handlers manually in IIS 7, but my boss seems to think we need to have wsconfig do that for us in case it is putting code elsewhere and we are missing configuration changes that really puts us in a spiral.  Thoughts/suggestions anyone?  I hope I was clear enough.
    Another thing is that we have our CFIDE folder for CF9 located in a different directory, for security purposes I'm guessing, yet I can't figure out how CF is recognizing that it should go there to run.  In CF Administrator it is referring to a different folder for CFIDE that doesn't exist.  I have only seen one referrence to the correct location, and that was in the registry when I was ensuring CF11 references were deleted. CF9 had it there. I guess I'm wondering if there is a setting somewhere that i need to change so CF11 will look in the correct location and then run and go forward with the migration/configuration part of the instalation.  I can't find it in any of my searches that look for that foldername in the files.
    I have inherited this project and there is very little documented regarding configuration changes that were done.
    Thanks in advance!!
    Jennifer

    OK, my installation is working, although I'm still trying to get the applications to work (permissions issues I think).  Since I kept having migration difficulties we created a CAR first with CF9.  We then ended up just doing a straight upgrade on our development server.  I performed the install with server configuration and selected Configure my webserver for ColdFusion 11, IIS.  When you launch the browser to connect to CF11 administrator if you get the 500 error message it may be because the SSL for the CFIDE>Administrator folder in IIS is selected.  Deselect it and that error messge should go away (if it is that that is).  We kept getting a 404.7 error message of deny file extension.  I was thinking it had to do with my cfm extensions because I was trying to open a cfm, but it wasn't the case.  The error message mentioned isapi.redirect.dlls.  I finally found an error message under my IIS FailedRequestLogs that mentioned something about Request Filtering.  Turns out .dll was not in the allowed list of my virtual Jakarta folder.  Once I added this and restarted IIS I was able to get into my CF Administrator 11 and installed the CAR file.
    Now I keep getting Unauthorized errors and need to figure that out. Permissions are looking like the cause of that.
    Things I learned (you may already know this):
    CF9 can have CFIDE placed wherever, but CF11 needs to keep it where it is installed.
    CF11 doesn't need IIS 6 Metabase Compatability installed, whereas CF9 did (at least ours did)
    We kept getting a duplicat MIME Type error message too for .air.  That was added at the server level and inherited at the website level.  I deleted it at the server level and added it at the website level.
    I hope this helps someone.

  • How can i execute a workflow using a bapi/wapi??

    Hi All,
    How can i execute a workflow using a bapi/wapi??
    pls advice
    thanks

    Hi Hrus,
    it's not as simple as a single BAPI to approve a workflow.
    Workflow comes with a Workflow API (WAPI) that you can use to programmatically interact with the workflow system. The WAPI is implemented as a group of RFC-enabled function modules that are prefixed with "SAP_WAPI_".
    Approving a workflow is simply taking a decision path for a workflow item. It is logically no different to rejecting the same workflow item or any other workflow decision.
    As part of NetWeaver workflow is tightly coupled to the WAS platform you are running on so you may need to perform WAPI operations slightly differently on older releases.
    Some of the WAPI calls you might need to use include: -
      SAP_WAPI_GET_HEADER to get the workitem header
      SAP_WAPI_READ_CONTAINER to get the workitem container
      SAP_WAPI_GET_OBJECTS to get the attached objects
      SAP_WAPI_DECISION_READ to get a list of possible decisions
      SAP_WAPI_SET_WORKITEM_STATUS to set the workitem status
      SAP_WAPI_WRITE_CONTAINER to write to the workitem container
      SAP_WAPI_EXECUTE_WORKITEM to execute the workitem
    I usually do what you are trying to do by adding the decision to the workflow container and then executing the workflow.
    Be warned, you can really stuff things up if you get this wrong! Make sure you know what you are doing.
    Quoting from Practical Workflow for SAP by Alan Rickayzen, et al from SAP Press...
    Writing directly to the workflow container is dangerous because it can compromise the integrity of the process.
    ...be careful that you do not waste time duplicating existing ad hoc features of SAP's Workflow Engine.
    For example you can use events (combined with wait steps), instead of container modifications to force the workflow to restart.
    Cheers
    Graham Robbo

  • How to migrate the Objects from 3.1c to BI7

    Hi,
    We are in Functional Upgradation.
    How to Migrate the Objects( Infocubes,DSO,Datasources,Rules...etc...) from 3.1C to BI 7.0
    Please help me to doing this....
    regards,
    anil

    BW Upgrade tasks (BW 3.1C to BI 7.0)
    Prepare Phase:
    Task     How-To     Who
    Review BI 7.0 feature lists     Review BI 7.0 feature lists for possible inclusion in developments.     Basis/BW
    Obtain the BI 7.0 upgrade guide     Download the upgrade guide from http://service.sap.com/inst-guides -> SAP NetWeaver -> Upgrade
         Basis/BW
    Review all upgrade SAP notes     In addition to the upgrade guide, check, download, and review all SAP notes for your upgrade
         BI 7.0 Upgrade notes
         SAP Web Application Server 6.40 upgrade notes
         OS and DB specific upgrade notes
         SAP BW Add-on upgrade notes
    (e.g. SAP SEM, ST-PI, etc)
         Plug-In upgrade SAP notes
         Other notes identified in above notes and/or upgrade guides.
         Basis/BW
    Check DB and OS requirements for the target SAP BW release     Check DB version/patch level and OS version/patch level required for upgrade
         First check the most current information from the SAP BW homepage http://Service.sap.com/BW  -> <SAP BW release> -> Availability
         Additionally, the u201CPlatformsu201D link will take you to the main DB/OS page for BI 7.0 and SAP Web AS 6.40.
         Note: In some cases there are differing requirements for SAP BW 3.0B/SAP BW 3.1 Content and BI 7.0
         Basis
    Check SAP BW Add-on upgrade requirements     Do you have SAP BW add-ons installed that require additional handling (e.g. SAP SEM, Enterprise Portal Plug-in, etc)?
         SAP SEM (SAP BW based components) requires SAP SEM 4.0 which is part of the mySAP ERP 2004 suite.
         WP-PI release must be at 6.00 before the upgrade begins. As mentioned before this add-on is merged with PI_Basis after the upgrade.
         Basis
    Check SAP BW upgrade requirements          Minimum Support Package and kernel levels for upgrade
         SAP BW Frontend requirements for new SAPGUI, SAP BW BEx Frontend and SAP BW Web applications.
         Source system Plug-In requirements     Basis
    Check compatibility requirements with 3rd party software          3rd Party Reporting tools (example: Crystal)
         ETL Tools (example:  Ascential, DataStage, etc)
         Scheduling tools (example. Control-M, Maestro, etc)
         Monitoring tools (example: HP OpenView, Patrol, etc)
         Other OS or DB related tools     Basis
    Check new component requirements for BI 7.0          If SAP BW web reports were developed in SAP BW 2.x, a windows version of IGS 6.40 (Internet Graphics Service) is required for conversion and future rendering of web graphics (i.e. Charts and GIS Maps).
    The IGS chart migration will also be required after the SAP BW web report conversion.
         If you used or activated any SAP BW Web Applications in SAP BW 3.x, or if you have used charts in SAP BW 2.x web reports, you will need a windows version of IGS 6.40 (Internet Graphics Service) to execute the IGS chart migration after the upgrade.
         If ESRI GIS software is in use, a different version of ESRI software maybe required for BI 7.0.  (ArcView 8.2?).
         If you plan to use Information Broadcasting, please review the requirement for additional infrastructure components such as EP, KMC, Workbook pre-calculation service, and Web AS connectivity to your mail servers.
    Detailed information is available in the SAP NetWeaver u201904 master planning guide (http://service.sap.com/instguides  -> SAP NetWeaver).
         Basis
    Test and distribute new SAP BW Frontend
              Install and test the new BI 7.0 Frontend (including the new version of SAPGUI for Windows if applicable).
         A detailed FAQ on the new BI 7.0 Frontend is available on the SAP service marketplace alias BWFAQ (http://service.sap.com/BWFAQ).
         After successful testing, the new SAPGUI for Windows and SAP BW Frontend can be distributed to the BW teams and end users.
         Basis
    Alpha Conversion:
    Ensure that your InfoObject data is consistent from a u201Cconversionu201D perspective (Alpha Converter tool)      Check that you have executed the Alpha Converter tool to check the consistency of your InfoObject definitions and data for InfoObjects that utilize the ALPHA, NUMCV and GJAHR conversion exits.
    Note: The Alpha conversion is not part of the SAP BW upgrade itself, but the upgrade simply checks to ensure you have successfully executed the check tool.
    Transaction RSMDCNVEXIT
    Check the system status:
         u201CAll Characteristics Have Correct Internal Valuesu201D: The Alpha converter has been successful executed. The upgrade preparation can continue.
         u201CNo Check yet/Inconsistent Internal Vales existu201D:
    The Alpha converter check has not been executed.
         u201CCharacteristics have Inconsistent Internal Valuesu201D:
    The Alpha converter tool check has been executed and data problems have been detected. The InfoObject and data must be processed before the upgrade can be started.
         BW
    Upgrade SAP Note updates     Check for newer versions of your SAP notes for the Upgrade.
    Tip: The SAP service marketplace offers an option to subscribe to OSS notes so you can be notified of changes when you log on.
         Basis/BW
    Confirm SAP BW support package, kernel and DB/OS configuration     Analyze current Support Package and DB/OS/Kernel configurations in your SAP BW landscape in relation to the SAP BW 3.x upgrade requirements.
         Apply necessary support packages, kernel patches, and DB and OS patches to meet upgrade requirements
         Basis
    Alignment of SAP BW objects within your SAP BW system landscape     Check and, where required, re-align SAP BW Objects and developments in your SAP BW system landscape (Development, Quality Assurance and Production).
    SAP BW Object differences can impact the quality of testing in the Development and Test environment and can lead to change management issues.
         This check is to minimize risk and ensure productive objects are being tested prior to the Production upgrade.
    Where alignment issues exist and realignment is not possible, alternative testing plans should be devised.
         Basis/BW
    Confirm all developments are deployed.     Ensure that all SAP BW developments are deployed or they are to be re-developed/tested after the upgrade.
         In the DEV system, all SAP BW development transports should be released (i.e. transport created and released) and imported to all downstream systems (i.e. QAS and PRD systems).
    For SAP BW developments not already collected in the transport collector, a decision must be made:
    Deploy the developments or wait until the upgrade has completed to deploy.
    o     Development to be deployed should be collected, released, and imported into the QAS and PRD systems.
    o     Developments that should be deployed after the upgrade should be re-tested/re-developed after the upgrade.
         In the QAS or PRD systems, ensure that all SAP BW development transports have been imported prior to the upgrade.
         BW
    Implement BI 7.0 Business Explorer Frontend     Install, evaluate, test and distribute the new BI 7.0 Business Explorer Frontend.
         Basis/BW
    Pre-upgrade Process:
    Download required BI 7.0 support package Stack for inclusion in the upgrade     Determine the equivalent support package level of the source SAP BW release and the target SAP BW release.
         There is a minimum requirement that you upgrade to at least the equivalent support package level on the target SAP BW release so that you do not lose functionality, corrections, and data.
         It is recommended to upgrade to the latest version of all support packages during the upgrade via the upgradeu2019s support package binding functionality.
         BI 7.0 Support Packages are delivered via SAP NetWeaver u201904 Support Package stacks (SP-Stacks). It is not recommended to partially apply some of the SP-Stacksu2019 individual support packages. You should apply all of the SP-Stacks support packages at once.
    For more information on the SP-Stacks and SAP NetWeaver SP-Stacks, please see the SAP service marketplace alias SP-Stacks (http://service.sap.com/sp-stacks)
         You should also review, download, and bind in support packages for all add-on components that are installed on SAP BW and will be upgraded during the SAP BW upgrade (e.g. SEM-BW, ST-PI, etc)
         Basis
    Apply latest Support Package tool patch     Apply latest SPAM patch before executing PREPARE     Basis
    Validate the SAP BW (ABAP) Data Dictionary and the Database Data Dictionary for consistency     Check Database consistency
         Transaction DB02:
    o     Execute ABAP SAP_UPDATE_DBDIFF and re-execute DB02 check. This gives a truer view of the SAP BW objects in DB02.
    o     Check missing database objects (indices, tables, etc)
    o     Missing indices may identify erred data loads or process problems
    Tip: Missing indices on InfoCubes can be restored by RSRV or ABAP SAP_INFOCUBE_INDEXES_REPAIR
    Note: check for running data loads before executing a repair!
    o     Check DDIC/DB consistency
         Verify database objects and consistency
    (e.g. SAPDBA check for offline data files)
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         BW
    Validate your SAP BW Objects for correctness prior to your upgrade     Using the SAP BW Analysis Tool (transaction RSRV), perform extensive tests on all important SAP BW Objects to ensure their correctness prior to the upgrade.
    Note: this test should be repeatable so you can re-validate after the upgrade!
         Ensure that any inconsistencies are identified and corrected
         RSRV has a number of extensive tests and if all checks are executed will consume a large amount of time. Multiple tests can be performed in parallel.
         Tip: Some corrections in development can be deployed to other systems via transport in advance of the next upgrade.
         BW
    Ensure DB Statistics are up to date prior to the upgrade          Check DB statistics for all tables.
    Tables without statistics, especially system tables, can seriously impact upgrade runtimes.
         Check DB statistics for missing Indexes for InfoCubes and Aggregates
    o     User transaction RSRV to check      BW
    Check SAP BW Support Package status     Check the status of all support packages (via transaction SPAM)
         Ensure the Support Package queue is empty
         Confirm all applied Support Packages     Basis
    Check all u2018Repairsu2019     Check for unreleased repair transports
         Release all unreleased transports
    In your QAS and PRD system, check if all repair transports have been imported (i.e. systems are aligned)
         Import missing repair transports into down stream systems. This will avoid differing message and/or errors during the upgrade.
         BW
    Check InfoObject status          Check for revised (modified) InfoObjects that have not been activated.
    All InfoObjects should be active or saved (not activate):
    o     Check all inactive InfoObjects:
    Transaction RSD1 (Edit InfoObjects),
    click on u201CAll InfoObjectsu201D radio button and click the u201CDisplayu201D button.
    Modified InfoObjects are denoted by yellow triangles!
    o     Determine if revision should be activated or removed.
         'Reorgu2019 or u2018Repairu2019 all InfoObjects
    This checks and repairs any discrepancies in the InfoObject definition and structures. It is common to have obsolete DDIC and table entries for InfoObjects after multiple upgrades and definition changes. These obsolete entries normally do not effect normal SAP BW operations.
         Transaction RSD1 (Edit InfoObjects), Select u201CExecute Repairu201D or u201CExecute Reorgu201D Use expert mode for selective executions.
         BW
    All ODS data loads must be activated.          Activate all inactivated ODS Object requests.
    All ODS u2018Mu2019 tables must be emptied prior to the upgrade as a new activate process is implemented
    o     Inactivated ODS request can be located via the Admin workbench -> u2018Monitoringu201D button -> u2018ODS Status Overviewu201D
         BW
    All Transfer and Update rules should be active          Check for inactive Update and Transfer Rules
    o     All update rules and transfer rules should be active or deleted.
    o     Look into the table RSUPDINFO for update rules and search for the version "not equal" to "A". Likewise use the table RSTS for Transfer rules/structure.     BW
    All InfoCubes should be active          Check for inactive InfoCubes and Aggregates (Aggregates are InfoCubes too!)
    o     All InfoCubes should be activated or deleted.
    o     Execute ABAP RSUPGRCHECK to locate any inactive InfoCubes. See SAP note 449160.
         BW
    All Web Report objects should be consistent prior the upgrade.          Check the consistency of your SAP BW web objects (web reports, web templates, URLs, roles, etc). All objects should be consistent prior to web object conversion after the upgrade. It is recommended to ensure consistency before the upgrade.
    o     For Original release SAP BW 3.x:
    A SAP BW web reporting objects check can be executed via a new check in RSRV. This is provided via a SAP BW support package.
    Please see SAP note 484519 for details.
         BW
    Backup your system before starting PREPARE     Before execution PREPARE, perform a full database backup (including File system). Ensure you can recover to the point in time before PREPARE was executed.
         Database admin
    Address any instructions/errors generated by PREPARE          Address any issues listed in log files Checks. Log generated by PREPARE.
    o     Repeat PREPARE until all checks are successful.     Basis
    Complete any Logistic V3 data extractions and suspend V3 collection processes          Extract and empty Logistics V3 extractor queues on SAP R/3 source systems.
    o     The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss. V3 collector jobs should be suspended for the duration of the upgrade.
    They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Complete any data mart data extractions and suspend any data mart extractors          Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
    o     The SAP BW Service SAPI, which is used for internal and u2018BW to BWu2019 data mart extraction, is upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the upgrade to avoid any possibility of data loss.
         Note: If you perform any data loads after executing PREPARE, re-check the status of all delta queues in SAP BW and the source systems(s).
         BW
    Check that your customer defined data class definitions conform to SAP standards          Check all customer created Data classes used by SAP BW Objects (i.e. InfoCubes, ODS Objects, Aggregates, InfoObjects, and PSAs) to ensure they conform to SAP standards.
    o     Check your data class definitions as detailed in SAP Notes 46272 and 500252.
    o     Incorrect data classes could create activation errors during the upgrade.
         BW
    Remove unnecessary SAP BW temporary database objects     Delete all SAP BW temporary database objects:
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
         This reduces the numbers of database objects that need to be copied during the upgrade.
         Note: take care not to delete objects that are in use as this will cause queries, compressions, etc to terminate.
         Basis/BW
    Backups!     Before executing the upgrade, ensure that you have a backup strategy in place so you can return to the point where loading was completed and the upgrade started.
    Ensuring you can return to a consistent point in time (without having to handle rollback or repeats of data loads) is key to having a successful fallback plan.
         Database Admin
    Before Execution:
    All SAP BW administration tasks should have ceased          Cease all SAP BW administration tasks such as Object maintenance, query/web template maintenance, data loads, transports, etc at the beginning of the upgrade.
    The Administrators Workbench and the Data Dictionary are locked in the early phases of the upgrade.
         Reminder: Users can execute queries until the time that the upgrade determines that the SAP BW System should be closed*
    - timing depends on the type of upgrade selected
         Basis/Admin
    Remove unnecessary SAP BW temporary database objects     Repeat the deletion of all SAP BW temporary database objects after you have stopped using the SAP BW Admin workbench*
         Execute routine housekeeping ABAP SAP_DROP_TMPTABLES.
    For more information see SAP note 308533 (2.x) and 449891 (3.x).
    - timing depends on the type of upgrade selected
         BW
    Check system parameters     Check OS, DB, and Instance profile parameters.
         Check System Instance parameters for new BI 7.0 specific parameters. See SAP note 192658 for details
         Check for any DB specific parameters for BI 7.0
         Check for any new OS parameters     Basis
    Check Database archiving mode     Turn database archive log mode back on if it was disabled during the upgrade!
         Database Admin
    After Execution:
    Check the systemu2019s installation consistency     Execute Transaction SICK to check installation consistency
         BW
    Check the system logs     Perform a technical systems check.
         Example: Check system and all dispatcher logs (inc. ICM logs)
         Basis
    Apply latest executable binaries     Apply the latest 6.40 Basis Kernel for all executables
         Tip: use the SAP NetWeaver u201904 SP-Stack selection tool to find all binaries. (http://service.sap.com/swdc)
         Basis
    Review BI 7.0 Support Packages for follow-up actions.          Review SAP Notes for all SAP BW Support packages applied during (bound into the upgrade) and applied after the upgrade:
    o      Search for Note with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Apply latest patches          Apply the latest SPAM patch
         Apply any required support packages that were not bound into the upgrade.
         Basis
    Apply additional BI 7.0 Support Packages
    (if required)          SAP recommends that customer remain current on SAP Support Packages.
         Review SAP Notes for all SAP BW Support packages applied in previous task.
    o      Search for Notes with the keyword u201CBWu201D, u201CSAPBWNEWSu201D, and u201C<BW release>u201D
    o     Follow any required instructions identified in the SAP Notes
         Basis
    Resolve any modified SAP delivered Role issues      If SAP delivered Roles were modified, then these modifications may incorrectly appear in the upgrade modification adjustment tool (SPAU).
         Review and implement SAP note 569128 as required     Basis
    Configuring Information Broadcasting EP/KMC Connections
         If you plan to use the EP integration functionality of Information broadcasting (Broadcast to the EPu2019s PCD, Broadcast to KMC, or Broadcast to Collaboration Rooms):
         Ensure the SAP EP is at the same SP-Stack level as your SAP BW system.
         Follow the online help documentation to configure and connect the SAP BW system and the SAP EP system. (http://help.sap.com).
         For broadcasting to KMC, ensure that KM has the u2018BEx Portfoliou2019 content available.
         Basis
    Re-check SAP BW Object and consistency     Execute RSRV to check SAP BW Object consistency
         Repeat tests that we executed prior to the upgrade.
         Validate results      BW
    Check InfoCube views for consistency     Check consistency of InfoCube fact table views
         It is possible that fact table view /BIC/V<InfoCube>F is missing if a number of SAP BW upgrades have been performed before. See SAP Note 525988 for instructions for the check and repair program.
         BW
    Perform SAP BW Plug-in (SAPI) upgrade follow-up tasks          If required, Re-activate the SAP BW u201CMyselfu201D source system in SAP BW.
         The SAP BW internal plug-in (SAPI), which is used for internal data mart extraction and u2018BW to BWu2019 communication, is upgraded during the SAP BW upgrade. The source system is de-activated to prevent extractions and loading during the upgrade.
         It may be required to replicate export DataSources and reactivate transfer structures/rules for internal data loads (i.e. ODS Object to InfoCube objects).
    o     Tip: It is advised to do this step for all export DataSources to avoid possible errors during execution of InfoPackages
         Check that all other Source Systems are active.
    o     Activate as required.     Basis/BW
    Check SAP BW Personalization is implemented     (SAP BW 2.X upgrades will have performed this in the previous task).
    Validate that personalization has been activated in your SAP BW system.
    Note: It has been observed that in some cases, BEx Personalization has to be re-activated after an upgrade from SAP BW 3.x to BI 7.0. It is advised to check the status of personalization after the upgrade.
         Enter the IMG (transaction SPRO), select SAP Business Warehouse -> Reporting relevant settings -> General Reporting Settings -> Activate Personalization in BEx
    Check the status of the Personalization settings. All entries should be active u2013 highlighted by an unchecked check box.
         To activate highlighted Personalization, click Execute.     BW
    For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert ODS secondary indexes to new standard     For SAP BW 2.0B/2.1C -> BI 7.0 Upgrades:
    Convert any customer created ODS Object secondary indexes to the new ODS Object index maintenance process.
         Re-create all indexes in the ODS Object definition screen in transaction RSA1.
         ODS indexes must conform to the new naming convention
         BW
    Converting IGS chart settings
         Convert you existing IGS chart settings (converts IGS chart settings from BLOB to new XML storage format)
         Ensure you have the latest SAP Web AS 6.40 IGS (stand alone windows version) installed and working
    o      Test via transaction RSRT
         Execute the conversion process as directed the BI 7.0 upgrade guide.
         Note: This step is required for all BI 7.0 upgrades     Basis
    Backup your SAP BW system     Perform a full database backup (including the File system)
    Remember to adjust your backup scripts to include new components such as the J2EE engine, pre-calculation service, etc.
         Database Admin

  • How to migrate Subscriptions from once instance to other

    Hi,
    How to migrate Subscriptions from once instance to other.?
    Thanks,
    Hemanth.

    Hi,
    Its Workflow Administrator Web Applications > Administrator Workflow > Business Events
    Search for business event and create the subscription here..
    Also we can disable the subscriptions here.
    If I create a new one and disable a old one..how can I migrate this to another instance?
    Thanks,
    HC

  • How to :Migration from existing 595 into new 595 in RAC?

    Hi all,
    This is the bit complicated task for me(i.e) first let me explain our environment
    We are having 595 two instances (RAC) and 8300 is our storage due to the position we are not able to enhance the memory and CPU in this existing 595 Server.So what we are planning to make another 595 servers with some high configuration?
    Since this is new area for me dont know any idea of how to migrate these into new 595 Servers.
    fy.i storage will not get any change it will be as it is.
    I need any docs or anyone pls share their ideas and steps how they did(suppose if anyone did this already)
    Waiting For your reply.
    Thanks & Regards
    M.Murali..

    If your objective is to replace the exiting 595's with new one's then follow the steps below :-
    1. configure both the new servers (595) for RAC installation - follow the pre-install steps required for installing clusterware etc. e.g. storage, network, ssh etc..
    2. add both the new servers as a "node3" and "node4" into the existing 2-node cluster - follow the "node add" procedure in the documentation
    3. turn-off the first 2 nodes on old servers (node1 and node2)
    4. test your application with only the nodes...
    5. remove the old nodes using "node delete" procedure given in the documentation
    reference - http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/adddelunix.htm#BEICADHD
    - Siba
    http://dbathoughts.blogspot.com

  • How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

    How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
    Aditya Mediratta

    Hi Aditya,
    please find the answer in
    http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
    Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin. 
    Basically it's the same procedure as adding some PF Database in E2K3; just
    run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
    Wait until some initial data started to replicate; after that run
    Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
    After replication has finished you can do a
    .\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
    Please let me know if it worked.
    Kind regards,
    Martin

  • How to migrate the Flexmonkey's ActionScripts to run in FlexUnit?

    how to migrate the Flexmonkey's ActionScripts to run in FlexUnit?
    an example will be great. thanks!!

    You don't need to migrate anything.
    The earlier FlexMonkey code as well as the current will run in FlexUnit 4 without modification. The only issue that you may encounter is that there is a known bug (waiting for a fix from the authors) where FlexUnit .9 tests (older FlexMonkey tests) run in the newer environment don't complete 100% of the time. Hoping we will see a fix on this shortly.
    Mike

  • How to Migrate Oracle Apps Business Events

    Hi,
    How to Migrate Oracle Apps R12 Business Events from DEV environment to STAGE and STAGE to PRODUCTION environment?
    Please help me as early as possible.
    Thanks,
    Sumit

    I have opened this link and I didn't get exactly because I am new in Business Events.
    Can you please help for simple steps for migrate Business Events from DEV to STAGE or TEST environment.
    Your prompt reply will highly appreciated.
    Thanks & Regards,Complete the steps under "Step 1: Locating and Downloading Business Events" and "Uploading Annotated File Back to a Database" sections to download/upload business events.
    Thanks,
    Hussein

  • How to migrate exadata across data centers?

    How to migrate exadata across data centers? Is forklift (or lift & shift) only option for this kind of migration since we are talking about migrating appliance?
    Any best practices/experiences around such migrations?
    Thanks,
    Abhi

    Hi,
    We recently had a data center move and moved some exadata machines to a new location.
    There are a few things to consider before move happens;
    1) Get the network ready on new Data Center and make sure all connectivity (e.g. you can remote access to it) are working.  In our case the new center has same IPs network.
    2) Get the Vendor who does transporting of Hardware Machines.
    3) On the last day before move, Shutdown the Exadata Machine ( shut down database, RAC, shutdown db nodes, cell nodes, infinity band etc.. )
    4) Power off Exadata Machine
    5) Unplug all network cables.
    6) Let the Hardware cool down.
    7) Transport to new location and move the Machines to correct Bay and wait for machines to be acclimatized
    8) Plug Network cables.
    9) Power On Exadata.
    I found a Support note which also you can refer; What Needs to be Done When Moving Cluster Nodes to a New Data Center (Doc ID 1332423.1)
    HTH,
    Pradeep

Maybe you are looking for