SAP RV_EXPORT_CONTROL_DELIVERY Function Module for NOTRANSL: Gesetzliche Kontrolle: Durchführung der Ges. Kontrolle in der Li









RV_EXPORT_CONTROL_DELIVERY is a standard rv export control delivery 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: Gesetzliche Kontrolle: Durchführung der Ges. Kontrolle in der Li 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 rv export control delivery FM, simply by entering the name RV_EXPORT_CONTROL_DELIVERY into the relevant SAP transaction such as SE37 or SE38.

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



Function RV_EXPORT_CONTROL_DELIVERY 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 'RV_EXPORT_CONTROL_DELIVERY'"NOTRANSL: Gesetzliche Kontrolle: Durchführung der Ges. Kontrolle in der Li
EXPORTING
EXPORT_DATE_NEW = "Export Date : New
* I_PREDECESSOR_DOCUMENT = ' ' "
* EXPORT_DATE_OLD = '00000000' "Export Date : Old
CONSIGNEE_NEW = "Export Partner: Ship-to Party : New
* CONSIGNEE_OLD = ' ' "Export Partner: Ship-to Party : Old
* EXPORT_NUMBER = ' ' "Export Data : EIKP Segment Number
* LINE_LIPS = ' ' "Workarea : Delivery : Item Data
* LINE_VBPA = ' ' "Workarea : Partner Data
* I_PROT_ACTIVE = ' ' "Kennzeichen : Protokoll ausgeben beim Sichern
* I_LOG_LEVEL = ' ' "Kennzeichen : Ebene des zu sichernden Protok.

IMPORTING
E_PROTOCOL = "Log flag:E_ANALY is not empty

TABLES
* I_VBAPVB = "Table : Order : Item Data
* I_VBPAVB = "Table : Partner Data
* I_LIPSVB = "Tabelle : Lieferung : Positionsdaten
* E_ANALY = "Analysis Result from Export Control
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV52E_001 SD Legal Control: User exit for additional license checks

IMPORTING Parameters details for RV_EXPORT_CONTROL_DELIVERY

EXPORT_DATE_NEW - Export Date : New

Data type: LIKP-LFDAT
Optional: No
Call by Reference: No ( called with pass by value option)

I_PREDECESSOR_DOCUMENT -

Data type: TVLK-AUFER
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORT_DATE_OLD - Export Date : Old

Data type: LIKP-LFDAT
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

CONSIGNEE_NEW - Export Partner: Ship-to Party : New

Data type: LIKP-KUNNR
Optional: No
Call by Reference: No ( called with pass by value option)

CONSIGNEE_OLD - Export Partner: Ship-to Party : Old

Data type: LIKP-KUNNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORT_NUMBER - Export Data : EIKP Segment Number

Data type: LIKP-EXNUM
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

LINE_LIPS - Workarea : Delivery : Item Data

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

LINE_VBPA - Workarea : Partner Data

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

I_PROT_ACTIVE - Kennzeichen : Protokoll ausgeben beim Sichern

Data type: TVAK-EXDIA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LOG_LEVEL - Kennzeichen : Ebene des zu sichernden Protok.

Data type: TVLK-EXCLG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RV_EXPORT_CONTROL_DELIVERY

E_PROTOCOL - Log flag:E_ANALY is not empty

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

TABLES Parameters details for RV_EXPORT_CONTROL_DELIVERY

I_VBAPVB - Table : Order : Item Data

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

I_VBPAVB - Table : Partner Data

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

I_LIPSVB - Tabelle : Lieferung : Positionsdaten

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

E_ANALY - Analysis Result from Export Control

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

Copy and paste ABAP code example for RV_EXPORT_CONTROL_DELIVERY 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_vbapvb  TYPE STANDARD TABLE OF VBAPVB, "   
lv_e_protocol  TYPE VBAPVB, "   
lv_export_date_new  TYPE LIKP-LFDAT, "   
lv_i_predecessor_document  TYPE TVLK-AUFER, "   SPACE
lt_i_vbpavb  TYPE STANDARD TABLE OF VBPAVB, "   
lv_export_date_old  TYPE LIKP-LFDAT, "   '00000000'
lt_i_lipsvb  TYPE STANDARD TABLE OF LIPSVB, "   
lv_consignee_new  TYPE LIKP-KUNNR, "   
lt_e_analy  TYPE STANDARD TABLE OF VBEXAN, "   
lv_consignee_old  TYPE LIKP-KUNNR, "   SPACE
lv_export_number  TYPE LIKP-EXNUM, "   SPACE
lv_line_lips  TYPE LIPS, "   SPACE
lv_line_vbpa  TYPE VBPA, "   SPACE
lv_i_prot_active  TYPE TVAK-EXDIA, "   SPACE
lv_i_log_level  TYPE TVLK-EXCLG. "   SPACE

  CALL FUNCTION 'RV_EXPORT_CONTROL_DELIVERY'  "NOTRANSL: Gesetzliche Kontrolle: Durchführung der Ges. Kontrolle in der Li
    EXPORTING
         EXPORT_DATE_NEW = lv_export_date_new
         I_PREDECESSOR_DOCUMENT = lv_i_predecessor_document
         EXPORT_DATE_OLD = lv_export_date_old
         CONSIGNEE_NEW = lv_consignee_new
         CONSIGNEE_OLD = lv_consignee_old
         EXPORT_NUMBER = lv_export_number
         LINE_LIPS = lv_line_lips
         LINE_VBPA = lv_line_vbpa
         I_PROT_ACTIVE = lv_i_prot_active
         I_LOG_LEVEL = lv_i_log_level
    IMPORTING
         E_PROTOCOL = lv_e_protocol
    TABLES
         I_VBAPVB = lt_i_vbapvb
         I_VBPAVB = lt_i_vbpavb
         I_LIPSVB = lt_i_lipsvb
         E_ANALY = lt_e_analy
. " RV_EXPORT_CONTROL_DELIVERY




ABAP code using 7.40 inline data declarations to call FM RV_EXPORT_CONTROL_DELIVERY

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.

 
 
"SELECT single LFDAT FROM LIKP INTO @DATA(ld_export_date_new).
 
"SELECT single AUFER FROM TVLK INTO @DATA(ld_i_predecessor_document).
DATA(ld_i_predecessor_document) = ' '.
 
 
"SELECT single LFDAT FROM LIKP INTO @DATA(ld_export_date_old).
DATA(ld_export_date_old) = '00000000'.
 
 
"SELECT single KUNNR FROM LIKP INTO @DATA(ld_consignee_new).
 
 
"SELECT single KUNNR FROM LIKP INTO @DATA(ld_consignee_old).
DATA(ld_consignee_old) = ' '.
 
"SELECT single EXNUM FROM LIKP INTO @DATA(ld_export_number).
DATA(ld_export_number) = ' '.
 
DATA(ld_line_lips) = ' '.
 
DATA(ld_line_vbpa) = ' '.
 
"SELECT single EXDIA FROM TVAK INTO @DATA(ld_i_prot_active).
DATA(ld_i_prot_active) = ' '.
 
"SELECT single EXCLG FROM TVLK INTO @DATA(ld_i_log_level).
DATA(ld_i_log_level) = ' '.
 


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!