Agreement Change Management - Commitments - Intergraph Smart Materials - 2017 R1 (2.1) - Administration & Configuration - Hexagon

Intergraph Smart Materials EcoSys Integration 2017 R1 (2.1)

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

All the Line Items of a valid agreement are posted to Commitment Line Items of EcoSys.

All the agreement Line Items are posted to Commitment Line Items section of EcoSys. In Smart Materials, once the agreement is approved, any of the Line Items data cannot be changed, but a supplement can be created to make any changes to the agreement Line Items. Or, you can reverse the approval of the agreement supplement and apply the changes.

Once the latest changes of the agreement are posted to EcoSys, you can see the latest supplement number of the corresponding agreement is updated in the EcoSys Commitment header section.

When a new Change Order (CO) is created for an agreement

If the Cost, Quantity, Currency, or Account Code of the Agreement Line Item changes, then the change is sent to maintain the budget at EcoSys.

By default, if Cost or Quantity change, then the difference in these values is sent as a new Commitment Line Item to EcoSys.

By default, if the Currency or Account Code of Agreement Line Item changes, then the Commitment Line Items sent earlier to EcoSys are nullified, by sending the negative value of cost which was sent earlier and a new Commitment Line Item is sent to EcoSys with the latest Currency and Account Code.

These change management columns can be customized using the CIP m_pck_ecosys_custom.get_po_li_modifiers.

If the EcoSys account code at agreement header is removed in Smart Materials after the agreement data is posted to EcoSys, then all the supplements data of that agreement is nullified.

Example of Change Management

  1. Initially post few Agreement line items to EcoSys as shown in below snapshot. Let us consider four line items and different parameters of Change Management.

    • 1-1 line item has Quantity = 100 EA

    • 2-1 line item has cost = 1000 USD

    • 3-1 line item has Account Code = TRG-01.1.1.01-LAB

    • 4-1 line item has Currency = USD

      EcoSys35

  2. Now, create a Change Order in Smart Materials for the above Agreement and modify Quantity, Cost, Account Code, and Currency as described below.

    • 1-1 line item changed Quantity to 300 EA. The delta value is +200

    • 2-1 line item changed discounted price to 2000 USD. The delta value is +1000

    • 3-1 line item changed Account Code to ā€˜TRG-01.1.1.01-ODCā€™

    • 4-1 line item changed Currency to ā€˜GBPā€™

  3. Now approve the agreement and run the Agreements job. In the following snapshot observe how the change management is handled.

    EcoSys36

When an agreement Approval is Reversed

If agreements job is run immediately after reverse approval of an agreement in Smart Materials, then all the agreement line items of that supplement which are posted to EcoSys are nullified by updating the existing records to 0 (zero).

EcoSys37

EcoSys38

If Agreements job is run after reverse approving an agreement, changing it and approving it again, then all the agreement line items which are already posted to EcoSys will be updated to 0 (zero) and modified lines are sent separately along with new line items.

EcoSys39

EcoSys40

  • Currency Code assigned to Agreements should be in EcoSys Currency Codes LOV or vice versa.

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

    • 'NFL' - Nullified Line Item

    • 'NFA' - Nullified Agreement

    • 'RA' - Reverse Approved item

    • '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 agreement header is re-assigned.

  • OTHERCOST column holds Other Cost Code if it is other cost record or it holds default value N/A.

  • Quantity Unit assigned to Agreements should be in EcoSys Currency Codes LOV or vice versa.

  • Modification of project default values, CIPs in the custom package 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.

  • Adding or deleting of columns should be done only in views MVW_ECO_PO_HEADERS and MVW_ECO_PO_LINE_ITEMS.

  • 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 the same column name must be appended to the nullifier attribute list in the get_po_li_modifiers CIP.

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

  • Invoice line items of an agreement are posted to EcoSys only if each line item of an agreements is assigned with an EcoSys Account code irrespective of the EcoSys account code assigned at agreement header.