Updated: February 27, 2025 2:56pm

Resources

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. (See the Prism Replication Profiles topic for sample profiles.)

Resource Notes
addresstype The addresstype resource replicates the address types defined in Admin Console > Node Preferences > Data Types. (ADDRESS_TYPE table). 
adjustment The adjustment resource replicates adjustment memos (quantity, price, cost). 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 The allocationpattern resource replicates allocation patterns. Allocation patterns specify the relative quantities to be ordered (PO or TO) for each store. The system assigns quantities for individual stores based upon the total order quantity.
ammessages This resource replicates the contents of the AM_MESSAGES table, which contains all messages, both alerts and user-to-user messages.
ammonitorevents This resource replicates the contents of the AM_MONITOR_EVENTS table, which contains an entry for each event.
amsystemmonitor This resource replicates the contents of the AM_SYSTEM_MONITOR table, which lists the events to be monitored.
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 The calendar resource replicates the CALENDAR table, which contains the list of calendars.
chargeterm The chargeterm resource replicates the CHARGE_TERM table. Charge terms are defined in the customer record (Payment tab).
comment The comment resource replicates the COMMENTS table. This includes Comment 1, Comment 2 on transactions, PO Instructions, PO Fee Types, Slip Comments, Voucher Comments, Check In/Out and Customer Store Credit.
company The company resource replicates the COMPANY table, which contains 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 table.
contacttype The contacttype resource replicates the contact types defined in Admin Console > Node Preferences > Data Types. (CONTACT_TYPE table)
controller The controller resource replicates the CONTROLLER table. This is a core resource.
controllerlicense The controllerlicense resource replicates the CONTROLLER_LICENSE table. This is a core resource.
controllerstore The controllerstore resource replicates the CONTROLLER_STORE table. This is a core resource.
country The country resource replicates the list of countries (COUNTRY table).
couponset, couponsetcoupon The couponset and couponsetcoupon resources replicate the serialzed coupon sets and coupons defined in the Promotions area (COUPON_SET and COUPON_SET_COUPON tables).
currency The currency resource replicates the currencies added or edited in Admin Console > Global Preferences > Currency > General. This is a core resource.
customer Replicates customer information (except UDF, loyalty information, class and store credit, which are handled by separate resources). (CUSTOMER and related tables)
An important thing to consider with replication of customer information has to do with the Share Type field in the customer record. The Share Type field in the Customer record controls the subsidiaries and stores where a customer record will be available. The available settings are Not Shared, Local, Global, or Region. If a customer's Share Type field is set to Global, the record will be shared to all stores in all subsidiaries EVEN IF the replication profile uses subsidiary filtering.
customerclass Customer class is way of grouping customers for reporting purposes.
customerdocumenthistory In Prism, certain key data about each transaction and its items is stored as part of the customer record. This data is replicated along with the customer record. If a customer is available at an installation, then the customer history will be available, too, although the full document may not be. If a user wants to view a document that does not exist locally, then the document will have to be viewed at the POA (or the document can be replicated separately). If you want to view a document that does not exist locally, make sure the customerdocumenthistory resource is selected.
customerudf The customerudf resource is used to replicate customer udf fields (CUSTOMER_UDF table). In Prism, define customer udf fields in Admin Console > Node Preferences > Customers > UDF Fields. Note: If there are more than 500 UDF values for a UDF, the data is not replicated.
customschema The customschema resource replicates the CUSTOM_SCHEMA table. This is a core resource.
dcs The dcs resource replicates department information (DCS table).
docposflag The docposflag resource replicates POS flag information defined in Admin Console > Node Preferences > Transactions > POS Flags. (DOC_POS_FLAG and DOC_POS_FLAG_OPTION tables in the Prism DB)
document The document resource replicates transactions (sales, returns, orders). Documents created in Prism BEFORE the profile is linked to the connection ARE NOT replicated. Only documents created AFTER the profile is linked to the connection are replicated. This resource replicates the DOCUMENT and related tables in the Prism DB.
documentfeetype The documentfeetype resource is used to replicate the fee types defined for use at POS. These fee types are defined in Admin Console > Node Preferences > Transactions > Fees/Shipment. DOCUMENT_FEE_TYPE table in Prism DB
drawerevent The drawerevent resource replicates drawer events (DRAWER_EVENT table). The Pop Drawer event is NOT replicated. The Paid In, Paid Out and Cash Drop drawer events ARE replicated. In addition, Z-Out drawer open events are replicated via the drawerevent resource.
emailtype The emailtype resource replicates Email Types defined in Admin Console > Node Preferences > Data Types. (EMAIL_TYPE table in Prism DB)
employee The employee resource replicates employee information (EMPLOYEE table). This is a core resource.
employeeudf The employeeudf resource replicates employee user-defined fields, defined in Admin Console > Node Preferences > Employee > UDF Fields. (EMPLOYEE_UDF and EMPLOYEE_UDF_OPTION fields in Prism DB).
Note: If there are more than 500 UDF values for a UDF, the data is not replicated. Having so many UDF values for a single UDF field indicates the field is being used as general data storage rather than as a dictionary-style list as intended.
exchangerate The exchangerate resource replicates exchange rates defined in Admin Console > Global Preferences > Currencies > Exchange Rates. (EXCHANGE_RATE table in Prism DB)
fiscaldocument The fiscaldocument resource replicates fiscal documents (FISCAL_DOCUMENT table)
fiscalsequence The fiscalsequence resource replicates fiscal document sequences (FISCAL_SEQUENCE table)
griddata The griddata resource controls the replication of grid format information (defined in Admin Console > Node Preferences > Grid Formats and stored in GRID_DATA table). Changes to grid formats made at the Corp, Subsidiary, or Store level will replicate with other preferences. Workstation settings will not replicate. Any workstation-specific grid format settings must be made at each individual workstation that needs them.
inventory The inventory resource replicates Inventory information (INVN_SBS_ITEM and related tables).
inventorystyle The inventorystyle resource replicates Inventory style information (INVN_STYLE table).
invnlot The invnlot resource replicates lot number information for inventory items (INVN_SBS_ITEM_LOT, INVN_SBS_ITEM_LOT_QTY tables).
invnminmax The invnminmax resource replicates Min Qty and Max Qty information for inventory items (INVN_SBS_MINMAX and INVN_SBS_MINMAX_QTY tables).
invnsbssublocationqty The invnsbssublocationqty resource replicates sublocation quantities (INVN_SBS_SUBLOCATION_QTY table). 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 The invnserial resource replicates inventory item serial number information (INVN_SBS_ITEM_SN and INVN_SBS_ITEM_SN_QTY tables).
invnudf The invnudf resource replicates Inventory UDF field information (defined in Admin Console > Node Preferences > Merchandise > UDF Fields). If there are more than 500 UDF values for a UDF, the data is not replicated. Having so many UDF values for a single UDF field indicates the field is being used as general data storage rather than as a dictionary-style list as intended.
job The job resource replicates job titles. You can assign a Job Title on employee records. (JOB table in Prism DB)
kitcomponent The kitcomponent resource replicates kit component item information. Kit components are the individual items that together comprise a kit item (KIT_COMPONENT table).
language The language resource replicates languages added (or changed) in Prism (RPS_LANG table).
ltylevel The ltylevel resource replicates Loyalty Levels defined in Prism POS > Customers > Customer Loyalty area. Loyalty levels are stored in the LTY_LEVEL table.
ltylevelprogram The ltylevelprogram resource replicates loyalty level programs, defined in Prism POS > Customers > Customer Loyalty area. (LTY_LEVEL_PROGRAM table)
markdown The markdown resource replicates price markdowns. Price markdowns separately from other Inventory information using the MARKDOWN resource and MARKDOWN Adjustments profile.
The MARKDOWN resource sends the Markdown list (so its basic information may be viewed at another location).
The MARKDOWN ADJUSTMENTS profile filters for the specific Adjustment memos created by the PPA and sends to other locations to be processed by the scheduler to perform the price adjustment.
Notes
  • Requires including the MARKDOWNS resource and MARKDOWNS ADJUSTMENTS profile linked to replicate for both directions of the link (Store to POA/POA to Store).
  • The MARKDOWN resource must be link to send the markdown list
  • The MARKDOWN ADJUSTMENTS profile must be linked to ensure the adjustment memos created by markdown are sent
