Record Layout - Intergraph Smart Materials - Version 10.2 - Help - Hexagon

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

All import data is initially loaded into the OMI interface table, either through SQL*Loader, by using a customized version of the m_pck_omi_custom.omi_load API package procedure, or indirectly by using the PDS report data source option.

If you intend to use the OMI API, it is up to you to ensure that your data conforms to the interpretation of each of these fields. If you use SQL*Loader, the fields in each record of the import file are transferred into physical columns of this interface table by applying the mapping rules from the SQL*Loader control file.

SHARED Tip For more information on this PL/SQL API, refer to Open API.

The following table illustrates the mapping; it also introduces the logical column names that are used in the next section, explaining the detailed record layouts for each OMI record type.

Position of physical field in the import file

Physical column name in the interface table

Logical name
(used on the B.40.01 screen)

Interpretation

1

KIND

Record Type

Static

2

ONE

F-1

Variable

3

TWO

F-2

Variable

4

THREE

F-3

Variable

5

FOUR

F-4

Variable

6

FIVE

F-5

Variable

7

SIX

F-6

Variable

8

SEVEN

F-7

Variable

9

EIGHT

F-8

Variable

10

NINE

F-9

Variable

11

TEN

F-10

Variable

12

ELEVEN

F-11

Variable

13

TWELVE

F-12

Variable

14

OBJECT

Object Code

Static

15

REV

Rev

Static (data item is obsolete)

16

UNIT

Unit Code

Static

17

OPTION_CODE

Option Code

Static

18

ITEM

Item Type

Static

19

IN_3

Input 3

Static

20

IN_4

Input 4

Static

21

IN_5

Input 5

Static

22

THIRTEEN

F-13

Static

23

FOURTEEN

F-14

Static

24

FIFTEEN

F-15

Static

25

SIXTEEN

F-16

Static

26

SEVENTEEN

F-17

Static

Table 1: Mapping import fields

While some fields always have the same meaning for the OMI main program (mainly the fields needed for the POS record type), other fields are interpreted differently, depending on the value in the ‘Record Type’ column. The field indicating the logical record type must always be the first physical field in the import file; the remaining fields must follow in the sequence shown above.

Intermediate fields that are not needed by a specific record type must be left empty, such that the field separator character is still present.

For detailed record layout requirements and the corresponding field interpretations, please refer to the following tables. The value in the O/M column indicates whether the data item is optional (O) or mandatory (M).

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

NODE_BEGIN

Character

N/A

M

Record type keyword as a constant

F-1

Node Type

Character

10

M

List Structure Code (B.10.03)

F-2

Node Name

Character

10

M

F-3

Issue Status

Character

10

O

Defaults to job parameter, if not present.

Table 2: Record layout for NODE_BEGIN

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

NODE

Character

N/A

M

Record type keyword as a constant

F-1

Node Type

Character

10

M

List Structure Code (B.10.03)

F-2

Node Name

Character

10

M

F-3

Issue Status

Character

10

O

Defaults to job parameter, if not present.

Table 3: Record layout for NODE

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

NODE_NLS

Character

N/A

M

Record type keyword as a constant

F-1

Language

Character

60

M

Language Description (A.10.01)

F-2

Short Desc

Character

20

M

F-3

Description

Character

60

M

Table 4: Record layout for NODE_NLS

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

NODE_A

Character

N/A

M

Record type keyword as a constant

F-1

Attribute Code

Character

30

M

Attribute Code (A.50.01)

F-2

Attribute Value

Character

255

O

Unit Code

Unit Code

Character

10

O

If unit in A.50.01 differs: unit conversion

Table 5: Record layout for NODE_A

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

DISC

Character

N/A

M

Record type keyword as a constant

F-1

Discipline Code

Character

10

M

Discipline Code (A.10.09)

Table 6: Record layout for DISC

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

NODE_MODIFIER

Character

N/A

M

Record type keyword as a constant

F-1

Node Type

Character

10

M

List Structure Code (B.10.03)

F-2

Node Name

Character

10

M

May contain SQL wildcards

F-3

Attribute Code

Character

30

M

Attribute Code (A.50.01)

F-4

Attribute Value

Character

255

O

Unit Code

Unit Code

Character

10

O

If unit in A.50.01 differs: unit conversion

