FSCD_SAMPLE_V820 SAP Function module - Change Insurance Object Data after Changes in Credit Management

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

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

Pattern for FM FSCD_SAMPLE_V820 - FSCD SAMPLE V820

CALL FUNCTION 'FSCD_SAMPLE_V820' "Change Insurance Object Data after Changes in Credit Management
  EXPORTING
    iv_insobject =              " insobject_md  Identification for an Insurance Object
    iv_partner =                " bu_partner    Business Partner Number
    iv_origin =                 " origin_mdc_kk  Origin of Request for Change to Master Data
    iv_type =                   " type_mdc_kk   Change Type
    is_dfkkcms =                " dfkkcms       Credit Management: Master Data Replication
  CHANGING
    cs_relevants =              " fscd_cr_bpc_update_insobject  Update Insurance Object for Changes in Credit Management
    .  "  FSCD_SAMPLE_V820

ABAP code example for Function Module FSCD_SAMPLE_V820

The ABAP code below is a full code listing to execute function module FSCD_SAMPLE_V820 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_cs_relevants) = 'Check type of data required'.

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

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

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

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

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

CALL FUNCTION 'FSCD_SAMPLE_V820'
  EXPORTING
    iv_insobject =               ld_iv_insobject
    iv_partner =                 ld_iv_partner
    iv_origin =                  ld_iv_origin
    iv_type =                    ld_iv_type
    is_dfkkcms =                 ld_is_dfkkcms
  CHANGING
    cs_relevants =               ld_cs_relevants
    .  "  FSCD_SAMPLE_V820

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_cs_relevants
 
 TYPE FSCD_CR_BPC_UPDATE_INSOBJECT ,
ld_iv_insobject
 
 TYPE INSOBJECT_MD ,
ld_iv_partner
 
 TYPE BU_PARTNER ,
ld_iv_origin
 
 TYPE ORIGIN_MDC_KK ,
ld_iv_type
 
 TYPE TYPE_MDC_KK ,
ld_is_dfkkcms
 
 TYPE DFKKCMS .


ld_cs_relevants = 'Check type of data required'.
ld_iv_insobject = 'Check type of data required'.
ld_iv_partner = 'Check type of data required'.
ld_iv_origin = 'Check type of data required'.
ld_iv_type = 'Check type of data required'.
ld_is_dfkkcms = 'Check type of data required'.