Skip to Content

To start working on a scalable solution in SAP Business ByDesign studio Feature Pack 4.0 which was developed on a release lower then FP40, a solution move is required because Partner Development Tenants are not upgraded to higher SAP Business ByDesign releases. With the Solution Move the scalable solution resources are relocated to the Partner Development Tenant of the higher release and the solution is marked as obsolete in the lower release.

With the availability of FP40, Solution Partners can order for FP40 Partner Development Tenants (see How can I request new development and test tenants?) now.

The Solution Move needs to be requested by the partner for each solution by creating an ByD Service Request with the content following the request template (see Solution Move FP3.5 to FP4.0).

To request a solution move, all of the following conditions must be met:

  1. The partner has requested the partner development tenant of the higher release (FP4.0), and SAP has handed the tenant over to the partner.
  2. The partner solution has passed the SAP quality review at least once.
  3. All patches have been deployed to a quality review system and no patches are open.
  4. The partner solution has been migrated to the new SAP Business ByDesign scripting language compiler version.

After a solution has been moved, it is obsolete in the lower release. This means it can no longer be installed on customer systems with a lower SAP Business ByDesign release.

The Solution Move is only valid for Scalable Solutions. Customer-Specifc Solutions do not require a solution move as they are upgraded during the customer system upgrade.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Andreas Eissmann

    Hi Ralf,

    thank you for sharing the details about the process here. What I don’t understand is how a customer solution doesn’t need a solution move? How will SAP garantuee that if the solution is more complex? An example could be the use of a deprecated object that will be no longer avaiable in next release…this change also requires a solution move of the customer solution, no?

    Thanks.

    Andreas

    (0) 
    1. Ralf Baumann Post author

      Hi Andreas,

      thanks for your comment. Its a very valid point, that partners need to react to deprecated objects. A Health Check report in backend checks for required actions by partners in customer tenants and would inform the KeyUser of the system, if changes to the solution are required.

      Regards,

      Ralf

      (0) 

Leave a Reply