SD_CONTRACT_CONDITION_TYPES SAP Function module

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

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

Pattern for FM SD_CONTRACT_CONDITION_TYPES - SD CONTRACT CONDITION TYPES

CALL FUNCTION 'SD_CONTRACT_CONDITION_TYPES' "
  EXPORTING
    i_komk =                    " komk          Pricing Procedure - Contract
*   condition_type = ' '        " t685a-kschl   Condition type that has been selected
    position =                  " komg-posnr
  IMPORTING
    condition_type =            " t685a-kschl   Condition type that has been selected
    condition_type_text =       " t685t-vtext
  EXCEPTIONS
    CONDITION_NOT_IN_CONTRACT = 1  "
    CONTRACT_ACCESS_DOES_NOT_EXIST = 2  "
    NO_CONDITION_TYPE_SELECTED = 3  "
    .  "  SD_CONTRACT_CONDITION_TYPES

ABAP code example for Function Module SD_CONTRACT_CONDITION_TYPES

The ABAP code below is a full code listing to execute function module SD_CONTRACT_CONDITION_TYPES 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_condition_type  
 
 TYPE T685A-KSCHL
,
ld_condition_type_text  
 
 TYPE T685T-VTEXT
.


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

SELECT single KSCHL 
  FROM T685A 
  INTO @DATA(ld_condition_type).



DATA(ld_position) = Check type of data required
.

CALL FUNCTION 'SD_CONTRACT_CONDITION_TYPES'
  EXPORTING
    i_komk =                     ld_i_komk
*   condition_type =             ld_condition_type
    position =                   ld_position
  IMPORTING
    condition_type =             ld_condition_type
    condition_type_text =        ld_condition_type_text
  EXCEPTIONS
    CONDITION_NOT_IN_CONTRACT =    1
    CONTRACT_ACCESS_DOES_NOT_EXIST =    2
    NO_CONDITION_TYPE_SELECTED =    3
    .  "  SD_CONTRACT_CONDITION_TYPES

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_condition_type
 
 TYPE T685A-KSCHL ,
ld_i_komk
 
 TYPE KOMK ,
ld_condition_type_text
 
 TYPE T685T-VTEXT ,
ld_condition_type
 
 TYPE T685A-KSCHL ,
ld_position
 
 TYPE KOMG-POSNR .


ld_i_komk = 'Check type of data required'.

SELECT single KSCHL 
  FROM T685A 
  INTO ld_condition_type.


ld_position = Check type of data required