cancel
Showing results for 
Search instead for 
Did you mean: 

Entity Type and Relationships

Former Member
0 Kudos

Hi All,

I am creating new data model, I am confused what entity type goes with what relationships.

Can someone pleased explain while creating relationships below points:

1)What does From entity stands for and To entity type stands for?

2) Entity type 3 relationship with Type 1 Entity?

3)Cardinality - 0:N ,1:N and 1:1 stands for?

Please ,i ts a request don't provide help.sap links .

Kindly explain.

Regards,

Swati

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member193350
Active Participant
0 Kudos

Hi Swati,

Let me try to explain you in simple terms.

1. What does From entity stands for and To entity type stands for?:-

To Entity means the (referencing entity type) and the from-entity (referenced entity type), like suppose Material(MARA) and Plant(MARC),

so the relationship is from Material to Marc, as a single material can be extended to many plant hence we have relationship as:-

From         To          Cardinality

Material     MARC     1:N

2. Entity type 3 relationship with Type 1 Entity?

From        To       Cardinality   Type:

Type3    Type1    1:N/0:N         Referencing

3. Cardinality - 0:N ,1:N and 1:1 stands for?

0:N means optional-to- many relationship  date of death--->person

1:N means 1 to many relationship   like person-->books

1:1 means 1 to 1 relationship          like person-->weight

Hope it helps.

Regards

Prateek Agarwal

Former Member
0 Kudos

Hi Parteek,

Thanks,

I am trying Type 1 and Type 3 entity relationship, I am getting error.

Regards,

Swati

former_member193350
Active Participant
0 Kudos

Hi Swati,

What error are you getting and what are r/ship you are trying to maintain?

Regards

Prateek Agarwal

Former Member
0 Kudos

Hi Prateek,

I am assigning Type 3 entity in From entity type and Type 1 in To entity type with relationship Referencing and Cardinality 1:N.

But it shows :

Number of leading entity types is invalid

The following error is

For entity types with storage and use type 3 for which the check table is predefined by the data element or domain, the other key fields in the check table must be mapped using relationships with Leading as the relationship type. The check table for entity type ZPTCR contains 2 additional key fields. However, &V4 leading entity types are defined using relationships.

Regards,

Swati

former_member193350
Active Participant
0 Kudos

Hi Swati,

As per the above screenshot above you need to maintain one additional leading entity type, like in your scenario you are havig a type 3 entity ZPTCR contains some check table which is more then 1 key field so if you can go to entry/help cjheck tab in your table you ca find that check table name.

so you need to assign the relationship between that check table ad your's type3 entity check table as leading with cardinality 1:N.

Hope it helps.

Regards

Prateek

Former Member
0 Kudos

Hi Swati

Please refer below chart

Former Member
0 Kudos

Hi Sanjay,

Thanks for your reply.

Regards,

Swati

Former Member
0 Kudos

Hi Prateek,

Thanks for your reply,

Will try and let you know if the issue is resolve.

Thanks & Regards,

Swati

Former Member
0 Kudos

Hi Swati

Please refer

https://help.sap.com/erp_mdg_addon61/helpdata/en/89/4879b23c71449e8b4af0d403d39513/content.htm?frame...

MDG Data Model: Details
This section describes the entity types and the relationship types used in the MDG Application Framework (MDGAF).
  1. Entity TypesAn MDG data model consists of the following entity types:
    • Entity Type with Storage and Use Type 1 (Type–1 Entity Type)Storage and use type 1 must be used for entity types that can be processed in MDGAF. They have the following characteristics:
      • They represent root objects that are subject to governance.
      • More than one type–1 entity type is possible in one data model.
      • Data storage is generated (edition dependent and staging area).
      • They are used for modeling attributes and relationships.
      • They are processed in the first step of the change requests
      • Non-assignment of data elements is optional.
      • Input help is linked to a generated check table.
    • Entity Type with Storage and Use Type 2 (Type–2 Entity Type)Storage and use type 2 must be used for entity types that cannot be processed with MDG and which are not available in the system. They have the following characteristics:
      • They model lists of values and descriptions that can be uploaded.
      • They model key enhancements for type-1 and type-4 entity types.
      • Data storage is generated (no edition, no staging area).
      • No further modeling is possible (only check tables and text tables generated).
      • No processing in change requests is possible.
      • They require an assignment of a data element.
      • Check table values of data elements are ignored.
      • Input help is linked to a generated check table.
    • Entity Type with Storage and Use Type 3 (Type–3 Entity Type)Storage and use type 3 must be used for entity types that should not be processed by MDG, but are available in the system. They have the following characteristics:
      • They model external entities used in the data model.
      • They model additional primary keys for the tables of type-1 and type-4 entity types.
      • No data storage is generated
      • No further modeling is possible.
      • No processing in MDG is possible at all.
      • They require an assignment of a data element.
      • Check tables and domain fixed values are used.
      • Input help is linked to a check text table and a domain fixed value of data elements; only key fields are processed in check tables.
    • Entity Type with Storage and Use Type 4 (Type–4 Entity Type)Storage and use type 4 must be used for entity types that can be processed in MDG within the context of other entity types. They have the following characteristics:
      • They represent dependent nodes of objects to structure object data.
      • Entity type 4 must be processed on the UI together with required leading type-1 entity types.
      • Data storage is generated (edition dependent and staging area).
      • They model attributes and relationships.
      • No assignments of data elements are possible.
  2. Relationship TypesAn MDG data model consists of the following relationship types:
    • Leading Relationships
      • Type-1 entity type can lead type-1 entity types and type–4 entity types.
        • Type-4 entity types must be linked to a leading type-1 entity type.
        • A type-1 entity type can have a leading type-1 entity type.
    • Qualifying Relationships
      • Entity types are qualified using additional key attributes.
      • Type-2 and type-3 entity types can enhance the keys of type-1 and type-4 entity types.The key of an type-4 entity type must be enhanced by at least one type–1, type–2, or type–3 entity type.
    • Referencing Relationships
      • The key of a referenced entity type becomes an attribute of the referencing entity type.
Former Member
0 Kudos

Hi Sanjay,

I am looking no explanation from help.sap links and materials related to that.