SAP SVMCRT_TRANS_JARC_UPLOAD Function Module for









SVMCRT_TRANS_JARC_UPLOAD is a standard svmcrt trans jarc upload 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 svmcrt trans jarc upload FM, simply by entering the name SVMCRT_TRANS_JARC_UPLOAD into the relevant SAP transaction such as SE37 or SE38.

Function Group: SVMCRT_TRANS
Program Name: SAPLSVMCRT_TRANS
Main Program: SAPLSVMCRT_TRANS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SVMCRT_TRANS_JARC_UPLOAD 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 'SVMCRT_TRANS_JARC_UPLOAD'"
  EXPORTING
   PF_MODULENAME =  "
   PF_COMPONENTNAME =  "
   PF_DEVCLASS =  "
*  PF_TRKORR =  "
   PF_DESCRIPTION =  "
   PF_FILENAME =  "
*  PF_IS_STICKY =  "

EXCEPTIONS
   MODULENAME_INVALID = 1    LOCKED = 10    DEPLOYMENT_FAILED = 11    JAVA_NOT_ACTIVE = 12    TADIR_ENTRY_CREATION_FAILED = 13    COMPONENTNAME_INVALID = 2    DEVCLASS_OR_TRKORR_INVALID = 3    PARAMETER_MISSING = 4    DESCRIPTION_MISSING = 5    CTS_CHECK_FAILED = 6    PERMISSION_DENIED = 7    FILE_NOT_READABLE = 8    CTS_ORDER_INSERT_FAILED = 9
.



IMPORTING Parameters details for SVMCRT_TRANS_JARC_UPLOAD

PF_MODULENAME -

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

PF_COMPONENTNAME -

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

PF_DEVCLASS -

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

PF_TRKORR -

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

PF_DESCRIPTION -

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

PF_FILENAME -

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

PF_IS_STICKY -

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

EXCEPTIONS details

MODULENAME_INVALID -

Data type:
Optional: No
Call by Reference: Yes

LOCKED -

Data type:
Optional: No
Call by Reference: Yes

DEPLOYMENT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

JAVA_NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: Yes

TADIR_ENTRY_CREATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

COMPONENTNAME_INVALID -

Data type:
Optional: No
Call by Reference: Yes

DEVCLASS_OR_TRKORR_INVALID -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_MISSING -

Data type:
Optional: No
Call by Reference: Yes

DESCRIPTION_MISSING -

Data type:
Optional: No
Call by Reference: Yes

CTS_CHECK_FAILED -

Data type:
Optional: No
Call by Reference: Yes

PERMISSION_DENIED -

Data type:
Optional: No
Call by Reference: Yes

FILE_NOT_READABLE -

Data type:
Optional: No
Call by Reference: Yes

CTS_ORDER_INSERT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SVMCRT_TRANS_JARC_UPLOAD 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_pf_modulename  TYPE SVMCRTMODNAME, "   
lv_modulename_invalid  TYPE SVMCRTMODNAME, "   
lv_locked  TYPE SVMCRTMODNAME, "   
lv_deployment_failed  TYPE SVMCRTMODNAME, "   
lv_java_not_active  TYPE SVMCRTMODNAME, "   
lv_tadir_entry_creation_failed  TYPE SVMCRTMODNAME, "   
lv_pf_componentname  TYPE SVMCRTCOMPNAME, "   
lv_componentname_invalid  TYPE SVMCRTCOMPNAME, "   
lv_pf_devclass  TYPE DEVCLASS, "   
lv_devclass_or_trkorr_invalid  TYPE DEVCLASS, "   
lv_pf_trkorr  TYPE TRKORR, "   
lv_parameter_missing  TYPE TRKORR, "   
lv_pf_description  TYPE SVMCRTMODDESCR, "   
lv_description_missing  TYPE SVMCRTMODDESCR, "   
lv_pf_filename  TYPE TEXT255, "   
lv_cts_check_failed  TYPE TEXT255, "   
lv_pf_is_sticky  TYPE XFLAG, "   
lv_permission_denied  TYPE XFLAG, "   
lv_file_not_readable  TYPE XFLAG, "   
lv_cts_order_insert_failed  TYPE XFLAG. "   

  CALL FUNCTION 'SVMCRT_TRANS_JARC_UPLOAD'  "
    EXPORTING
         PF_MODULENAME = lv_pf_modulename
         PF_COMPONENTNAME = lv_pf_componentname
         PF_DEVCLASS = lv_pf_devclass
         PF_TRKORR = lv_pf_trkorr
         PF_DESCRIPTION = lv_pf_description
         PF_FILENAME = lv_pf_filename
         PF_IS_STICKY = lv_pf_is_sticky
    EXCEPTIONS
        MODULENAME_INVALID = 1
        LOCKED = 10
        DEPLOYMENT_FAILED = 11
        JAVA_NOT_ACTIVE = 12
        TADIR_ENTRY_CREATION_FAILED = 13
        COMPONENTNAME_INVALID = 2
        DEVCLASS_OR_TRKORR_INVALID = 3
        PARAMETER_MISSING = 4
        DESCRIPTION_MISSING = 5
        CTS_CHECK_FAILED = 6
        PERMISSION_DENIED = 7
        FILE_NOT_READABLE = 8
        CTS_ORDER_INSERT_FAILED = 9
. " SVMCRT_TRANS_JARC_UPLOAD




ABAP code using 7.40 inline data declarations to call FM SVMCRT_TRANS_JARC_UPLOAD

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!