/AWS1/IF_OMX=>CREATEVARIANTSTORE()¶
About CreateVariantStore¶
Amazon Web Services HealthOmics variant stores and annotation stores will no longer be open to new customers starting November 7, 2025. If you would like to use variant stores or annotation stores, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see Amazon Web Services HealthOmics variant store and annotation store availability change.
Creates a variant store.
Method Signature¶
METHODS /AWS1/IF_OMX~CREATEVARIANTSTORE
IMPORTING
!IO_REFERENCE TYPE REF TO /AWS1/CL_OMXREFERENCEITEM OPTIONAL
!IV_NAME TYPE /AWS1/OMXSTORENAME OPTIONAL
!IV_DESCRIPTION TYPE /AWS1/OMXDESCRIPTION OPTIONAL
!IT_TAGS TYPE /AWS1/CL_OMXTAGMAP_W=>TT_TAGMAP OPTIONAL
!IO_SSECONFIG TYPE REF TO /AWS1/CL_OMXSSECONFIG OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_omxcrevariantstorersp
RAISING
/AWS1/CX_OMXACCESSDENIEDEX
/AWS1/CX_OMXCONFLICTEXCEPTION
/AWS1/CX_OMXINTERNALSERVEREX
/AWS1/CX_OMXRESOURCENOTFOUNDEX
/AWS1/CX_OMXSERVICEQUOTAEXCDEX
/AWS1/CX_OMXTHROTTLINGEX
/AWS1/CX_OMXVALIDATIONEX
/AWS1/CX_OMXCLIENTEXC
/AWS1/CX_OMXSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
io_reference TYPE REF TO /AWS1/CL_OMXREFERENCEITEM /AWS1/CL_OMXREFERENCEITEM¶
The genome reference for the store's variants.
Optional arguments:¶
iv_name TYPE /AWS1/OMXSTORENAME /AWS1/OMXSTORENAME¶
A name for the store.
iv_description TYPE /AWS1/OMXDESCRIPTION /AWS1/OMXDESCRIPTION¶
A description for the store.
it_tags TYPE /AWS1/CL_OMXTAGMAP_W=>TT_TAGMAP TT_TAGMAP¶
Tags for the store.
io_sseconfig TYPE REF TO /AWS1/CL_OMXSSECONFIG /AWS1/CL_OMXSSECONFIG¶
Server-side encryption (SSE) settings for the store.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_omxcrevariantstorersp /AWS1/CL_OMXCREVARIANTSTORERSP¶
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->createvariantstore(
io_reference = new /aws1/cl_omxreferenceitem( |string| )
io_sseconfig = new /aws1/cl_omxsseconfig(
iv_keyarn = |string|
iv_type = |string|
)
it_tags = VALUE /aws1/cl_omxtagmap_w=>tt_tagmap(
(
VALUE /aws1/cl_omxtagmap_w=>ts_tagmap_maprow(
key = |string|
value = new /aws1/cl_omxtagmap_w( |string| )
)
)
)
iv_description = |string|
iv_name = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_resourceid = lo_result->get_id( ).
lo_referenceitem = lo_result->get_reference( ).
IF lo_referenceitem IS NOT INITIAL.
lv_referencearn = lo_referenceitem->get_referencearn( ).
ENDIF.
lv_storestatus = lo_result->get_status( ).
lv_string = lo_result->get_name( ).
lv_creationtime = lo_result->get_creationtime( ).
ENDIF.