Non Numeric EONUM and the Overflow Elcode
This is the Dragon's Mouth...
The EONUM field in the HDMS is numeric. In the BCD, it is alphanumeric. The conversion requires the data to be converted to a numeric field.
Overflow Elcodes
If you have overflow ET records, be certain to modify the Overflow ET records in exactly the method described below.
Overflow ET records are records created to attach new EOR records because the original (or "true") ET has exhausted its 999 available EONUM possibilities. If you have none of these, you can skip this configuration step, but go on to the EONUM QC further down on this page.
However, each time you configure more overflow ET records, you must do all the QC steps on this page (even if you already ran them before). This is because the configuration of additional overflow ET records can produce duplicate EONUM values (or invalid EONUM values) if the configuration is not done correctly.
- Identify your overflow ET records and the "true elcode" for each.
- Open each of the overflow ET records (not the "true elcode" record).
- At the beginning of the GTAXCOM field (or delete the data in GTAXCOM before editing), type the following:
Overflow for {true_elcode}*{qualifying_number}
Where
{true_elcode} = the true elcode (should be different than the elcode of this record, and it should refer to an existing ET record)
{qualifying_number} = the number to add to each eonum (must be in multiples of 1000)
Example:
(In the ET for ABNYF0706X), the GTAXCOM field has: Overflow for ABNYF07060*1000
(In the ET for ABNYF0706Y), the GTAXCOM field has: Overflow for ABNYF07060*2000
QC Procedure
First execute IS_OVERFLOW at TCL. This generates a message that will verify what conditions the program is checking to determine if an ET represents an overflow record. In the case where this document and the message differ, trust the message.
- SELECT ET WITH IS_OVERFLOW
- LIST ET IS_OVERFLOW GTAXCOM
- Examine the list and make certain that all your overflow ET records appear on the list. If you see any error messages, fix the configuration and re-run the QC. If one of your overflow Elcodes is not listed, go to that record and make certain it is properly configured.
Numeric EONUM QC
This QC does not examine EONUM directly, but rather examines the conversion symbolic field. The
Default Conversion will convert an EONUM that begins with a letter and ends with two digits into a 4-digit EONUM value; in some cases, the resulting EONUM may even have 5 digits, but usually this is the result of an overflow elcode configuration.
QC Procedure
- SELECT EOR WITHOUT { NUM( {HDMS_BEST_EONUM} ) }
- LIST EOR EONUM HDMS_BEST_EONUM JUSTLEN T35
- Most of the errors encountered by this QC will require you to execute a CODE CHANGE to properly convert the error records to a number (sometimes the letter "o" needs to be replaced with a zero).
Unique ELCODE*NATION*STATE*EO_NUM
In the HDMS, every EO must be unique on four attributes (in the HDMS system, this is ensured via the ELEMENT_SUBNATIONAL_ID and the EO_NUM).
QC Procedure
Run a tally on the HDMS_EOR_KEY field.
- From the Main Menu, choose Reports | Report Library | General Use | Tally. Then choose screen or dos file (whichever you prefer).
- Choose "Specify All Conditions..."
- For "Database:" enter EOR
- For "Field to tally on:" enter HDMS_EOR_KEY
- For "Minimum count to report:" enter 2
- Press F9 to execute the tally.
- Examine the results. If you see duplicates on the report, chances are you need to re-configure the overflow elcode to a higher qualifying number. This will happen if the element in question has alphanumeric EONUM values on the "true" elcode whose conversion may generate an EONUM as high as 3599. Make certain in such a case to set the qualifying number higher than 4000.
- Re-run the QC until no duplicates are reported.
Default Conversion
1) Ensure that EONUM is a number:
- If EONUM is a number, nothing happens.
- If EONUM starts with a letter, that letter is converted to a number that is the position of the letter in the alphabet plus 9 (e.g., "A" turns into "10"; "B" turns into "11").
- Otherwise, an error is reported.
2) If the EOR is connected to an overflow ET, get qualifying number from the configured ET, then add that number to the EONUM.
Back to DataQc