Business Integration Solutions Documentation

Walkthrough: Vendor Replication

About this walkthrough

This walkthrough provides an overview on how to synchronize vendor master data.

This is a simple replication demonstrating on how you can use same internal document for both publication and subscription connections, in case the table structure is same, therefore saving time and effort.

Prerequisites

You can choose to create two companies for demonstration purpose. In the following scenario we have:

  • CRONUS International Ltd. [as a Publishing Company]
  • CRONUS Sales [as a Subscription Company]
Template Description Type Company

TI_RM_VENDOR.OUT

STAEDEAN Template-Publish Vendors for Synchronization

Publication

CRONUS International Ltd.

TI_RM_VENDOR.IN

STAEDEAN Template-Subscribe Vendors for Synchronization

Subscription

CRONUS Sales

Template - Publish Vendors

Story

  • This connection uses the Timer Event to trigger the Pipeline.
  • The connection contains an XML Generator which creates an XML-file, based on the internal document.
  • The created XML-file is stored on a file location, specified in the File Writer Endpoint.

Vend Out

Setup

  1. Select the publishing company. Company - CRONUS International
  2. Import Publication-TI_RM_Vendor.OUT.zip configuration package. VO Import
  3. Open the TI_RM_VENDOR.OUT connection. On the connection page, edit the File Writer settings and provide the Folder Name. VO Settings

Process

  1. Process the connection.
  2. Check the output folder location.

Result

VO Settings

One XML-file with a complete overview of your Vendors is created and available on the specified location.

Template - Subscribe Vendors

Story

This connection uses the File Reader Endpoint to read the published file from the file system.
The XML-file contains a complete list with Vendors, so for a proper traceability the Splitter Activity is added to the connection.

The Record Generator Activity creates records and updates the NAV tables based on the internal document.

In this scenario we assume that the table structure is the same as in the publishing company and the various posting groups (like Gen. Bus. Posting Group, VAT Bus. Posting Group and Vendor Posting Group) are already available in the system, so we are using the same internal document as used for the publishing connection.

VI Pipeline

Setup

  1. Select the subscription company. Company - CRONUS Sales
  2. Import Subscription-TI_RM_VENDOR.IN.zip configuration package. VI Import
  3. Open the TI_RM_VENDOR.IN connection. On the connection page, edit the File Reader settings and provide the Folder Name. VI Settings

The File Reader Endpoint contains some typical Replication Management properties, like Leave File on File System, Read New Files Only and Last Processed at. In many cases the Internal Document from the Publication Connection can be reused for the Subscription Connection.

Process

  1. Process the connection.
  2. If the processing is successful, to check the result click History. Select the Message Entry, click Actions, Show Record.

Result

VI Settings

The Vendors are imported. You can also use the Transaction Log to see more details for each import.