For immediate markdowns, Prism creates a one-time scheduled task for each adjustment to avoid a delay in replication. For scheduled markdowns, a one-time scheduled task is created at the Prism Point of Authority. This task is also scheduled throughout the enterprise.
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, 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, 100 scheduled tasks will be automatically created 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 The pcppromotion resource is responsible for replicating promotions (PCP_PROMOTION and related tables). Add the pcppromotion resource to individual profiles to replicate promotions from one server to another. When you press the Broadcast button, promotions are prepared for replication.
Promotions are sent one promotion per message (instead of one large message with all promotions). If the promotion contains a long list of items it will still be a large message, but not as large as before. Also, since promotions are now sent as multiple messages, they can be processed in parallel with multiple day-to-day consumer threads.
A field in the PCP_PROMOTION table - PUBLISHED_DATETIME - tracks the date and time when that specific promotion was broadcast. The PUBLISHED_DATETIME is compared to the MODIFIED_DATETIME on the same record and if the MODIFIED_DATETIME is older than the PUBLISHED_DATETIME, the promotion will NOT be sent when you press the Broadcast button. This means that only those promotions edited after the last broadcast will be sent.
The Promotions list is created and managed at the headquarters location (or designated central location). The headquarters location then broadcasts the list to stores. Important! When you broadcast promotions, Promotions will be overwritten at the locations that receive the broadcast. The actual promotions that can be used at each individual store will be limited to those promotions assigned to the store itself or to "All Stores."
Broadcast Promotions from RA to Stores
Currently, any location can broadcast Promotions simply by clicking the Broadcast button on the interface.; however, you should only broadcast Promotions from the RA server down to the child POAs and stores. If stores broadcast promotions back up to the POA, then there is a chance that promotions priority can be duplicated at locations across the enterprise, leading to unexpected results.
phonetype The phonetype resource replicates the Phone Types defined in Admin Console > Node Preferences > Data Types. (PHONE_TYPE table)
plugindata The plugindata resource replicates information about plugins, defined in Admin Console > Customizations. (PLUGIN_DATA table)
pricelevel The pricelevel resource replicates the price levels defined in Admin Console > Node Preferences > Merchandise > Pricing > Price Levels. This is a core resource. (PRICE_LEVEL table)
pricerounding The pricerounding resource replicates price rounding instructions (future release). PRICE_ROUNDING table.
printarea The printarea resource replicates print areas. (PRINT_AREA table)
printareavalue The printareavalue resource replicates the values assigned to print areas. (PRINT_AREA_VALUE table)
printertype The printertype"resource replicates printer types defined in Admin Console > Node Preferences > Hardware > Printer Types. (PRINTER_TYPE and related tables)
prismlicensetransmit The prismlicensetransmit resource replicates Prism licensing information. This is a core resource. (PRISM_LICENSE_TRANSMIT table)
puchaseorder The purchaseorder resource replicates purchase orders. (PO and related tables)
purchfeetype The purchfeetype resource replicates Purchasing fee types defined in Admin Console > Node Preferences > Purchasing > Vouchers > PO/Voucher Fee Types. (PURCH_FEE_TYPE table)
purgeresource The purgeresource resource replicates the records updated by the PII Removal Tool. This is a core resource.
reason The reason resource replicates reasons defined in Admin Console > Node Preferences > System > General for things like discounts.
receiving The receiving resource sends both ASN vouchers and vouchers. Replication of Batch Receiving (Shipping Package Numbers) Shipping package numbers and other batch receiving information replicates as part of the ASN voucher.
Special configuration options are available for controlling the replication of ASNs generated from transfer slips. See the section titled "Replication of ASNs generated from Transfer Slips" section of this document.
region The region resource regions created in Admin Console > Global Preferences > Regional Inventory > Corporate Regions. (REGION and REGION_SUBSIDIARY tables)
scale The scale resource replicates grid scale information for Inventory styles. (SCALE and related tables)
scalepattern The scalepattern resource replicates grid scale size/attribute patterns for Inventory styles. (SCALE_PATTERN and SCALE_PATTERN_QTY tables)
season The season resource replicates the seasons defined in Admin Console > Global Preferences > Season. This is a core resource. (SEASON table)
shippingmethod The shippingmethod resource replicates the shipping methods (i.e., carriers like USPS, FEDEX, UPS) defined in Admin Console > Node Preferences > Transactions > Fees/Shipment. (SHIP_METHOD table)
store The store resource replicates store record information. This is a core resource. (STORE table)
storetype The storetype"resource replicates the store types Store types. Stores types are added/edited in the Store record. This is a core resource. (STORE_TYPE table)
sublocation The sublocation resource replication sublocation information. This is a core resource. (SUBLOCATION table)
sublocationsegpref The sublocationsegpref resource replicates information about sublocation segments (i.e., the number and length of sublocation segments). This is a core resource. (SUBLOCATION_SEQ_PREF table)
subsidiary The subsidiary resource replicates subsidiary record information. (SUBSIDIARY table)
taxarea The taxarea resource replicates tax area information, including tax rules created in Admin Console > Node Preferences > Taxes > Tax Areas. This is a core resource. (TAX_AREA table)
taxcode The taxcode resource replicates tax codes (created in Admin Console > Node Preferences > Taxes > Tax Areas). This is a core resource. (TAX_CODE table)
till The till resource replicates till records, defined in Admin Console > Node Preferences > Reporting > X/Z-Out. (TILL table)
timeclock The timeclock resource replicates check in/check out records for employees. (TIME_CLOCK table)
title The title resource replicates the titles (Mr., Mrs., Dr., etc.) that can be assigned to Customers and vendor contact persons. In Prism, define titles in Admin Console > Node Preferences > Data Types. (TITLE table)
touchmenu The touchmenu resource replicates the touch menus defined in Admin Console > Node Preferences > Touch POS. (TOUCH_MENU table)
tranfeetype The tranfeetype resource replicates fee types for transfers, defined in Admin Console > Node Preferences > Transfers > General. (TRAN_FEE_TYPE table)
transferorder The transferorder resource replicates transfer orders. (TORD table)
transferslip The transferslip resource replicates transfer slips. (SLIP table)
transformdesign Document designs. This is a core resource. (TRANSFORM_DESIGN table)
transrule The transrule resource replicates the Transfer Resolution Rules defined in Admin Console > Node Preferences > Transfers > Resolution Rules. These rules dictate how the system will handle discrepancies in the sent/received items and quantities on out slips when compared to the voucher on which the items were received.
usergroup The usergroup resource replicates employee groups. This is a core resource. (USER_GROUP table)
userpasswordhistory

The userpasswordhistory resource replicates passwords between Prism servers. (USER_PASSWORD_HISTORY table)
vendor The vendor resource replicates vendor records (VENDOR table). Vendors are defined in Store Operations > Merchandise > Vendors.
vendorinvoice The vendorinvoice resource replicates vendor invoices. (VENDOR_INVOICE table)
vendorudf The vendorudf resource replications vendor udf options defined in Admin Console > Node Preferences > Merchandise > Vendors > UDF Fields. Note: If there are more than 500 UDF values for a UDF, the data is not replicated. Having so many UDF values for a single UDF field indicates the field is being used as general data storage rather than as a dictionary-style list as intended. (VENDOR_UDF and VENDOR_UDF_OPTION tables)
zoutcontrol The zoutcontrol resource replicates Z-Out reports. Z-Out reports are not replicated between RIL and Prism; however, Z-Out Drawer Open and Drawer Close reports are replicated from Prism store servers to the POA (Prism-to-Prism) and from child POAs to the RA. Z-Outs are replicated via the drawerevent resource. (ZOUT_CONTROL table)

 


 

Previous
Next

Search Documentation