Updated: November 9, 2023 8:52am


Resources are the data types replicated from one Prism server to another. When configuring data replication, you create profiles that include the resources you need to send from the server to other locations. When you link a profile to a connection, the resources specified in the profile will be sent to the server at the other end of the connection.

Resource Notes
addresstype List of address types. Define address types in Admin Console > Preferences & Settings > Node Preferences > Data Types. The address types defined in preferences can be assigned to individual addresses in customer records.
adjustment Adjustment memos. Adjustment memos are typically only sent UPSTREAM, from a store to its POA or from the POA to HQ. Best practice is to not send adjustment memos downstream from HQ to stores
allocationpattern Allocation patterns for allocating orders of items among multiple stores.
biometrics Biometrics login information. Two database columns play a key role in biometric login: user_name and empl_name.
The Prism RPSODS database EMPLOYEE table includes user_name and empl_name columns. The BIOMETRICS table includes empl_name column.
  • The user_name column is unique across all subsidiaries. When a user does a regular log in using user name and password, the server looks in the EMPLOYEE table and tries to find a matching record. The employee resource is a core resource and cannot be filtered or excluded from replication. As a result, you can use the user_name and password of any employee and login to Prism at any store.
  • The empl_name column is unique within a single subsidiary. When a user does a biometric log in using a fingerprint, the server first looks in the BIOMETRICS table and retrieves the empl_name and sbs_sid. The server tries to match the retrieved information with a corresponding empl_name and orig_sbs_sid in the EMPLOYEE table. If a match is found, the server uses the user_name and password from the EMPLOYEE table for the login. The biometrics resource is not a core resource; therefore, you can apply a filter or simply not replicate the resource. This creates the possibility that a user may be able to log in using the username and password but the log in using the fingerprint fails.
If you want to filter your data by subsidiary but still want all fingerprints to be replicated you must create a separate profile that only includes the biometrics resource and do not apply any filter to it. The rule is: empl_name + orig_sbs_sid from EMPLOYEE table MUST match empl_name + sbs_sid from BIOMETRICS table. Therefore when you create a biometrics record, you should pass empl_name and sbs_sid equal to empl_name and orig_sbs_sid (important! Not employee sbs_sid but employee orig_sbs_sid) of the employee who you are creating the fingerprint for.
calendar List of calendars.
chargeterm Charge terms. Charge terms are defined in customer records.
comment Comments for POS documents.
company The list of companies that can be assigned to customer records. When a new company is entered in a customer record, the company is added to the database in a special table and will be available for selection on customer records.
contacttype Contact type (Mail, Phone, Email). Contact types are defined in Admin Console > Preferences & Settings > Data Types.
country List of countries
couponset Coupon set. (Defined in coupon sets and coupons in Point of Sale > Promotions > Coupons)
couponsetcoupon Coupon set coupon. (Defined in coupon sets and coupons in Point of Sale > Promotions > Coupons)
customer The list of customer records. Customer class, customer document history and customer UDF fields are replicated using their own dedicated resources (see the entries that follow).
customerclass The Class field is used to group customers for marketing and other purposes. This resource replicates the class field info.
customerdocumenthistory Information about customer purchasing history.
customerudf Information about customer UDF fields, defined in Admin Console > Node Preferences > Customers > UDF
dcs The list of departments (groupings of merchandise).
docposflag POS flags. Defined in Admin Console > Preferences & Settings > Node Preferences > Merchandise > POS Flags.
document Transactions.
documentfeetype Fee types assigned to fee amounts on documents. Define fee types in Admin Console > Node Preferences > Transactions > Fees/Shipment.
drawerevent Z-Out drawer open events.
emailtype Email type (e.g. Home, Work, Other). Email types are defined in Admin Console > Preferences & Settings > Data Types.
employeeudf Employee user-defined fields. Defined in the employee record.
exchangerate The list of exchange rates for each currency. Define exchange rates in Admin Console > Global Preferences > Currency > Exchange Rate.
fiscaldocument Fiscal documents.
fiscalsequence Fiscal document sequences.
griddata Grid format settings. Grid data settings are defined in Admin Console > Preferences & Settings > Grid Formats.
inventory Inventory information. Note: If using loyalty, as part of the inventory resource, each item's Loyalty Redeem and Loyalty Reward point values are replicated as well as the Item Reward information if the item is part of an Item Reward program.
inventorystyle Inventory style information.
invnlot Inventory lot number information. Lot number information is added in the Inventory item record.
invnminmax (Prism 2.1 and above) To replicate Min/Max levels for Inventory items, select the invnminmax resource in the profile. Care should be taken when selecting this resource to avoid replicating a lot of excess data. When the invnminmax resource is selected, Prism replicates the Min/Max tables and the New Min, New Max values. Configuration for Auto Min/Max is not replicated.
invnsbssublocationqty Sublocation quantities. Sublocation data and the corresponding resources are spit between the sublocations themselves and their item quantities. At a store, a sublocation can be created or modified, and this will be replicated enterprise wide. But a store's sublocation item quantities are modified by documents. Subsequent stock quantity updates are executed by the documents through replication. Sublocations and their properties are core resources to ensure that the sublocation of a document exists at the document target.
Note: The sublocationsegpref resource is part of the "Core" resources and as such it is not displayed in the list of resources. This resource is sent with the other core resources during initialization (or if the profile has the core resources checkbox selected).
invnserial Inventory serial number information. Serial number information is added in the Inventory item record.
invnudf User-defined fields for inventory items, defined in Admin Console > Node Preferences > Merchandise > Inventory > UDF.
job Job titles (e.g. Manager, Associate, Cashier).
kitcomponent Information about Kit Items and their components.
language List of languages.
ltylevel Customer loyalty-level assignments.
ltylevelprogram Loyalty levels and programs.
markdown (Prism 2.1 and above) The markdown resource sends the Price Adjustment Memos created when updating a markdown in Price Manager. Previously, replicating markdowns required sending the Inventory resource (a time-consuming resource to process).By creating a separate resource for markdowns, Prism replicates these price changes more efficiently.
  • For an immediate markdown, Prism creates a one-time scheduled task for each adjustment, so replication is not delayed.
  • For a scheduled markdown, a one-time scheduled task is created.
  • Requires both the "markdown" and "adjustments" resources in the replication profile for both directions of the link (Store to POA/POA to Store).
  • Adjustment memos created by a markdown, when replicated to stores/POA and applied to Inventory through Scheduler, are processed by PrismBackofficeService. This might slow down PrismBackofficeService. For example, suppose a user creates a markdown with 100,000 items and clicks Apply Now. This creates 100 Adjustment Memos (1000 items per memo) that will be replicated. When the other side of the connection (store) receives the adjustments, it will create 100 scheduled tasks to apply the markdown to Inventory.
