SAP CONN_BUPA_ATTRIB_CONV Function Module for









CONN_BUPA_ATTRIB_CONV is a standard conn bupa attrib conv 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 conn bupa attrib conv FM, simply by entering the name CONN_BUPA_ATTRIB_CONV into the relevant SAP transaction such as SE37 or SE38.

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



Function CONN_BUPA_ATTRIB_CONV 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 'CONN_BUPA_ATTRIB_CONV'"
  EXPORTING
   FLT_VAL =  "Data Element and Context Name
   I_DIRECTION =  "Direction in Conversion of Internal/External Display
   IV_PARTNER_GUID =  "Field name
   IV_PARTNER_ID =  "Field name

 IMPORTING
   E_WAS_EXECUTED =  "Boolean Variable
   E_RESULT =  "Return Code

CHANGING
   CT_MNT_APPLICATION_LOG =  "Entries in Application Log in Condition Maintenance
   CS_WORKING_SET_ITEM_INT =  "Generic Type
   CS_WORKING_SET_ITEM_EXT =  "Generic Type
.



IMPORTING Parameters details for CONN_BUPA_ATTRIB_CONV

FLT_VAL - Data Element and Context Name

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

I_DIRECTION - Direction in Conversion of Internal/External Display

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

IV_PARTNER_GUID - Field name

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

IV_PARTNER_ID - Field name

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

EXPORTING Parameters details for CONN_BUPA_ATTRIB_CONV

E_WAS_EXECUTED - Boolean Variable

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

E_RESULT - Return Code

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

CHANGING Parameters details for CONN_BUPA_ATTRIB_CONV

CT_MNT_APPLICATION_LOG - Entries in Application Log in Condition Maintenance

Data type: /SAPCND/T_MNT_APPLICATION_LOG
Optional: No
Call by Reference: Yes

CS_WORKING_SET_ITEM_INT - Generic Type

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

CS_WORKING_SET_ITEM_EXT - Generic Type

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

Copy and paste ABAP code example for CONN_BUPA_ATTRIB_CONV 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_flt_val  TYPE /SAPCND/ROLLNAME_CONTEXTNAME, "   
lv_e_was_executed  TYPE /SAPCND/BOOLEAN, "   
lv_ct_mnt_application_log  TYPE /SAPCND/T_MNT_APPLICATION_LOG, "   
lv_e_result  TYPE SYSUBRC, "   
lv_i_direction  TYPE /SAPCND/DIRECTION, "   
lv_cs_working_set_item_int  TYPE ANY, "   
lv_iv_partner_guid  TYPE /SAPCND/FIELDNAME, "   
lv_cs_working_set_item_ext  TYPE ANY, "   
lv_iv_partner_id  TYPE /SAPCND/FIELDNAME. "   

  CALL FUNCTION 'CONN_BUPA_ATTRIB_CONV'  "
    EXPORTING
         FLT_VAL = lv_flt_val
         I_DIRECTION = lv_i_direction
         IV_PARTNER_GUID = lv_iv_partner_guid
         IV_PARTNER_ID = lv_iv_partner_id
    IMPORTING
         E_WAS_EXECUTED = lv_e_was_executed
         E_RESULT = lv_e_result
    CHANGING
         CT_MNT_APPLICATION_LOG = lv_ct_mnt_application_log
         CS_WORKING_SET_ITEM_INT = lv_cs_working_set_item_int
         CS_WORKING_SET_ITEM_EXT = lv_cs_working_set_item_ext
. " CONN_BUPA_ATTRIB_CONV




ABAP code using 7.40 inline data declarations to call FM CONN_BUPA_ATTRIB_CONV

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!