FVF4_KMART_CHECK SAP Function module - F4 Help for Corporate Action Type (KMART)

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

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

Pattern for FM FVF4_KMART_CHECK - FVF4 KMART CHECK

CALL FUNCTION 'FVF4_KMART_CHECK' "F4 Help for Corporate Action Type (KMART)
  EXPORTING
    kmtyp =                     " vwkmko-herk   zulässiger KMTYP für F4-Hilfe
    dynpr_fieldname =           " dynpread-fieldname  Name des Dynprofeldes für KMART
*   mod = SPACE                 " c             R: Es wird keine KMART zurückgeliefert
*   all_types = SPACE           " c
  IMPORTING
    kmart =                     " vwkmko-kmart  Ausgewählte KMART
  EXCEPTIONS
    NO_POSTING_SELECTED = 1     "               keine Bewegungsart ausgewählt
    POSTING_NOT_FOUND = 2       "               keine Bewegungsart gefunden
    .  "  FVF4_KMART_CHECK

ABAP code example for Function Module FVF4_KMART_CHECK

The ABAP code below is a full code listing to execute function module FVF4_KMART_CHECK 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_kmart  
 
 TYPE VWKMKO-KMART
.

 

SELECT single HERK 
  FROM VWKMKO 
  INTO @DATA(ld_kmtyp).



DATA(ld_dynpr_fieldname) = some text here

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

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

CALL FUNCTION 'FVF4_KMART_CHECK'
  EXPORTING
    kmtyp =                      ld_kmtyp
    dynpr_fieldname =            ld_dynpr_fieldname
*   mod =                        ld_mod
*   all_types =                  ld_all_types
  IMPORTING
    kmart =                      ld_kmart
  EXCEPTIONS
    NO_POSTING_SELECTED =        1
    POSTING_NOT_FOUND =          2
    .  "  FVF4_KMART_CHECK

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
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_kmart
 
 TYPE VWKMKO-KMART ,
ld_kmtyp
 
 TYPE VWKMKO-HERK ,
ld_dynpr_fieldname
 
 TYPE DYNPREAD-FIELDNAME ,
ld_mod
 
 TYPE C ,
ld_all_types
 
 TYPE C .



SELECT single HERK 
  FROM VWKMKO 
  INTO ld_kmtyp.


ld_dynpr_fieldname = some text here
ld_mod = 'Check type of data required'.
ld_all_types = 'Check type of data required'.