SAP ROS_BUPA_CREATE_PROSP Function Module for









ROS_BUPA_CREATE_PROSP is a standard ros bupa create prosp 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 ros bupa create prosp FM, simply by entering the name ROS_BUPA_CREATE_PROSP into the relevant SAP transaction such as SE37 or SE38.

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



Function ROS_BUPA_CREATE_PROSP 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 'ROS_BUPA_CREATE_PROSP'"
  EXPORTING
   IS_DATA =  "
   IS_DATA_ORGAN =  "
   IS_ADDRESS =  "
*  IV_DUNS_ID =  "

 IMPORTING
   EV_PARTNER =  "
   EV_PARTNER_GUID =  "
   EV_SUPP_EXIST =  "
   EV_CUSTOMER_INFO =  "

TABLES
   IT_ADTEL =  "
*  IT_ADFAX =  "
   IT_ADSMTP =  "
*  IT_PROD_CAT =  "
*  ET_RETURN =  "
.



IMPORTING Parameters details for ROS_BUPA_CREATE_PROSP

IS_DATA -

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

IS_DATA_ORGAN -

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

IS_ADDRESS -

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

IV_DUNS_ID -

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

EXPORTING Parameters details for ROS_BUPA_CREATE_PROSP

EV_PARTNER -

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

EV_PARTNER_GUID -

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

EV_SUPP_EXIST -

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

EV_CUSTOMER_INFO -

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

TABLES Parameters details for ROS_BUPA_CREATE_PROSP

IT_ADTEL -

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

IT_ADFAX -

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

IT_ADSMTP -

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

IT_PROD_CAT -

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

ET_RETURN -

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

Copy and paste ABAP code example for ROS_BUPA_CREATE_PROSP 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_is_data  TYPE BAPIBUS1006_CENTRAL, "   
lt_it_adtel  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_ev_partner  TYPE BU_PARTNER, "   
lt_it_adfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_is_data_organ  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lv_ev_partner_guid  TYPE BU_PARTNER_GUID, "   
lt_it_adsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_is_address  TYPE BAPIBUS1006_ADDRESS, "   
lv_ev_supp_exist  TYPE XFELD, "   
lv_iv_duns_id  TYPE BBP_CT_DUNS, "   
lt_it_prod_cat  TYPE STANDARD TABLE OF BIDCC, "   
lv_ev_customer_info  TYPE STRING, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'ROS_BUPA_CREATE_PROSP'  "
    EXPORTING
         IS_DATA = lv_is_data
         IS_DATA_ORGAN = lv_is_data_organ
         IS_ADDRESS = lv_is_address
         IV_DUNS_ID = lv_iv_duns_id
    IMPORTING
         EV_PARTNER = lv_ev_partner
         EV_PARTNER_GUID = lv_ev_partner_guid
         EV_SUPP_EXIST = lv_ev_supp_exist
         EV_CUSTOMER_INFO = lv_ev_customer_info
    TABLES
         IT_ADTEL = lt_it_adtel
         IT_ADFAX = lt_it_adfax
         IT_ADSMTP = lt_it_adsmtp
         IT_PROD_CAT = lt_it_prod_cat
         ET_RETURN = lt_et_return
. " ROS_BUPA_CREATE_PROSP




ABAP code using 7.40 inline data declarations to call FM ROS_BUPA_CREATE_PROSP

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!