Updated: April 11, 2025 1:42pm

Retail Pro Prism 2.4 Replication Profile Recommendations

Retail Pro Prism Replication Profile Recommendations PDF

This topic presents sample profile configurations for data replication: Day-to-Day (D2D) and Initialization. 
A profile specifies the resources that will be replicated from one end of a connection to the other in a specific direction. You can use a different profile for sending data in each direction for the connection, or you can reuse the same profile. By carefully selecting the types of data to replicate from one server to another, you can ensure that only the needed data is sent and avoid bottlenecks/performance issues. For example, the profile used to send data from a store to the RA/POA will include resources like document (transactions), drawerevent (e.g., cash drop) and zoutcontrol (Z-Out reports). The profile used to send data from the RA/POA to stores will include resources like dcs (departments), employees, inventory and vendors; however, it will not include the document, drawerevent, or zoutcontrol resources. (See the Resources topic for information about each resource)
The following are general guidelines based on methods that have been successfully deployed in the field, but each entity must carefully consider what their individual replication needs are at each level and ensure that they create profiles that will correctly address these needs.

Resource D2D - RA/POA to Store D2D - Store to RA/POA    Initialize - RA/POA to Store  
addresstype Yes No Yes
adjustment Optional No No
allocationpattern Yes No Yes
ammessages No Yes No
ammonitorevents No Yes No
amsystemmonitor No Yes No
biometrics Yes No Yes
calendar Yes No Yes
chargeterm Yes No Yes
comment Yes No Yes
company Yes No Yes
contacttype Yes No Yes
controller (core resource) Yes No Yes
controllerlicense (core resource) Yes Yes Yes
controllerstore (core resource) Yes No Yes
country Yes No Yes
couponset No No No
couponsetcoupon No No No
currency (core resource) Yes No Yes
customer Yes Yes Yes
customerclass Yes No Yes
customerdocumenthistory No No No
customerudf Yes No Yes
customschema (core resource) Yes No Yes
dcs Yes No Yes
docposflag Yes No Yes
document No Yes No
documentfeetype No No No
drawerevent No Yes No
emailtype Yes No Yes
employee (core resource) Yes No Yes
employeeudf Yes No Yes
exchangerate Yes No Yes
fiscaldocument No Yes No
fiscalsequence No Yes No
griddata No No No
inventory Yes No Yes
inventorystyle Yes No Yes
invnlot Yes No Yes
invnminmax Yes No Yes
invnsbssublocationqty Yes No Yes
invnserial Yes No Yes
invnudf Yes No Yes
job No No No
kitcomponent Yes No Yes
language Yes No Yes
ltylevel Yes No No
ltylevelprogram Yes No Yes
markdown Optional No No
mediatype Yes No Yes
pcppromotion No No No
phonetype Yes No Yes
plugindata No No No
pricelevel (core resource) Yes No Yes
pricerounding Yes No Yes
printarea No No No
printareavalue No No No
printertype No No No
purchaseorder Optional No No
purchfeetype Optional No No
purgeresource Yes No Yes
reason Yes No Yes
receiving Optional Yes No
region Yes No Yes
scale Yes No Yes
scalepattern Yes No Yes
season (core resource) Yes No Yes
shipping method Yes No Yes
store (core resource) Yes No Yes
storetype (core resource) Yes No Yes
sublocation (core resource) Yes No Yes
sublocationsegpref (core resource) Yes No Yes
subsidiary (core resource) Yes No Yes
taxarea (core resource) Yes No Yes
taxcode (core resource) Yes No Yes
tenant (core resource) No No No
till Yes No Yes
timeclock No Yes No
title Yes No Yes
touchmenu Yes No Yes
tranfeetype Yes No Yes
transferorder Optional No No
transferslip Optional Yes No
transformdesign (core resource) Yes No Yes
transrule Yes No Yes
usergroup (core resource) No No No
userpasswordhistory No Yes No
vendor Yes No Yes
vendorudf Yes No Yes
vendorinvoice Optional Yes No
zoutcontrol No Yes No

 

 

Previous
Next

Search Documentation