SAP SCTC_CONV_LOGSYS_NAME_2 Function Module for Concurrent jobs for logical system name conversion









SCTC_CONV_LOGSYS_NAME_2 is a standard sctc conv logsys name 2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Concurrent jobs for logical system name conversion 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 sctc conv logsys name 2 FM, simply by entering the name SCTC_CONV_LOGSYS_NAME_2 into the relevant SAP transaction such as SE37 or SE38.

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



Function SCTC_CONV_LOGSYS_NAME_2 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 'SCTC_CONV_LOGSYS_NAME_2'"Concurrent jobs for logical system name conversion
  EXPORTING
   IV_NEW_LOGSYS =  "Logical System
*  IV_MAXSIZE = 100000 "Processed Database Table Rows
*  IV_VARIANT = '0' "Character Field Length 1
*  IV_FLG_RELEASE = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
*  IV_FLG_CHECK_NAMES = 'X' "Boolean Variable (X=True, -=False, Space=Unknown)
*  IV_OLD_LOGSYS =  "Logical System
*  IV_CLIENT =  "Client

TABLES
*  I_TAB_PAIRS =  "Pairs of logical system names for conversion
*  I_RNG_PAIR_TABNAME =  "Structure for ranges table with tabname
*  E_TAB_RETURN =  "Return Parameter
.



IMPORTING Parameters details for SCTC_CONV_LOGSYS_NAME_2

IV_NEW_LOGSYS - Logical System

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

IV_MAXSIZE - Processed Database Table Rows

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

IV_VARIANT - Character Field Length 1

Data type: CHAR01
Default: '0'
Optional: No
Call by Reference: No ( called with pass by value option)

IV_FLG_RELEASE - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FLG_CHECK_NAMES - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_OLD_LOGSYS - Logical System

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

IV_CLIENT - Client

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

TABLES Parameters details for SCTC_CONV_LOGSYS_NAME_2

I_TAB_PAIRS - Pairs of logical system names for conversion

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

I_RNG_PAIR_TABNAME - Structure for ranges table with tabname

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

E_TAB_RETURN - Return Parameter

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

Copy and paste ABAP code example for SCTC_CONV_LOGSYS_NAME_2 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:
lt_i_tab_pairs  TYPE STANDARD TABLE OF SCTC_SC_S_CONV_PAIRS, "   
lv_iv_new_logsys  TYPE LOGSYS, "   
lv_iv_maxsize  TYPE SYDBCNT, "   100000
lt_i_rng_pair_tabname  TYPE STANDARD TABLE OF SCTC_SC_S_RNG_TABNAME, "   
lv_iv_variant  TYPE CHAR01, "   '0'
lt_e_tab_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_flg_release  TYPE BOOLEAN, "   'X'
lv_iv_flg_check_names  TYPE BOOLEAN, "   'X'
lv_iv_old_logsys  TYPE LOGSYS, "   
lv_iv_client  TYPE MANDT. "   

  CALL FUNCTION 'SCTC_CONV_LOGSYS_NAME_2'  "Concurrent jobs for logical system name conversion
    EXPORTING
         IV_NEW_LOGSYS = lv_iv_new_logsys
         IV_MAXSIZE = lv_iv_maxsize
         IV_VARIANT = lv_iv_variant
         IV_FLG_RELEASE = lv_iv_flg_release
         IV_FLG_CHECK_NAMES = lv_iv_flg_check_names
         IV_OLD_LOGSYS = lv_iv_old_logsys
         IV_CLIENT = lv_iv_client
    TABLES
         I_TAB_PAIRS = lt_i_tab_pairs
         I_RNG_PAIR_TABNAME = lt_i_rng_pair_tabname
         E_TAB_RETURN = lt_e_tab_return
. " SCTC_CONV_LOGSYS_NAME_2




ABAP code using 7.40 inline data declarations to call FM SCTC_CONV_LOGSYS_NAME_2

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_maxsize) = 100000.
 
 
DATA(ld_iv_variant) = '0'.
 
 
DATA(ld_iv_flg_release) = 'X'.
 
DATA(ld_iv_flg_check_names) = 'X'.
 
 
 


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!