SAP /ISDFPS/GET_FORCE_LOGSYS Function Module for









/ISDFPS/GET_FORCE_LOGSYS is a standard /isdfps/get force logsys 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 /isdfps/get force logsys FM, simply by entering the name /ISDFPS/GET_FORCE_LOGSYS into the relevant SAP transaction such as SE37 or SE38.

Function Group: /ISDFPS/BAPI_WF
Program Name: /ISDFPS/SAPLBAPI_WF
Main Program: /ISDFPS/SAPLBAPI_WF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /ISDFPS/GET_FORCE_LOGSYS 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 '/ISDFPS/GET_FORCE_LOGSYS'"
EXPORTING
I_FORCE_ID = "
I_FORCE_CNT = "

IMPORTING
E_LOGSYS = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for /ISDFPS/GET_FORCE_LOGSYS

I_FORCE_ID -

Data type: /ISDFPS/FORCE_ID
Optional: No
Call by Reference: Yes

I_FORCE_CNT -

Data type: /ISDFPS/FORCE_CNT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for /ISDFPS/GET_FORCE_LOGSYS

E_LOGSYS -

Data type: LOGSYS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /ISDFPS/GET_FORCE_LOGSYS 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_e_logsys  TYPE LOGSYS, "   
lv_not_found  TYPE LOGSYS, "   
lv_i_force_id  TYPE /ISDFPS/FORCE_ID, "   
lv_i_force_cnt  TYPE /ISDFPS/FORCE_CNT. "   

  CALL FUNCTION '/ISDFPS/GET_FORCE_LOGSYS'  "
    EXPORTING
         I_FORCE_ID = lv_i_force_id
         I_FORCE_CNT = lv_i_force_cnt
    IMPORTING
         E_LOGSYS = lv_e_logsys
    EXCEPTIONS
        NOT_FOUND = 1
. " /ISDFPS/GET_FORCE_LOGSYS




ABAP code using 7.40 inline data declarations to call FM /ISDFPS/GET_FORCE_LOGSYS

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.

 
 
 
 


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!