CONV_API_CONVERT_BOM_ASSEMBLY SAP Function module

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

Associated Function Group: CONV_API
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CONV_API_CONVERT_BOM_ASSEMBLY - CONV API CONVERT BOM ASSEMBLY

CALL FUNCTION 'CONV_API_CONVERT_BOM_ASSEMBLY' "
  EXPORTING
*   change_number_int =         " aennr
*   change_number =             " aennr
*   key_date_int =              " datum
*   key_date =                  " csap_mbom-datuv
*   material_root_int =         " mbm_class_data-matnr
*   material_root =             " csap_mbom-matnr
*   plant_root =                " mbm_class_data-werks
    application =               " tc04-capid
    type_filter =               " draw-dokar
*   version_filter =            " draw-dokvr
    application_filter =        " draw-dappl
*   document_status_int =       " dokst
*   document_status =           " tdwst-stabk
*   foreground =                " xfeld
  IMPORTING
    error_message =             " messages
    .  "  CONV_API_CONVERT_BOM_ASSEMBLY

ABAP code example for Function Module CONV_API_CONVERT_BOM_ASSEMBLY

The ABAP code below is a full code listing to execute function module CONV_API_CONVERT_BOM_ASSEMBLY 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_error_message  
 
 TYPE MESSAGES
.


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

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

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


DATA(ld_key_date) = some text here


DATA(ld_material_root_int) = some text here


DATA(ld_material_root) = some text here


DATA(ld_plant_root) = some text here
 

SELECT single CAPID 
  FROM TC04 
  INTO @DATA(ld_application).

 

SELECT single DOKAR 
  FROM DRAW 
  INTO @DATA(ld_type_filter).

 

SELECT single DOKVR 
  FROM DRAW 
  INTO @DATA(ld_version_filter).

 

SELECT single DAPPL 
  FROM DRAW 
  INTO @DATA(ld_application_filter).


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

SELECT single STABK 
  FROM TDWST 
  INTO @DATA(ld_document_status).


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

CALL FUNCTION 'CONV_API_CONVERT_BOM_ASSEMBLY'
  EXPORTING
*   change_number_int =          ld_change_number_int
*   change_number =              ld_change_number
*   key_date_int =               ld_key_date_int
*   key_date =                   ld_key_date
*   material_root_int =          ld_material_root_int
*   material_root =              ld_material_root
*   plant_root =                 ld_plant_root
    application =                ld_application
    type_filter =                ld_type_filter
*   version_filter =             ld_version_filter
    application_filter =         ld_application_filter
*   document_status_int =        ld_document_status_int
*   document_status =            ld_document_status
*   foreground =                 ld_foreground
  IMPORTING
    error_message =              ld_error_message
    .  "  CONV_API_CONVERT_BOM_ASSEMBLY

IF SY-SUBRC EQ 0.
  "All OK
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_error_message
 
 TYPE MESSAGES ,
ld_change_number_int
 
 TYPE AENNR ,
ld_change_number
 
 TYPE AENNR ,
ld_key_date_int
 
 TYPE DATUM ,
ld_key_date
 
 TYPE CSAP_MBOM-DATUV ,
ld_material_root_int
 
 TYPE MBM_CLASS_DATA-MATNR ,
ld_material_root
 
 TYPE CSAP_MBOM-MATNR ,
ld_plant_root
 
 TYPE MBM_CLASS_DATA-WERKS ,
ld_application
 
 TYPE TC04-CAPID ,
ld_type_filter
 
 TYPE DRAW-DOKAR ,
ld_version_filter
 
 TYPE DRAW-DOKVR ,
ld_application_filter
 
 TYPE DRAW-DAPPL ,
ld_document_status_int
 
 TYPE DOKST ,
ld_document_status
 
 TYPE TDWST-STABK ,
ld_foreground
 
 TYPE XFELD .


ld_change_number_int = 'Check type of data required'.
ld_change_number = 'Check type of data required'.
ld_key_date_int = 'Check type of data required'.

ld_key_date = some text here

ld_material_root_int = some text here

ld_material_root = some text here

ld_plant_root = some text here

SELECT single CAPID 
  FROM TC04 
  INTO ld_application.


SELECT single DOKAR 
  FROM DRAW 
  INTO ld_type_filter.


SELECT single DOKVR 
  FROM DRAW 
  INTO ld_version_filter.


SELECT single DAPPL 
  FROM DRAW 
  INTO ld_application_filter.

ld_document_status_int = 'Check type of data required'.

SELECT single STABK 
  FROM TDWST 
  INTO ld_document_status.

ld_foreground = 'Check type of data required'.