SAP SLAD_COPY_OBJECT Function Module for









SLAD_COPY_OBJECT is a standard slad copy object 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 slad copy object FM, simply by entering the name SLAD_COPY_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function SLAD_COPY_OBJECT 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 'SLAD_COPY_OBJECT'"
EXPORTING
P_SOURCE_OBJECT = "

IMPORTING
P_TARGET_OBJECT = "

EXCEPTIONS
CX_SLAD_REQUEST = 1 CX_SLAD_ILLEGAL_INPUT = 2
.



IMPORTING Parameters details for SLAD_COPY_OBJECT

P_SOURCE_OBJECT -

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

EXPORTING Parameters details for SLAD_COPY_OBJECT

P_TARGET_OBJECT -

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

EXCEPTIONS details

CX_SLAD_REQUEST -

Data type:
Optional: No
Call by Reference: Yes

CX_SLAD_ILLEGAL_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SLAD_COPY_OBJECT 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_cx_slad_request  TYPE STRING, "   
lv_p_source_object  TYPE SLAD_OBJECT_KEY, "   
lv_p_target_object  TYPE SLAD_OBJECT_KEY, "   
lv_cx_slad_illegal_input  TYPE SLAD_OBJECT_KEY. "   

  CALL FUNCTION 'SLAD_COPY_OBJECT'  "
    EXPORTING
         P_SOURCE_OBJECT = lv_p_source_object
    IMPORTING
         P_TARGET_OBJECT = lv_p_target_object
    EXCEPTIONS
        CX_SLAD_REQUEST = 1
        CX_SLAD_ILLEGAL_INPUT = 2
. " SLAD_COPY_OBJECT




ABAP code using 7.40 inline data declarations to call FM SLAD_COPY_OBJECT

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!