SAP TERM_CHECK_PLAUSIBILITY Function Module for NOTRANSL: Check Plausibility of SAPterm Parameters









TERM_CHECK_PLAUSIBILITY is a standard term check plausibility SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check Plausibility of SAPterm Parameters processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for term check plausibility FM, simply by entering the name TERM_CHECK_PLAUSIBILITY into the relevant SAP transaction such as SE37 or SE38.

Function Group: STERM_MULTI
Program Name: SAPLSTERM_MULTI
Main Program: SAPLSTERM_MULTI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function TERM_CHECK_PLAUSIBILITY pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'TERM_CHECK_PLAUSIBILITY'"NOTRANSL: Check Plausibility of SAPterm Parameters
  EXPORTING
*  CONCEPT =  "CHAR32 data element for SYST
*  ONLINE_CAT =  "Terminology Concept Category
*  COUNTRY =  "KW Attribute: Country in SAPterm
*  INDUSTRY =  "KW Attribute: Industry in SAPterm
*  IND_REL =  "Enhancement Release
*  FIRST_REL =  "KW Attribute: Release in SAPterm
*  IND_LREL =  "Enhancement Release
*  LAST_REL =  "KW Attribute: Release in SAPterm
*  WORD_TYP =  "Noun, Verb, Adjective
*  GENDER =  "Grammatical Gender of Terminology Entry
*  CREA_TSTUT =  "Time stamp (date and time) with reference to UTC (GMT)
*  OBJECT =  "CHAR32 data element for SYST
*  CREA_NAME =  "Author of the Repository object
*  CREA_ORG =  "Author's Firm or Organization
*  CHAN_TSTUT =  "Time stamp (date and time) with reference to UTC (GMT)
*  CHAN_NAME =  "Author of the Repository object
*  CHAN_ORG =  "Author's Firm or Organization
*  GLOS =  "Transfer String for TBX
*  SOURCE =  "Transfer String for TBX
*  COMM =  "Transfer String for TBX
*  ADDCOMP =  "Transfer String for TBX
*  USAGE_NOTE =  "Transfer String for TBX
*  COMPONENT =  "Application Component
*  REF =  "Transfer String for TBX
*  CODEPAGE_LANGU =  "Language Key
*  CREA_LAN =  "Language Key
*  LANGU =  "Language Key
*  TEXT =  "Term
*  STATUS =  "Terminology Maintenance Status
*  OBJECT_TYP =  "Terminology Entry Category
*  ONLINE_TXT =  "Online Text Indicator

EXCEPTIONS
   OBJECT_TYP_FAIL = 1    ONLINE_TXT_FAIL = 10    ONLINE_CAT_FAIL = 11    USAGE_NOTE_FAIL = 12    LANGU_FAIL = 13    CREA_LAN_FAIL = 14    INDUSTRY_FAIL = 15    FIRST_REL_FAIL = 16    LAST_REL_FAIL = 17    IND_REL_FAIL = 18    IND_LREL_FAIL = 19    STATUS_FAIL = 2    WORD_TYP_FAIL = 3    GENDER_FAIL = 4    GLOS_FAIL = 5    SOURCE_FAIL = 6    COMM_FAIL = 7    REF_FAIL = 8    TEXT_FAIL = 9
.



IMPORTING Parameters details for TERM_CHECK_PLAUSIBILITY

CONCEPT - CHAR32 data element for SYST

Data type: SYCHAR32
Optional: Yes
Call by Reference: Yes

ONLINE_CAT - Terminology Concept Category

Data type: TM_ON_CAT
Optional: Yes
Call by Reference: Yes

COUNTRY - KW Attribute: Country in SAPterm

Data type: TM_COUNTRY
Optional: Yes
Call by Reference: Yes

INDUSTRY - KW Attribute: Industry in SAPterm

Data type: TM_BRANCHE
Optional: Yes
Call by Reference: Yes

IND_REL - Enhancement Release

Data type: IWEXTREL
Optional: Yes
Call by Reference: Yes

FIRST_REL - KW Attribute: Release in SAPterm

Data type: TM_RELEASE
Optional: Yes
Call by Reference: Yes

IND_LREL - Enhancement Release

Data type: IWEXTREL
Optional: Yes
Call by Reference: Yes

