OI0_VALIDATE_EXSDUT SAP Function module - Validating Excise Duty Fields

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

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

Pattern for FM OI0_VALIDATE_EXSDUT - OI0 VALIDATE EXSDUT

CALL FUNCTION 'OI0_VALIDATE_EXSDUT' "Validating Excise Duty Fields
  EXPORTING
    handling_type =             " sapplsef_prod_tax_char_code  Proxy Data Element (Generated)
    ed_pricing_key =            " sapplsef_price_type_code_cont  Coded representation of the type of a price
  CHANGING
    cht_messages =              " bapirettab    Table with BAPI Return Information
    .  "  OI0_VALIDATE_EXSDUT

ABAP code example for Function Module OI0_VALIDATE_EXSDUT

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

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

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

CALL FUNCTION 'OI0_VALIDATE_EXSDUT'
  EXPORTING
    handling_type =              ld_handling_type
    ed_pricing_key =             ld_ed_pricing_key
  CHANGING
    cht_messages =               ld_cht_messages
    .  "  OI0_VALIDATE_EXSDUT

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_cht_messages
 
 TYPE BAPIRETTAB ,
ld_handling_type
 
 TYPE SAPPLSEF_PROD_TAX_CHAR_CODE ,
ld_ed_pricing_key
 
 TYPE SAPPLSEF_PRICE_TYPE_CODE_CONT .


ld_cht_messages = 'Check type of data required'.
ld_handling_type = 'Check type of data required'.
ld_ed_pricing_key = 'Check type of data required'.