Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Insert excerpt
FWINT HEAD
FWINT HEAD
nopaneltrue

Return to Sage Timberline Initial Estimate Integration

Article Index

Table of Contents

Integrated Fields

The integration of Sage of Sage Timberline Initial Estimate to Framework ECM is Estimate to Framework ECM is fully customisable via the integration mapping database.

_PEE_ESTIMATE_COVERPG_SETUP

Sage

Timberline Database

Timberline Database Field Name

Sage

Timberline Field

Timberline Field Label

Create

Update

Framework Database Field Name

Framework Database Field Label

Project_Address

 


Yes

Yes

Special #5: job lot num, job street num, job street name.

 


Project_City

 


Yes

Yes

Framework - s_job_suburb

 


Project_Name

 


Yes

 


Framework - s_job_num

 


Project_Zip_Code

 


Yes

Yes

Framework - s_job_state

 


Job_Cost_Job_Numbr

 


Yes

 


Framework - s_job_num

 


User_Job_Class_3

 


Yes

Yes

Framework - s_hType_name

 


Database Models

The following database model(s) displays the manner in which data is integrated between the third party application and Framework and Framework Integration.Image Removed

...


Integration Process

The following information is a low level account of the integration process including criteria, decisions, and outcomes. This information is technical in nature and is provided "as-is" for a detailed analysis of the integration process for system administrators.

  1. Get eligible Framework jobs for integration from v_sched_tlGold1 where

    1. Job.l_prd_hType_id > 0

    2. Client.s_name is not null

    3. Client.s_name_ref is not null

    4. Job.s_link_boq <> ‘N/A’

    5. Job.l_wfl_stgMajor_id <> -5 (Maintenance)

    6. Job.l_job_status_gl_id = -7(Active) or -10(On Hold) or l_job_status_gl_id = -946 (Pending Cancellation) (-8 and d_cont_cancelled is in the last 14 days)

    7. and apply Criteria Method criteria where CriteriaMethod is

    8. 1 – Single Region Division • job.l_context_id = ‘CriteriaMethodID’

    9. 2 – Single Job • job.s_job_num = ‘CriteriaMethodID’

    10. 3 – Single Team • job.l_team_id = ‘CriteriaMethodID’

    11. 4 – All Jobs • job.l_job_id <> 0

    12. 5 – Accounts Entity • job.l_accounts_e_id = ‘CriteriaMethodID’

  2. Next make sure the job does not already exist in the destination by taking the job.s_job_num value (use job.s_link_boq if not empty), and adding _Pee_Estimate_Coverpg_Setup to make the table name to search for.

  3. The Estimation table is either updated or created.