Contract Core Task Automation List (TAL) - Repair Direct Sales Workflow

Core Current Open Items

The TAL table below displays workflow items that may require user attention. 

NOTE: Items in the repair lists are suspended. They are not included in reporting, rebate calculations, or government pricing calculations. 

To review the workflow items, select the GO button. 

 ________________________________________________________________________________________________________________
 

Repair Direct Sales with Invalid Customer, Product, GL Code
 

The Repair Direct Sales with Invalid Customer, Product, GL Code workflow will allow the user to view and automatically repair Invalid Customer, Invalid Product, Invalid GL Code, Invalid Contract, Invalid Rebate, and Invalid Rebate Period errors.
 
When repairing, move through the errors tabs from left to right, beginning with resolving the Invalid Customer error.
Invalid Customer -> Invalid Product -> Invalid GL Code -> Invalid Contract -> Invalid Rebate -> Invalid Rebate Period

Related Interfaces

• Direct Sales
• Rebate Payments

NOTE: If there are errors that the user does not want to correct, the interface can be reversed, or the line can be deleted by enabling the role: DELETE_SUSPENDED_DIRECT_SALES. 

Invalid Customer

This process will allow a user to view and automatically repair Invalid Customer data. 
The Invalid Customer link lists the direct sales data uploaded with an Invalid Customer that does not exist in the system.

Invalid Customer Troubleshooting – Common Errors and Resolutions

Reason: Data for a new direct customer was uploaded, but the customer hasn’t been added into the iContracts application yet.
Fix: Add the new customer via Contract Core -> Customer Maintenance -> Add.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve.

Reason: An existing direct customer has a new ERP ID or a new additional identifier.
Fix: Find the existing customer via Contract Core -> Customer Maintenance -> Change. Add the new ID as an alias.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve.

Reason: Mapping issue in the direct sales file itself.
Fix: Reverse the direct sales file by going to Contract Core -> Interfaces -> Interface History.

Correct the formatting and re-upload the file; or, if the Customer ID was the only mapping issue, within the Invalid Customer tab, the user can type the correct customer ID in the ‘Customer Id’ column, select the customer from the drop down, and click SUBMIT.

Invalid Product

This process will allow a user to view and automatically repair Invalid Product data. 
The Invalid Product link lists the direct sales data uploaded with an Invalid Product. 

Invalid Product Troubleshooting – Common Errors and Resolutions

Reason: Data for a new product was loaded that hasn’t been added into the iContracts application yet.
Fix: Add the new product via Contract Core -> Product Maintenance -> Add.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve.

Reason: An existing product has a new ERP ID or a new additional identifier.
Fix: Find the existing product via Contract Core -> Product Maintenance -> Change. Add the new ID as an alias.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve.

Reason: Mapping issue in the direct sales file itself.
Fix: Reverse the direct sales file by going to Contract Core -> Interfaces -> Interface History.

Correct the formatting and re-upload the file; or, if the product ID was the only mapping issue, within the Invalid Product tab, the user can type the correct product ID in the ‘Product Id’ column, select the product from the drop down, and click SUBMIT.

Invalid GL Code

This process will allow a user to view and automatically repair Invalid Direct Sales data.
The Invalid GL Code link lists the direct sales data uploaded with an Invalid GL code.  

Invalid GL Code Troubleshooting – Common Errors and Resolutions

Reason: A new GL Code was loaded in the direct sales file that hasn’t been added into the iContracts application yet.
Fix: Add the new GL Code via Contract Core -> Id Maintenance -> GL Code. 

Visit the Repair workflow again and the sales with this error should resolve

Reason: Mapping issue in the direct sales file itself.
Fix: Reverse the direct sales file by going to Contract Core -> Interfaces -> Interface History. 
Correct the formatting and re-upload the file; or, if the GL Code was the only mapping issue, within the Invalid GL Code tab, the user can type the correct GL Code in the ‘GL Code’ column, select the GL Code from the drop down, and click SUBMIT.

Invalid Contract

This process will allow a user to view and automatically repair Invalid Contract data.
The Invalid Contract link lists the direct sales data uploaded with an Invalid Contract Id.  

