SAP SDOK_LOIO_CREATE Function Module for Create a Logical Document
SDOK_LOIO_CREATE is a standard sdok 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 for Create a Logical Document 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 sdok loio create FM, simply by entering the name SDOK_LOIO_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDCL
Program Name: SAPLSDCL
Main Program: SAPLSDCL
Appliation area: S
Release date: 29-Oct-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function SDOK_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 'SDOK_LOIO_CREATE'"Create a Logical Document.
EXPORTING
* OBJECT_CLASS = "Object Class
* OBJECT_UNIQUE_ID = "Unique Object Identification
* CLIENT = SY-MANDT "Client
IMPORTING
OBJECT_ID = "BOR Key for the Object
TABLES
* PROPERTIES = "Name and Value of Attributes
EXCEPTIONS
MISSING_CLASS = 1 BAD_CLASS = 2 MISSING_PROPERTIES = 3 BAD_PROPERTIES = 4 NOT_AUTHORIZED = 5 DUPLICATE_OBJECT_ID = 6 EXCEPTION_IN_EXIT = 7
IMPORTING Parameters details for SDOK_LOIO_CREATE
OBJECT_CLASS - Object Class
Data type: SDOKLOCL-LO_CLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_UNIQUE_ID - Unique Object Identification
Data type: SDOKLOIO-LOIO_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SDOK_LOIO_CREATE
OBJECT_ID - BOR Key for the Object
Data type: SDOKOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SDOK_LOIO_CREATE
PROPERTIES - Name and Value of Attributes
Data type: SDOKPROPTYOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MISSING_CLASS - Object Class Not Specified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_CLASS - Object class unknown
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_PROPERTIES - Required Attributes Not Specified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_PROPERTIES - Attributes Not Specified Correctly
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DUPLICATE_OBJECT_ID - Object already exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION_IN_EXIT - Exception in application exit
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SDOK_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_object_id | TYPE SDOKOBJECT, " | |||
| lt_properties | TYPE STANDARD TABLE OF SDOKPROPTY, " | |||
| lv_object_class | TYPE SDOKLOCL-LO_CLASS, " | |||
| lv_missing_class | TYPE SDOKLOCL, " | |||
| lv_bad_class | TYPE SDOKLOCL, " | |||
| lv_object_unique_id | TYPE SDOKLOIO-LOIO_ID, " | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_missing_properties | TYPE SY, " | |||
| lv_bad_properties | TYPE SY, " | |||
| lv_not_authorized | TYPE SY, " | |||
| lv_duplicate_object_id | TYPE SY, " | |||
| lv_exception_in_exit | TYPE SY. " |
| CALL FUNCTION 'SDOK_LOIO_CREATE' "Create a Logical Document |
| EXPORTING | ||
| OBJECT_CLASS | = lv_object_class | |
| OBJECT_UNIQUE_ID | = lv_object_unique_id | |
| CLIENT | = lv_client | |
| IMPORTING | ||
| OBJECT_ID | = lv_object_id | |
| TABLES | ||
| PROPERTIES | = lt_properties | |
| EXCEPTIONS | ||
| MISSING_CLASS = 1 | ||
| BAD_CLASS = 2 | ||
| MISSING_PROPERTIES = 3 | ||
| BAD_PROPERTIES = 4 | ||
| NOT_AUTHORIZED = 5 | ||
| DUPLICATE_OBJECT_ID = 6 | ||
| EXCEPTION_IN_EXIT = 7 | ||
| . " SDOK_LOIO_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM SDOK_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 LO_CLASS FROM SDOKLOCL INTO @DATA(ld_object_class). | ||||
| "SELECT single LOIO_ID FROM SDOKLOIO INTO @DATA(ld_object_unique_id). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
Search for further information about these or an SAP related objects