Checking and Updating LookUp Tables
If data that is assigned to a site does not arrive in the data set of the site, or if the site receives data for which it is not responsible, you may have to update the LookUp tables. For LookUp tables, see: Modeling Realignment.
The LookUp tables can be checked and updated, based on the definitions in the Administration Console for the Object Types
subscription and interlinkage. If required, data sets are added or deleted. You do this by creating SUBCHECK jobs.
You can only check and update tables for sites whose type allows for the processing of sBDoc Types. This assignment is performed in the BDoc Modeler. See: Modeling a Synchronization or Mobile Application BDoc Type
Proceed as follows:
Choose , and choose the Object Type
subscription or interlinkage.
Double-click the subscription or interlinkage and choose:
Create SUBCHECK Job
in the context menu or
The button
(Create SUBCHECK Job
)
in the menu
The SUBCHECK job is created.
To check the LookUp tables of deleted interlinkages or several existing interlinkages, choose the Object Type
interlinkage.
However, do not choose a specific interlinkage, but:
The button
(Create SUBCHECK Job
)
in the menu
You can select Existing Interlinkages
or Deleted Interlinkages
in the display frame.
To perform the check, choose Create Job
.
The LookUp tables are updated with the corresponding entries in the SUBCHECK queue. The check and the update are performed for all sites that are assigned to this subscription. You can monitor the SUBCHECK jobs under . See also: Replication and Realignment Queues.
If customer data is missing on a mobile client, the SUBCHECK job for the subscription that was generated for the publication, based on CAPGEN_OBJECT_WRITE
, has to be triggered.
If customer contacts are missing on the mobile client, the SUBCHECK job for the interlinkage CAP/CON has to be triggered. CON is then checked and updated.