You must assign an application class to every application that wants to use the BRF.

You can only create a maximum of one application class as the original in a system. In doing so, you ensure that different applications using the BRF do not define the same application class by chance, thus having an impact on one another.

In addition, development partners or customers must ensure that they are operating in their assigned namespace.

From a technical point of view, an application class is a unique identifier, serving as the leading key field in almost all BRF tables. This means that BRF access across application classes is expressly forbidden.