Generate Dependencies (ttpmc1240s000)

Use this session to generate the dependency relations between solutions that must be installed together at a customer system.

These dependency relations are generated:

  • Prerequisite relations.
  • Co-requisite relations to the same solutions in other base VRCs, if these solutions have one or more components in common.

    Conditions for co-requisites:

    • Base VRCs must belong to the same base VRC combination.
    • Solution numbers must be identical.

These dependency relations cannot be generated, but must be specified manually:

  • Co-requisite relations to solutions in the same base VRC
  • Post-requisite relations

To start this session, you can click Generate Dependencies on the appropriate menu of the Dependencies (ttpmc1140m000) session, which in turn you must start from the appropriate menu of the Solutions (ttpmc1100m000) session.

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.

Solution Code

A unique identification of the solution in a base VRC.

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.
Delete also manually entered

If this check box is selected, the dependencies you might have specified manually are deleted when you regenerate the dependencies.

Regenerate dependencies

If this check box is selected, all existing dependency relations are deleted, and the relations are regenerated.

Note: Manually specified relations are not deleted, unless you select the Delete also manually entered check box.
Related topics