Enable incremental changes

An incremental change collects together a number of structure changes to a component such as addition or removal of components or changes to attachments (data). Effectivity can be applied to incremental changes to configure the associated changes. This method of change control allows several independent structure changes to be made concurrently, including the addition or removal of unrelated components. Those changes can be implemented in any sequence. This method of change control is suitable for large, flat structures without nested subassemblies or components. Before enabling incremental changes, you must Create the necessary change types by using BMIDE When creating incremental change, Teamcenter does not distinguish between change types for change management and incremental change. It is therefore advisable to name the change types clearly. Provide users with access Your can use an In IC Context rule to allow Structure Manager or another structure editor application to control access to operations tracked by incremental change. This rule is unlike other rules because it does not depend on the properties of the object. Define releases statuses Your can set the Incremental_Change_ReleaseStatus preference to define the release status. Defining a release status in this way allows you to specify effectivity as soon as the incremental change is created. If you do not set this preference, you release the incremental change after it is created. The choice of which of these approaches to implement depends on your business practices. For example, you might set this preference to Pending IC. The status defined in the preference must already exist. You must also create an access rule that allows write access to objects with this status or you cannot create changes in the incremental change.

Note The status is applied only to incremental change if the effectivity is supplied when it is created. Create revision rules When you apply a revision rule in Structure Manager, it configures both the structure item revisions and the incremental change revisions. This consideration is important if you use incremental change in combination with traditional revision configuration of structure item revisions. If you want to configure the structure item revisions and incremental change revisions independently, you must apply a separate status. The revision rule you create depends on whether the incremental changes are configured by unit or date effectivity, or simply by release date. It also depends on the release status to apply. For example, you can apply the Pre-Released status to the item revisions and the IC in Process status to the incremental change revisions. Allow users to copy or cut structure lines with incremental changes By default, if you cut or copy a line and then paste it to a new location, incremental change elements (ICEs) are not copied. This may necessitate significant manual recreation of data if you are cutting or copying many lines together. To automatically copy ICEs, the administrator must set two Business Modeler IDE constants: Fnd0EnableIceCarryOver Defines item types of the source and destination parent BOM line under which ICEs should be copied while copying, cutting, and pasting. For example, by default, the constant value for Process is set to true, and if the source and destination parent BOM line are both Process, Teamcenter copies any ICEs. Fnd0AttrIcesToExclude Defines the occurrence attributes which Teamcenter does not copy to the target location for occurrence attribute changes. These settings apply to in-context changes to structure lines, their attachments, and their occurrence attributes.

Note For structure changes, only remove changes associated with the original line are carried forward to the new location. Teamcenter does not consider add structure changes; otherwise, two occurrences appear at the same time at two different locations. Teamcenter copies attribute changes made in the immediate parent context, but higher level contexts are excluded. The new ICEs created are associated to the original IC revision. Allow users to baseline structures with active incremental changes By default, this enhancement is not configured and you must set the following preferences to use it: IC_baseline_carry_forward_active_changes Set to True to carry over active incremental changes when creating a baseline. IC_baseline_carry_forward_status Defines a list of status names to consider when carrying forward active incremental changes. The default value is pending. Set preferences to enable incremental changes You can enable incremental changes by setting the following preferences: Preference Value Incremental_Change_Management Set to true to enable incremental changes. Enables incremental change functionality and displays the relevant menu commands. By default, this functionality is disabled. Enabling incremental change using the site preference activates this functionality in all applications where it is available. EnableIntents Set to off by default as configuration with intents adds a performance overhead if your site does not use intents. If you set this preference to on, the intent tabs appear in the appropriate dialog boxes. ShowUnconfiguredByChangeEffectivity By default, the unconfigured changes are visible to the user. To view all incremental changes (configured and unconfigured), set this preference to false. Incremental_Change_ReleaseStatus Defines a release status that is attached to an incremental change when the user first creates it, for example, Pending. The status must already exist and have an access rule that allows write access to objects with this status. MoveICCreationToMenu Determines if the Create IC Object button on the incremental change toolbar or the Incremental Change>Create Context menu command is visible. If this preference is True, the menu command is visible unless suppressed with Command Suppression; if it is False, the button is visible. IC_baseline_carry_forward_active_changes Set to True to carry over active incremental changes when creating a baseline. IC_baseline_carry_forward_status Defines a list of status names to consider when carrying forward active incremental changes. The default value is pending.