Show TOC
# Combining Authorizations

In many cases, two authorizations can be combined even if all their dimensions are filled. This process is called Merging.

In the simplest case, there are two identical authorizations.

The following examples are more complex.

Example 1:

Authorization 1:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Pencil |

Authorization 2:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Case |

All combinations in the time period 1999-2002 with Pencil or Case are authorized. Both Pencil and Case are authorized, which means a logical OR. It therefore makes sense to simplify the two authorizations into one single authorization, that is, to combine them into a "mixed" authorization.

Result:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Pencil, Case |

The general rule for this is as follows:

Authorizations can be combined if they differ in a maximum of one dimension (entries for a characteristic).

Example 2:

Authorization 1:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Pencil |

0CUSTOMER |
Smith |

0COUNTRY |
DE, US |

Authorization 2:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Case |

0CUSTOMER |
Smith |

0COUNTRY |
DE, US |

These can be combined to produce:

Result:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Pencil, Case |

0CUSTOMER |
Smith |

0COUNTRY |
DE, US |

Example 3:

In this case, an authorization has all authorizations for all characteristics. This can cover all other authorizations with the same characteristics.

Authorization 1:

Characteristics | Values |
---|---|

0CALYEAR |
* |

0PRODUCT |
* |

0CUSTOMER |
* |

0COUNTRY |
* |

Authorization 1:

Characteristics | Values |
---|---|

0CALYEAR |
1999-2002 |

0PRODUCT |
Case |

0CUSTOMER |
Smith |

0COUNTRY |
DE, US |

These can be combined to produce:

Result:

Characteristics | Values |
---|---|

0CALYEAR |
* |

0PRODUCT |
* |

0CUSTOMER |
* |

0COUNTRY |
* |

0BI_ALL is a special authorization of this type, which automatically contains all authorization-relevant characteristics, with authorization for all respective values.

Note:

The reduction in the number of authorizations does not influence the authorized combinations. It is an optimization that is only made for performance reasons. This is not logically necessary. In some cases, authorizations are not combined because it would take too much time to recognize and take advantage of the respective situation.

An example of a case in which authorizations are not combined is if there are two authorizations that have intervals in all dimensions. In each dimension of the first authorization, the interval is selected in such a way that it overlaps the interval of the second authorization. It would be possible to combine this into one authorization, but because it would take too much time to recognize, this optimization is not made.