|
The following rules apply to
interface providers:
|
·
|
When a table is defined as interface provider, all its columns
AND the domains for these columns are also turned into interface
providers. |
Afterwards, you can undo this
and mark specific columns and domains as NOT being an interface
provider.
|
·
|
When a table is defined as interface provider, and the table is
part of a subtype constelllation, the whole constellation will
become an interface provider. |
|
·
|
For domain interface providers with allowed values, these
values are always interface providers. |
|
·
|
The primary key columns of an interface provider table must be
interface providers. The Interface field cannot be cleared. |
|
·
|
When the Interface field for a column is cleared, the
underlying domain is still an interface provider. |
|
·
|
For a domain, the Interface field can only be cleared when
there are no column interface providers based on this domain. |
|
·
|
For a batch job that is an interface provider, external sets
with their elements that are an Input Parameter Set or Output
Parameter Set are automatically turned into interface
providers. |
|
·
|
External sets cannot manually be set or removed as interface
provider. This is done automatically. |
The following rules apply to
interface consumers:
|
·
|
On the consumer side, you cannot define a subtype table with an
interface table as its supertype. |
|
·
|
On the consumer side, you cannot define a new relationship with
an interface table as the child table in the relationship. |
|
