CREATELANGUAGEMODEL()`¶

About CreateLanguageModel¶

Creates a new custom language model.

When creating a new custom language model, you must specify:

If you want a Wideband (audio sample rates over 16,000 Hz) or Narrowband (audio sample rates under 16,000 Hz) base model
The location of your training and tuning files (this must be an Amazon S3 URI)
The language of your model
A unique name for your model

Method Signature¶

METHODS /AWS1/IF_TNB~CREATELANGUAGEMODEL
  IMPORTING
    !IV_LANGUAGECODE TYPE /AWS1/TNBCLMLANGUAGECODE OPTIONAL
    !IV_BASEMODELNAME TYPE /AWS1/TNBBASEMODELNAME OPTIONAL
    !IV_MODELNAME TYPE /AWS1/TNBMODELNAME OPTIONAL
    !IO_INPUTDATACONFIG TYPE REF TO /AWS1/CL_TNBINPUTDATACONFIG OPTIONAL
    !IT_TAGS TYPE /AWS1/CL_TNBTAG=>TT_TAGLIST OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_tnbcrelanguagemdelrsp
  RAISING
    /AWS1/CX_TNBBADREQUESTEX
    /AWS1/CX_TNBCONFLICTEXCEPTION
    /AWS1/CX_TNBINTERNALFAILUREEX
    /AWS1/CX_TNBLIMITEXCEEDEDEX
    /AWS1/CX_TNBCLIENTEXC
    /AWS1/CX_TNBSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_languagecode` `TYPE /AWS1/TNBCLMLANGUAGECODE` `/AWS1/TNBCLMLANGUAGECODE`¶

The language code that represents the language of your model. Each custom language model must contain terms in only one language, and the language you select for your custom language model must match the language of your training and tuning data.

For a list of supported languages and their associated language codes, refer to the Supported languages table. Note that US English (en-US) is the only language supported with Amazon Transcribe Medical.

A custom language model can only be used to transcribe files in the same language as the model. For example, if you create a custom language model using US English (en-US), you can only apply this model to files that contain English audio.

`iv_basemodelname` `TYPE /AWS1/TNBBASEMODELNAME` `/AWS1/TNBBASEMODELNAME`¶

The Amazon Transcribe standard language model, or base model, used to create your custom language model. Amazon Transcribe offers two options for base models: Wideband and Narrowband.

If the audio you want to transcribe has a sample rate of 16,000 Hz or greater, choose WideBand. To transcribe audio with a sample rate less than 16,000 Hz, choose NarrowBand.

`iv_modelname` `TYPE /AWS1/TNBMODELNAME` `/AWS1/TNBMODELNAME`¶

A unique name, chosen by you, for your custom language model.

This name is case sensitive, cannot contain spaces, and must be unique within an Amazon Web Services account. If you try to create a new custom language model with the same name as an existing custom language model, you get a ConflictException error.

`io_inputdataconfig` `TYPE REF TO /AWS1/CL_TNBINPUTDATACONFIG` `/AWS1/CL_TNBINPUTDATACONFIG`¶

Contains the Amazon S3 location of the training data you want to use to create a new custom language model, and permissions to access this location.

When using InputDataConfig, you must include these sub-parameters: S3Uri, which is the Amazon S3 location of your training data, and DataAccessRoleArn, which is the Amazon Resource Name (ARN) of the role that has permission to access your specified Amazon S3 location. You can optionally include TuningDataS3Uri, which is the Amazon S3 location of your tuning data. If you specify different Amazon S3 locations for training and tuning data, the ARN you use must have permissions to access both locations.

Optional arguments:¶

`it_tags` `TYPE /AWS1/CL_TNBTAG=>TT_TAGLIST` `TT_TAGLIST`¶

Adds one or more custom tags, each in the form of a key:value pair, to a new custom language model at the time you create this new model.

To learn more about using tags with Amazon Transcribe, refer to Tagging resources.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_tnbcrelanguagemdelrsp` `/AWS1/CL_TNBCRELANGUAGEMDELRSP`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

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->createlanguagemodel(
  io_inputdataconfig = new /aws1/cl_tnbinputdataconfig(
    iv_dataaccessrolearn = |string|
    iv_s3uri = |string|
    iv_tuningdatas3uri = |string|
  )
  it_tags = VALUE /aws1/cl_tnbtag=>tt_taglist(
    (
      new /aws1/cl_tnbtag(
        iv_key = |string|
        iv_value = |string|
      )
    )
  )
  iv_basemodelname = |string|
  iv_languagecode = |string|
  iv_modelname = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_clmlanguagecode = lo_result->get_languagecode( ).
  lv_basemodelname = lo_result->get_basemodelname( ).
  lv_modelname = lo_result->get_modelname( ).
  lo_inputdataconfig = lo_result->get_inputdataconfig( ).
  IF lo_inputdataconfig IS NOT INITIAL.
    lv_uri = lo_inputdataconfig->get_s3uri( ).
    lv_uri = lo_inputdataconfig->get_tuningdatas3uri( ).
    lv_dataaccessrolearn = lo_inputdataconfig->get_dataaccessrolearn( ).
  ENDIF.
  lv_modelstatus = lo_result->get_modelstatus( ).
ENDIF.

/AWS1/IF_TNB=>CREATELANGUAGEMODEL()¶