Failed Communication Sessions

Automatically Repeating Communication

If the source station has not received confirmation that the communication file has been input on the target station within the time period defined in the Days to reception field (see Confirmation), the communication process is treated as having failed, and the communication file is automatically output again.

• The system determines which records need to be output again based on the communication logs on the source station. Logs older than 6 months are ignored.
• The format entered in the communication logs must be selected in the current communication connection, i.e. communication is only repeated for formats which are in current use.
• For each communication connection and format, a "repetition file" is output, unless the communication file originally sent is still available and not older than 7 days.
• The new communication file is named according to the current date. This ensures that files are input on the target station in the correct order.
• New communication logs are added for any "repetition files". The status of unconfirmed communication logs is set to "not relevant" and these are no longer taken into account by the system.

If the data models on both stations are not identical (error 46), the communication process is also repeated automatically, see Outdated Data Model at Branch Offices.

Outdated Data Model at Branch Offices

If a branch office communicates with the main office and the data model on the branch office is outdated, the data in the communication file may not be input on the target station (e.g. if fields and info areas in the data model have been deleted on the target station). Instead, the file is moved to the ERR directory.

The input process' communication log is assigned the Status "Error" (Error No. 46). The notification file requests that the data be resent by the branch office.

The main office automatically outputs the current data model for the target station in the next communication process, see Communicating Data Model Changes in the CRM.core Administrator Guide.

When inputting the file on the branch office, the data model is updated first. Once the input process is complete, all changes since the last successful outbound communication process are output. The new communication file therefore includes both the changes in the communication file rejected by the main office and all changes made since then on the branch office.

Once the communication file is successfully input on the main office, the error has been resolved and the communication file that caused the error can be deleted from the ERR directory.

Once the branch office has input the confirmation receipt from the main office, the Status of the log referring to the failed communication session is set to "not relevant" on the branch office. The Destination: received and Destination: input fields are enabled and the date of the new output process is entered in the Retry date field.

As of versions 7.0.6.214 and 7.0.7.72, branch offices also automatically output their data model. Based on this information, data in info areas that have been changed in the data model on the target station can also be input, provided no fields or info areas have been deleted.

Manually Repeating Communication

To manually repeat a failed communication session:

1. Search for the last successful output process in the Communication Logs info area on the source station (Status: OK).
2. Navigate to the penultimate output to the affected target station.
3. Make a note of the values in the Dateand Time fields.
4. Switch to the target station in the Station info area.
5. Enter the values you noted down into the Last Output Date and Last Output Time fields.
6. Output the file for the target station again.

   A communication file containing all missing records since the last successful communication session is created.