| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Return to Sage Timberline Sales Estimating Document Integration
Article Index
| Table of Contents |
|---|
Integrated Fields
The integration of Sage of Sage Timberline Sales Estimate Document to Framework ECM is Document to Framework ECM is fully customisable via the integration mapping database.
[JobNumber][_suffix]_pee_estimate_coverpg_setup
Sage |
|---|
Timberline Database Field Name | Sage |
|---|
Timberline Field Label | Create | Update | Framework Database Field Name | Framework Database Field Label | |
|---|---|---|---|---|---|
user_job_class_3 | Yes | Yes | Framework - s_hType_name | s | |
project_zip_code | Yes | Framework - s_job_state | |||
project_city | Yes | Yes | Framework - s_job_suburb | ||
project_name | Yes | Yes | Special #5: job lot numb, job street num, job street name | ||
job_cost_job_number | Yes | Yes | Framework - job.s_job_num |
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.
...
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.
After entering the Framework job.s_job_num we get the job details from v_TLWizardJobInfo where
Job.s_job_num = the job number entered
Job.l_context_id matches the region division selected in the combo box.
If the job is found the client.s_name and client.s_name_ref fields are checked to make sure they’re not empty.
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 the suffix specified, (unless the suffix is set to None), and finally adding _Pee_Estimate_Coverpg_Setup to make the table name to search for.
If the table does not already exist then we get the document details the user has selected from v_dlgAppWizard where
Doc.l_doc_id = selected document and doc.l_doc_type_gl_id = -226 (Tender) or -228(Variation Order) or -230 (FVL)
Doc.l_doc_stat_gl_id = -222 (final) Documents must be final
To export the job we get it’s details again from v_sched_tlGold1 where job.s_job_num = the job number entered.
Create the Estimate table, or staging table if we’re using staging,
Open the access database and create a temporary table in there for the database.
Then we synchronise the job data into the temporary access table.
Then we export the table from access to Timberline Estimation.