SAP BDS_LOIO_CREATE Function Module for









BDS_LOIO_CREATE is a standard bds loio create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bds loio create FM, simply by entering the name BDS_LOIO_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDS_METHODS
Program Name: SAPLBDS_METHODS
Main Program: SAPLBDS_METHODS
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BDS_LOIO_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 'BDS_LOIO_CREATE'"
EXPORTING
* LOGICAL_SYSTEM = "
CLASSNAME = "
CLASSTYPE = "
* CLIENT = SY-MANDT "

IMPORTING
LO_OBJECT = "

TABLES
PROPERTIES = "

EXCEPTIONS
ERROR_KPRO = 1 INTERNAL_ERROR = 2 PARAMETER_ERROR = 3 NOTHING_FOUND = 4 NOT_AUTHORIZED = 5 NOT_ALLOWED = 6
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLBDS_METHODS_001 Customer Exit for BDS_BARCODE_CREATE

IMPORTING Parameters details for BDS_LOIO_CREATE

LOGICAL_SYSTEM -

Data type: BAPIBDS01-LOG_SYSTEM
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLASSNAME -

Data type: BAPIBDS01-CLASSNAME
Optional: No
Call by Reference: No ( called with pass by value option)

CLASSTYPE -

Data type: BAPIBDS01-CLASSTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

CLIENT -

Data type: BAPIBDS01-CLIENT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BDS_LOIO_CREATE

LO_OBJECT -

Data type: SDOKOBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDS_LOIO_CREATE

PROPERTIES -

Data type: SDOKPROPTY
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_KPRO -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOTHING_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_AUTHORIZED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BDS_LOIO_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_lo_object  TYPE SDOKOBJECT, "   
lv_error_kpro  TYPE SDOKOBJECT, "   
lt_properties  TYPE STANDARD TABLE OF SDOKPROPTY, "   
lv_logical_system  TYPE BAPIBDS01-LOG_SYSTEM, "   
lv_classname  TYPE BAPIBDS01-CLASSNAME, "   
lv_internal_error  TYPE BAPIBDS01, "   
lv_classtype  TYPE BAPIBDS01-CLASSTYPE, "   
lv_parameter_error  TYPE BAPIBDS01, "   
lv_client  TYPE BAPIBDS01-CLIENT, "   SY-MANDT
lv_nothing_found  TYPE BAPIBDS01, "   
lv_not_authorized  TYPE BAPIBDS01, "   
lv_not_allowed  TYPE BAPIBDS01. "   

  CALL FUNCTION 'BDS_LOIO_CREATE'  "
    EXPORTING
         LOGICAL_SYSTEM = lv_logical_system
         CLASSNAME = lv_classname
         CLASSTYPE = lv_classtype
         CLIENT = lv_client
    IMPORTING
         LO_OBJECT = lv_lo_object
    TABLES
         PROPERTIES = lt_properties
    EXCEPTIONS
        ERROR_KPRO = 1
        INTERNAL_ERROR = 2
        PARAMETER_ERROR = 3
        NOTHING_FOUND = 4
        NOT_AUTHORIZED = 5
        NOT_ALLOWED = 6
. " BDS_LOIO_CREATE




ABAP code using 7.40 inline data declarations to call FM BDS_LOIO_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 LOG_SYSTEM FROM BAPIBDS01 INTO @DATA(ld_logical_system).
 
"SELECT single CLASSNAME FROM BAPIBDS01 INTO @DATA(ld_classname).
 
 
"SELECT single CLASSTYPE FROM BAPIBDS01 INTO @DATA(ld_classtype).
 
 
"SELECT single CLIENT FROM BAPIBDS01 INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!