SAP BAPI_XBP_VARIANT_CREATE Function Module for Create a variant
BAPI_XBP_VARIANT_CREATE is a standard bapi xbp variant create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create a variant 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 bapi xbp variant create FM, simply by entering the name BAPI_XBP_VARIANT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXBP_VAR
Program Name: SAPLSXBP_VAR
Main Program: SAPLSXBP_VAR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_XBP_VARIANT_CREATE 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 'BAPI_XBP_VARIANT_CREATE'"Create a variant.
EXPORTING
ABAP_PROGRAM_NAME = "ABAP program: Current master program
ABAP_VARIANT_NAME = "Variant Name
ABAP_VARIANT_TEXT = "Program variant short text
* DIA = "Reference type CHAR1 for background processing
* PROTECTED = "Flag (character)
EXTERNAL_USER_NAME = "XMI logging: Name of User in External Management Tool
IMPORTING
RETURN = "Return Parameters
TABLES
* VARIANT_INFO = "Information About a Report Variant
* VARIANT_INFO_L = "Information About a Report Variant
IMPORTING Parameters details for BAPI_XBP_VARIANT_CREATE
ABAP_PROGRAM_NAME - ABAP program: Current master program
Data type: BAPIXMREP-REPORTIDOptional: No
Call by Reference: No ( called with pass by value option)
ABAP_VARIANT_NAME - Variant Name
Data type: BAPIXMREP-VARIANTNAMOptional: No
Call by Reference: No ( called with pass by value option)
ABAP_VARIANT_TEXT - Program variant short text
Data type: RVART_VTXTOptional: No
Call by Reference: No ( called with pass by value option)
DIA - Reference type CHAR1 for background processing
Data type: BTCH0000-CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
PROTECTED - Flag (character)
Data type: VARID-PROTECTEDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTERNAL_USER_NAME - XMI logging: Name of User in External Management Tool
Data type: BAPIXMLOGR-EXTUSEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_XBP_VARIANT_CREATE
RETURN - Return Parameters
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_XBP_VARIANT_CREATE
VARIANT_INFO - Information About a Report Variant
Data type: BAPIVARINFOOptional: Yes
Call by Reference: Yes
VARIANT_INFO_L - Information About a Report Variant
Data type: BAPIVARINFO_LOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_XBP_VARIANT_CREATE 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_return | TYPE BAPIRET2, " | |||
| lt_variant_info | TYPE STANDARD TABLE OF BAPIVARINFO, " | |||
| lv_abap_program_name | TYPE BAPIXMREP-REPORTID, " | |||
| lt_variant_info_l | TYPE STANDARD TABLE OF BAPIVARINFO_L, " | |||
| lv_abap_variant_name | TYPE BAPIXMREP-VARIANTNAM, " | |||
| lv_abap_variant_text | TYPE RVART_VTXT, " | |||
| lv_dia | TYPE BTCH0000-CHAR1, " | |||
| lv_protected | TYPE VARID-PROTECTED, " | |||
| lv_external_user_name | TYPE BAPIXMLOGR-EXTUSER. " |
|   CALL FUNCTION 'BAPI_XBP_VARIANT_CREATE' "Create a variant |
| EXPORTING | ||
| ABAP_PROGRAM_NAME | = lv_abap_program_name | |
| ABAP_VARIANT_NAME | = lv_abap_variant_name | |
| ABAP_VARIANT_TEXT | = lv_abap_variant_text | |
| DIA | = lv_dia | |
| PROTECTED | = lv_protected | |
| EXTERNAL_USER_NAME | = lv_external_user_name | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| VARIANT_INFO | = lt_variant_info | |
| VARIANT_INFO_L | = lt_variant_info_l | |
| . " BAPI_XBP_VARIANT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_XBP_VARIANT_CREATE
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.| "SELECT single REPORTID FROM BAPIXMREP INTO @DATA(ld_abap_program_name). | ||||
| "SELECT single VARIANTNAM FROM BAPIXMREP INTO @DATA(ld_abap_variant_name). | ||||
| "SELECT single CHAR1 FROM BTCH0000 INTO @DATA(ld_dia). | ||||
| "SELECT single PROTECTED FROM VARID INTO @DATA(ld_protected). | ||||
| "SELECT single EXTUSER FROM BAPIXMLOGR INTO @DATA(ld_external_user_name). | ||||
Search for further information about these or an SAP related objects