To make manual post-processing adjustments to a rate file, click an
Import status cell, double click a required import batch or select it and click
Match columns.
The opened
Parsed rates window shows the way the System recognized the column content and matched it to the predefined columns of 5gVision. The olive-colored column headers are 5gVision predefined columns, while the green column headers are columns from the original file. It is possible to drag and drop the green headers to the desired position creating a new match, if you are not satisfied with the automatic processing results. It is also possible to combine two original columns into one by dragging one green column under another and selecting the separator for the merged columns in the
Join by listbox.
The System also makes some minor corrections on the spot, like removing "-" sings from codes or adding time to dates without time. These changes are displayed in the "final" columns (like
Code final).
In case of errors occurred during processing, the opened window will be initially filtered to show errors only (see the full list of the errors in
Parsing errors).
Unlike most of the errors, it is possible to fix the
CountryNotFound ,
BadCountryCode,
?DateFrom,
?DateTill,
NoDateFrom,
NoDateTill, and
DuplCode errors on the spot.
The
CountryNotFound error occurs when the System was unable to find the country name in the reference dictionary. The
BadCountryCode error occurs when the country prefix does not match the prefix defined in the 5gVision DB. As the System processes the file and tries to match the prefixes and names from the rate file to the reference prefixes and names kept in the DB, it is possible to stumble upon a country or code not present in the dictionary (e.g. due to spelling errors and such). You can either change the country records in 5gVision (if you are sure they are the wrong ones) or fix the original file. To repair the error, go to the
Country codes module or invoke the pop-up menu and click
Add country code.
In the opened window you can specify the following parameters:
- Code - the country phone number prefix.
- Full Country Name - the full official name of the country.
- Country name to search for, one or two consecutive names - the name
of the country to search for in processed rate files during the auto import.
Once this name is found, the System will try to match it to the corresponding prefix using
this table. The searched words must be unique across the table. If the first
word of country name is shared among different countries (like "western"),
the parameter should contain two words for the match to be unambiguous (e.g. "western sahara" and "western samoa").
- Dont try to match this code - activate the checkbox, if you want the System to ignore the specified code when matching codes to country names. This may be useful for satellite routes as they are numerous and have too many naming variants.
The
?DateFrom and
?DateTill errors may occur when the System is unable to determine the correct date format, as the date string can result in multiple valid dates. For instance, there is no way of telling whether the following format is Day/Month or Month/Day: 09/11/2014.
Another date-related errors are
NoDateFrom and
NoDateTill, which are signalled when the System expected the original file to contain dates but found none. To fix both kinds of errors, you need to click
Re-parse options in the
Match columns window. A new window will open, similar to the one in
Import rate file, where you can define the required date format and determine whether absence of certain date columns should raise errors or not.
If you get
DuplCode, you can also click
Re-parse options and define how to treat duplicate codes.
After trying to correct these issues, you may click
Re-parse rates in the
Match columns window, and the system will try to process the rate file using new country, date definitions and duplicate codes settings. Please mention that the buttons
Re-parse rates in this module and the
Re-parse sheet in the
Inbox act differently. The first one tries to fix the issues by changing column order right in the DB, which is quicker. But this wont work in all situations, then we need to try doing
Re-parse sheet - loading info anew from file to the DB.
Some errors may be fixed using
Column actions functionality. Column actions for the current batch can be opened using the
Column actions button, or if you click the
Column actions button or the
Edit Column actions to fix errors link in the
Re-parse options window and click , the
ColAction-batch window will appear, filtered to display column actions for this batch only (see
Column actions).
All other errors require alterations of the original file for now, however you can disable the row with the error and import the file without it. To disable one or several rows, select them, invoke the pop-up menu
and click
Disable selected rows.
In order not to repeat the manual column match process again for the same Partner, it is possible to save the resulting column layout. Once all processing is complete, click
Save config for Partner in the
Match columns window. This will store the selected match for this current Partner, which can be viewed in the
Parsing config table. This also copies batch column actions back to the partner column actions config (see
Column actions). When the System gets another rate file from the same partner, it will try to parse it using the stored options. Please note that all the changes to batch matching process are valid for the batch only and do not affect the partner config unless saved to it.
Once all the preparations are complete and the batch has no errors or all erroneous rows are disabled, you may proceed with the next step in batch processing and import the rates into the
Import edit table (click
Move to Import edit) or directly into the Main
RateCust /
RateVend table (click
Move to Main, see
Move to Main from Parsing log / Import edit / Compare).
If you loaded a push/target list on the previous step, you can make a push/target report right from the
Parsed rates window using the
Push/target report button (see more in
Push/target).