Profile data

The following requirements apply to all profile data sources used in trigger systems.

  • Profile data is not required. However, if profile data is not defined, all the data used in a trigger system (including any required profile data) must be included in the transaction data.
  • When profile data is defined, for every customer represented in your transaction file, there must be a single record for that customer in your associated profile.

    When a transaction file is associated with a profile flat file, the system ignores transaction records without an associated profile record, and ignores profile records without an associated transaction record. In both cases, these orphan records affect processing efficiency.

  • When profile files are used, a profile file must exist for each set of transactions with the same date suffix. The date suffix of the profile file must match that of the transaction files. A profile file with a different date suffix cannot be used.