For messages and web service actions, you can use table events to track data changes. You can define, for each table, which table events are logged. The table events are logged in the Data synchronization log.To fully process the logged events, process the:

1. Data synchronization log: The logged events are processed and for each applicable message or web service action, a record is added to the Outbound queue.
2. Outbound queue: For each record, the related message or web service action is run to export the applicable data.

This topic explains how to process the data synchronization log.

 

Note:

• Events are logged only for tables and event types that are defined in the data synchronization setup of any message or web service action.
• If on the data synchronization setup, the Update check box and the Check used fields check box are selected, event logging is restricted to changes to the fields as defined for the record in the applicable source document.
• Only the event is logged and used for further processing. So, in case of an update, an event is logged of type Update. However, the changed data is not marked as changed and not used for further processing. For example, if you change a customer address, an event is logged that the customer is updated. However, the address change as such is not logged. When, for the logged event, a record is processed in the outbound queue, the then current data of the customer is used.
• If a logged event is processed, it is deleted from the data synchronization log.

Example:

This table gives examples of the results for several data synchronization log processing scenarios:

Number of pages	Page size	Limit records	Number of records to be processed	Result
5	10,000	No	40,000	4 pages of 10.000 records are processed
5	10,000	Yes	40,000	4 pages of 10.000 records are processed
5	10,000	No	80,000	5 pages of 16.000 records are processed
5	10,000	Yes	80,000	5 pages of 10.000 records are processed

 

Standard procedure

1.	Click Connectivity studio Integration operations.
2.	Click Process data synchronization log.
3.	To improve the performance when processing a lot of logged events, you can use paging. For paging, the logged events are split over several pages that are run in parallel batch tasks. It can be that you can run only a limited number of batch jobs in parallel or that you want to use a limited number of batch jobs. If so, define the maximum allowed number of pages.
	In the Number of pages field, enter a number.
	Note: If the number of records to be processed is less than the the defined 'Number of pages' x 'Page size', less than the defined number of pages are processed.
4.	You can split the records to be processed over several pages (batch tasks). Define the number of events to be processed by one batch task (page).
	In the Page size field, enter a number.
	Note: If the number of records to be processed exceeds the defined 'Number of pages' x 'Page size', and 'Limit records' is set to: No, the number of records per page is increased to get all records processed. Yes, the maximum number of records per page is fixed. So, not all records are processed.
5.	You can limit the number of records that is processed at once. This is only applied when the number of records to be processed exceeds the defined 'Number of pages' x 'Page size'. If Yes, the maximum number of records that is processed is the defined 'Number of pages' x 'Page size'. So, the number of records per page does not exceed the page size.
	Select Yes in the Limit records field.
6.	Usually, all records in the data synchronization log are processed. However, you can also process a number of oldest records only. For example, if you fill in '100', only the 100 oldest records are processed. This can be helpful to investigate if issues occur when processing older records.
	In the Oldest set of field, enter a number.
	Note: If you enter a number in the 'Oldest set of' field, these fields are not considered: Number of pages Page size Limit records
7.	Sub-task: Set up batch processing.
7.1	Usually, you process the data synchronization log in batch in a recurring pattern.
	Expand the Run in the background section.
7.2	Select Yes in the Batch processing field and fill in the other fields as desired.
7.3	Set up the recurrence for the data synchronization log processing.
	Click Recurrence and fill in the fields as desired.
7.4	Click OK.
8.	Click OK.

Notes

You can also process specific data synchronization log records. To do so:

1. Go to Connectivity studio > Inquiries > Data synchronization log.
2. Select the records to be processed.
3. Click Process selection.

See also

• Set up data synchronization for message