EC_START_CONVERSION SAP Function module

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

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

Pattern for FM EC_START_CONVERSION - EC START CONVERSION

CALL FUNCTION 'EC_START_CONVERSION' "
  EXPORTING
    pobsetid =                  " crmobsetid    Check Results Management: ID of Object Set to Be Checked
    pobsetki =                  " crmobsetki    Check Results Management: Type of Object Set to Be Checked
*   pautoid = 'X'               " flag          General Flag
    ptxtoset =                  " crmdescr      Check Results Management: Description
    pdeldays =                  " numc2         Two Digit Number
*   batch = ' '                 " flag          General Flag
    pminbtc =                   " crmnbrwp      Check Results Management: Number of Work Processes
    pmaxbtc =                   " crmnbrwp      Check Results Management: Number of Work Processes
*   ppostpro = 'X'              " flag          General Flag
*   pact = 'X'                  " flag          General Flag
    psession_id =               " crmseqnbr     Check Results Management: Numbering
  TABLES
    pobjcol =                   " crm_selection_conditions  Check Results Management: Selection Criterion
    pchk =                      " crm_selection_conditions  Check Results Management: Selection Criterion
    .  "  EC_START_CONVERSION

ABAP code example for Function Module EC_START_CONVERSION

The ABAP code below is a full code listing to execute function module EC_START_CONVERSION 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:
it_pobjcol  
 
 TYPE STANDARD TABLE OF CRM_SELECTION_CONDITIONS,"TABLES PARAM
wa_pobjcol
 
 LIKE LINE OF it_pobjcol
,
it_pchk  
 
 TYPE STANDARD TABLE OF CRM_SELECTION_CONDITIONS,"TABLES PARAM
wa_pchk
 
 LIKE LINE OF it_pchk
.


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

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

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

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

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

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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_pobjcol to it_pobjcol.
 

"populate fields of struture and append to itab
append wa_pchk to it_pchk.
.

CALL FUNCTION 'EC_START_CONVERSION'
  EXPORTING
    pobsetid =                   ld_pobsetid
    pobsetki =                   ld_pobsetki
*   pautoid =                    ld_pautoid
    ptxtoset =                   ld_ptxtoset
    pdeldays =                   ld_pdeldays
*   batch =                      ld_batch
    pminbtc =                    ld_pminbtc
    pmaxbtc =                    ld_pmaxbtc
*   ppostpro =                   ld_ppostpro
*   pact =                       ld_pact
    psession_id =                ld_psession_id
  TABLES
    pobjcol =                    it_pobjcol
    pchk =                       it_pchk
    .  "  EC_START_CONVERSION

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_pobsetid
 
 TYPE CRMOBSETID ,
it_pobjcol
 
 TYPE STANDARD TABLE OF CRM_SELECTION_CONDITIONS ,
wa_pobjcol
 
 LIKE LINE OF it_pobjcol,
ld_pobsetki
 
 TYPE CRMOBSETKI ,
it_pchk
 
 TYPE STANDARD TABLE OF CRM_SELECTION_CONDITIONS ,
wa_pchk
 
 LIKE LINE OF it_pchk,
ld_pautoid
 
 TYPE FLAG ,
ld_ptxtoset
 
 TYPE CRMDESCR ,
ld_pdeldays
 
 TYPE NUMC2 ,
ld_batch
 
 TYPE FLAG ,
ld_pminbtc
 
 TYPE CRMNBRWP ,
ld_pmaxbtc
 
 TYPE CRMNBRWP ,
ld_ppostpro
 
 TYPE FLAG ,
ld_pact
 
 TYPE FLAG ,
ld_psession_id
 
 TYPE CRMSEQNBR .


ld_pobsetid = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_pobjcol to it_pobjcol.
ld_pobsetki = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_pchk to it_pchk.
ld_pautoid = 'Check type of data required'.
ld_ptxtoset = 'Check type of data required'.
ld_pdeldays = 'Check type of data required'.
ld_batch = 'Check type of data required'.
ld_pminbtc = 'Check type of data required'.
ld_pmaxbtc = 'Check type of data required'.
ld_ppostpro = 'Check type of data required'.
ld_pact = 'Check type of data required'.
ld_psession_id = 'Check type of data required'.