One-to-One

Two variations are possible, the classic master-slave relation and the inline relation where the data is concentrated in a single record.

Figure 193 Schematic

Master

In a master relation, the master record contains the pointer to the slave record. This reference can be modified without impacting the slave record or other master records. For example, changing the ordering customer account on the payment will have no impact on the actual static data account with that identifier. A payment can be made from only one ordering customer account and that account field is unique in that payment.

Example: Payment - Payment Account

Payment 1 Payment Data Reference to Account 1 -> Account 1 Data 1

Table 192 Master to Slave Representation

Figure 194 Master

Inline (Optimized One-to-One)

Inline entities are entities where the data forms an integral part of the parent data. For example, a party has an address. If this party.address is modified, it is modified for that party only. When a second party has the same address, those modifications will have no impact on the second party. Every party has separate address information stored within its own data record.

Example Party – Address

Party 1 Party Name Party Address | Street | City

Table 193 Inline Representation

Figure 195 Inline