| Docs Help
  AppSource  
Docs  /  App  /  NAVAX Replication  /  Working with the App

 Replication Entries


2026/02/20 • 6 min. to read
Creating, deleting, modifying, or renaming a record of a table that is set up for replication triggers the creation of replication entries. These replication entries can be reviewed, edited, and of course executed via "RPL Replication Entries". When a new record is created, an Insert entry is created, which creates the primary key in the respective target company. In some situations, the insert entry may not be created. In this case, the record is then automatically created with the modify entry as well. With the Modify entry, the remaining fields are populated, or if there is no insert entry, the record is created (note that in this case all fields according to the setup are rolled out once). Deleting a table record creates a Delete entry. Each entry contains detail lines with information regarding the individual fields. By clicking on "Replication Entries" or "Details", you can expand and collapse these lines respectively.

Fields

ViewHere you can filter to the desired status of the lines.

Replication Entries

Entry No.The replication entries are automatically numbered in ascending order. When entries are transferred to another database, this entry no. remains the same as in the master company. Therefore, there are usually gaps in the entry no. in the target database.
RemoteIf checked -> this entry will be replicated to another database.
CompanyThis is the "Company" to which this entry is to be replicated.
Table No.No. of the affected table.
RecordThis column provides you with the information (key values) about which record of the table is to be replicated. You can click on the field to display the record.
OperationOperation of this entry: Insert, Modify, Delete, Rename.
DependenciesIf this record is a replication entry of a dependent table, you will receive information about the main table here.
Status
  • Open - This entry still needs to be replicated. If you manually change the status from another status to "Open", the system will attempt to replicate this entry during the next replication run.
  • Replicated - This entry has been successfully processed.
  • Skipped - Entries with this status are ignored during processing. They also no longer stop processing if there is an error text in this line. You can set this status manually in an entry. In various situations, this status is also set automatically by the replication. E.g., when a record is to be deleted that no longer exists, or when a record is to be inserted that already exists.
  • Error - If an error occurs during processing, the status "Error" is set and the date and time of the error are documented. The full error text is displayed in the "Error Text" column. Processing of all subsequent entries for this company is then stopped. All other companies continue to be replicated. When the error is resolved, replication will resume at this point for the affected company on the next call.
  • Waiting - These records have not yet been replicated and are waiting for another event. This is often the case with dependent tables where the record of the main table has not yet been replicated.
  • To check - This status has the same effect as the "Skipped" status. Replication is therefore also not stopped with the "To check" status. For example, you can set defective replication entries to this status so that they do not block the replication run, and resolve the cause of the error at a later time. The advantage of this status is that you can use a filter to display only those entries that still need to be checked, and not all consciously skipped entries with the "Skipped" status.
Error TextIf an error occurred during replication, the corresponding error text is displayed here.
Creation Date/TimeSpecifies when this replication entry (triggered by inserting, modifying, renaming, or deleting a record) was created.
Transfer Date/TimeSpecifies when this entry was successfully executed.
Error Date/TimeSpecifies when an error occurred for this entry. If no error has occurred or it has been resolved, this field is empty.
Created by User IDSpecifies who caused the replication entry by inserting, modifying, renaming, or deleting a table entry, or also through the replication setup of the table.

Details

Here you can see the detailed replication data (fields) of the selected replication entry. For each field to be replicated, there is a detail entry.
Entry No.The detail entries for the replication entry are automatically numbered in ascending order.
Table No.Identifies the affected table.
Field No.Identifies the affected field.
Field Value(New) value of the field.
Field Name and Field CaptionTechnical name and display name of the field.
SkipSpecifies whether this field should be skipped during replication.

Actions

  • Replication Setup General

  • Replication Setup Databases

  • Replication Setup Companies

  • Replication Setup Company Groups

  • Replication Setup Tables

  • Table Filter Setup

  • Manual Replication Setup

  • Person Accounts/Country Codes Posting Groups

  • Automatic Status Change

  • Execute Replication

    This action starts the processing of the replication entries. This action can also be performed via a job queue. If you start the replication not in the master data company but in a target company, only replication entries of the current company will be processed. Processing within a company always occurs in ascending order by entry no. However, for clarity, the data is displayed in descending order - with the most recent replication entry at the top.
  • Execute Replication with Filter

    This function is only displayed if you are a "Replication Administrator". When executed, the "Execute Replication" function is performed as usual. However, only those replication entries are considered that have been filtered in the current window.
  • Execute Status Change with Filter

    This function is only displayed if you are a "Replication Administrator". When called, a filter window is displayed showing the currently set filter of the replication entries. You must confirm this and select the desired status for all filtered entries. This status will be applied to all entries upon execution. Please note that execution WITHOUT a filter is not permitted.
  • Show Record

    The selected record is displayed.
  • Transfer from Base Database

    This function is only available in target databases (i.e., not in the database of the master data company). It imports all not yet imported replication entries from the base database that concern this database. In addition, the replication setups are automatically updated.

Related information




Submit feedback for
DE|EN Imprint