SAP CIF_GET_DEST_LOGSYS Function Module for NOTRANSL: Ermittle das 'Own Logsys' des Zielsystems









CIF_GET_DEST_LOGSYS is a standard cif get dest logsys SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermittle das 'Own Logsys' des Zielsystems 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 cif get dest logsys FM, simply by entering the name CIF_GET_DEST_LOGSYS into the relevant SAP transaction such as SE37 or SE38.

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



Function CIF_GET_DEST_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 'CIF_GET_DEST_LOGSYS'"NOTRANSL: Ermittle das 'Own Logsys' des Zielsystems
EXPORTING
IS_CTRLPARAMS = "Control Parameters for Data Transfers
IV_QUEUENAME = "Name of tRFC queue
* IV_COMMIT = ' ' "Checkbox

IMPORTING
EV_DEST_OWN_LOGSYS = "Logical System
EV_ASYNC_UPDATE = "Checkbox

EXCEPTIONS
BGRFC_TRANSFER_FAILED = 1
.



IMPORTING Parameters details for CIF_GET_DEST_LOGSYS

IS_CTRLPARAMS - Control Parameters for Data Transfers

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

IV_QUEUENAME - Name of tRFC queue

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

IV_COMMIT - Checkbox

Data type: XFELD
Default: SPACE
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CIF_GET_DEST_LOGSYS

EV_DEST_OWN_LOGSYS - Logical System

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

EV_ASYNC_UPDATE - Checkbox

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

EXCEPTIONS details

BGRFC_TRANSFER_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CIF_GET_DEST_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_is_ctrlparams  TYPE CIFCTRLPAR, "   
lv_ev_dest_own_logsys  TYPE LOGSYS, "   
lv_bgrfc_transfer_failed  TYPE LOGSYS, "   
lv_iv_queuename  TYPE TRFCQNAM, "   
lv_ev_async_update  TYPE XFELD, "   
lv_iv_commit  TYPE XFELD. "   SPACE

  CALL FUNCTION 'CIF_GET_DEST_LOGSYS'  "NOTRANSL: Ermittle das 'Own Logsys' des Zielsystems
    EXPORTING
         IS_CTRLPARAMS = lv_is_ctrlparams
         IV_QUEUENAME = lv_iv_queuename
         IV_COMMIT = lv_iv_commit
    IMPORTING
         EV_DEST_OWN_LOGSYS = lv_ev_dest_own_logsys
         EV_ASYNC_UPDATE = lv_ev_async_update
    EXCEPTIONS
        BGRFC_TRANSFER_FAILED = 1
. " CIF_GET_DEST_LOGSYS




ABAP code using 7.40 inline data declarations to call FM CIF_GET_DEST_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.

 
 
 
 
 
DATA(ld_iv_commit) = ' '.
 


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!