Message type: E = Error
Message class: AD - Data Dictionary application messages
Message number: 736
Message text: Foreign key &-& (enter valid cardinality)
You have entered a semantic foreign key without specifying the
cardinality.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enter a cardinality. The following cardinalities are possible:
C There may not be more than one dependent record for each record in
the check table.
1 Exactly one dependent record exists for each record in the check
table.
CN Any number of dependent records may exist for each record in
the check table.
N At least one dependent record must exist for each record in the
check table.
Error message extract from SAP system. Copyright SAP SE.
AD736
- Foreign key &-& (enter valid cardinality) ?The SAP error message AD736, which states "Foreign key &-& (enter valid cardinality)," typically occurs in the context of data modeling or when defining relationships between tables in the SAP system. This error indicates that there is an issue with the foreign key relationship you are trying to establish, specifically regarding the cardinality of the relationship.
Cause: Invalid Cardinality: The cardinality defined for the foreign key relationship does not match the actual data model. For example, if you are trying to define a one-to-many relationship but the data suggests a many-to-many relationship, this error will occur. Missing or Incorrect Foreign Key Definition: The foreign key may not be properly defined in the database schema, or the referenced primary key may not exist. Data Integrity Issues: There may be existing data that violates the foreign key constraints, leading to inconsistencies. Configuration Errors: Incorrect settings in the data model or configuration settings in the SAP system can
Get instant SAP help. Sign up for our Free Essentials Plan.
AD735
Foreign key &-& (flag as a semantic foreign key)
What causes this issue? A foreign key must be flagged either as a semantic foreign key or as a screen foreign key. In the case of a screen foreign ke...
AD734
Foreign key &-& (indicate the foreign key type)
What causes this issue? A foreign key must be flagged either as a semantic foreign key or as a screen foreign key. In the case of a screen foreign ke...
AD737
Check field &-& missing from foreign key field definition
What causes this issue? The (check) field with which the foreign key of his table is defined is not contained in the assignment of foreign key fields...
AD738
& & too long for logging (must be < &)
What causes this issue? The logging flag is set in the technical settings for this table. The logs are written to the database table DBTABPRT as defa...
Click on this link to search all SAP messages.