EXIT_SAPLV50R_CREA_001 SAP Function module - Data Transfer - BAPI Interface External -> Internal

EXIT_SAPLV50R_CREA_001 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EXIT_SAPLV50R_CREA_001 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: XV50RCREA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM EXIT_SAPLV50R_CREA_001 - EXIT SAPLV50R CREA 001

CALL FUNCTION 'EXIT_SAPLV50R_CREA_001' "Data Transfer - BAPI Interface External -> Internal
  EXPORTING
    is_techn_control =          " bapideliciouscontrol  Technical Control Delivery BAPI
    is_delivery_extend =        " bapideliciousdelivery  Delivery That Is To Be Added to
  TABLES
    it_extension1 =             " bapiextc      Container for 'Customer Exit' Parameters
    it_extension2 =             " bapiext       Container for 'Customer Exit' Parameters
    it_request =                " bapideliciousrequest  Interface for Creating Deliveries
  CHANGING
    cs_delivery_extend =        " leshp_delivery_extend_rv  Data for Enhancement of Deliveries in RV_DELIVERY_CREATE
    cs_control =                " leshp_delivery_proc_control_in  Control Parameters - Delivery Processing (Internal View)
    ct_interface_internal =     " leshp_delivery_create_t  Internal Interface for Creating Deliveries
    ct_package_to_deliver =     " shp_vl10_package_t  Table with Packets of Items (Order Combination)
    .  "  EXIT_SAPLV50R_CREA_001

ABAP code example for Function Module EXIT_SAPLV50R_CREA_001

The ABAP code below is a full code listing to execute function module EXIT_SAPLV50R_CREA_001 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_it_extension1  
 
 TYPE STANDARD TABLE OF BAPIEXTC,"TABLES PARAM
wa_it_extension1
 
 LIKE LINE OF it_it_extension1
,
it_it_extension2  
 
 TYPE STANDARD TABLE OF BAPIEXT,"TABLES PARAM
wa_it_extension2
 
 LIKE LINE OF it_it_extension2
,
it_it_request  
 
 TYPE STANDARD TABLE OF BAPIDELICIOUSREQUEST,"TABLES PARAM
wa_it_request
 
 LIKE LINE OF it_it_request
.


DATA(ld_cs_delivery_extend) = 'Check type of data required'.

DATA(ld_cs_control) = 'Check type of data required'.

DATA(ld_ct_interface_internal) = 'Check type of data required'.

DATA(ld_ct_package_to_deliver) = 'Check type of data required'.

DATA(ld_is_techn_control) = 'Check type of data required'.

DATA(ld_is_delivery_extend) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_it_extension1 to it_it_extension1.
 

"populate fields of struture and append to itab
append wa_it_extension2 to it_it_extension2.
 

"populate fields of struture and append to itab
append wa_it_request to it_it_request.
.

CALL FUNCTION 'EXIT_SAPLV50R_CREA_001'
  EXPORTING
    is_techn_control =           ld_is_techn_control
    is_delivery_extend =         ld_is_delivery_extend
  TABLES
    it_extension1 =              it_it_extension1
    it_extension2 =              it_it_extension2
    it_request =                 it_it_request
  CHANGING
    cs_delivery_extend =         ld_cs_delivery_extend
    cs_control =                 ld_cs_control
    ct_interface_internal =      ld_ct_interface_internal
    ct_package_to_deliver =      ld_ct_package_to_deliver
    .  "  EXIT_SAPLV50R_CREA_001

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_cs_delivery_extend
 
 TYPE LESHP_DELIVERY_EXTEND_RV ,
ld_is_techn_control
 
 TYPE BAPIDELICIOUSCONTROL ,
it_it_extension1
 
 TYPE STANDARD TABLE OF BAPIEXTC ,
wa_it_extension1
 
 LIKE LINE OF it_it_extension1,
ld_cs_control
 
 TYPE LESHP_DELIVERY_PROC_CONTROL_IN ,
ld_is_delivery_extend
 
 TYPE BAPIDELICIOUSDELIVERY ,
it_it_extension2
 
 TYPE STANDARD TABLE OF BAPIEXT ,
wa_it_extension2
 
 LIKE LINE OF it_it_extension2,
ld_ct_interface_internal
 
 TYPE LESHP_DELIVERY_CREATE_T ,
it_it_request
 
 TYPE STANDARD TABLE OF BAPIDELICIOUSREQUEST ,
wa_it_request
 
 LIKE LINE OF it_it_request,
ld_ct_package_to_deliver
 
 TYPE SHP_VL10_PACKAGE_T .


ld_cs_delivery_extend = 'Check type of data required'.
ld_is_techn_control = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_extension1 to it_it_extension1.
ld_cs_control = 'Check type of data required'.
ld_is_delivery_extend = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_extension2 to it_it_extension2.
ld_ct_interface_internal = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_it_request to it_it_request.
ld_ct_package_to_deliver = 'Check type of data required'.

SAP Documentation for FM EXIT_SAPLV50R_CREA_001