Pmorey: /* Default Tables */

2023-12-04T19:08:30Z

Default Tables

← Older revision		Revision as of 19:08, 4 December 2023
Line 22:		Line 22:

	===Default Tables===		===Default Tables===

			<p><i>NOTE: Any company database tables NOT listed below are cleared of all data when office data is loaded at the remote site.</i></p>

	{\| border="3" cellspacing="0" cellpadding="3"		{\| border="3" cellspacing="0" cellpadding="3"

Pmorey: /* Default Tables */

2023-12-04T19:06:27Z

Default Tables

@@ Line 198: / Line 198: @@
+|
 | Yes
 |-
 | CCTFORM
 | System Forms
-| Yes (a/o Keystone 3.1.2)
+| Yes (a/o 3.1.2)
+|
 |-
 | CCTOPTN
@@ Line 218: / Line 233: @@
+|
 | Yes
 |-
 | DITPRJLD
@@ Line 236: / Line 266: @@
 | GLTACGRP
 | G/L Account Groups
 | Yes
+|

WikiAdmin: 1 revision imported

2023-07-14T13:00:37Z

1 revision imported

← Older revision	Revision as of 13:00, 14 July 2023
(No difference)

Intra>Pmorey: /* Transferring Data */

2017-01-17T16:19:40Z

Transferring Data

New page

Setting up remote ticketing systems can be a complex process. Here are some guidelines to simpify the process.

==Initial Keystone Setup==

When you first install Keystone on the remote system, you will need to enter information on the Keystone Activation form.

*Use the same Serial No. as the office system.
*Use a unique System Location for each remote system (never zero!)

[[Image:RemoteLicenseSetup.PNG]]

==Configuring the Location==

Using Location Maintenance add a new location for the remote system.

*Use the Location Id that was entered in the Keystone Activation form.
*Select Remote Ticketing for the Type.
*Select File for both Transfer In Via and Transfer Out Via.
*You should rarely have to setup LOCALTABLES in the Xfr In parameters on the remote system (see [[#Default Tables|Default Tables]] for the list of tables that are copied from the office and preserved at the remote.)

[[Image:RemoteLocationSetup.PNG]]

===Default Tables===

{| border="3" cellspacing="0" cellpadding="3"
! Keytone Table
! Description
! Copied from Office?
! Preserved at Remote?
|-
| ARTCTCLS
| A/R Credit Terms Classes
| Yes
|
|-
| ARTCUCLS
| A/R Customer Classes
| Yes
|
|-
| ARTCUST
| A/R Customers
| Yes
|
|-
| ARTDIV
| A/R Divisions
|
| Yes
|-
| ARTDRIV
| A/R Drivers
| Yes
|
|-
| ARTEXCLS
| A/R Tax Exempt Classes
| Yes
|
|-
| ARTJOBCL
| A/R Job Classes
| Yes
|
|-
| ARTJOBDT
| A/R Job Prices (Detail)
| Yes
|
|-
| ARTJOBHD
| A/R Job Prices (Header)
| Yes
|
|-
| ARTLOC
| System Locations
|
| Yes
|-
| ARTORDDT
| A/R Remote Orders (Detail)
|
| Yes
|-
| ARTORDHD
| A/R Remote Orders (Header)
|
| Yes
|-
| ARTOWNER
| A/R Owners
| Yes
|
|-
| ARTPLANT
| A/R Plants
|
| Yes
|-
| ARTPLTCK
| A/R Plants Last Used Ticket Numbers
|
| Yes
|-
| ARTPRAUT
| A/R Automatic Products
| Yes
|
|-
| ARTPRCLS
| A/R Product Classes
| Yes
|
|-
| ARTPRGRP
| A/R Price Groups
| Yes
|
|-
| ARTPRICE
| A/R Special Prices
| Yes
|
|-
| ARTPROD
| A/R Products
| Yes
|
|-
| ARTPRSTR
| A/R Product Structure
| Yes
|
|-
| ARTPTKCK
| A/R Remote Tickets Processed by Office
| Yes
|
|-
| ARTPTKDT
| A/R Remote Plant Tickets (Detail)
|
| Yes
|-
| ARTPTKHD
| A/R Remote Plant Tickets (Header)
|
| Yes
|-
| ARTSLSPN
| A/R Salespeople
| Yes
|
|-
| ARTTRAIL
| A/R Trailers
| Yes
|
|-
| ARTTRCLS
| A/R Truck Classes
| Yes
|
|-
| ARTTRUCK
| A/R Trucks
| Yes
|
|-
| ARTTXAUT
| A/R Tax Authorities
| Yes
|
|-
| ARTTXLOC
| A/R Tax Localities
| Yes
|
|-
| ARTTXSTR
| A/R Tax Structure
| Yes
|
|-
| ARTUMS
| A/R Units of Measure
| Yes
|
|-
| ARTZONE
| A/R Zones
| Yes
|
|-
| CCTDEVICE
| System Devices
|
| Yes
|-
| CCTFORM
| System Forms
| Yes (a/o Keystone 3.1.2)
|
|-
| CCTOPTN
| System Options
|
| Yes
|-
| CCTSECTL
| System Security Control
|
| Yes
|-
| CCTSESSN
| System Sessions
|
| Yes
|-
| DITPRJLD
| Dispatch Projected Loads
|
| Yes
|-
| DITUSECL
| Dispatch Usage Classes
| Yes
|
|-
| GLTACCT
| G/L Accounts
| Yes
|
|-
| GLTACGRP
| G/L Account Groups
| Yes
|
|-
| Z$ARTPRTRX
| A/R Product Transactions (Summarized)
| Yes
|
|}

==Configuring the Plant==

Using Plant Maintenance add a new plant for the remote system. You will need to use SuperUser mode to access Plant Maintenance.

*Set the Location Id to the same value entered in Location Maintenance.

[[Image:RemotePlantSetup.PNG]]

==Transferring Data==

*Never use Backup/Restore to bring data to a remote system! This has negative security and performance implications.
*Never edit a ticket form on a remote system! Ticket forms should always be setup on the office system. They will then transfer to the plant as part of Beginning of Day (a/o Keystone 3.1.2.)

Remote Plant Ticketing Setup - Revision history

Pmorey: /* Default Tables */

Pmorey: /* Default Tables */

WikiAdmin: 1 revision imported

Intra>Pmorey: /* Transferring Data */