Technical Implementation - Intergraph Smart Materials - 2.3 - Administration & Configuration - Hexagon

Intergraph Smart Materials EcoSys Integration (2.3)

English (United States)
Intergraph Smart Materials
EcoSys Integration
Search by Category
Administration & Configuration

The requisitions of a Smart Materials project are loaded only when the project default ZI_E_RQSER is set to Y, and a name of EcoSys project is assigned to the project default ZI_E_PROJ, and the project belongs to the product group specified under DBA setting ECO_PRODUCT_GROUP. All the requisitions which are released to procurement are posted to EcoSys. The following sequence of operations are executed each time the service runs in the background.

Load Requisition Headers into staging table

The service pulls all the requisition headers meeting the required criteria and loads that data into staging table M_ECO_REQ_HEADER_STAGINGS using the view MVW_ECO_REQ_HEADERS. If there are multiple supplements for a single Requisition Header in Smart Materials, the header details which are present at highest supplement (by the time job executes) will only be posted.

Load Requisition Line Items into staging table

The service then pulls all the line items of Requisition which have account codes of EcoSys and meeting required criteria and loads into staging table M_ECO_REQ_LI_STAGINGS using the view MVW_ECO_REQ_ LINE_ITEMS. For a requisition having multiple supplements, the line item details present at highest supplement (by the time job executes) will only be loaded into staging table.

Post the data from staging tables to EcoSys API

Finally, the data from these two staging tables is posted to corresponding exposed APIs of EcoSys, which are RequisitionHeader and RequisitionLineItems specified in project defaults ZI_E_RHAPI and ZI_E_RLAPI respectively.

After the data is posted, the service then gets the value of the DBA setting ECO_REQ_FREQ and updates the repeat_interval attribute of the job which is initiating this service.

  • Smart Materials to provide currency, UOM values which are valid in EcoSys.

  • If you change the unique constraint structure of account code, then the newly added unique key position from job fields needs to be added to the views and CIP get_req_li_modifiers.

  • INSERTREASON column is included in Line Items Spreadsheet to identify the reason why the line items are inserted. The columns will hold default values like

    • 'NFL' - Nullified Line Item, 

    • 'NFR' - Nullified Requisition, 

    • 'A' - New Record (indicates that particular line item is the latest record),  

    • 'I' - Modified in supplements, 

    • 'DU' - This line item is a dummy record for compensating the cost when the EcoSys account code at requisition header is re-assigned.

  • Modification of CIPs in the custom package, project default values and spreadsheets at EcoSys should not be done while the job is running and until all the records from staging tables are posted to EcoSys.

  • You should not delete or modify staging tables data.

  • If any new column is added in views, please ensure that length of the column should not exceed 120 characters as EcoSys custom field accepts.

Once data is successfully posted, the Requisitions of Smart Materials can be seen in Commitments of EcoSys as below.