Rockton Pricing Management (RPM) is a pricing engine that works in conjunction with an ERP, such as Microsoft Dynamics GP. To calculate pricing, specific data from Dynamics GP needs to be shared with RPM so the pricing engine can calculate the price and return that price to Dynamics GP.
This article explains how data flows between Dynamics GP and RPM. It also details what data must be setup directly in the Dynamics GP and what must be setup in RPM.
RPM is a stand-alone web application that integrates with multiple ERPs. In this example, Dynamics GP is the focus. Some data flows from Dynamics GP to RPM and some data is created within RPM to return a price in Dynamics GP. When you enter a transaction in Dynamics GP, RPM calculates the price based on the data from the transaction and returns a price.
Dynamics GP to RPM
During the initial implementation and setup of RPM with Dynamics GP, Export Scenarios are created to ensure that when certain data is created in Dynamics GP, the same information is automatically created in RPM. This ensures both programs remain in sync.
The following data is created in Dynamics GP and synced to RPM:
This information is always created in Dynamics GP and sent to RPM during the sync process. If the information is created in RPM, it does not sync back to Dynamics GP. This is also true if you edit a record. The edit must be done in Dynamics GP and then sync to RPM.
If you delete a record in Dynamics GP, it does not delete it in RPM. If you no longer want it to appear in RPM, you must delete it there as well. If you delete a record from RPM, it does not delete it from Dynamics GP.
After the overall setup and implementation is complete, there is also data created and maintained within RPM. This data is used when calculating an item price, which is passed back to Acumatica in the form of a computed price.
The following data is created within RPM:
- Price Schedule – matches to a Price Level in Dynamics GP
- Price Calculations
- Pricing Filters
- Price Books
- Rounding Rules
- Customer Attributes
- Item Attributes
Note: The Customer/Item Attributes come from Dynamics GP but the set-up is completed within RPM.
This information is used in RPM to determine the best price to compute for an item and is then passed back to Dynamics GP with the best price, based on the setup and pricing method selected.