The following errors describe the GISB standard error codes and how they are used by NrG's EDM implementation. Wherever possible NrG has used the standard error codes and messages but in some cases we have also added additional codes to provide better feedback in the event of error conditions not identified in the GISB EDM Implementation Guide. All non-standard codes and additional descriptive text are displayed in red.

EDM Protocol Errors

These errors may be generated as responses to incoming EDM requests, and indicate that there were problems with the message received to the extent that it could not be processed. No trans-id value will be returned in these cases.

EEDM100: Missing FROM DUNS
EEDM101: Missing TO DUNS
EEDM102: Missing Input Format
EEDM103: Missing Data File
EEDM104: Missing Transaction Set
EEDM105: Invalid FROM DUNS - must be 9 digits
EEDM105: Invalid FROM DUNS - must be numeric
EEDM105: Invalid FROM DUNS - not found
EEDM106: Invalid TO DUNS - must be 9 digits
EEDM106: Invalid TO DUNS - must be numeric
EEDM106: Invalid TO DUNS - not found
EEDM107: Invalid Input Format - must be x12 or error
EEDM108: Invalid Transaction Set - %s not found
EEDM108: Invalid Transaction Set - format is Gnnnaaaa
EEDM108: Invalid Transaction Set - must be 8 characters
EEDM999: Invalid HTTP Request Method - must be POST
EEDM999: Invalid MIME Format - must be multipart
EEDM999: Mandatory data elements missing in error response
This error indicates that one of the items in an error notification text block is missing. All of orig-from, orig-to, orig-input-format, resp-time-c, resp-server-id, resp-trans-id, request-status and comments are expected to be present.
EEDM999: No EDM Receiver found for DUNS '%s' Transaction-Set '%s'
NrG sets up an EDM receiver site for each GISB transaction-set code that may be received from a company. This error indicates that no setup has been completed for the indicated company and transaction-set combination. Incoming EDM requests are not accepted until this setup has occurred because there is no way of sending back EDM responses once the transaction has been received.

Other Errors

These errors may be generated during processing of an EDM request and will be sent back to the sender's EDM receiver site.

EEDM200: Security violation; %s not authorized for %s on %s
NrG sets up security based on who the EDM request is from, who it is destined for and what type of transaction it is. This error indicates that the sender has not been authorized to send the indicated type of transactions to the receiver.
EEDM300: Failed to translate X12 file
This error indicates that the NrG EDI X12 translator was unable to translate the received X12 transaction. This may be due to bad X12 data, missing partner profile setup information, etc.
EEDM301: Bad inbound 997 functional acknowledgement
NrG processes inbound 997 functional acknowledgement transactions by looking up the X12 control number specified in the file for the "from company" and "transaction-set". This error indicates that the combination of "from company", "transaction-set" and "control number" in the X12 file is not recognized as corresponding to a previously sent outbound EDM transaction. The combination does not acknowledge any transactions that originated at NrG.
EEDM400: Transaction-set mismatch
During processing of EDM transactions NrG checks to ensure that the transaction-set code listed in the EDM request matches the transaction-set code in the associated X12 file. This error indicates that the EDM request specified one transaction-set while the X12 file specified another.
EEDM604: ViaCrypt PGP Error %03d (%s)
During decryption of an inbound EDM transaction the ViaCrypt PGP product may return a specific error code. This error indicates the PGP error code and associated message. In practice, for these types of failures, the error produced is almost always code 8 (Invalid File Op Error).
EEDM605: Decryption Failed (%03d)
During decryption of an inbound EDM transaction the NrG processes around PGP check to ensure that the digital signature matches the EDM "from company". This error indicates that the signatures don't match or that some other problem has caused the signature check to fail.
EEDM999: No Current PGP Key found for EDM Receiver %d URL %s
NrG maintains a list of one or more PGP public keys for each EDM trading partner URL and determines which key to use based on an effective date. This error indicates that for the current date, no valid PGP key could be found for the associated URL. There may be none set up, or the current list of keys has none that are active on the current date.

NrG Internal Errors

These errors may be generated as responses to incoming EDM requests or during processing of the requests. They indicate internal problems at NrG.

EEDM999: Cannot append to log file
As each EDM transaction is received NrG makes an entry in a log file to aid in tracking transactions. This error indicates that there is a problem with creating this log entry.
EEDM999: Cannot write received file
Upon receipt of an EDM transaction NrG saves the incoming data to disk. This error indicates that the data could not be saved.
EEDM999: edm_err_txn -- $ret_str
Upon receipt of an EDM error transaction NrG looks up the various data elements and attempts to relate the error message back to a previously sent outbound EDM transaction. Once this has been completed successfully a new transaction ID is generated and returned to the EDM sender. This error indicates that for some reason the related message could not be found or updated or a new transaction ID could not be created.
EEDM999: edm_new_txn -- $data
Upon receipt of an EDM X12 transaction NrG looks up the various data elements to ensure that they are valid and then creates a transaction ID to return to the EDM sender. This error indicates that for some reason the transaction ID could not be created.
EEDM999: Invalid Transaction Type: %d
Upon receipt of an EDM transaction NrG looks up the GISB transaction-set code and translates it into an internal transaction type identifier. This type identifier is then used to look up an internal software service code. This error indicates that the lookup for software service code was unsuccessful. Note that this error should not occur as the mapping from GISB transaction-set code to NrG transaction type to NrG software service code is all maintainted in one database table.


Updated 05/04/00