about ddic

[Former Member]

what is meant by cardinality.?

can u explain clearly

points will be awarded

[Former Member]

cardinality means the number of records that can be contained in a internal table.

0..n means: minimum of zero records and maximum of 'n' records can be contained in the internal table.

0..1 means: minimum of zero records and maximum of '1' records can be contained in the internal table.

1..n means: minimum of one records and maximum of 'n' records can be contained in the internal table.

1..1 means: minimum of one records and maximum of '1' records can be contained in the internal table.

Regards.

Ashish.

[Former Member]

hi thr....

The cardinality (n:m) describes the foreign key relationship with regard to the number of possible dependent records (records of the foreign key table) or referenced records (records of the check table).

The left side (n) of the cardinality is defined as follows:

n=1: There is exactly one record assigned to the check table for each record of the foreign key table.

n=C: The foreign key table may contain records which do not correspond to any record of the check table because the foreign key field is empty. This can occur for example if the field of the foreign key table is optional, in which case it does not have to be filled.

The right side (m) of the cardinality is defined as follows:

m=1: There is exactly one dependent record for each record of the check table.

m=C: There is at most one dependent record for each record of the check table.

m=N: There is at least one dependent record for each record of the check table.

m=CN: There may be any number of dependent records for each record of the check table.

do reward if helpful

[Former Member]

Hi swetha,

The cardinality (n:m) describes the foreign key relationship with regard to the number of possible dependent records (records of the foreign key table) or referenced records (records of the check table).

"Cardinality" is a basic technical term related not just to

SAP

Please find below the explanation for the same

http://help.sap.com/saphelp_nw70/helpdata/en/b2/fbb859c64611d295dd00a0c929b3c3/content.htm

Regards

Byju

[Former Member]

Hi,

Check this Thread [;

Regards

Sandipan

[prasanth_kasturi]

cardinality :The cardinality (n:m) specifies the number of dependent (target) and independent (source) entities which can be in the relationship.

The two sides of the cardinality expression have the following significance:

n = 1:

There is exactly one independent entity for each dependent entity.

n = C:

There may be entities of the dependent entity type which have no relationship to an entity of the source entity type.

m = 1:

There is exactly one dependent entity for each source entity type entity.

m = C:

There is at most one dependent entity for each source entity type entity.

m = N:

There is at least one dependent entity for each source entity type entity.

m = CN:

There are any number of dependent entities for each source entity type entity.

reward if helpful

prasanth

[Former Member]

Hi

The cardinality (n:m) describes the foreign key relationship with regard to the number of possible dependent records (records of the foreign key table) or referenced records (records of the check table).

The left side (n) of the cardinality is defined as follows:

n=1: There is exactly one record assigned to the check table for each record of the foreign key table.

n=C: The foreign key table may contain records which do not correspond to any record of the check table because the foreign key field is empty. This can occur for example if the field of the foreign key table is optional, in which case it does not have to be filled.

The right side (m) of the cardinality is defined as follows:

m=1: There is exactly one dependent record for each record of the check table.

m=C: There is at most one dependent record for each record of the check table.

m=N: There is at least one dependent record for each record of the check table.

m=CN: There may be any number of dependent records for each record of the check table.

[Former Member]

Hi Sweta,

The cardinality of the foreign key relationship describes, for each value in the check table, how many rows of data are allowed to be in the foreign key table. It is entered on the Create Foreign Key screen (refer to Figure 4.3). Cardinality is described as X:Y, where X refers to the check table and Y refers to the foreign key table. X can only have the values 1 or C, and Y can be 1, C, N, or CN.

The values of X mean:

1: If the application program deletes a row from the check table it will also delete the corresponding rows from the foreign key table. For example, if the application program deletes the value US from the check table, it will delete all rows from the foreign key table where land1 = US. In other words, if there is a value in the foreign key table, there is always one and only one row having that value in the check table.

C: Deletes are allowed from the check table without deleting the corresponding rows from the foreign key table. In other words, there can be values in the foreign key table without corresponding values in the check table.

The values of Y mean:

1: There is always one, and only one, row in the foreign key table for each row in the check table.

C: There is, at the most, one row in the foreign key table for each row in the check table.

N: There is always at least one row in the foreign key table for each row in the check table.

CN: There might or might not be rows in the foreign key table for each row in the check table.

Cardinality is not enforced by the R/3 system. Specifying cardinality is optional, and the system will not check cardinality to determine whether that update should be allowed to take place if an ABAP/4 program updates a table. The only time cardinality is used is when you create an aggregate object in the DDIC.

Regards,

Phani,

Points If Helpful.