: Big things that happened at Game Developer Conference!
Introduction
In Public Cloud, the customization transport process differs from Private Cloud (STMS). The request is now called Collection. When transporting objects in In-App mode, each modification generates a new version within the Software Collection. You can add only the modified items, include comments, and use filters to streamline the search process. After importing the collection into the Test environment, performing the Forward action is necessary to make it available for import into PRD.
Step 1
Access the Export Software Collection app.
Create a Software Collection (if one does not already exist for the relevant topic or module/organization in the environment).
Name your Software Collection and click Create.
Once the Software Collection is created, note that it is versioned. This means that with every object modification and transport, a new version is automatically created for transport.
In Add Items, you can select the objects to be included in this Collection for transport.
Support Filters are available to assist with object searches within the environment.
After adding the desired objects, click Check to verify if there are any blockers, dependencies, or inconsistencies for transport.
Check Option
Note: It is possible to transport only the modified items or all items again. The first option is always recommended.
A log is generated at the end, displaying the transport status.
Export Option – This is where the release (Export) to the Test environment actually takes place.
A comment can be added for each versioned transport.
A log is generated at the end, displaying the transport status.
Step 2
After exporting, log in to the Test environment and access the Import Collection app.
Use the available filters to search for the desired collection. Upon reaching the Test environment, the versioned collection will have the status “Ready for Import.”
Select the desired versioned collection and choose Check and Import.
Add a transport comment.
Click Manual Import.
The import process starts, and the collection status changes to “Importing” during processing.
Once the import is complete, a confirmation message is displayed:
Step 3
The collection has only been imported into the Test environment but is not yet available for import into the Production environment.
To make it available for import into PRD, it is necessary to perform the Forward action.
Select the collection and click Forward.
The collection is forwarded to the Production environment transport path.
To finalize, log in to the Production environment and access the Import Collection app.
Select the desired collection and import it.
The collection has been successfully imported into the PRD environment.
IntroductionIn Public Cloud, the customization transport process differs from Private Cloud (STMS). The request is now called Collection. When transporting objects in In-App mode, each modification generates a new version within the Software Collection. You can add only the modified items, include comments, and use filters to streamline the search process. After importing the collection into the Test environment, performing the Forward action is necessary to make it available for import into PRD.Step 1Access the Export Software Collection app.Create a Software Collection (if one does not already exist for the relevant topic or module/organization in the environment).Name your Software Collection and click Create.Once the Software Collection is created, note that it is versioned. This means that with every object modification and transport, a new version is automatically created for transport.In Add Items, you can select the objects to be included in this Collection for transport.Support Filters are available to assist with object searches within the environment.After adding the desired objects, click Check to verify if there are any blockers, dependencies, or inconsistencies for transport.Check OptionNote: It is possible to transport only the modified items or all items again. The first option is always recommended.A log is generated at the end, displaying the transport status.Export Option – This is where the release (Export) to the Test environment actually takes place. A comment can be added for each versioned transport.A log is generated at the end, displaying the transport status. Step 2After exporting, log in to the Test environment and access the Import Collection app.Use the available filters to search for the desired collection. Upon reaching the Test environment, the versioned collection will have the status “Ready for Import.”Select the desired versioned collection and choose Check and Import.Add a transport comment.Click Manual Import.The import process starts, and the collection status changes to “Importing” during processing. Once the import is complete, a confirmation message is displayed:Step 3The collection has only been imported into the Test environment but is not yet available for import into the Production environment.To make it available for import into PRD, it is necessary to perform the Forward action. Select the collection and click Forward. The collection is forwarded to the Production environment transport path. To finalize, log in to the Production environment and access the Import Collection app. Select the desired collection and import it. The collection has been successfully imported into the PRD environment. Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
