Where Condition Header Definition - Intergraph Smart Materials - Version 10.2 - Administration & Configuration - Hexagon

Intergraph Smart Materials Classic Administration (10.2)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
10.2

You can define the header data for the where condition in the first (Where Conditions) block on the A.60.06 screen.

Header data includes a unique name in the Name field, the type of the where condition selected in the Kind of field, optionally language dependent description in the Short Desc and Description fields, and, most important, a module reference in the Module field. The module reference indicates which Smart Materials module can use the where condition.

For example, if you are setting up a where condition for a disposition rule, you need to select R1023 from the LOV as reference. Later on, in other modules (like R.10.23 Disposition Rule Details), you will be able to select only where conditions with a proper reference to the corresponding module (like R1023). The relations between the module that uses the where conditions on A.60.06 and the column for which the view will be generated are defined on the A.60.05 Where Condition Modules screen.

Below you see a list of available modules and the column to be mapped, as defined on the A.60.05 Where Condition Modules screen.

Module

Mapped to Column

Label

A2051

IDENT

A.20.51 UOM Configuration

A6008

INTERNAL

A.60.08 Define Formulas

A6009

INTERNAL

A.60.09 Formula Assignments

AS1004

IDENT

AS.10.04 Catalogs

B1001

LP_ID

B.10.01 Verifications

B1005

IDENT

B.10.05 BOM Rules

B200123

LP_ID

B.20.01.23 Reconcile BOM-Assemblies

B200126

LP_ID

B.20.01.26 Define Search/Repl Condition

B200135

LP_ID

B.20.01.35 Verification and Status

B200141

LP_ID

B.20.01.41 Start Job

B200144

LN_ID

B.20.01.44 Download

B2003

LP_ID

B.20.03 Adv. Maintain BOM

B4012_1

IDENT

B.40.12 BOM Work Packages (Where Condition for Ident)

B4012_2

LP_ID

B.40.12 BOM Work Packages (Where Condition for List Position)

B4021

IDENT

B.40.21 BOM Compare Structures

C1005_1

IDENT

C.10.05 Work Packages (Where Condition for Ident)

C1005_2

LP_ID

C.10.05 Work Packages (Where Condition for List Position)

C1005_3

LP_ID

C.10.05 Work Packages (Where Condition for mandatory LP)

C1005_4

LP_ID

C.10.05 Work Packages (Where Condition for CIP(List Pos))

C1005_5

IDENT

C.10.05 Work Packages (Where Condition for CIP(Ident))

E1011

IDENT

E.10.11 Estimate Calculation

E1012

IDENT

E.10.12 Update Estimations

ISK1002

IDENT

I-Sketch 10.02 SKEY Mappings

P1042

IDENT

P.10.42 Material Groups

P1091

LP_ID

P.10.91 Fabrication Types

P7072

IDENT

P.70.72 Expediting Details

R1023

IDENT

R.10.23 Disposition Rule Details

R1024

RLI_ID

R.10.24 Document Types

R1041

IDENT

R.10.41 Nodes and Templates

R1042

LP_ID

R.10.42 Req Split Criteria

R1051

IDENT

R.10.51 MTO Types Where Condition to exclude Idents

S8014

IDENT

S.80.14 OII - Export Jobs

SAP2001

IDENT

SAP.20.01 Transfer Jobs

For Attribute based where conditions, the required MAPPED_TO record(s) will automatically be filled in the second (Attributes for Where Conditions) block of A.60.06 when saving the new where condition, depending on the selected module.

The user who creates the where condition will be stored in the User field.

Only users who own the privilege CHANGE QUERY CONDITION are allowed to change where conditions from other users. Without this privilege, the user can only change his own where conditions.

The Regenerate check box indicates if it’s allowed to regenerate the build for this where condition. If the check box is not selected, the button is disabled for this where condition.

The Status field shows the status of the corresponding view. The view can be valid, invalid, not present, or outdated. Not present means the view was not yet generated. Outdated means that at least one of the attribute definitions assigned to the where conditions has been modified after the view was generated using the button. In that case, the view must be regenerated using the button.

The Comment field can be used to add a comment up to 2000 characters.