M_PCK_SCREEN_CUSTOM - Intergraph Smart Materials - Version 10.1 - Customization & Programming - Hexagon

Intergraph Smart Materials Customization (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Customization & Programming
Smart Materials/Smart Reference Data Version
10.1

This package contains functions for configuration/customization of Smart Materials screens.

As examples, two functions are provided to retrieve the supplier's company name (get_company_names) and an indicator whether order is approved (get_cycle_approved_inds).

To be displayed in the Manage CIPs dialog, the functions have to follow a specific format:

  • It must be a function (not a procedure)

  • There must be only one parameter which is of type m_type_numbers: p_ids m_type_numbers

  • The function must return a ref cursor: RETURN ref_cursor

Using the collection type m_type_numbers you can write a simple join:

  • Create a table from the collection type: TABLE(p_ids) ids

  • Use the property “COLUMN_VALUE” to join with the corresponding column: sup.sup_id = ids.COLUMN_VALUE

The first selected value in the SELECT statement must be the COLUMN_VALUE because it is used for internal processing, the second value is the value shown on client side.

You can return all standard Oracle data types, numeric and date values are automatically formatted on client side.

The parameter p_ids contains a list of the primary keys of the corresponding grid for which you’re implementing the CIPs.

Transfer of PK_ID and PK_TYPE combination

Another example function (get_ppl_forecast_date) is provided to retrieve PK_ID / PK_TYPE combination with a value. Requisites for these CIPs are:

  • It must be a function (not a procedure)

  • There must be only one parameter which is of type m_type_pk_data_tab

  • The function must return a ref cursor: RETURN ref_cursor

The collection type m_type_pk_data_tab contains the type m_type_pk_data which has the properties "pk_id" and "pk_type". The first selected value in the SELECT statement must be the "pk_id" and the second value must be the "pk_type" because they are used for internal  processing, the third value is the value shown on client side. All standard Oracle data types can be returned, numeric and date values are automatically formatted on client side. The parameter p_keys contains a list of primary keys and primary key types of the corresponding grid for which you’re implementing the CIPs.