Packages by Patch Header (ttpmc1107m000)
Use this session to maintain packages by patch header.
You can start this session from the session.
Field Information
- Base VRC
-
base VRC
- Patch Code
-
A unique identification for the solution in a base VRC.
- Package
-
The package code.
- Derived From Base VRC
-
Using this field, you can define relationships between the base VRC of a derived product and the related parent product. You use this relationship if you create and derive update VRCs at a recipient during installation of a Feature Pack. You must always define the relationship to the base VRC of the Feature Pack on which the Feature Pack of the derived product is built.
Example:
The following products are available:
- Standard product PARENT with package p1, p2, and p3
- Derived product LOC1, which is derived from PARENT. Packages p1 and p2 are changed. Note that package p3 is not changed for LOC1. A new package, p4, was introduced for LOC1.
- Derived product LOC2, which is derived from LOC1. Packages p1, p2, p3, and p4 are changed. Note that package p3 is changed for LOC2.
Two Feature Packs are available. In this scenario, you must populate the Derived From Base VRC as follows:
Product Feature Pack Package Base VRC Derived From Base VRC PARENT 1 p1 B61_a1 PARENT 1 p2 B61_a1 PARENT 1 p3 B61_a1 PARENT 2 p1 B61_a2 PARENT 2 p2 B61_a2 PARENT 2 p3 B61_a2 LOC1 1 p1 B61L_a1_loc1 B61_a1 LOC1 1 p2 B61L_a1_loc1 B61_a1 LOC1 1 p4 B61L_a1_loc1 LOC1 2 p1 B61L_a2_loc1 B61_a2 LOC1 2 p2 B61L_a2_loc1 B61_a2 LOC1 2 p4 B61L_a2_loc1 LOC2 1 p1 B61L_a1_loc2 B61L_a1_loc1 LOC2 1 p2 B61L_a1_loc2 B61L_a1_loc1 LOC2 1 p3 B61L_a1_loc2 B61_a1 LOC2 1 p4 B61L_a1_loc2 B61L_a1_loc1 LOC2 2 p1 B61L_a2_loc2 B61L_a2_loc1 LOC2 2 p2 B61L_a2_loc2 B61L_a2_loc1 LOC2 2 p3 B61L_a2_loc2 B61_a2 LOC2 2 p4 B61L_a2_loc2 B61L_a2_loc1