Which integrated ERP systems support the 'Sub Job' concept?

Last updated
Save as PDF

Answer

If your company has enabled the ERP Integrations tool for one of the supported integrated ERP systems, a sub job is a child project of a parent project. For example, a Commercial High Rise project might have a separate Low Rise Executive Office building as a child project. Many, but not all, of the supported ERP systems utilise this concept.

For companies using the

ERP Integrations tool: Show/Hide

QuickBooks®:

Sub jobs are NOT supported.

Sage 100 Contractor®:

To configure the ERP Integrations tool for Sage 100 Contractor®. See Sage 100 Contractor®: Setup Guide.
To enable the Sub Jobs feature in Procore. See Enable Sub Jobs for Sage 100 Contractor®.
To import a sub job into Procore, you must:
- Create a Phase in Sage 100 Contractor®. See your Sage 100 Contractor® documentation for instructions.
- Follow the steps in Add a Phase from Sage 100 Contractor® to a Procore Project as a Sub Job.

Sage 300 CRE®:

To configure the ERP Integrations tool for Sage 300 CRE®. See Sage 300 CRE®: Setup Guide.
To enable sub jobs, see Enable Sub Jobs for Sage 300 CRE®.
To add a sub job and export it to Sage 300 CRE® as an 'Extra', see the Steps below.
Note: There is a maximum character limit for 'Extras' in Sage 300 CRE®. See What is the maximum character length for a Sub Job?
Alternatively, you can create an 'Extra' in Sage 300 CRE® and then import it into Procore, see Add a Sage 300 CRE® Extra to a Procore Project as a Sub Job.
If you are exporting a Sub Job from Procore to Sage 300 CRE®, a code is required prior to export. Once the Sub Job has been synced with Sage 300 CRE®, a code can no longer be applied, preventing the Sub Job from being used in the Main Contract Bill of Quantities.

Viewpoint® Spectrum®

Sub jobs are NOT supported.

Integration by Ryvit:

Sub jobs are NOT supported.

Yardi Voyager®

Sub jobs are NOT supported.

UndefinedNameError: reference to undefined name 'integrations_mri' (click for details)
Callstack: at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[1]/div/p[7]/strong/span, line 1, column 1 at wiki.page() at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

Sub jobs are NOT supported.

UndefinedNameError: reference to undefined name 'integrations_xero' (click for details)
Callstack: at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[1]/div/p[8]/strong/span, line 1, column 1 at wiki.page() at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

Sub jobs are NOT supported.

For companies using the

ERP Integrations tool: Show/Hide

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)
Callstack: at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/p/strong/span, line 1, column 1 at wiki.page() at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

To configure the ERP Integrations tool for

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[1]/span, line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

. See

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[1]/a/span, line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

: Setup Guide.

To enable sub jobs, see Enable Sub Jobs for

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[2]/a/span, line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

Alternatively, you can create an 'Project Task' in

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[3]/span, line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

and then import it into Procore, see Import a ERP Sub Job to a Procore Project.

If you are exporting a Sub Job from Procore to

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[4]/span[1], line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

, a code is required prior to export. Once the Sub Job has been synced with

UndefinedNameError: reference to undefined name 'integrations_myob' (click for details)

Callstack:
    at (Media_Library/Language_Specific_Media/Reusable_Snippets/Reusable_Text_Snippets), /content/body/div[13]/div[2]/div[2]/div/ul/li[4]/span[2], line 1, column 1
    at wiki.page()
    at (faq/which-integrated-erp-systems-support-the-sub-job-concept), /content/body/div[1]/div/pre, line 2, column 10

, a code can no longer be applied, preventing the Sub Job from being used in the Main Contract Bill of Quantities.

Answer

See Also