LAST_REL - KW Attribute: Release in SAPterm

Data type: TM_RELEASE
Optional: Yes
Call by Reference: Yes

WORD_TYP - Noun, Verb, Adjective

Data type: WORD_TYP
Optional: Yes
Call by Reference: Yes

GENDER - Grammatical Gender of Terminology Entry

Data type: GENDER
Optional: Yes
Call by Reference: Yes

CREA_TSTUT - Time stamp (date and time) with reference to UTC (GMT)

Data type: SYSTTSTUT
Optional: Yes
Call by Reference: Yes

OBJECT - CHAR32 data element for SYST

Data type: SYCHAR32
Optional: Yes
Call by Reference: Yes

CREA_NAME - Author of the Repository object

Data type: AUTHOR
Optional: Yes
Call by Reference: Yes

CREA_ORG - Author's Firm or Organization

Data type: ORG
Optional: Yes
Call by Reference: Yes

CHAN_TSTUT - Time stamp (date and time) with reference to UTC (GMT)

Data type: SYSTTSTUT
Optional: Yes
Call by Reference: Yes

CHAN_NAME - Author of the Repository object

Data type: AUTHOR
Optional: Yes
Call by Reference: Yes

CHAN_ORG - Author's Firm or Organization

Data type: ORG
Optional: Yes
Call by Reference: Yes

GLOS - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

SOURCE - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

COMM - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

ADDCOMP - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

USAGE_NOTE - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

COMPONENT - Application Component

Data type: UFFCTR
Optional: Yes
Call by Reference: Yes

REF - Transfer String for TBX

Data type: TBX_STRING
Optional: Yes
Call by Reference: Yes

CODEPAGE_LANGU - Language Key

Data type: LANGU
Optional: Yes
Call by Reference: Yes

CREA_LAN - Language Key

Data type: LANGU
Optional: Yes
Call by Reference: Yes

LANGU - Language Key

Data type: LANGU
Optional: Yes
Call by Reference: Yes

TEXT - Term

Data type: TERM_TEXT
Optional: Yes
Call by Reference: Yes

STATUS - Terminology Maintenance Status

Data type: TERMSTATUS
Optional: Yes
Call by Reference: Yes

OBJECT_TYP - Terminology Entry Category

Data type: TERM_TYP
Optional: Yes
Call by Reference: Yes

ONLINE_TXT - Online Text Indicator

Data type: ONLINE_TXT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

OBJECT_TYP_FAIL - Unknown Object Type

Data type:
Optional: No
Call by Reference: Yes

ONLINE_TXT_FAIL - Part of Speech Errors

Data type:
Optional: No
Call by Reference: Yes

ONLINE_CAT_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

USAGE_NOTE_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

LANGU_FAIL - Unknown Language

Data type:
Optional: No
Call by Reference: Yes

CREA_LAN_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INDUSTRY_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

FIRST_REL_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

LAST_REL_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

IND_REL_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

IND_LREL_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

STATUS_FAIL - Unknown status

Data type:
Optional: No
Call by Reference: Yes

WORD_TYP_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

GENDER_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

GLOS_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

SOURCE_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

COMM_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

REF_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

