Transporting Key-User In-App Extensions

To move key user in-app extensions through your landscape, you must export them from the customizing tenant of the development system using the Export Software Collection app. Subsequently, use the Import Collection app to deploy them into the test and production systems.

In the Export Software Collection app, you create a collection and add the specific extension items you wish to release. It is essential to include items with dependencies in the same collection to ensure they function correctly after the transport.

For instance, if you create a custom business object and a corresponding custom catalog extension, you should export and import them together.

Before exporting, use the Check function to identify potential errors or missing dependencies. If the system detects related items not yet in the collection, select Add Missing Items to include them automatically.

When ready, select Export for a standard release. If you need to deliver urgent fixes for extensions that were previously transported, use the Hotfix option instead.

For detailed guidance, refer to the documentation on exporting software collections in the SAP Help Portal.

The Import Collection app serves as the central tool for importing various extension types. This includes key user in-app extensions, business content changes from SAP Central Business Configuration, and developer extensions created in the development tenant.

The standard workflow requires importing extensions into the test system first for quality assurance. Once testing is successful, you can forward the collection to the production system directly from the app. To make these changes available to end-users, you must perform a final import within the production system.

The app displays several import types to indicate how a collection was processed:

• Manual: The import was started manually by a user.
• Manual (forecast): The system indicates that manual intervention is likely required, often due to potential conflicts or previous failures.
• Automatic: The import occurred automatically, such as when business content is synchronized between SAP Central Business Configuration and the development system.
• Automatic (scheduled): The import was executed based on a predefined automation schedule.
• Not relevant: The collection is no longer eligible for import, typically because it is Outdated or Discarded (for example, if it was not imported before a major software upgrade).

To manage this risk, check the Business Interruption column in the app. If the risk is high, schedule the import during off-peak hours when user activity is minimal.

For more information, see the documentation on importing software collections in the SAP Help Portal.