IBM Support

HD57951: PDG: BOOLEAN / PAD DOESNT MOVE UNDER ADD FEATURE BY ADD BOOLEAN OPERATION.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as suggestion for future release.

Error description

  • PDG: BOOLEAN / PAD DOESNT MOVE UNDER ADD
    FEATURE BY ADD BOOLEAN OPERATION.
    .
    SCENARIO:
    1. File / Open IMAI032.CATPart
    2. Click MB3 on Pad_71 / Pad_71 object / Add. Add
    dialog box is displayed.
    3. Click OK. Warning is pop-up as follow: You are
    trying to create a Boolean operation which breaks
    relation order between geometrical elements.
    Operand body will not be moved under the Boolean
    feature. Do you want to continue?
    4. Click Yes. Then Pad_71 does not move under
    Add.1 feature. This is the problem.
    5. Delete the created Add.1.
    6. Delete Pocket.26.
    7. Repeat step 2 & 3. Then Pad_71 moves under
    Add.2 feature without the warning.
    .
    .
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • THIS APAR IS CONSIDERED AS A SUGGESTION
    FOR IMPROVEMENT WHICH CANNOT BE
    INCORPORATED IN VERSION 5R18
    PLEASE CONTACT YOUR SUPPORT DEPARTMENT IN
    ORDER TO OPEN A REQUIREMENT FORM.
    .
    Incident Diagnosis:
    During the creation of a boolean feature, current
    algorithm check for relation order of selected
    bodies wrt operated body (base operand).The
    provided CATPart  does not obey relation order.
    Hence, during the creation of new boolean feature,
    the error message is displayed (because it detects
    the existing linearity error in the model.)
    .
    Development Justification
    To handle situations where relation order is not
    broken because of newly created boolean, the
    check has to be put between the two operands
    before the creation of Boolean. The changes
    required will be really complex one. Also it will be
    very impacting to current algorithm. Such
    complexity and impact not feasible to manage
    through APAR channel. Such activities feasible to
    manage through development channel .Hence this
    scenario considered as suggestion for development
    in future.
    .
    .
    

APAR Information

  • APAR number

    HD57951

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    516

  • Status

    CLOSED SUG

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-10-11

  • Closed date

    2006-10-27

  • Last modified date

    2006-10-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"516","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 October 2006