mediatype This resource is not currently used in Prism and can be safely omitted from profiles, including initialization.
pcppromotion Promotions created in Prism.
phonetype Phone type (e.g. Home, Work, Other). Phone types are defined in Admin Console > Node Preferences > Data Types.
plugindata Customization and plugin data.
pricerounding Price rounding information.
printarea List of print areas in Admin Console > Node Preferences > Hardware > Print Preferences.
printareavalue Values for the individual print areas defined in Admin Console > Node Preferences > Hardware > Print Preferences.
printertype List of printer types defined in Admin Console > Node Preferences > Hardware > Printer Types.
puchaseorder Purchase orders.
purchfeetype Fee types for purchase orders. Define fee types for POs in Admin Console > Preferences & Settings > Purchasing > General.
reason Reasons for applying discounts and other actions. Define reasons in Admin Console > Preferences & Settings > System > Reasons and Notes.
receiving Receiving documents.
region Corporate regions (for regional inventory).
scale Grid scales (sets of size/attribute combinations).
scalepattern Inventory grid scale patterns (size/attribute patterns).
shippingmethod This resource contains the shipment carriers and methods (e.g. USPS, UPS, FEDEX).
till List of tills.
timeclock Check In/Check Out records.
title Titles (Mr., Mrs., Ms., etc.). Titles are defined in Admin Console > Node Preferences > Data Types.
touchmenu Touch menus and buttons. (Important! If the touch menus use item images, those images must be available at the other end of the connection. You can define a central image server in Node Preferences > Themes and Layouts, or export the images, extract and copy to the ...\ProgramData\RetailPro\Server\images folder at the other location.)
tranfeetype Fee Types for transfer orders, defined in Admin Console > Preferences & Settings > Node Preferences > Transfers > General
transferorder List of transfer orders.
transferslip List of transfer slips.
transrule Resolution rules for transfer verification. Resolution rules are defined in Admin Console > Preferences & Settings > Transfers > Resolution Rules.

The userpasswordhistory resource helps Prism to enforce the password history setting. By replicating the resource, Prism servers will have up-to-date information about user password history.

vendor List of vendors. Vendors are defined in Store Operations > Merchandise > Vendors.
vendorinvoice Vendor invoices. Vendor invoices record the actual amount charged by the vendor for an order. Each vendor invoice is matched with one or more vouchers.
vendorudf Vendor user-defined fields.
zoutcontrol Z-Out) reports provide end-of-day reporting of sales totals.