SAP OUTBOUND_CALL_00700410_P Function Module for









OUTBOUND_CALL_00700410_P is a standard outbound call 00700410 p 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 outbound call 00700410 p FM, simply by entering the name OUTBOUND_CALL_00700410_P into the relevant SAP transaction such as SE37 or SE38.

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



Function OUTBOUND_CALL_00700410_P 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 'OUTBOUND_CALL_00700410_P'"
EXPORTING
I_VIOB01 = "
I_VIMI01 = "
I_VIKOKO = "
I_VZSORT = "
I_SANO1 = "
I_AKTYP = "

TABLES
IT_AREA = "
IT_VIOB39 = "
IT_VIOB42 = "
ET_MSG = "
IT_VZZKOPO = "
IT_VIMI08 = "
IT_VIMI02 = "
IT_VIOB10 = "
IT_VIMI38 = "
IT_VZGPO = "
IT_VIEIGE = "
IT_VIOB38 = "
.



IMPORTING Parameters details for OUTBOUND_CALL_00700410_P

I_VIOB01 -

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

I_VIMI01 -

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

I_VIKOKO -

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

I_VZSORT -

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

I_SANO1 -

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

I_AKTYP -

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

TABLES Parameters details for OUTBOUND_CALL_00700410_P

IT_AREA -

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

IT_VIOB39 -

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

IT_VIOB42 -

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

ET_MSG -

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

IT_VZZKOPO -

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

IT_VIMI08 -

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

IT_VIMI02 -

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

IT_VIOB10 -

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

IT_VIMI38 -

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

IT_VZGPO -

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

IT_VIEIGE -

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

IT_VIOB38 -

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

Copy and paste ABAP code example for OUTBOUND_CALL_00700410_P 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_it_area  TYPE STANDARD TABLE OF VIOB41, "   
lv_i_viob01  TYPE VIOB01, "   
lt_it_viob39  TYPE STANDARD TABLE OF VIOB39, "   
lt_it_viob42  TYPE STANDARD TABLE OF VIOB42, "   
lt_et_msg  TYPE STANDARD TABLE OF SYMSG, "   
lv_i_vimi01  TYPE VIMI01, "   
lt_it_vzzkopo  TYPE STANDARD TABLE OF VZZKOPO, "   
lv_i_vikoko  TYPE VIKOKO, "   
lt_it_vimi08  TYPE STANDARD TABLE OF VIMI08, "   
lv_i_vzsort  TYPE VZSORT, "   
lt_it_vimi02  TYPE STANDARD TABLE OF VIMI02, "   
lv_i_sano1  TYPE SANO1, "   
lt_it_viob10  TYPE STANDARD TABLE OF VIOB10, "   
lv_i_aktyp  TYPE BU_AKTYP, "   
lt_it_vimi38  TYPE STANDARD TABLE OF VIMI38, "   
lt_it_vzgpo  TYPE STANDARD TABLE OF VZGPO, "   
lt_it_vieige  TYPE STANDARD TABLE OF VIEIGE, "   
lt_it_viob38  TYPE STANDARD TABLE OF VIOB38. "   

  CALL FUNCTION 'OUTBOUND_CALL_00700410_P'  "
    EXPORTING
         I_VIOB01 = lv_i_viob01
         I_VIMI01 = lv_i_vimi01
         I_VIKOKO = lv_i_vikoko
         I_VZSORT = lv_i_vzsort
         I_SANO1 = lv_i_sano1
         I_AKTYP = lv_i_aktyp
    TABLES
         IT_AREA = lt_it_area
         IT_VIOB39 = lt_it_viob39
         IT_VIOB42 = lt_it_viob42
         ET_MSG = lt_et_msg
         IT_VZZKOPO = lt_it_vzzkopo
         IT_VIMI08 = lt_it_vimi08
         IT_VIMI02 = lt_it_vimi02
         IT_VIOB10 = lt_it_viob10
         IT_VIMI38 = lt_it_vimi38
         IT_VZGPO = lt_it_vzgpo
         IT_VIEIGE = lt_it_vieige
         IT_VIOB38 = lt_it_viob38
. " OUTBOUND_CALL_00700410_P




ABAP code using 7.40 inline data declarations to call FM OUTBOUND_CALL_00700410_P

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!