BBP_CT_MAP_ATTRIBUTE SAP Function module

BBP_CT_MAP_ATTRIBUTE 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 BBP_CT_MAP_ATTRIBUTE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BBP_CT_MAP_ATTRIBUTE - BBP CT MAP ATTRIBUTE

CALL FUNCTION 'BBP_CT_MAP_ATTRIBUTE' "
  EXPORTING
    i_content_provider_guid =   " bbpt_ct_partner_guid
    i_standard_schema_type =    " schema_type
    i_schema_owner =            " bbp_schema_owner
*   i_schema_id = SPACE         " bbp_schema_id
    i_attribute_id =            " bbp_ct_attribute_id
  IMPORTING
    e_settype_guid =            " comt_frgtype_guid
    e_my_attr_guid =            " comt_attr_guid
    e_my_attr_id =              " comt_attr_id
  EXCEPTIONS
    MAP_ERROR = 1               "
    IGNORE_RECORD = 2           "
    TRANSFER_NAMEVALUE = 3      "
    .  "  BBP_CT_MAP_ATTRIBUTE

ABAP code example for Function Module BBP_CT_MAP_ATTRIBUTE

The ABAP code below is a full code listing to execute function module BBP_CT_MAP_ATTRIBUTE 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:
ld_e_settype_guid  
 
 TYPE COMT_FRGTYPE_GUID
,
ld_e_my_attr_guid  
 
 TYPE COMT_ATTR_GUID
,
ld_e_my_attr_id  
 
 TYPE COMT_ATTR_ID
.


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

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

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

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

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

CALL FUNCTION 'BBP_CT_MAP_ATTRIBUTE'
  EXPORTING
    i_content_provider_guid =    ld_i_content_provider_guid
    i_standard_schema_type =     ld_i_standard_schema_type
    i_schema_owner =             ld_i_schema_owner
*   i_schema_id =                ld_i_schema_id
    i_attribute_id =             ld_i_attribute_id
  IMPORTING
    e_settype_guid =             ld_e_settype_guid
    e_my_attr_guid =             ld_e_my_attr_guid
    e_my_attr_id =               ld_e_my_attr_id
  EXCEPTIONS
    MAP_ERROR =                  1
    IGNORE_RECORD =              2
    TRANSFER_NAMEVALUE =         3
    .  "  BBP_CT_MAP_ATTRIBUTE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
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_e_settype_guid
 
 TYPE COMT_FRGTYPE_GUID ,
ld_i_content_provider_guid
 
 TYPE BBPT_CT_PARTNER_GUID ,
ld_e_my_attr_guid
 
 TYPE COMT_ATTR_GUID ,
ld_i_standard_schema_type
 
 TYPE SCHEMA_TYPE ,
ld_e_my_attr_id
 
 TYPE COMT_ATTR_ID ,
ld_i_schema_owner
 
 TYPE BBP_SCHEMA_OWNER ,
ld_i_schema_id
 
 TYPE BBP_SCHEMA_ID ,
ld_i_attribute_id
 
 TYPE BBP_CT_ATTRIBUTE_ID .


ld_i_content_provider_guid = 'Check type of data required'.
ld_i_standard_schema_type = 'Check type of data required'.
ld_i_schema_owner = 'Check type of data required'.
ld_i_schema_id = 'Check type of data required'.
ld_i_attribute_id = 'Check type of data required'.