Previous Topic: Report on Subset Contents or UsageNext Topic: Generating the Expansion Conflict Report


Report Protection Downgrades to Expect at Checkout

The Expansion Conflict Report identifies potential conflicts for subset checkouts. After defining a subset, you can run the report before or after checking out the subset to identify:

As a rule, run the report only if a checkout does not produce all the required objects. Running the report before checkout actually expands your subset definition: If you check out the subset after running the report, you pay for expansion twice.

11/04/01 EXPANSION CONFLICT REPORT PAGE 1 10:34 MODEL NAME: TRUST AND STOCKHOLDER MANAGEMENT SUBSET NAME: EMPLOYEE TRUST SUBSET USING OBJECT OBJECT REQUESTED DOWNGRADED TYPE OBJECT NAME PROT PROT SUBSET NAME PROT/IND USER ----- ----------- ---------- ---------- ----------- -------- ------ ATTRUSR SS_TAX_ID DELETE UPDATE STOCKHOLDER ACCESS DAACMLH ATTRUSR SYMBOL DELETE ACCESS STOCKHOLDER UPDATE DAACMLH HLENT BROKERAGE DELETE READ STOCKHOLDER DELETE DAACMLH HLENT CUSTOMER DELETE UPDATE INCOMPLETE DACCRMN HLENT DIVISION MODIFY ACCESS STOCKHOLDER MODIFY

Note: In this report:

This report itemizes all downgraded objects, not only downgraded scoping objects. For example, it includes downgraded expansion objects:

The Expansion Conflict Report shows only the first IDs that conflict with your subset. Behind these objects may be other conflicting objects. Overriding the checkout status of the objects that are shown in the report solve the problem. However, an override may not resolve conflicts behind those shown.

If a Requested Protection of Delete results in INCOMPLETE appearing in the PROT/IND column under the Subset Using Object heading on this report, it means that you did not include all usages of that item. Delete protection cannot be granted unless you have all usages of that object in the subset. To find everything you include in the subset to get delete protection, use the Object Cross-Reference Delete report.