SAP Tables

FKKBOL_MAINTAIN_OKCOD SAP Function module




FKKBOL_MAINTAIN_OKCODis a standard SAP function module available within R/3 SAPsystems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import/export parameters, exceptions etc as well as any documentation contributions specific to the object. See here to view full function module documentation and code listing, simply by entering the name FKKBOL_MAINTAIN_OKCOD into the relevant SAP transaction such as SE37 or SE80.

Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FKKBOL_MAINTAIN_OKCOD or its description.


Pattern for FM FKKBOL_MAINTAIN_OKCOD - FKKBOL MAINTAIN OKCOD
Associated Function Group: FKB4_BOL
Released Date: Not Released
CALL FUNCTION 'FKKBOL_MAINTAIN_OKCOD' "
  EXPORTING
    i_okcod =                   " sy-ucomm
*   i_doubleclick =             " boole-boole
*   i_payment_confirm =         " boole-boole
*   i_go_back =                 " boole-boole
*   i_go_back_noconf =          " boole-boole
*   i_need_line =               " boole-boole
    .  "  FKKBOL_MAINTAIN_OKCOD

ABAP code example for Function Module FKKBOL_MAINTAIN_OKCOD

The ABAP code below is a full code listing to execute function module FKKBOL_MAINTAIN_OKCOD including all data declarations. The code uses the latest in-line data declaration syntax but I have included an abap code snipet 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_i_okcod) = 'some text here'.

DATA(ld_i_doubleclick). = 'some text here'

DATA(ld_i_payment_confirm). = 'some text here'

DATA(ld_i_go_back). = 'some text here'

DATA(ld_i_go_back_noconf). = 'some text here'

DATA(ld_i_need_line). = 'some text here'. CALL FUNCTION 'FKKBOL_MAINTAIN_OKCOD' EXPORTING i_okcod = ld_i_okcod * i_doubleclick = ld_i_doubleclick * i_payment_confirm = ld_i_payment_confirm * i_go_back = ld_i_go_back * i_go_back_noconf = ld_i_go_back_noconf * i_need_line = ld_i_need_line . " FKKBOL_MAINTAIN_OKCOD
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_i_okcod TYPE SY-UCOMM ,
ld_i_doubleclick TYPE BOOLE-BOOLE ,
ld_i_payment_confirm TYPE BOOLE-BOOLE ,
ld_i_go_back TYPE BOOLE-BOOLE ,
ld_i_go_back_noconf TYPE BOOLE-BOOLE ,
ld_i_need_line TYPE BOOLE-BOOLE .

ld_i_okcod = 'some text here'.

DATA(ld_i_doubleclick). = 'some text here'

DATA(ld_i_payment_confirm). = 'some text here'

DATA(ld_i_go_back). = 'some text here'

DATA(ld_i_go_back_noconf). = 'some text here'

DATA(ld_i_need_line). = 'some text here'.