FTZ Management: Preparation - Validation Status and Transaction Correction
The
Validation Status
screen is used for scanning transactions to determine if any corrections need to be made. Later, the screen can be used to confirm these corrections were made. The Validation Screen
can be utilized after the Staging Data Transfer
step. This screen can be accessed by choosing Validation Status
from the Preparation
menu. - To begin the validation process, clickValidate.
If the workflow is currently running, theValidatebutton will be temporarily disabled until the validation is complete. During validation, the following message will display: 
- After the validation has been completed, the following message will display:
- ClickRefreshto update immediately, or you can wait for theValidation Statustable to automatically update every four seconds. If any validation errors appear within the “Warning” column, use theTransaction Correctionscreen to correct.
- Once changes are made, either clickRevalidateon theTransaction Correctionscreen or return toValidation Statusand clickValidateto run the workflow again.
Transaction Correction (Validation Errors)
The
Transaction Correction
screen is used for correcting transaction errors and warnings identified in the Validation Status steps.To access the
Transaction Correction
screen:- ChooseTransaction Correctionfrom thePreparationmenu.
- Use theFilter fielddrop-down to choose a filter option, then use theFilter valuedrop-down to choose an error type.
- Error results and warning results will be separated into separate tabs.
- To correct an error or warning identified by the previousValidation Statusprocess, choose an error/warning from the grid and selectEdit. Make all necessary changes and save.
- ClickEditto open theEdit Transactionscreen. All fields containing a validation error will be surrounded in red. Make all necessary changes, and then clickSave.
- Once all errors in theValidation Errorsscreen have been resolved, clickRevalidateat the top of the screen. This will redirect the user to theValidation Statusscreen. Run the validation workflow again. Repeat this process until all errors have been resolved.
Transaction Correction Table
Definitions: Errors vs. Warnings
Definitions: Errors vs. Warnings |
Description |
|---|---|
Error |
A hard stop in the user's daily processing. This data is invalid or missing and must be resolved before the user can move beyond the validation step. |
Warning |
A potential issue with complete data. This data is also invalid, but you can move beyond the validation step and return to resolve/ignore warning at a later time. If only warnings remain and you wish to ignore the warnings to continue with processing, do not click Revalidate. Revalidation will return the warnings each time until they are resolved. |
Source Fields and Default Sources
Many of the fields in the FIFO transaction tables (txdFIFOProcessing/HTSValues) have source fields for the data elements that can be utilized to pull the data from various maintenance tables:
SOURCE FIELD |
DATA SOURCE |
|---|---|
I |
Item Master |
M |
Manufacturer ID |
H |
HS Codes |
C |
Item Master Custom Rules |
P |
Pre Receipts |
(Blank) |
User Company’s ERP System |
You can edit data in
FIFO Processing
or Transaction Correction
to set ‘Default Sources’ for any of the following source fields. Default Source = I (tmdItemMaster/HTSValues) |
|---|
ProductTypeCodeSource |
ProductDescSource |
NaftaCertifiedSource |
TxnQtyUomSource |
WeightSource |
WeightUomSource |
StatusCodeSource |
CountryOfOriginSource |
ManufacturerIDSource |
HtsIndexSource |
HtsNum2Source |
ValueSource |
Value2Source |
CurrencyCodeSource |
AltValueSource |
AltValue2Source |
AltCurrencyCodeSource |
HtsUomConvFactorSource |
AddlHtsUomConvFactorSource |
ADDutyRateSource |
CVDutyRateSource |
RCO21Source |
RCO22Source |
RCO23Source |
ReceiptSupplementSource |
RPO11Source |
RPO12Source |
RPO13Source |
DEFAULT SOURCE = H (TMDHTS) |
|---|
HtsNumSource |
SpiCode1Source |
SpiCode2Source |
HtsDescSource |
AdValoremRateSource |
SpecificRateSource |
RptQtyUomSource |
AddlRptQtyUomSource |
AddlSpecificRateSource |
Default Source = M (tmfManufacturer) |
|---|
RelationshipFlagSource |
Note that for positive adjustments (i.e., transactions with TxnCode = ‘APPC’ or ‘APIM’), the system will utilize the Default Source (superseding the Source Field value) for data elements that are relevant to the CBP, such as:
- CountryOfOriginSource
- HtsNumSource
- ManufacturerIDSource
- ValueSource
The following fields are "open" fields that can hold additional FIFO transaction date elements. These allow you to work with the Thomson Reuters implementation team to decide which fields will be of greatest use to your business environment.
Open parent record fields (txdFIFOProcessing) |
Open child record fields (txdFIFOProcessingHTSValues) |
|---|---|
RPO11 |
RCO21 |
RPO12 |
RCO22 |
RPO13 |
RCO23 |
Related Content
-
FTZ Management: Preparation - Loading Integration Files and File Load Manager
Format:
Article,
3 min read
-
FTZ Management: Tools - Handling Shipment Quantity Mismatches in Pending Adjustments
Format:
Article,
1 min read
-
FTZ Management: e214 - Understading the Process
Format:
Article,
1 min read