Show TOC

Function documentationMaintaining Terms in Other Contexts Locate this document in the navigation structure

 

You can use the Create Context-Dependent Entry function to add other main entries to a main entry of a terminology concept, in the same language, with this function.

You can use the function in the following situations:

  • The terminology has changed.

    Example Example

    The term Function Library was valid until Release 4.0A. From Release 4.0A, this term has been replaced by Function Builder. The terminology change should be documented in the terminology database.

    End of the example.

  • There are country or industry sector-specific different names for the same thing: for example, all countries have their own version of social insurance.

    Example Example

    Example of Country-Specific Names

    This graphic is explained in the accompanying text.

    The terminology database should document that these are all names for different country versions of the same concept.

    End of the example.

    Example Example

    Example of Industry Sector-Specific Names

    SAP Standard: Material

    Industry sector (Retail): Article

    End of the example.

In a concept-oriented database, all entries belong to the same concept. The entries must have different context attributes.

Function Library and Function Builder have different context attributes "changed in Release" (4.0A and unspecified). The terms "national insurance", "social security", and "social security program" have different context attributes "Country" (GB, US, CA).

Note Note

Terms with the same context attributes cannot be maintained in parallel as two independent main entries. These are treated as valid synonyms.

End of the note.

Prerequisites

Before you can create an additional main entry under a new context, you must first have saved the initial main entry.

Activities

  1. Edit a main entry.

  2. Under Context, maintain the following, depending on the situation:

    • To indicate that this term is only valid after a specific release, enter the name of this release in the First Basis Release field (for terms from the standard system). For terms from industry solutions and any other non-SAP developments, enter the name of the release in the First IS Release field.

    • To indicate that this term will no longer be valid after a specific release, enter the name of this release in the Invalid after Basis rel. field (for terms from the standard system). For terms from industry solutions and any other non-ABAP developments, enter the name of the release in the Invalid after IS release field.

    • To indicate that this term is only valid in a specific country, enter the two-character ID of this country in the Country field (you can use F4 Help to choose the country ID).

    • To indicate that this term is only valid in a specific industry, enter the ID of this industry in the Industry field (you can use F4 Help to choose the industry ID).

  3. To create another entry, choose   Goto   Create Context-Dependent Entry  .

  4. Edit the new term.

  5. Under Context for this term, maintain the context attributes that differ from those of the main entry.

  6. Save your entries.

Example

To document the fact that the term Function Library was valid until Release 4.0A and has been replaced by Function Builder from Release 4.0A onwards, proceed as follows:

  1. Maintain the main entry, in this case Function Library.

  2. Under Context for this entry, enter 4.0A in the Invalid after Basis Rel. field.

  3. Save the entry.

  4. Now choose   Goto   Create Context-Dependent Entry  .

  5. In this screen, maintain the new term, in this case Function Builder.

  6. Under Context for this entry, enter 4.0A in the First Basis Release field.

  7. Save your entries.

The terminology concept detail display now contains two English entries. You can see from the context attributes that the entry Function Library has been replaced from Release 4.0A by the term Function Builder.