Technical implementation - Intergraph Smart Materials - 2017 R2 (2.2) - Administration & Configuration - Hexagon

Intergraph Smart Materials EcoSys Integration 2017 R2 (2.2)

Language
English
Product
Intergraph Smart Materials
Subproduct
EcoSys Integration
Search by Category
Administration & Configuration
Version Smart Materials Web API
2017 R2 (2.2)

The following sequence of operations are executed each time the service runs in the background.

Load Line Items of an Invoice into table

The service loads the invoice line items corresponding to all invoices from the view MVW_ECO_IVC_LINE_ITEMS into the table M_ECO_IVC_STAGINGS only if that line item is not yet in the table (Invoice line item data is fetched from the table M_INVOICE_DETS). The invoice line items must have account codes retrieved from EcoSys. The invoices of a project are considered for loading only if the project default ZI_E_IVSER is set to Y and if project default ZI_E_PROJ has the name of an EcoSys project assigned.

Load Other Costs of an Invoice into table

The service loads the other costs corresponding to an invoice from the view MVW_ECO_IVC_OTHER_COSTS into the table M_ECO_IVC_STAGINGS only if that other cost is not yet in the table (Invoice other costs data is fetched from the table M_INVOICE_DETS). The other costs of an invoice must have account codes retrieved from EcoSys. The other costs of an invoice of a project are loaded only if the project defaults ZI_E_IVSER and ZI_E_PHOC are set to Y, and the project default ZI_E_PROJ has the name of an EcoSys project assigned.

Load Additional Invoice Items of an Invoice into table

The service loads the Additional Invoice Items corresponding to an invoice from the view MVW_ECO_IVC_ADD_COSTS into the table M_ECO_IVC_STAGINGS only if that record is not present in the table (Invoice Additional Items Cost data is fetched from the table M_INVOICE_DETS). The additional invoice items must have account codes retrieved from EcoSys. The additional invoice items of an invoice of a project are loaded only if the project default ZI_E_IVSER is set to Y, and the project default ZI_E_PROJ has the name of an EcoSys project assigned.

Posting the data from staging table to EcoSys API

The table M_ECO_IVC_STAGINGS now has the complete data of all the invoices. Finally, the data from this table is posted to EcoSys using the published InvoiceDetails API, which is specified in the project default ZI_E_IVAPI. Table looks like below, it is based on the columns customer specifies in the views.

EcoSys47

  • 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.

  • 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.

  • Agreements job should always run before Invoices job to make sure that invoice line items of all the agreements are posted to EcoSys. In case an agreement is not posted to EcoSys, the invoice line items of that agreement are not posted to EcoSys as per default settings provided in EcoSys (it throws an error by default, this can be customized in EcoSys spread sheet column settings).

Once data is successfully posted, the invoices of Smart Materials can be seen in the Actuals of EcoSys, as shown below.

EcoSys48