/AWS1/IF_TEX=>STARTLENDINGANALYSIS()

About StartLendingAnalysis

Starts the classification and analysis of an input document. StartLendingAnalysis initiates the classification and analysis of a packet of lending documents. StartLendingAnalysis operates on a document file located in an Amazon S3 bucket.

StartLendingAnalysis can analyze text in documents that are in one of the following formats: JPEG, PNG, TIFF, PDF. Use DocumentLocation to specify the bucket name and the file name of the document.

StartLendingAnalysis returns a job identifier (JobId) that you use to get the results of the operation. When the text analysis is finished, Amazon Textract publishes a completion status to the Amazon Simple Notification Service (Amazon SNS) topic that you specify in NotificationChannel. To get the results of the text analysis operation, first check that the status value published to the Amazon SNS topic is SUCCEEDED. If the status is SUCCEEDED you can call either GetLendingAnalysis or GetLendingAnalysisSummary and provide the JobId to obtain the results of the analysis.

If using OutputConfig to specify an Amazon S3 bucket, the output will be contained within the specified prefix in a directory labeled with the job-id. In the directory there are 3 sub-directories:

• detailedResponse (contains the GetLendingAnalysis response)

• summaryResponse (for the GetLendingAnalysisSummary response)

• splitDocuments (documents split across logical boundaries)

Method Signature

METHODS /AWS1/IF_TEX~STARTLENDINGANALYSIS
  IMPORTING
    !IO_DOCUMENTLOCATION TYPE REF TO /AWS1/CL_TEXDOCUMENTLOCATION OPTIONAL
    !IV_CLIENTREQUESTTOKEN TYPE /AWS1/TEXCLIENTREQUESTTOKEN OPTIONAL
    !IV_JOBTAG TYPE /AWS1/TEXJOBTAG OPTIONAL
    !IO_NOTIFICATIONCHANNEL TYPE REF TO /AWS1/CL_TEXNOTIFCHANNEL OPTIONAL
    !IO_OUTPUTCONFIG TYPE REF TO /AWS1/CL_TEXOUTPUTCONFIG OPTIONAL
    !IV_KMSKEYID TYPE /AWS1/TEXKMSKEYID OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_texstartlendingalyrsp
  RAISING
    /AWS1/CX_TEXACCESSDENIEDEX
    /AWS1/CX_TEXBADDOCUMENTEX
    /AWS1/CX_TEXDOCUMENTTOOLARGEEX
    /AWS1/CX_TEXIDEMPOTENTPRMMIS00
    /AWS1/CX_TEXINTERNALSERVERERR
    /AWS1/CX_TEXINVALIDKMSKEYEX
    /AWS1/CX_TEXINVALIDPARAMETEREX
    /AWS1/CX_TEXINVALIDS3OBJECTEX
    /AWS1/CX_TEXLIMITEXCEEDEDEX
    /AWS1/CX_TEXPROVTHRUPUTEXCDEX
    /AWS1/CX_TEXTHROTTLINGEX
    /AWS1/CX_TEXUNSUPPORTEDDOCEX
    /AWS1/CX_TEXCLIENTEXC
    /AWS1/CX_TEXSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

io_documentlocation TYPE REF TO /AWS1/CL_TEXDOCUMENTLOCATION /AWS1/CL_TEXDOCUMENTLOCATION

DocumentLocation

Optional arguments:

iv_clientrequesttoken TYPE /AWS1/TEXCLIENTREQUESTTOKEN /AWS1/TEXCLIENTREQUESTTOKEN

The idempotent token that you use to identify the start request. If you use the same token with multiple StartLendingAnalysis requests, the same JobId is returned. Use ClientRequestToken to prevent the same job from being accidentally started more than once. For more information, see Calling Amazon Textract Asynchronous Operations.

iv_jobtag TYPE /AWS1/TEXJOBTAG /AWS1/TEXJOBTAG

An identifier that you specify to be included in the completion notification published to the Amazon SNS topic. For example, you can use JobTag to identify the type of document that the completion notification corresponds to (such as a tax form or a receipt).

io_notificationchannel TYPE REF TO /AWS1/CL_TEXNOTIFCHANNEL /AWS1/CL_TEXNOTIFCHANNEL

NotificationChannel

io_outputconfig TYPE REF TO /AWS1/CL_TEXOUTPUTCONFIG /AWS1/CL_TEXOUTPUTCONFIG

OutputConfig

iv_kmskeyid TYPE /AWS1/TEXKMSKEYID /AWS1/TEXKMSKEYID

The KMS key used to encrypt the inference results. This can be in either Key ID or Key Alias format. When a KMS key is provided, the KMS key will be used for server-side encryption of the objects in the customer bucket. When this parameter is not enabled, the result will be encrypted server side, using SSE-S3.

RETURNING

oo_output TYPE REF TO /aws1/cl_texstartlendingalyrsp /AWS1/CL_TEXSTARTLENDINGALYRSP

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->startlendinganalysis(
  io_documentlocation = new /aws1/cl_texdocumentlocation(
    io_s3object = new /aws1/cl_texs3object(
      iv_bucket = |string|
      iv_name = |string|
      iv_version = |string|
    )
  )
  io_notificationchannel = new /aws1/cl_texnotifchannel(
    iv_rolearn = |string|
    iv_snstopicarn = |string|
  )
  io_outputconfig = new /aws1/cl_texoutputconfig(
    iv_s3bucket = |string|
    iv_s3prefix = |string|
  )
  iv_clientrequesttoken = |string|
  iv_jobtag = |string|
  iv_kmskeyid = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_jobid = lo_result->get_jobid( ).
ENDIF.