You find many items are inactive in the in-development PDI solution after AWS migration/tenant move.
- SAP Cloud Application Studio SDK
- SAP Cloud for Customer
For the solutions with "in development" status, only BC and custom BO would be activated. Others will be inactive. After migration, you need to manually activate the in-development solution. This is the standard system behavior.
- Before AWS migration/tenant move
If you would like to avoid the manual activation for the in-development solution, please kindly check if this solution could be assembled. If so, please kindly assemble the solution. Because for deployed or assembled solutions, tenant lifecycle management process takes care of activating all the contents as the solutions will be in a consistent state and read-only. Please note that once this solution is assembled, it will be in the maintenance mode.
- After AWS migration/tenant move (AWS migration/tenant move has been done for your tenant)
If your in-development solution has inactive items after AWS migration, please kindly manually activate them in the order they were developed. For example, you need to activate the reuse library first and then activate the absl where this reuse library is used.
AWS;Migration;Tenant Move;PDI;In development; , KBA , AP-RC-BDS-LM , ByDesign Studio Lifecycle Management , How To