Show TOC

Function documentationRelationship Category Maintenance

 

This function allows you to create and maintain the relationship categories that appear in a mobile client application.

Features

  • Record Property

    Determines the access rights to a particular record.

    SAP provides certain relationship categories, each of which has one of the following record properties.

    • System Entry, Not Changeable: The record cannot be changed or deleted.

    • Modifiable Entry, Not Deletable: The record can be changed but cannot be deleted.

    • Example Entry: The record can be changed or deleted.

    The other possible record property is Customer Entry. This is a customer-defined entry and can be changed or deleted. By default, the record property of a new relationship category is always set to Customer Entry. Internally, the system stores these record properties as:

    • S: System entry

    • M: Modifiable entry

    • E: Example entry

    • Y: Customer entry

  • Source and destination parameters

    • Source and Source Type

      Indicates the type of source business object of the relationship category depending on the source value.

      The source type 0006 for the source CAP is, for example, used for a business partner who is a competitor.

      You can enter either the code or an asterisk (*) as the source type.

    • Destination and Destination Type

      Indicates the target business object that is linked to the source

      The destination type 0006 for the destination CAP is, for example, used for a business partner who is a competitor.

      You enter either the code for the destination type or an asterisk (*).

      Note Note

      By entering an asterisk (*), you indicate that the information is not specific to a single business object and can be used for all business objects. As described above, an asterisk is valid for the following fields:

      End of the note.

  • Classification

    Indicates whether you can change a relationship category record after you create it.

    • User: Can be changed

    • R/3 System: Cannot be changed

    • System: Cannot be changed

    Internally, the system stores these classifications as:

    • U for User

    • R for R/3 System

    • S for System

  • Directed

    Indicates that the text descriptions of a relationship category differ depending on whether the relationship is viewed from the source or the destination.

    Note Note

    If the relationship category is Directed, it must have both a source and a destination entry for the View From column in the Relationship Category Text tile. The two text descriptions must reflect the difference in the relationship category, when viewed from the source versus when viewed from the destination.

    End of the note.

  • Reversible

    A relationship category is reversible, if the:

    • Source object assumes the role of the destination object

    • Destination object assumes the role of the source object

    You select this indicator if the text describing the relationship category is the same for the source and destination.

    Example Example

    is a competitor of is a relationship category between the objects Coca Cola (source) and Pepsi (destination). This relationship category is reversible if Coca Cola is the source in one scenario and Pepsi is the source in another.

    End of the example.

  • Cardinality

    Represents the number of times an object can be the destination of a source. You indicate either the number of possible links that can be made or an asterisk (*) to indicate that there is no limit. If two objects are connected by a relationship category that is reversible, the cardinality applies to the source and the destination.

  • Time Dependency

    Allows you to choose a time constraint, such as no gaps or no overlapping periods. This reflects the settings made in CRM using the BUBA transaction.

  • Standard Indicator

    Allows you to indicate the standard relationship category.

  • Relationship Category - Link Table tile

    You can indicate the name of the link table in which the relationship category must be stored after it is created on the mobile client. A single relationship category can be stored in multiple tables. Make an entry for each table in which the relationship category is to be used.

    You select a link table based on the types of business objects you are linking for the relationship category.

    Example Example

    You select the link table KVBEZ6 for a relationship category between business partners and contacts that have the following source and destination combinations:

    • Business Partner (CAP) – Contact (CON)

    • Business Partner (CAP) – Business Partner (CAP)

    • Contact (CON) – Contact (CON)

    You select the link table KVBEZ7 for a relationship category between business partners or contacts and employees that have the following source and destination combinations:

    • Business Partner (CAP) – Employee (EMP)

    • Contact (CON) – Employee (EMP)

    End of the example.

  • Relationship Category Texts

    Allows you to create language-dependent descriptions of each relationship category.

    Note Note

    The following reports are available in CRM for downloading customer relationship categories and partner functions from CRM to CDB:

    • CRM_DOWNLOAD_CDB_BP_PFT for partner functions

    • CRM_DOWNLOAD_BP_RELTYPE for relationship categories

    End of the note.