Table 7: Record layout for NODE_MODIFIER

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

POS

Character

N/A

M

Record type keyword as a constant

F-1

Spec Code

Character

16

O

S.50.03

F-2

Short Code

Character

10

O

F-3

Size 1

Character

7

O

F-4

Size 2

Character

7

O

F-5

Commodity Code

Character

60

O

S.30.01

F-6

Ident Code

Character

13

O

S.80.*

F-7

Quantity

Number

(15,3)

M

F-8

Pos

Character

10

O (M)

BOM position number.
Processing method depends on project default ZI_OMI_POS.

F-9

Tag Number

Character

60

O

Processing depends on item type

F-10

CCL Short

Character

2000

O

For creation of tagged items only

F-11

CCL Long

Character

2000

O

For creation of tagged items only

F-12

Assembly Level

Number

2

M

Must be 1 for main positions; must have the appropriate value for BOM assembly structures.
See Processing Logic.

Object

Object Code

Character

100

O

See Object Codes and Recognize Mode.

Rev

Rev

Number

2

O

Obsolete; only included for backwards compatibility of file format. Always enter 0.

Unit Code

Unit Code

Character

10

M

If position has an ident (either direct or indirect), and the unit associated with this ident differs: unit conversion.

Option Code

Option Code

Character

10

O

Defaults to Option 1, if not specified

Item

Item Type

Character

10

O

A.10.15; if not specified, default item type with item rule SOT will be assigned.

Input 3

Size 3

Character

10

O

Input 4

Size 4

Character

10

O

Input 5

Size 5

Character

12

O

F-13

Group Code

Character

10

O

For creation of tagged items only; overrides ZB_TAGPART.
For shape material, the project default ZB_SH_PART will be used and
cannot be overridden by import data.

F-14

Part Code

Character

10

O

For creation of tagged items only; overrides ZB_TAGPART.
For shape material, the project default ZB_SH_PART will be used and
cannot be overridden by import data.

F-15

List Status Code

Character

10

O

If not present, job parameter for list status will be used

F-16

Requisition Ind

Character

1

O

Must be either Y or N; defaults to Y

F-17

Plate Number

Character

24

O

For creation of shape material only

Table 8: Record layout for POS

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

POS_A

Character

N/A

M

Record type keyword as a constant

F-1

Attribute Code

Character

30

M

Attribute Code (A.50.01)

F-2

Attribute Value

Character

255

O

Unit Code

Unit Code

Character

10

O

If unit in A.50.01 differs: unit conversion

Table 9: Record layout for POS_A

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

POS_DOCUMENT

Character

N/A

M

Record type keyword as a constant

F-1

Document Code

Character

255

M

Document Code (D.10.11)

F-2

Revision

Character

5

O

If not present, highest revision

Table 10: Record layout for POS_DOCUMENT

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

IDENT_A

Character

N/A

M

Record type keyword as a constant

F-1

Attribute Code

Character

30

M

Attribute Code (A.50.01)

F-2

Attribute Value

Character

255

O

Unit Code

Unit Code

Character

10

O

Table 11: Record layout for IDENT_A

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

RENAME_TAG_CC

Character

N/A

M

Record type keyword as a constant

F-1

Old Tag Number

Character

24

M

Tag Number to rename

F-2

New Tag Number

Character

24

M

Tag Number to which to rename to

Table 12: Record layout for RENAME_TAG_CC

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

RENAME_TAG

Character

N/A

M

Record type keyword as a constant

F-1

Old Tag Number

Character

24

M

Tag Number to rename

F-2

New Tag Number

Character

24

M

Tag Number to which to rename to

Table 13: Record layout for RENAME_TAG

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

UPDATE_TAG_DESC

Character

N/A

M

Record type keyword as a constant

F-1

Tag Number

Character

24

M

Tag Number for which order description should be changed

F-2

Language

Character

24

M

Language of order description to change

F-10

New CCL Short

Character

2000

M

F-11

New CCL Long

Character

2000

M

Table 14: Record layout for UPDATE_TAG_DESC

Logical Column

Data Content

Data
Type

Length

O/M

Comment

Record Type

PROJECT

Character

N/A

M

Record type keyword as a constant

F-1

Smart Materials project

Character

10

M

Smart Materials project into which this data may be imported

Table 15: Record layout for PROJECT