Correcting Errors
In addition to processing status codes, which indicate the general state of documents within the import or export process, the system generates detailed error messages during eCommerce processing. These messages display on the terminal running the process session and are summarized on a number of reports. How you correct an error depends on where in the process the error occurred. lists processing error messages and related corrective actions.
Example: The system detects an error while loading an imported file into the exchange file repository (status 11). The document is copied into an error file that is placed in the directory specified in eCommerce Control.
If the load error involves the way mapping is defined in eCommerce, resolve the mapping problem in the appropriate maintenance program. Then, in Document Import (35.1), set File Type (New/Error) to Error. The selection list shows only error files, whose names begin with the prefix specified in eCommerce Control. Select the appropriate file, then rerun the import.
Sometimes the load error originated in an SNF file from the EC subsystem—for example, missing data in a mandatory field. Contact the trading partner to have them correct the file. In that case, you would start the import over again, treating the corrected file as new input.
In a similar case involving an exported file—when required data is missing from a business document, producing a status 31—correct the document in the appropriate maintenance program. Then, reexport it as a new document.
When documents successfully complete the load or transfer process and are placed in the document repository, you can fix some errors there. eCommerce provides a set of programs you can use for modifying data in the exchange file or application document repository.