1.  The Integration Interchange Process


From the ClickHome point of view, interacting with the client’s other systems is purely dependant on what the client currently has implemented an could vary with each new client.  Consequently, as ClickHome is implemented for each client there is usually some development work to be done, either by ClickHome or by the client’s own IT resources.

Click Home provides standard points of interface so, from its own perspective the interchange process is always the same.  This minimises the task of creating the different interface facilities for each client.  The common points of interface are focussed on the standard interface tables provided in the ClickHome database.

As a result of this, it is not possible for this User Guide to be explicit about the interchange process.  It is possible to say, though, that in general the interfacing is largely automatic and will require minimal involvement by the client’s staff on a day by day basis.

The interchange of data is part of the customer integration documentation provided as part of the implementation process


1.1  Suppliers Interchange with ClickHome

For a successful interface of purchase orders Suppliers must be present in ClickHome therefore new Suppliers and changes to existing Suppliers will be automatically detected and interfaced across to ClickHome.

As well as this progressive synchronisation of the Supplier details between ClickHome and the other systems, a Complete Reload facility is also provided as a tool the user can use at his discretion.  Typically this will be used at the initial point where ClickHome is implemented, but may also be useful at any time where the client needs to verify the integrity of the Suppliers’ details in ClickHome.

There is no provision for passing Supplier details from ClickHome to the other systems.

The interface table used to provide Supplier details to ClickHome is called tblInterfaceVendors


1.2  Purchase Orders Interchange with ClickHome

  New Purchase Orders and changes to existing Purchase Orders can be interfaced across into ClickHome from the clients accounting system.

  Purchase Orders entered into ClickHome in this way are subject to the detailed rule-based processing that is discussed later this user guide.        Outcomes achieved by ClickHome for Purchase Orders are:

· Progressive or ‘end-of-task’ approval-to-pay on purchase orders;

· Updating of the correct supplier to use on certain tasks for a Job;

· Inclusion/exclusion of certain tasks on a Job where they are or are not applicable;

· Scaling of  Job task duration according to purchase order value or quantity ordered;

· The ability to dispatch purchase order details to suppliers when a task is ‘called on’ can be provided. 

· Addition of supplier details to a purchase order, if not provided by the accounting system, from its record of relevant suppliers for a template task.

· Splitting of tasks when two or more suppliers are required to complete the task.

· Auto creation of tasks for purchase orders raised without a matching task.

  The returning of purchase order related details back to the other systems is limited to certain specific items. 

· Purchase order percentage approvals are fed back as related tasks are flagged as progressively completed;

· Where a supplier is not provided in the original purchase order and the local ClickHome users selects the supplier or allows the default to apply,      that supplier selection is passed back;

  The interface tables used for Purchase Orders are called tblInterfacePOHeader and tblInterfacePOLines as documented in Appendix A.