The system looks at the product and customer to find the contract. 
The product and customer can only be eligible for one direct contract for the look up to function.

If there is no ID listed in the Invalid Contract Id column, this means the application was not able to find a contract with a DIRECT or BOTH MOP where both the Customer ID and Product ID are eligible on the contract at the time of the invoice date.

Invalid Contract ID Troubleshooting – Common Errors and Resolutions

If the ‘Invalid Contract ID’ contains a value...

Reason: A new direct contract was included in the file that hasn’t been added into the iContracts application yet.

Fix: Add the new contract via Contract Core -> Contract Maintenance -> Add.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve.

Reason: An existing direct contract has a new ERP ID or a new additional identifier.

Fix: Find the existing contract via Contract Core -> Contract Maintenance -> Change.
Add the new ID as an alias.

Visit the Repair Direct Sales workflow again and the sales with this error should resolve

Reason: Mapping issue in the direct sales file itself.

Fix: Reverse the direct sales file by going to Contract Core -> Interfaces -> Interface History.
Correct the formatting and re-upload the file; or, if the contract ID was the only mapping issue, within the Invalid Contract tab, the user can type the correct contract ID in the ‘Contract Id’ column, select the contract from the drop down, and click SUBMIT.

If the ‘Invalid Contract ID’ field is blank...

Reason: The iContracts application was not able to find a direct contract where both the customer listed in the Customer ID column and product listed in the Product ID column, are eligible on the contract at the time of the invoice date, listed in the Invoice Date column.

Fix: To identify the reason why the sale didn’t resolve, the user can either:

1) Review the direct contract itself by going to Contract Core -> Contract Maintenance -> Change.
Check the 4. Product tab and 5. Purchaser tab to make sure the invoice date on the sale falls in between the effective dates for both the product and contract.

2) Navigate to Contract Core ->Contract Maintenance -> Price Lookup.
Enter the customer, product, MOP, and the date range that includes the invoice date. 

• If more than one contract is returned, the sale will not resolve because iContracts doesn’t know which contract the sale should be attached to. Double check the contracts and delete or end date the product or customer from the unwanted contracts.  Then hit GO.
• If no direct contract appears, double-check the contract setup in Contract Core -> Contract Maintenance -> Change and make sure both the product and customer are active at the time of the invoice date. If a customer and/or product do not exist, add them.

Once a correction is made so that one direct contract matches the customer and product, the next time the user enters the Invalid Contract screen, the sales will resolve to that contract.  

Invalid Rebate

This process will allow a user to view and automatically repair Invalid Rebate data.
The Invalid Rebate link lists the direct sales data uploaded with an Invalid Rebate Id. 

Enter an existing rebate ID in the Rebate Id column, then select from the dropdown list.  Select [SUBMIT].

Invalid Rebate ID Troubleshooting – Common Errors and Resolutions

Reason: Mapping issue in the rebate payment file itself.

Fix: Reverse the rebate payment file by going to Contract Core -> Interfaces -> Interface History. 
Correct the formatting and re-upload the file.

Invalid Rebate Period

This process will allow a user to view Invalid Rebate Period data.
The Invalid Rebate Period link lists the direct sales data uploaded with an Invalid Rebate Period, meaning the Rebate Period Date does not match the Rebate Dates in iContracts. 

Invalid Rebate Period Troubleshooting – Common Errors and Resolutions

Reason: Rebate period date from the file falls before the start date of the rebate or after the end date of the rebate.
Fix: Extend the rebate’s start and/or end date via Rebate Payer -> Rebate Maintenance -> Change.
Enter the problematic Rebate ID, then hit GO.


*If no results are returned, try selecting the “All” radio button to return both ACTIVE and EXPIRED rebates.

To adjust/change the rebate end date, click CHANGE, then navigate to End Date on the Rebate Header. Update the date, then hit SAVE.



Alternatively, a user should review the submitted Rebate Id to see if the correct Rebate Id has been used. 

Visit the Repair Direct Sales workflow again and the lines with this error should resolve.

Reason: Mapping issue in the rebate payment file itself.

Fix: Reverse the rebate payment file by going to Contract Core -> Interfaces ->Interface History. 
Correct the formatting and re-upload the file.