View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:Store Server BP Data Segmentation

Contents

Introduction

This project will focus on implementing data segmentation of Business Partners from the central server to the store server. Data segmentation means that only specific BPs are synchronized to the store server. For example only the BPs which have ordered a product in the store.

Depending on the country and law, it is also possible that restrictions apply on what data can be present on a store server. Also in the case of external stores (franchising) there can be restrictions.

BP synchronization and segmentation plays a role in 2 distinct moments:

For the runtime sync the statement can be made that the business partner is selected in WebPOS and from there creation in the store is triggered. There are however cases when the store server is offline and the BP is created in the central server. In this case the new BP has to be synced from the central to the store server.

A choice need to be made if this syncing is done using Symmetric DS or a custom syncing through the import entry framework.


How business partner are segmentated

Changes done to a business partner will be synchronized to a store if any of these conditions are met:

Both the table that stores the business partner-store relation and the flag to determine if a business partner is a standard customer are initialized using the following ant task:

ant -f modules/org.openbravo.retail.storeserver.synchronization initialize.bp.segmentation.tables

Adding a business partner to a store

When a business partner is included in a store by adding a rowto the Business Partner by Server window, it is required to synchronize to the store the relevant rows of c_bpartner and other tables related to it. The list of tables related with c_bpartner is defined in this window:


TablesRelatedWithBusinessPartner.png

This tables, along with c_bpartner, are synchronized to the server by "touching" (updating the updated column to the current timestamp) the relevant rows, so that the changes are detected by SymmetricDS, whose business partner router will now be able to route these data to the proper store, as the router takes into account the Business Partner by Server window.

Tracking issue

Retrieved from "http://wiki.openbravo.com/wiki/Projects:Store_Server_BP_Data_Segmentation"

This page has been accessed 322 times. This page was last modified on 23 May 2016, at 09:25. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.