| | Solutions (ttpmc1100m000)Use this session to maintain solutions. For a single solution see Solution (ttpmc1600m000). The scope of this session covers the life cycle of a solution
from the solution's creation to the solution's release. In this session, you
can maintain the basic data of a solution. You can use this session to change the status of a solution
manually under certain conditions. Hinweis Check out and check in is not restricted to the Current
Package VRC. You can check out or check in all components for which you are
authorized. For check out you need the following
authorizations: - VRC authorization
- Module authorization
- Language authorization
- Authorization for components of which you are not the
developer. These authorizations are specified in the Developer Authorizations
Template.
For check in the same authorizations are required. You can
only check in components that were checked out by yourself. The check out and check in functionality displays a message
with the number of components for which you are not authorized. For solutions that are linked to a translation run
(ttpmc4510m000), which is part of the composite Translations (ttpmc4610m000) session, these restrictions apply: - These solutions cannot be deleted.
- These solutions cannot be set to “released”.
These solutions are displayed in the Solutions by Translation Run (ttpmc4512m000) session. To start this session, click
the default button on a record in the Translation Runs (ttpmc4510m000) session. Hinweis Translation-related sessions, fields, statuses, and commands
are only available on our internal translation server. To log on to a translation server, specify this command in
the LN environment
connection settings: -set TRANSLATION_SERVER=1 Alternatively, add this line in $BSE\lib\bse_vars: TRANSLATION_SERVER=1
Base VRC A means in PMC to identify products in a unique way. Updates at
the distributor side are provided with the base VRC identifier. A base VRC can
contain the code of the physical VRC in which the related master product is
installed, for example, B61_a, but can also be a code not related to a physical
VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked
to a base VRC identifier. The installation process checks if the base VRC
identifier of the update matches with the base VRC identifier of the update
VRC. If not, you cannot install the update in that update VRC. Export VRC The physical VRC from which components that belong to a PMC
solution must be exported at the PMC distributor side. Each base VRC has an export VRC linked, so components for
different products are exported from different physical VRCs. Base VRC Combination A Base VRC combination is defined at the PMC distributor
side and consists of a set of related base VRCs. A base VRC combination
controls the creation of co-requisites between base VRCs. You can only define
co-requisites between base VRCs that are part of the same base VRC combination.
Base VRC combinations prevent the unwanted creation of co-requisites between
base VRCs. Solution Code A unique identification of the solution in a base VRC. The solution code has the following
characteristics: - Datatype: alpha-numerical string.
- Maximum length: 14 characters.
- Forbidden characters: All characters that have a special
meaning in UNIX, such as $, *, and so on. If you specify a forbidden character,
the code will not be accepted.
Status The following statuses describe the progress of the maintenance
of solutions, Collections, and patches. To keep the descriptions readable, only
solutions are described. However, in each case, collections and patches are
intended as well, unless explicitly excepted. The status of the solution is only used at the distributor
side. A history of status changes is recorded in the Maintenance History table. To distinguish maintained solutions at the distributor side
from imported solutions at the recipient side, the status is cleared when the
solution is imported. This also applies to patches, but not to collections. The
reason is that a collection is not known as such at the recipient side. Only
the solutions contained in the collection are known at the recipient
side. In progress The initial status of the solution upon creation. Dependencies defined The dependencies between the various solutions are defined,
and the solution is ready to be exported. You must select this status manually,
because you might want to create dependencies that cannot be created
automatically. Exported The solution is exported. The system handles this status. You
cannot set the status manually. However, you can set a solution with the status
Exported back to In Progress, Solved, Completed, or Dependencies Defined. If
you change anything in an exported solution, the status is always set back to
Dependencies Defined, and you must export the solution again. Before you can
release a solution, the status must be Exported. Released The solution is released, which means that the solution is
frozen. You can no longer change anything in the solution. To release a
solution, you must change the status from Exported to Released, and you must
save the solution with this status.
Patch If the solution is also part of a patch,
the patch code appears in this field. Text If this check box is selected, a text appears with
additional information. Click Text to add, read, or change the
text. Patch The code of the patch to which a solution can be linked. | |