The transaction interface loader process starts by collecting transactions from the API based on the parameters provided by the user and looking at transactions in the API that have the following load_status:
• UNLOADED: Status of the transaction when it is first loaded into the API table. It also denotes that it has not been picked up for loading into the
CN_COMMISSION_HEADERS table.
• ERROR - PRIOR ADJUSTMENT: This means that the value of the collection parameter Allow Prior Period Adjustments? has been set to No and the transaction processed_date has a column value that is less than the last processed transaction processed_date. To resolve this, perform the following:
1. Make sure to set the parameter to Yes so that the system can process prior period adjustments.
2. If the paramet is set to No, change the processed_date on the transaction to be greater than the date for which calculation was last run.
• ERROR - TRX_TYPE: This means that the trx_type column value of the transaction is not a system recognized transaction type. The possible values for this column are Claw Back, Credit Memo, Give Back, Invoice, Manual Adjustment, Booked Orders, Payment Received, or Write Off. To resolve this, fix the trx_type value on the transaction.
• ERROR - REVENUE CLASS: This means that the revenue_class_id column value provided on the transaction is not defined in the system. To resolve this, make sure that the revenue_class_id value populated on the transaction refers to the revenue class defined in the system.
• ERROR - NO EXCH RATE GIVEN: This means that the transaction currency is
different from the functional currency defined for the system and the value of the exchange_rate column is not populated. To resolve this, populate the exchange_rate column with a value on the transaction.
• ERROR - INCORRECT CONV GIVEN: This means that no value has been given to the transaction_currency_code column and the exchange_rate column but the value of the transaction_amount is not equal to acctd_transaction_amount. To resolve this, make sure that the transaction's transaction_amount column is not a functional currency based value, and then provide values for the transaction_currency_code and exchange_rate columns. This error should not occur if you are using
SQL*LOADER or importing a spreadsheet. This is because the acctd_transaction_amount is not required in those cases.
• ERROR - CANNOT CONV/DEFAULT: This is a catch-all bucket in case the process cannot do currency conversion of transaction_amount column of the transaction.
Possibly the currency code has not been defined.
• SALESREP ERROR: This means that the process did not find any resources defined in the system for the given employee_number column value or salesrep_id column value. To resolve this, perform the following procedure:
1. Make sure the employee_number or salesrep_id column is populated with a value in the API table. If you are using SQL*LOADER or a spreadsheet, only employee_number needs to be entered.
2. Make sure the employee_number or salesrep_id on the transaction is defined in the system and active for the processed_date of the transaction.
• PERIOD ERROR: This means that the given processed_date column value on the transaction does not fall within the compensation period start date and end date that is defined in the system. To resolve this, do the following:
1. Provide a value for the column processed_date on the transaction for which the compensation period start date and end date are defined in the system and also Open.
2. Verify that the compensation period start date and end date are defined in the system to include the processed_date column value on the transaction.
For example, if periods are defined as follows:
Jan-06 (1-Jan-06 to 31-Jan-06) Feb-06 (1-Feb-06 to 28-Feb-06)
A transaction that is processed for 2-March-06 will create a period error message.
The transaction interface loader process does not pick up transactions in the API that have the following load_status:
• OBSOLETE: The transaction has been adjusted prior to the transaction interface loader being run and cannot be uploaded into the system.
• FILTERED: As part of Standard collections, the post collection process is defined to filter this transaction, therefore that it cannot be loaded into the system.
• LOADED: The transaction is already successfully loaded from the table
CN_COMM_LINES_API into the transaction table CN_COMMISSION_HEADERS.
See Validation Checks and Resolution Method for more details.
• SCA_PENDING: The transaction has been transferred to the Sales Credit Allocation engine but has not been processed yet.
Additional Note
The Reload Errored Transactions parameter (Configuration Workbench > Collection >
Setup Collection Parameters) allows you to decide whether or not to attempt to load the unloaded transactions which failed to load in prior attempts. The default value for this parameter is No. When the parameter is set to Yes, the transaction interface loader attempts to load the transactions that failed to load in prior loads.
If API transaction data are populated through Collection or created through Maintain Transaction, the data is always valid. Invalid data, in most cases, are introduced into the API table by a direct upload into the API table from an external source.
For example, suppose that the invalid salesrep_id, invalid employee_number or both columns are null. For such invalid transactions, the loader sets the Load_Status to SALESREP ERROR or PERIOD ERROR, respectively. To fix this problem, correct the data and then set the Reload Errored Transactions parameter to Yes so that these error transactions can be picked up again in the next run of the load process. Because this is an expensive operation, the parameter should be set to Yes only if errors have indeed been fixed in the transactions that could not be loaded.