Deny/Error codes: Hide
For a CA transaction, this indicates that the Seller ID does not exist within DTN TABS as received from the terminal. Either the terminal is sending the wrong Seller ID or the Seller has not been established in the DTN TABS database. PetroDex Support works with the terminal to correct the Seller ID within the terminal automation system (TAS) or will set up the Seller ID in DTN TABS.
For a CA transaction, this indicates that the Shipper ID for a third party transaction does not exist with your DTN TABS database as received from the terminal. PetroDex Support will work with the terminal to correct the Shipper ID within TAS or will set up the Shipper ID in DTN TABS.
For a CA transaction, this indicates that the Truck Number as received from the terminal does not exist within your DTN TABS database. PetroDex Support will work with the terminal to correct the Truck Number being sent by TAS or will set up the Truck Number for the corresponding carrier within DTN TABS.
For a CA transaction, this indicates that the Terminal ID as received from TAS does not match a Terminal ID within your DTN TABS database. PetroDex Support will work with the terminal to correct the Terminal ID transmission from TAS or will add the Terminal ID to the Seller's DTN TABS database.
For a CA transaction, this indicates that the Consignee Number as received from TAS does not match a Consignee Number within your DTN TABS database. A Deny 05 code can also indicate that the consignee was not assigned to the terminal. PetroDex Support will work with the terminal to correct the Consignee Number transmitted by TAS or will add the Consignee Number to your DTN TABS database or will assign the consignee to the terminal. .
For a CA transaction, this indicates that the allocation was set up as a Deny. The consignee will need to contact the seller in order to resolve the deny situation.
For a CA transaction, this indicates that the Apply Credit Allocations option in the Allocations > Credit > Manage > Credit Allocation Setup page was selected, but no credit allocation was created and attached to the allocation record. The seller needs to go the Allocations > Credit > Manage > Credit Allocation Setup page and either unselect the Apply Credit Allocations option or create and attach a credit allocation to the allocation record.
For a CA transaction, this indicates that the Apply Product Allocations option in the Allocations > Product > Manage page was selected but no product allocation was created and attached to the allocation record. The seller needs to go to the Allocations > Product > Manage page and either unselect the Apply Product Allocations option or create and attach a product allocation to the allocation record.
For a CA transaction, this indicates the consignee has exceeded a limit established by a credit allocation for the consignee at this terminal. The consignee will have to contact the seller in order to update the credit allocation.
For a CA transaction, this indicates the consignee has exceeded a limit established by a product allocation for the consignee at this terminal. The consignee will have to contact the seller in order to update the product allocation. A Deny 10 code can also indicate that the product allocation was not correctly setup with DTN TABS. PetroDex Support can review the Allocations > Product > Manage page to be sure that a product allocation record was created, applied, and activated. PetroDex Support will also check to be sure that a Start Amount and Refresh Amount greater than zero were entered into the product allocation record. For a Deny 10 code, a Global Product Override may be issued with the seller's explicit, written approval only
For a CA transaction, this indicates the consignee has used up a one-time, pre-approved allocation. The consignee will need to contact the seller in order to update the allocation. .
Indicates that the transaction was not an allowable DTN TABS transaction (CA, BB, CB, PLA, BBL, or CBL). This typically occurs when TAS programming encounters an error when building the TABS transaction. PetroDex Support will contact the terminal to resolve the programming issue. A Deny 12 code can also indicate that the customer was set up without an Open allocation record or any other allocation record. The seller will need to work with PetroDex Support to check the Allocations > Product > Manage page and add an allocation if needed.
Indicates that the transaction was not the correct length to meet DTN TABS standards. This typically occurs when TAS programming encounters an error when building the TABS transaction. PetroDex Support will contact the terminal to resolve the programming issue.
Indicates that the Terminal Control Number (TCN) on the terminal record is invalid. You may need to re-enter the TCN for the terminal record on the Data Management > Terminals page.
Indicates a programming error in the transmission from TAS. PetroDex Support will contact the terminal to resolve the programming issue.
Indicates a programming error in the transmission from TAS. PetroDex Support will contact the terminal to resolve the programming issue.
Indicates that DTN TABS is down. Contact PetroDex Support for assistance.
Contact PetroDex Support for assistance.
Indicates that the Consignee Number was incorrectly entered or that the Consignee Number as entered does not exist within your DTN TABS database. Can also indicate that the consignee is not assigned to load product from the terminal. Make sure the Consignee Number or ID used by the terminal matches that in your DTN TABS system and that the consignee is assigned to the terminal.
Indicates that the Credit Name or ID was incorrectly entered or that the Credit Name/ID as entered does not exist within your DTN TABS database. Make sure the Credit Name or ID used by the terminal matches that in your DTN TABS system.
Indicates that the Seller ID was incorrectly entered or does not exist within DTN TABS as entered. Make sure the Seller ID used by the terminal matches that in your DTN TABS system.
Indicates that the Terminal ID was incorrectly entered or that the Terminal ID as entered does not exist within your DTN TABS database. Make sure the Terminal ID used by the terminal matches that in your DTN TABS system.
Indicates that DTN TABS was unable to match a CA or LA transaction with a CB or BL transaction within the Seller’s specified time frame. Thus the CA or LA record was dumped. When the BOL record finally came through, DTN TABS was unable to match it with the corresponding CA or LA transaction because it no longer existed. If you see a lot of RNF: BOL error codes on your Transaction Log Report, you may wish to contact Telvent DTN and increase the amount of time that Telvent DTN should hold CA or LA transactions.
|
Contact Support - North America (N. A.) and Global Email Us (Global): TABSGlobalSupport@dtn.com
Call Us (Global): 855-493-0260
North America Hours: M-F, 7:00AM-6:00PM CT Global Hours: M-F, 8:00AM-7:00PM CET
To see whether to contact
us via email
|
Take the survey: DTN TABS Help Center feedback
|
DTN TABS® Help Center Copyright © 2019 DTN . |
