After you submit a file load, party records that pass all validations are successfully loaded into the interface tables. If any of the party records fail validation, then the record is marked with error and not loaded. The file load status is Partially Completed with Errors, Awaiting Resolution.
To resolve file load errors you can:
Correct specific types of errors online by:
Attribute: Correct all errors for one attribute at a time, across all party records. Use this option when errors are concentrated around particular attributes. A party record with errors, however, cannot be reloaded until all of its attributes with errors are corrected. See: Correcting Errors by Attribute.
Party Record: Correct all errors for one party record at a time, across all attributes. When all attributes for the party are corrected, that record is immediately revalidated for loading. See: Correcting Errors by Party Record.
You can switch between these two methods until you resolve all errors that are correctable online. See: Errors Correctable Online.
Export records with any type of errors to a file and correct errors offline. See: Correcting Errors Offline.
If the number of errors at the attribute level exceeds 200, then you must correct errors offline. Even if not, you might choose this option if there are many errors, or if you prefer to work with files offline. After you correct errors online, if you still see that there are errors, then those are errors that you can only correct offline.
Attention: You can export records for offline correction only once for each file load. You can still correct errors online after you export, but it is up to you to keep track of your work if you correct errors both offline and online. Consider your options and strategy for error resolution before you export.
These type of errors can be corrected online, either by attribute or party record.
Data Type: The source attribute contains a nonnumeric value for a target attribute that takes only numeric values.
Date Format: The source attribute value is a date in a format that differs from what is defined for the file load. See: Defining File Loads.
Lookup: If the target attribute uses lookups, then the source attribute value is validated against the lookup. For example, if a Gender target attribute uses lookup values Female and Male, the source attribute would fail if the provided value is anything else, such as F or M.
Mandatory Attributes: Some target attributes are mandatory, either conditionally or unconditionally. The corresponding source attributes would fail if they do not contain values for mandatory target attributes. For information on some of these validations, see: Mapping Rules and Validations, and Bulk Import Interface Tables, Oracle Trading Community Architecture Reference Guide.