1-866-477-6267 (toll-free)
Support Home > Integrations > Sage 300 CRE > Tutorials > Send a CCO to an ERP Integrations for Accounting Acceptance

Send a CCO to an ERP Integrations for Accounting Acceptance

Objective

To send a Commitment Change Order (CCO) to the ERP Integrations tool so it can be accepted by an accounting approver for export to your integrated ERP system

Background

When you create a CCO on a Procore project, the new CCO must be sent to the ERP Integrations tool in Procore for acceptance by an accounting approver. After acceptance, the system will export the CCO data to your integrated ERP system.

Things to Consider

  • Required User Permission:
    • 'Admin' level permission on the project's Commitments tool.
      AND
    • 'Admin' level permission on the project's Change Orders tool.
      (Note: Typically, the project manager is responsible for sending an approved Commitment Change Order (CCO) to the ERP Integrations tool for acceptance by an accounting approver. See What is the accounting approver role?).
  • Minimum CCO Requirements:
    Before you can send a CCO in the Change Orders tool to the ERP Integrations tool, the CCO must satisfy these requirements:
    • ID Number: Must be 12 characters or less. 
    • Date Created: The date the CCO was created in Procore will be exported to Sage 300 CRE by default. This field cannot be edited. This corresponds to the 'Commitment Date' in Sage.
    • Title: Must be 30 characters or less. 
    • Description: This value in this field is exported from Procore into the 'Scope' field in Sage 300 CRE. Sage  imposes a one thousand (1000) character maximum on this field. Entries that exceed the maximum will be truncated in Sage. The entire description will be stored in Procore.
    • Contract Company. Must be linked to a Sage 300 CRE vendor. See Link a Sage 300 CRE Vendor to a Procore Company.
    • Status. Must be 'Approved.' 
    • Schedule of Values (SOV). Must include at least one (1) line item with a Sage 300 CRE Cost Code. (Note: You can only add a line item to the commitment's SOV if its linked to an existing cost code and category.)
  • Additional Information:
    • If desired, you can configure your default settings to use your Procore Change Order Number for an exported commitment's Sage ID field. If enabled, the Sage ID will auto-populate with the Procore Change Order Number. However, the value can still be edited. (Enabling this account-wide configuration setting requires 'Admin' level access on the ERP Integrations tool.)
  • Limitations:
    • Sage 300 CRE does not permit users to modify a contract line item on a CCO more than once.
    • If a contract line item on a CCO includes more than one (1) modification, Procore will automatically calculate the sum for all of that line item's modifications. After acceptance by an accounting approver, the amount of the items and send it to Sage as a single (aggregated) value. 

Steps

  1. Navigate to the project's Change Orders tool.
  2. Click the Commitments subtab. 
  3. Locate the desired CCO in the list. Then click View.
    This reveals the selected CCO in the Commitments tool. 
  4. If all the CCO data appears as desired, click Send to ERP.

    (Notes:

    • If the Send to ERP (or Re-send to ERP) button is grayed out and unavailable, hover your cursor over the question mark (?) to learn why. Typically, its because the project's ERP data has not yet been synced or because the item does not meet the minimum requirements (see above). 
    • If the Retrieve from ERP button appears, the data has already been sent to the ERP Integrations tool). 

    The system sends the CCO data to the ERP Integrations tool so it can reviewed by the accounting approver. It also locks the following fields so they can no longer be edited in Procore: 'Contract Company', 'Title', 'Status', and 'Total Amount'). 
You must to post a comment.
Last modified
10:15, 3 Feb 2017

Tags

Classifications

This page has no classifications.