SAP SDOK_LOIOS_PHYSICAL_OBJECT_GET Function Module for Context-Specific Selection of Physical Documents









SDOK_LOIOS_PHYSICAL_OBJECT_GET is a standard sdok loios physical object get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Context-Specific Selection of Physical Documents 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 loios physical object get FM, simply by entering the name SDOK_LOIOS_PHYSICAL_OBJECT_GET 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_LOIOS_PHYSICAL_OBJECT_GET 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_LOIOS_PHYSICAL_OBJECT_GET'"Context-Specific Selection of Physical Documents
  EXPORTING
*  CLIENT = SY-MANDT "Client

TABLES
   OBJECT_LIST =  "List of Logical Information Objects
   CONTEXT =  "Context Description
*  PROPERTIES_REQUEST =  "Attribute Request List
   PHYSICAL_OBJECTS =  "Physical Information Objects for the Logical Information Objects
*  COVER_LOIOS =  "Assignment of Original to Substitute LOIO for LOIO Switch in Application Exit
*  PROPERTIES_RESULT =  "Attribute Results List
*  BAD_OBJECTS =  "Logical Object Without Suitable Physical Object
.



IMPORTING Parameters details for SDOK_LOIOS_PHYSICAL_OBJECT_GET

CLIENT - Client

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

TABLES Parameters details for SDOK_LOIOS_PHYSICAL_OBJECT_GET

OBJECT_LIST - List of Logical Information Objects

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

CONTEXT - Context Description

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

PROPERTIES_REQUEST - Attribute Request List

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

PHYSICAL_OBJECTS - Physical Information Objects for the Logical Information Objects

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

COVER_LOIOS - Assignment of Original to Substitute LOIO for LOIO Switch in Application Exit

Data type: SDOKLOGLOG
Optional: Yes
Call by Reference: Yes

PROPERTIES_RESULT - Attribute Results List

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

BAD_OBJECTS - Logical Object Without Suitable Physical Object

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

Copy and paste ABAP code example for SDOK_LOIOS_PHYSICAL_OBJECT_GET 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_client  TYPE SY-MANDT, "   SY-MANDT
lt_object_list  TYPE STANDARD TABLE OF SDOKOBJECT, "   
lt_context  TYPE STANDARD TABLE OF SDOKPROPTY, "   
lt_properties_request  TYPE STANDARD TABLE OF SDOKPROPTN, "   
lt_physical_objects  TYPE STANDARD TABLE OF SDOKLOGPHY, "   
lt_cover_loios  TYPE STANDARD TABLE OF SDOKLOGLOG, "   
lt_properties_result  TYPE STANDARD TABLE OF SDOKPROPTL, "   
lt_bad_objects  TYPE STANDARD TABLE OF SDOKERRMSG. "   

  CALL FUNCTION 'SDOK_LOIOS_PHYSICAL_OBJECT_GET'  "Context-Specific Selection of Physical Documents
    EXPORTING
         CLIENT = lv_client
    TABLES
         OBJECT_LIST = lt_object_list
         CONTEXT = lt_context
         PROPERTIES_REQUEST = lt_properties_request
         PHYSICAL_OBJECTS = lt_physical_objects
         COVER_LOIOS = lt_cover_loios
         PROPERTIES_RESULT = lt_properties_result
         BAD_OBJECTS = lt_bad_objects
. " SDOK_LOIOS_PHYSICAL_OBJECT_GET




ABAP code using 7.40 inline data declarations to call FM SDOK_LOIOS_PHYSICAL_OBJECT_GET

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 MANDT FROM SY 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!