TEXT_FAIL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TERM_CHECK_PLAUSIBILITY Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_concept  TYPE SYCHAR32, "   
lv_object_typ_fail  TYPE SYCHAR32, "   
lv_online_cat  TYPE TM_ON_CAT, "   
lv_online_txt_fail  TYPE TM_ON_CAT, "   
lv_country  TYPE TM_COUNTRY, "   
lv_online_cat_fail  TYPE TM_COUNTRY, "   
lv_industry  TYPE TM_BRANCHE, "   
lv_usage_note_fail  TYPE TM_BRANCHE, "   
lv_ind_rel  TYPE IWEXTREL, "   
lv_langu_fail  TYPE IWEXTREL, "   
lv_first_rel  TYPE TM_RELEASE, "   
lv_crea_lan_fail  TYPE TM_RELEASE, "   
lv_ind_lrel  TYPE IWEXTREL, "   
lv_industry_fail  TYPE IWEXTREL, "   
lv_last_rel  TYPE TM_RELEASE, "   
lv_first_rel_fail  TYPE TM_RELEASE, "   
lv_word_typ  TYPE WORD_TYP, "   
lv_last_rel_fail  TYPE WORD_TYP, "   
lv_gender  TYPE GENDER, "   
lv_ind_rel_fail  TYPE GENDER, "   
lv_crea_tstut  TYPE SYSTTSTUT, "   
lv_ind_lrel_fail  TYPE SYSTTSTUT, "   
lv_object  TYPE SYCHAR32, "   
lv_status_fail  TYPE SYCHAR32, "   
lv_crea_name  TYPE AUTHOR, "   
lv_crea_org  TYPE ORG, "   
lv_chan_tstut  TYPE SYSTTSTUT, "   
lv_chan_name  TYPE AUTHOR, "   
lv_chan_org  TYPE ORG, "   
lv_glos  TYPE TBX_STRING, "   
lv_source  TYPE TBX_STRING, "   
lv_comm  TYPE TBX_STRING, "   
lv_addcomp  TYPE TBX_STRING, "   
lv_usage_note  TYPE TBX_STRING, "   
lv_component  TYPE UFFCTR, "   
lv_word_typ_fail  TYPE UFFCTR, "   
lv_ref  TYPE TBX_STRING, "   
lv_codepage_langu  TYPE LANGU, "   
lv_crea_lan  TYPE LANGU, "   
lv_gender_fail  TYPE LANGU, "   
lv_langu  TYPE LANGU, "   
lv_glos_fail  TYPE LANGU, "   
lv_text  TYPE TERM_TEXT, "   
lv_source_fail  TYPE TERM_TEXT, "   
lv_status  TYPE TERMSTATUS, "   
lv_comm_fail  TYPE TERMSTATUS, "   
lv_ref_fail  TYPE TERMSTATUS, "   
lv_object_typ  TYPE TERM_TYP, "   
lv_text_fail  TYPE TERM_TYP, "   
lv_online_txt  TYPE ONLINE_TXT. "   

  CALL FUNCTION 'TERM_CHECK_PLAUSIBILITY'  "NOTRANSL: Check Plausibility of SAPterm Parameters
    EXPORTING
         CONCEPT = lv_concept
         ONLINE_CAT = lv_online_cat
         COUNTRY = lv_country
         INDUSTRY = lv_industry
         IND_REL = lv_ind_rel
         FIRST_REL = lv_first_rel
         IND_LREL = lv_ind_lrel
         LAST_REL = lv_last_rel
         WORD_TYP = lv_word_typ
         GENDER = lv_gender
         CREA_TSTUT = lv_crea_tstut
         OBJECT = lv_object
         CREA_NAME = lv_crea_name
         CREA_ORG = lv_crea_org
         CHAN_TSTUT = lv_chan_tstut
         CHAN_NAME = lv_chan_name
         CHAN_ORG = lv_chan_org
         GLOS = lv_glos
         SOURCE = lv_source
         COMM = lv_comm
         ADDCOMP = lv_addcomp
         USAGE_NOTE = lv_usage_note
         COMPONENT = lv_component
         REF = lv_ref
         CODEPAGE_LANGU = lv_codepage_langu
         CREA_LAN = lv_crea_lan
         LANGU = lv_langu
         TEXT = lv_text
         STATUS = lv_status
         OBJECT_TYP = lv_object_typ
         ONLINE_TXT = lv_online_txt
    EXCEPTIONS
        OBJECT_TYP_FAIL = 1
        ONLINE_TXT_FAIL = 10
        ONLINE_CAT_FAIL = 11
        USAGE_NOTE_FAIL = 12
        LANGU_FAIL = 13
        CREA_LAN_FAIL = 14
        INDUSTRY_FAIL = 15
        FIRST_REL_FAIL = 16
        LAST_REL_FAIL = 17
        IND_REL_FAIL = 18
        IND_LREL_FAIL = 19
        STATUS_FAIL = 2
        WORD_TYP_FAIL = 3
        GENDER_FAIL = 4
        GLOS_FAIL = 5
        SOURCE_FAIL = 6
        COMM_FAIL = 7
        REF_FAIL = 8
        TEXT_FAIL = 9
. " TERM_CHECK_PLAUSIBILITY




ABAP code using 7.40 inline data declarations to call FM TERM_CHECK_PLAUSIBILITY

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!