G-Type Attribute Mapping - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Integration (10.1)

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

The PDMS 30.02 screen is used to configure the origin of the attribute data for the PDMS transfer on PDMS 20.01 for the several GTypes.

There are several possibilities for the origin of the attributes:

  • Attributes of the geometric

  • Attributes came from CIP (customer defined procedure) M_PCK_PDMS_CUSTOM

  • Attributes of the commodity code details

    Table Name

    Table Details

    ATTR_CHAR 1 - 3

    ATTR_NUM 1 - 3

You can query all G-types, which are table details of the table with the interface translation ‘GTYPE’ for PDMS (A.50.I.01 Interface Tables).

The needed parameter list can vary from G-type to G-type. The parameter positions (Parameter Seq) can have another meaning within different G-types.

GType FILT

GType CROS

Type Geometric

For all geometry attributes that will be used, you must have a translation for the PDMS interface on A.50.I.02 Interface Attributes.

For the attributes such as diameter, length, thickness, and so on, PDMS needs a suffix (in), if you want to use the imperial unit system. The default suffix will be the unit code of the attribute (Unit field ). If you have entered an interface dependent unit (A.10.14), then the interface unit is used as the suffix. With the Use Unit indicator, you can determine which attribute needs a suffix. This is only required for the unit inch. If no suffix is attached to the parameter, PDMS knows that you are working with the metric unit mm (millimeter).

Type Commodity Code

If you use the Type ‘Commodity Code’, you can enter a tablename, which is from Type ‘COMMATTR’ (or a table link) and exists as a detail in the commodity rule.

With the selection in the Value defined in field on PDMS 30.02, you define the origin of the value. The available fields are: TD_CODE, ATTR_CHAR1, ATTR_CHAR2, ATTR_CHAR3, ATTR_NUM1, ATTR_NUM2, and ATTR_NUM3.

Type CIP

If you want to get the values from a CIP (customer-defined procedure), you can select all functions from the valid package M_PCK_PDMS_CUSTOM (owner M_SYS) with the input parameter P_IDENT.

M_PCK_PDMS_CUSTOM specification:

/*

|| function example_cip_pdms3002

||

|| this is only an example for a CIP function, which will be used in PDMS 30.02

|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.

|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)

||

*/

FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)

RETURN VARCHAR2;

M_PCK_PDMS_CUSTOM body:

/*

|| function example_cip_pdms3002

||

|| this is only an example for a CIP function, which will be used in PDMS 30.02

|| G-Type Attribute Mapping. The input parameter must be named P_IDENT.

|| The return value will be written to the PDMS_G.DAT file as VARCHAR2(19)

||

*/

FUNCTION example_cip_pdms3002 (P_IDENT IN M_IDENTS.IDENT%TYPE)

RETURN VARCHAR2

IS

v_return VARCHAR2(19);

BEGIN

v_return := 'CIP example';

--

RETURN v_return;

END example_cip_pdms3002;