Sage Timberline Land Integration - Profile Configuration

IntegrationType

Description: 

Specifies the type of integration to be performed. This is a fixed value that should not be changed.

Setting: 

Timberline Land

ODBCConnectionType

Description: 

Indicates if the Timberline database is SQL Server or Microsoft Access.

Setting: 

1: SQL Server

2: Microsoft Access

ODBCDSN_Framework

Description:

ODBC DSN name for the Framework database.

Setting: 

FworkSQLEcm

ODBCConnect_Framework

Description:

ODBC DSN connection string for the Framework database.

Setting: 

None

ODBCDSN_FrameworkLicense

Description:

ODBC DSN name for the Framework Licence database.

Setting:

FworkSQLLic

ODBCDSN_IntMapping

Description:

ODBC DSN name for the Framework Integration Mapping database.

Setting: 

FworkSQLIntMap

ODBCConnect_IntMapping

Description:

ODBC DSN connection string for the Framework Integration Mapping database.

Setting: 

None

ODBCDSN_Destination

Description:

ODBC DSN name for the Timberline system database.

Setting:

FworkTLGold

ODBCConnect_Destination

Description:

ODBC DSN connection string for the Timberline System database.

Setting:

"uid=enterUserName;pwd=enterPassword"

Mail_System

Description:

Email delivery method.

Setting: 

0: no email will be sent.

1: email will be sent using MAPI.

2 (default): email will be sent using SMTP.

Mapi_Profile

Description:

Microsoft Outlook user profile name.

Setting:

(default): Outlook

Mail_From

Description:

The name or email address of who/where the email is being sent from.

Setting:

FrameworkIntegration

Mail_Recipient

Description:

These are the mail recipients of integration logs. Multiple addresses can be added if separated with a semi-colon (;). Spaces are not necessary before or after the semi-colon.

Setting:

enterRecipientEmail@yourDomain.com.au;integrationsupport@insulagroup.com.au

Mail_Subject

Description:

Email subject heading.

Setting:

"Framework Integration : Timberline Land"

SMTP_Server

Description:

If using Mail_System 2 (SMTP), add the SMTP Server name.

Setting:

enterSMTPServerName (replace this text with your SMTP Server name)

SMTP_UseSecurity

Description:

Is security used for the STMP server?

Setting:

0 (default): A username or password is not required.

1: A username and password is required. If this setting is used, the SMTP_UserName and SMTP_Pwd fields must have a valid username and password.

SMTP_UserName

Description:

A valid username for the SMTP server.

Setting:

enterUserName (replace this text with a valid SMTP Server User Name)

SMTP_PWD

Description:

A valid password for the SMTP username.

Setting:

enterPassword (replace this text with a valid SMTP Server Password)

CriteriaMethod

Description:

Land selection criteria for retrieving records from Framework to process.

Setting:

1: Single region/division.

2: Single land.

3: Land team.

4 (default): All land.

5: Land accounts entity.

CriteriaData

Description:

Input criteria data for the criteria method.

Setting:

insert number; for example, if using CriteriaMethod 2, the setting for CriteriaData will be the specific land PKID (prefixed with an 'L') to integrate on.

TLJobNumberFormat

Description:

Job number format for referencing a Framework job in Timberline.

Setting:

0: not formatted.

1: 00-000

2: 0-0000-00

3: 00-0-0000

4: 00.0000

5: 00-0000

6: 0000-000-000

TLARCustomerFormat

Description:

Customer reference format for referencing a Framework client in Timberline.

Setting:

1: first 5 chars + 2 digit number.

2: first 4 chars + 2 digit number.

3: first 5 chars (padded with A's) + 2 digit number.

4: First 3 chars (padded with A's) + job number.

TLJobPrefix(x)

CGLPrefix(x)

JCSTACC(x)

Description:

This setting relates to the general ledger prefix (GLPrefix or GLCode) that is assigned to the job in Job Cost.

As the criteria method of integration can be chan

The value 'x' relates to the primary key value in Framework for the different types of criteria method.

Criteria Methods 1,2, 4: x is the l_rDiv_id from the rDiv table in Framework.

Criteria Method 3: x is the l_team_id from the teaged to different methods, the GLPrefix assigned to jobs matches this criteria.m table in Framework.

Criteria Method 5: x is the l_entity_id of the desired accounts company from the entity table in Framework.

Multiple .ini files keys should be added for each value of 'x' that will be found in the integration process.

Job Prefix assigned based on criteria method. If Criteria Method = 1,2, or 4 the rDiv pkid is used. ;If Criteria Method = 3 the team pkid is used. If Criteria Method = 5 the Accounts Entity Pkid is used. ;For each context/team/Accounts Entity pkid a TLJobPrefix(pkid) entry is required. ;-1 = Job Prefix Account Number for Sample Data

Setting:

The GL Prefix for the job based on the value of 'x' (e.g., "9-01-01")