Object to object relationships
Consider the object to object relationships, which associate logically related objects, to be recorded in the FTM data model.
The FTM data model can record the following distinct types of relationships:
- Inherent hierarchical relationships
- These are the relationships between the transmissions, batches, transactions, and so on, within a transmission file. They are essentially defined by the mapping specification and represented in the data model as direct foreign key references.
- Application process relationships
- These relationships are produced during transaction processing. For example, when a payment transaction must be repaired, a RepairRequest transaction, which is related to the original payment transaction, is created.
Note: By general convention, when there is a named relationship between two transactions, and those two
transactions have 1 to 1 relationships with respective transmissions, the two transmissions will be given the
same named relationship as the two transactions.
The following figure shows the relationships between the FTM objects for the non batch payment use case. In this single payment use case, the relationship between the payment origination objects and the RepairRequest objects is shown as optional since it only occurs for an invalid payment.
The following figure shows the relationships between the FTM objects for the batch payment use case. In this batch payment use case, the relationship between the payment origination objects and the RepairRequest does not exist because the batch use case does not consider repair of invalid payments.
