Before import from the interface tables into the TCA Registry, a record must pass import validations. All elements of an interface table record must succeed, or the entire record is considered with error.

Records that fail validations are marked, and all errors for one record are captured after the entire record is validated. After validation, only successful records are imported into the Registry.

The types of validations include:

• Lookups. For example, the HZ_ORG_CONTACTS.DEPARTMENT_CODE value should be from the DEPARTMENT_TYPE lookup. If the HZ: Allow Import of Records with Disabled Lookups profile option is set to Yes, then values that reference disabled lookups are still valid.

• Foreign keys. For example, HZ_LOCATIONS.COUNTRY should have a foreign key to FND_TERRITORIES.TERRITORY_CODE.

• Requirements, if a value is mandatory or conditionally required. For example, HZ_CONTACT_POINTS.CONTACT_POINT_TYPE is mandatory.

• Cross-column dependencies. For example, EDI as the value for HZ_CONTACT_POINTS.COMMUNICATION_TYPE is allowed only if the value for HZ_CONTACT_POINTS.OWNER_TABLE_ID is a party ID of an organization.

• TCA columns that are not updateable. Values that are entered for such columns are ignored without error.

• Flags that should have Y, N, or NULL as values.

• Flexfields. If the HZ: Validate Flexfields During Import profile option is set to Yes, then flexfields are validated based on the flexfield setups.

  These tables have flexfields:

  • HZ_CONTACT_POINTS

  • HZ_LOCATIONS

  • HZ_PARTIES

  • HZ_RELATIONSHIPS

• Address sharing. Multiple parties cannot share a single address. If the same address applies to two parties, you must enter the address for each party.

• Business rules.

The parent and child relationships of entities also affect whether a record succeeds or fails validation. See: Interface Table Parent and Child Relationships.

Other Sources

• Bulk Import Interface Tables, Oracle Trading Community Architecture Reference Guide