| Oracle Agile Engineering Data Management System Customization Management Release e6.2.1.0 E77560-01 |
|
 Previous |
 Next |
| Oracle Agile Engineering Data Management System Customization Management Release e6.2.1.0 E77560-01 |
|
Previous |
Next |
Bundles are the basic "envelope" to organize and manage modifications. Bundles are used to bundle customizing modifications. A bundle might hold several application objects, for example, a mask object (EDB-ART-SLI). These objects are exported to a loader file at the time the bundle is exported. Before you can begin tracking any modifications with SCM, a bundle must exist and needs to be set "current".
A Bundle consists of a list of changed objects, which have been grouped together. Each Bundle is defined by:
Bundle Number
Bundle Description
Short Description
Creator
Creation Date
Release Date
Table 6-1 Bundle general information attributes
| Bundle definition attributes | Description |
|---|---|
|
Bundle Number |
Unique identifier |
|
Short Description |
Description of the bundle |
|
General Description (Request) |
Description that explains why the customization is needed |
|
Detailed Description (Solution) |
Description of how the customization request has been solved and resolved |
|
Creator |
The user who created the bundle |
|
Start Date |
When the bundle was created |
|
Release Date |
The release date of the bundle |
|
PI (Progress Indicator) |
The release state of the bundle. The available states are defined in the lifecycle EDB-SCM |
|
Lifecycle |
Lifecycle name |
|
Valid From, Valid Until, Current |
Lifecylce fields that define the validity period |
To open the Bundle form, perform one of the following task:
In the Manager Menu, choose Tools > SCM > Bundle.
Click the L button beside the Bundle button on the SCM Toolbar to display the bundle list. See "SCM Toolbar" on page 2-1.
Table 6-2 Bundle Form Select menu functions
| Menu function | Description |
|---|---|
|
List |
Opens the bundle list. |
|
All Modifications |
Opens list of all modifications for all bundles. |
|
Create Parent Entries |
Create parent entries (object type FAT) in the modification list for the modification records in the bundle. |
|
Check Import |
Verifies if the import completed successfully. This feature compares the ”as-is” update date and/or the number of objects for the imported objects with the ”to be” update date and number of objects documented in the export file. Be aware, the corresponding information has to be logged in export file. |
|
Check C_ID |
After importing a bundle into current environment, this function updates the C_IDs in the SCM modification with current C_IDs. This is a prerequisite to re-export the bundle from current environment and to open the object with ”Show” command in the current environment. |
|
Set Active |
Defines the selected bundle as the current active bundle, so that all SCM modifications will be booked onto this bundle. |
|
Import |
Opens the dialog to select SCM control file (.loa.bin) for import. |
|
Export |
Starts exporting the selected bundle. |
The General Information tab defines attributes for the bundle.
A modification record represents the changed records which will be exported and other meta information for the changed records.
Modifications include the following fields.
Table 6-4 Modifications tab fields
| Modification field | Description |
|---|---|
|
Position |
Unique identifier number. |
|
Type (modification type) |
For a list of modification types, refer to "SCM Modification Types" on page 6-4. |
|
Object Type |
Key for object as defined in column "Object Type" in the SCM configuration list. |
|
Object Name |
Concatenated values from key fields as defined in columns "Field 1" to "Field 9" in the SCM configuration list (max. 80 characters). |
|
Object CID |
C_ID value of changed/new record |
|
Object Version |
C_VERSION value of changed/new record |
|
Modification Description |
Text to describe modification |
|
Object Key1 to 9 |
Values of key fields of changed record or new record. In the SCM configuration list for each entry the key fields are defined in columns "Field 1" to "Field 9". In each modification record the corresponding values for these fields are stored in columns "Object Key1" to "Object Key2". |
|
Subobject |
For records of object type "FAT", this field contains the concatenated object keys for the corresponding relation record. |
|
Old Value |
Old value |
|
New Value |
New value |
Table 6-5 Modifications list Select menu functions
| Menu function | Description |
|---|---|
|
Usage |
Show the bundles that include the current object. |
|
Show |
Opens the corresponding form to show the object details. Right now this userexit is only supported for records with object type.
|
|
Set Type to "LOA" |
Converts an entry of type INF into an entry of type LOA and fills the mandatory fields accordingly. |
|
Check C_ID |
After importing a bundle into current environment, this function updates the C_IDs in the SCM modification with current C_IDs. This is a prerequisite to re-export the bundle from current environment and to open the object with ”Show” command in the current environment. |
|
Check Table |
Checks for inconsistencies between table definition in the repository and database. |
|
Check Structure |
Checks the structure of modification records. |
|
LGV duplicate Line No. |
Search for duplicate position numbers in LogiView. |
When you add a modification to a bundle number, several modification entries are inserted, depending on LGV constants or default value settings.
The different type of modifications (T_SCM_CHG_OBJ) assigned to a bundle number are
Table 6-6 SCM Modification types
| Modification Type | Object Type | Remark |
|---|---|---|
|
DEL |
As defined in the SCM configuration list e.g. MAS, MEN, MAS-FLD |
LGV constant EDB_SCM_STO_AUTO = D or CD or AD or AFD |
|
DSC |
MAS.UBM MAS.UAM MAS.USA MAS.UEA MAS.UBA MAS.LAY MAS.SIG MAS.MEN MAS.BUT |
LGV constant EDB_SCM_STO_AUTO = A (Auto) If LGV constant EDB_SCM_DSC_MAS is set to TRUE For object type "MAS" -- Store each premask userexit/parameter for compatibility check (UBM). OBJECT_KEY1: Premask Userexit OBJECT_KEY2: Userexit Parameter -- Store each postmask userexit/parameter for compatibility check (UAM). OBJECT_KEY1: Postmask Userexit OBJECT_KEY2: Userexit Parameter -- Store each select action userexit/parameter for compatibility check (USA). OBJECT_KEY1: Select Action Userexit OBJECT_KEY2: Userexit Parameter -- Store each edit action userexit/parameter for compatibility check (UEA). OBJECT_KEY1: Edit Action Userexit OBJECT_KEY2: Userexit Parameter -- Store each pre action userexit/parameter for compatibility check (UBA). OBJECT_KEY1: Pre Action Userexit OBJECT_KEY2: Userexit Parameter -- Store each post action userexit/parameter for compatibility check (UAA). OBJECT_KEY1: Posmask Userexit OBJECT_KEY2: Userexit Parameter -- Store mask layout part1 for compatibility check (LAY). OBJECT_KEY1: T_MASK.C_ROW (row) OBJECT_KEY2: T_MASK.C_COL (column) OBJECT_KEY3: T_MASK.C_LEN (length) OBJECT_KEY4: T_MASK.C_WID (width) -- Store mask layout part2 for compatibility check (SIG). OBJECT_KEY1: T_MASK.C_SIGNUM (significant number of columns) OBJECT_KEY2: T_MASK.C_MAXREC (maximum records in mask) OBJECT_KEY3: T_MASK.C_HOR_BAR (horizontal scrollbar) OBJECT_KEY4: T_MASK.C_VER_BAR (vertical scrollbar) -- Store mask menus for compatibility check (MEN). OBJECT_KEY1: Select Menu OBJECT_KEY2: Non Select Menu OBJECT_KEY3: Edit Menu -- Store mask buttons for compatibility check (BUT). OBJECT_KEY1: Select Button OBJECT_KEY2: Non Select Button OBJECT_KEY3: Edit Button |
|
DSC |
TAB.FLD |
LGV constant EDB_SCM_STO_AUTO = A (Auto) If LGV constant EDB_SCM_DSC_TAB is set to TRUE For object type "TAB" (You get object type"TAB" only when you call it from Dataclasses widget) -- Store field definition for compatibility check (TAB.FLD). For each field of the table a TAB.FLD record is created: OBJECT_KEY1: Field Name OBJECT_KEY2: Field Type (in DB format) + NOT NULL (if NN flag set) OBJECT_KEY3: Index Type + Index Name (not working correctly when more than one index defined like in T_CFG_DAT) OBJECT_KEY4: Sequence |
|
EXEC |
LGV constant EDB_SCM_IMP_EXEC_FLG = "ASK" or "EXEC" Execute EXEC commands of bundle listed in column Object Name [T_SCM_CHG_OBJ.OBJECT_NAME] (Can be called from bundle context menu: Execute EXEC) |
|
|
FAT |
The object type for the relation e.g. MAS-FLD |
If LGV constant EDB_SCM_C_FAT_FLG is set to TRUE: For refine or aggregate object relations, store parent record information to the loader file to resolve the exported relations in the target environment. OBJECT_KEY1: Key value for first key field of parent entity OBJECT_KEY2: Key value for second key field of parent entity (if defined) OBJECT_KEY3: ... |
|
INF |
LGV constant EDB_SCM_STO_AUTO = A (Auto) You can add an INFO record manually and put a text to column "Modification Description" to provide hints for users who use your SCM loader files. |
|
|
INF |
Mask name |
LGV constant EDB_SCM_STO_AUTO = A (Auto) If CTRL-A is called in list or form that is not configured in the SCM configuration list then an info record is added to the modification list: Object Name: "MASK: maskname CID: c_id of record" |
|
INS |
As defined in the SCM configuration list e.g. MAS, MEN, MAS-FLD |
LGV constant EDB_SCM_STO_AUTO = C Insert record in list where SCM postaction EP_SCM/ScmStoChgPoa(...) has been added. Entries are not exported during Export. You have to change to type LOA before. |
|
LOA |
As defined in the SCM configuration list e.g. MAS, MEN, MAS-FLD. |
LGV constant EDB_SCM_STO_AUTO = A or AF The object record with Object CID will be exported to the loader file during export. OBJECT_KEY1: Key value for first key field of the record OBJECT_KEY2: Key value for second key field of the record (if defined) OBJECT_KEY3: ... |
|
STR |
MEN |
Inserted by "Check Structure". |
|
TAB |
Inserted by "Check Structure". |
|
|
LGV-DT |
Inserted by "Check Structure". |
|
|
UPD |
As defined in the SCM configuration list e.g. MAS, MEN, MAS-FLD |
LGV constant EDB_SCM_STO_AUTO = C or CD Update record in list where SCM postaction EP_SCM/ScmStoChgPoa(...) has been added Entries are not exported during Export. You have to change to type LOA before. |
The Loader tab displays information about when the current bundle was imported and exported. The types of information recorded include:
The Documents tab lists the documents associated with the bundle form. You can search for documents and add documents on this tab.
When LGV constants EDB_SCM_C_EIC_FLG and EDB_SCM_DSC_MAS and EDB_SCM_DSC_TAB are set to TRUE in the source environment then Export/Import Check (EIC) records are created. This allows you to check in the target environment for inconsistencies after import (update date for record is stored).
To open the Bundle list, perform one of the following tasks:
Choose List in the Bundle form context menu.
Click the Bundle button on the SCM Toolbar. See "SCM Toolbar" on page 2-1.
Table 6-8 Bundle List Non-select menu functions
| Menu function | Description |
|---|---|
|
Form |
Opens the Bundle form. |
|
All Modifications |
Opens the list of all modifications for all bundles. |
|
Get Objects |
Get all modifications done by user or/and by creation / update date. |
|
Import |
Opens the dialog that allows you to select the SCM control file for import. |
Table 6-9 Bundle List Select menu functions
| Menu function | Description |
|---|---|
|
Form |
Opens the bundle form for the selected record. |
|
Modifications |
Opens the modification list for bundle. |
|
In Patches |
Opens the list with patches where bundle is assigned to. |
|
Exp/Imp Check |
When LGV constant EDB_SCM_C_EIC_FLG is set to TRUE in the source environment then EIC records are created to be able to check in the target environment for inconsistencies after import (update date for record is stored and number of refine records). |
|
In Other Bundles |
Lists other bundles which also contain the modified object. |
|
Create Parent Entries |
Create parent entries (object type FAT) in the modification list for the modification records in the bundle. |
|
Check Import |
Verifies if the import completed successfully. This feature compares the ”as-is” update date and/or the number of objects for the imported objects with the ”to be” update date and number of objects documented in the export file. Be aware, the corresponding information has to be logged in export file. |
|
Check C_ID |
After importing a bundle into current environment, this function updates the C_IDs in the SCM modification with current C_IDs. This is a pre-requisite to re-export the bundle from current environment and to open the object with ”Show” command in the current environment. |
|
Execute EXEC |
Execute EXEC commands (LogiView procedures) of bundle listed in column "Object Name" |
|
Set Active |
Defines the selected bundle as the current active bundle, so that all SCM modifications will be booked onto this bundle. |
|
Export |
Starts exporting the selected bundle. |
Modifications are listed in the Modification list of a bundle. The entries in the list can be different modification types.
There are several methods to assign an object to a bundle.
Automatically by triggers
SCM comes with triggers which automatically assign an object to the current bundle if the object has been changed. These triggers must be included as post action triggers in the corresponding (definition) forms.
Manually by the user
You can assign the current object to the current bundle by pressing Ctrl-A
Automatically by searching for changes authored by a certain user and created or modified since a specified date and time.
There are three methods to record modifications:
Select the object row and press Ctrl-A.
Post-Action Userexit (see "Identify Modifications with Post Action UserExit" on page 8-2.)
Get Objects
Determines which objects have changed and adds them to the bundle. Choose Manager > Tools > SCM > Get Objects.
Get Objects is limited to 9999 objects per table.
Bundle objects can have several states:
110 In Work -> 230 Released
230 Released -> 240 In Change
240 In Change -> 230 Released
When creating a bundle definition, it begins in the state In Work. In this state, objects can be added and data can be modified.
When a Bundle is released, the bundle definition cannot be modified. All reservations on this bundle are reset and the original owner of the objects is restored.
Also a document is created in the document management of Agile e6 which is linked to this Bundle number. (Document type and document id are customizable).
A loader file is generated automatically and this loader file is checked-in at the created document (used vault is definable).
A record is written to history folder which indicates the transition from In Work to Released.
All locks for objects assigned to the released bundle number are also released.
When changing the state to In Change, objects of the bundle definition can be modified or new objects can be added. This transition also is also documented in history.
The All Modifications view is a collection of all objects belonging to any bundle. Use this view to find a specific object and to determine in which bundle it is contained.Also, you can use this view to analyze and determine whether an object is included in different bundles, which may cause concurrency issues.
Table 6-10 History tab, Bundle Form menu functions
| Menu function | Description |
|---|---|
|
Form |
Opens the bundle form for selected record. |
|
Modifications |
Opens the modification list of the bundle for selected record. |
|
In Patches |
Opens the patch list of where the bundle of the selected record is assigned to. |
|
Exp/Imp Check |
Export/Import Check See aldo "Exp/Imp Check Tab" on page 6-7. |
|
Export |
Begins exporting the bundle of the selected record. |
