Skip to content

/AWS1/IF_GLU=>CREATEGLOSSARYTERM()

About CreateGlossaryTerm

Creates a glossary term within a business glossary in Glue Data Catalog.

Method Signature

METHODS /AWS1/IF_GLU~CREATEGLOSSARYTERM
  IMPORTING
    !IV_GLOSSARYIDENTIFIER TYPE /AWS1/GLUGLOSSARYID OPTIONAL
    !IV_NAME TYPE /AWS1/GLUGLOSSARYTERMNAME OPTIONAL
    !IV_SHORTDESCRIPTION TYPE /AWS1/GLUGLOSSARYSHORTDESC OPTIONAL
    !IV_LONGDESCRIPTION TYPE /AWS1/GLUGLOSSARYLONGDESC OPTIONAL
    !IV_CLIENTTOKEN TYPE /AWS1/GLUHASHSTRING OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_glucreglossarytermrsp
  RAISING
    /AWS1/CX_GLUACCESSDENIEDEX
    /AWS1/CX_GLUALREADYEXISTSEX
    /AWS1/CX_GLUCONCURRENTMODEX
    /AWS1/CX_GLUENTITYNOTFOUNDEX
    /AWS1/CX_GLUINTERNALSERVICEEX
    /AWS1/CX_GLUINVALIDINPUTEX
    /AWS1/CX_GLUTHROTTLINGEX
    /AWS1/CX_GLUCLIENTEXC
    /AWS1/CX_GLUSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_glossaryidentifier TYPE /AWS1/GLUGLOSSARYID /AWS1/GLUGLOSSARYID

The unique identifier of the glossary in which to create the term.

iv_name TYPE /AWS1/GLUGLOSSARYTERMNAME /AWS1/GLUGLOSSARYTERMNAME

The name of the glossary term.

Optional arguments:

iv_shortdescription TYPE /AWS1/GLUGLOSSARYSHORTDESC /AWS1/GLUGLOSSARYSHORTDESC

A short description of the glossary term.

iv_longdescription TYPE /AWS1/GLUGLOSSARYLONGDESC /AWS1/GLUGLOSSARYLONGDESC

A long description of the glossary term.

iv_clienttoken TYPE /AWS1/GLUHASHSTRING /AWS1/GLUHASHSTRING

A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.

RETURNING

oo_output TYPE REF TO /aws1/cl_glucreglossarytermrsp /AWS1/CL_GLUCREGLOSSARYTERMRSP

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->createglossaryterm(
  iv_clienttoken = |string|
  iv_glossaryidentifier = |string|
  iv_longdescription = |string|
  iv_name = |string|
  iv_shortdescription = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_glossarytermid = lo_result->get_id( ).
  lv_glossaryid = lo_result->get_glossaryid( ).
  lv_glossarytermname = lo_result->get_name( ).
  lv_glossaryshortdescriptio = lo_result->get_shortdescription( ).
  lv_glossarylongdescription = lo_result->get_longdescription( ).
ENDIF.