Commission Data in SQL Replicated Database
Commission Data in¶
SQL Replicated Database
Commission Tables in the Exigo SQL Replicated Database¶
When commissions are calculated real time, the data is stored in memory on the server and cannot
be accessed via any tables on the reporting database. The API web services allows for pulling this
information for back office reports to be developed for the web.
The only real time commission data that is available would be the PeriodVolumes. This shows the
values for all volume buckets for the specified periodtypeid and periodid.
Once there is a commission run, regardless of the accepted or completed status, the following
tables will contain data for the run:
1.CommissionBonuses
a. Stores the amount of the earning for each bonus for each customer in the specified
commissionrunid.
b. You can join with the Bonus table to get descriptions of the BonusID value.
2.CommissionCustomers
a. Stores rankid, customertypeid, and customerstatusid information for all customers in
each run.
b. You can join with the Rank table to get descriptions for the RankID values, join with
CustomerStatuses and CustomerTypes to get descriptions for those ID values.
3.CommissionDetails
a. Stores the detail for the Commissions table which shows the customer and the order
information for each bonus calculation.
4.CommissionExchangeRates
a. Stores the exchange rates for each currency that were set at the time of the specified
commissionrunid.
5.CommissionOverrides
a. Stores the overrides that were put in place by customer at the time of the specified
commissionrunid.
b. You can join with the Overrides table to get the description for the overrideid.
6.CommissionRuns
a. Stores the commissionrunID values their description, rundate, accepteddate and
commissionrunstatusid information.
b. You can join with the CommissionRunStatuses table to get descriptions of the statusid.
7.Commissions
a. Summary level records of customer earning by currencycode with balance forward
information for each specified commissionrunid.
b. The detail of each summary record can be found in the CommissionDetails table.
8.CommissionEnrollerTree and CommissionUnilevelTree
a. Stores the copy of the tree as it was structured at the time of the commission run for the
specific CommissionRunID provided.
ONLY WHEN COMMISSIONS ARE ACCEPTED, YOU WILL SEE DATA FROM THE RUN CAN BE¶
FOUND IN THE FOLLOWING TABLES:
1.Bills
a. Stores vendor bills that were generated from the accepted run, each bill represents the
amount of the earning to be paid out.
2.Payouts
a. Once a bill is paid, the amount of the payment is represented in these records along with the
method of payout. There can be one payment record that is tied to multiple vendor bills.