/
Sage Timberline Land Integration - Reference

Sage Timberline Land Integration - Reference

Owned by Julie Doyle-Whitelock (Deactivated)
Aug 22, 2017

Integrated Fields

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

Master_Arm_Record_1

Sage Timberline Database Field Name

Sage Timberline Field Label

Create

Update

Framework Database Field Name

Framework Field Label

CADD1

 

Yes

Yes

Special #1: client street number & client street name

 

CBADD1

 

Yes

Yes

Special #1: client street number & client street name

 

CBCIY

 

Yes

Yes

s_client_suburb

 

CBEMAIL

 

Yes

Yes

s_client_email

 

CBSTATE

 

Yes

Yes

s_client_state

 

CBZIP

 

Yes

Yes

s_client_postcode

 

CCITY

 

Yes

Yes

s_client_suburb

 

CEMAIL

 

Yes

Yes

s_client_email

 

CFAX

 

Yes

Yes

s_client_fax

 

CNAME

 

Yes

Yes

Special #7: Client Name (job num).

 

CPHONE

 

Yes

Yes

s_client_phone

 

CSTATE

 

Yes

Yes

s_client_state

 

CTRADE

 

Yes

 

Fixed Value: None

 

CTXGR

 

Yes

 

Fixed Value: GST

 

CTYPEA

 

Yes

 

Fixed Value: Standard

 

CUST

 

Yes

 

Special #2: Gets the first four or five characters from client ref name (ini file key determines harmony) appends 2 numbers to it, adds leading 0 if needed.

 

CZIP

 

Yes

Yes

s_client_postcode

 

Master_JCM_Record_1_1

Sage Timberline Database Field Name

Sage Timberline Field Label

Create

Update

Framework Database Field Name

Framework Database Field Label

JACTCD

 

Yes

Yes

d_settle_act

 

JADDR1

 

Yes

Yes

s_addr_full

 

JARCUST

 

Yes

 

Special #2: Gets the first four or five characters from client ref name (ini file key determines harmony) appends 2 numbers to it, adds leading 0 if needed. 

 

JBCITY

 

Yes

Yes

s_name

 

JBSTATE

 

Yes

Yes

s_name_state

 

JBZIP

 

Yes

Yes

s_name_postcode

 

JCITY

 

Yes

Yes

s_name_suburb

 

JCNAME

 

Yes

Yes

s_client_name

 

JDESC

 

Yes

Yes

s_desc

 

JOB

 

Yes

 

Special #6: Fwork job number formatted to the Timberline format.

 

JORDER1

 

Yes

Yes

s_supervisor_name

 

JPRJMGR

 

Yes

Yes

s_administrator_name

 

JSTATE

 

Yes

Yes

s_name_state

 

JTYPE

 

Yes

Yes

land table

 

JZIP

 

Yes

Yes

s_postcode

 

JACTCD

 

Yes

Yes

d_settle_act

 

JBMETH

 

Yes

 

Fixed Value: Use Quick Bill. This value applies to using Timberline Quickbill for invoicing when not using Contracts.

Fixed Value: Use Contracts. This value applies to using Timberline Contracts

 


Database Models

The following database model(s) displays the manner in which data is integrated between the third party application 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.

  1. Get eligible Framework jobs using v_FWINT_Land where
    1. land.s_link_accts <> ‘N/A’
    2. and apply Criteria Method criteria where CriteriaMethod is
    3. 1 – Single Region Division
    4. land.l_context_id = ‘CriteriaMethodID’
    5. 2 – Single Land
    6. land.l_land_id = ‘CriteriaMethodID’
    7. 3 – Single Team
    8. land.l_team_id = ‘CriteriaMethodID’
    9. 4 – All Land
    10. land.l_land_id <> 0
    11. 5 – Accounts Entity
    12. land.l_accounts_e_id = ‘CriteriaMethodID’
  2. For each Framework Job search for the job in Databuild table jobs where
    1. 'L' land.l_land_id = Jobs.job_no else
    2. Jobs.job_no = land.s_link_accts
  3. If the land is found in databuild then
    1. The matching land record is retrieved from land
    2. If the records above are retrieved successfully we update the databuild job.
  4. If the job is not found in databuild then
    1. If the land.s_link_accts field is empty we create the job in databuild.
    2. The framework land.l_land_id value is checked. It must be <= 6 characters for us to be able to create the record. This is because we add an L to the front of Land PKID.
    3. We retrieve a link to the jobs table so we can add the new job
    4. If the table is accessed successfully then we create the databuild job.