This topic is relevant only if you are using CMS.
On the Development, Consolidation, Assembly, Test, Approval, and Production tab pages, you can use the Details function to display detail information and logs for the individual transport steps of a software component. This information is displayed in the Details and Logs dialog box. The System State tab page shows only the Details tab page, since you do not perform any transport steps here.
You can also use the Details function in the History display and in the system status display.
In the Transport Studio, select an entry in the list and choose Details. The Details and Logs dialog box appears.
You can use the following functions to navigate to any of the list entries in the dialog box:
● First: Takes you to the first entry in the import queue.
● Previous: Takes you to the previous entry in the import queue.
● Next: Takes you to the next entry in the import queue.
● Last: Takes you to the last entry in the import queue.
You can also go to an entry in the list directly by entering its number.
In this part of the dialog box, you see the selected entry in the list.
You can find the following information on this tab page.
Property |
Description |
Component |
Name of the software component |
Version |
Version of the software component; consists of <domain>_<track name>_<system ID>.<version number> |
Component Type |
Description of the transported content Software Component Version contains a complete software component in a specific variant. Software Component Change Request contains a specific part of a developed software component. Subset contains a quantity of XI change requests that have been created during a subset assembly |
State |
Import status/assembly status/approval status |
Source Version |
Source version from a source track |
User |
CMS user who performed the action |
Processed at (GMT) |
Time at which the action was performed in the CMS |
Process Result |
Technical information (contains a pointer to the logs) |
Details Specific to the Software Component Version |
|
Release |
Release name |
Support Package Number |
Number chosen during assembly for the Support Package of the software component version |
Patch Name |
Description entered during assembly for the software component version |
Patch Level |
Number chosen (in assembly) for the number of patches within in a Support Package |
Predecessor |
Direct predecessor version in the same system of a track |
Owner |
User who created the software component version |
Import Check State |
State of the test import (see Test Imports) |
Import Check Timestamp |
Timestamp on which the test import was performed |
Import Check User |
User who performed the test import |
Import Check Process Result |
Technical information containing a pointer to the logs in the file system. The logs are in the log folder under the defined transport directory, such as usr/sap/Jtrans/CMS/log/<Track ID>_<System>@<Domain ID> |
Details Specific to the Change Request |
|
Change Request Caption |
Short text of the change request that you created in an activity |
Export Timestamp |
Time at which the change request was released in SAP NetWeaver Developer Studio |
Owner |
User who created the change request in SAP NetWeaver Developer Studio |
This tab page provide links that you can use to call the logs for the individual transport steps.
If you select various logs one after the other, they all open in the same browser window.
If a software component has the status Import running or Assembly running, you can monitor the progress of the import steps on the Logs tab page. If you follow the link to a log, you can follow the current import step, as the logs are refreshed automatically.
You can activate or deactivate automatic refreshing of logs by setting Autorefresh Off/On accordingly.
The Refresh function enables you to update the logs and to see which import steps have already been created.
The following import steps exist:
● Repository-import: Log of the integration of the imported resources into the configured repository.
● CBS-make: Build log of the central build
● SDM-deploy: Deployment log for the deployment to the assigned runtime system
The following logs exist for the assembly step:
● Check-assembly: Checks whether the prerequisites for a successful assembly exist. The following individual checks are performed:
○ Are there open build requests in the buildspace?
○ Are there open conflicts in the workspace?
○ Are there any broken DCs in the build compartment?
○ Are there any “dirty DCs” in the build compartment?
○ Are there any problem DCs in the build compartment?
○ Are there any pending activities that are not yet completely activated?
● Repository export: Exports the source code files from the repository.
● CBS assembly: Extracts the build and deploy archives from the CBS buildspace.
● Export: Bundles the previous assembly results in the software component archive (SCA) and persisting in the file system.
The Content tab page gives you information about the content of the selected entry in the list, such as a the activities of a software component change request.
The Content tab page is displayed on different queues, depending on the type of queue entry selected:
● For queue entry types Software Component Change Request and Software Component Version, it is displayed on all queues.
● For queue entry type Subset, it is only displayed on the Assembly queue.