Communication Steps

Once a branch office has been initialized using a data stock download, the branch office can communicate with the main office.

The communication process involves the following steps:

  • The main office inputs changes received from branch offices (see Input).
  • The main office outputs changes for branch offices (see Output). The communication files are transferred to the branch offices (see Transferring Communication Files).
  • The branch offices each input the changes received from the main office (see Input).
  • The branch offices output changes made to data on the branch offices for the main office. These communication files are transferred to the main office.
  • The main office inputs changes received from the branch offices etc.
Note: You can communicate with a maximum of 1,000 stations in a single communication session.

Communication processes can be completely asynchronous: data stored in the Communication module determines which data needs to be output in the next communication session, see Output.

Communication logs are created each time data is input or output, see Communication Logs. The logs also include information on whether output communication files are input successfully (see Confirmation), whether records are missing (see Synchronization) and whether the output needs to be repeated (see Troubleshooting).

Note: The access rights defined in the Rights module are ignored when communicating, see Rights and Communication in the CRM.core Administrator Guide. Consequently, no triggers are initiated when inputting communication files, see Database Events in the CRM.core Administrator Guide.