SAP Function Modules

OIO_SC_GET_DELIVERY_EBAN SAP Function module - Get subsequent delivery for a requisition







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

Associated Function Group: OIO_SC
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM OIO_SC_GET_DELIVERY_EBAN - OIO SC GET DELIVERY EBAN





CALL FUNCTION 'OIO_SC_GET_DELIVERY_EBAN' "Get subsequent delivery for a requisition
  EXPORTING
    i_banfn =                   " banfn         Purchase requisition number
    i_bnfpo =                   " bnfpo         Item number of purchase requisition
  IMPORTING
    et_likp =                   " roio_t_likpvb  Delivery header update table
    et_lips =                   " roio_t_lipsvb  Delivery item update table
    e_incomplete =              " xfeld         Checkbox
  EXCEPTIONS
    NO_DELIVERY = 1             "
    .  "  OIO_SC_GET_DELIVERY_EBAN

ABAP code example for Function Module OIO_SC_GET_DELIVERY_EBAN





The ABAP code below is a full code listing to execute function module OIO_SC_GET_DELIVERY_EBAN 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_et_likp  TYPE ROIO_T_LIKPVB ,
ld_et_lips  TYPE ROIO_T_LIPSVB ,
ld_e_incomplete  TYPE XFELD .

DATA(ld_i_banfn) = 'Check type of data required'.
DATA(ld_i_bnfpo) = 'Check type of data required'. . CALL FUNCTION 'OIO_SC_GET_DELIVERY_EBAN' EXPORTING i_banfn = ld_i_banfn i_bnfpo = ld_i_bnfpo IMPORTING et_likp = ld_et_likp et_lips = ld_et_lips e_incomplete = ld_e_incomplete EXCEPTIONS NO_DELIVERY = 1 . " OIO_SC_GET_DELIVERY_EBAN
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "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_et_likp  TYPE ROIO_T_LIKPVB ,
ld_i_banfn  TYPE BANFN ,
ld_et_lips  TYPE ROIO_T_LIPSVB ,
ld_i_bnfpo  TYPE BNFPO ,
ld_e_incomplete  TYPE XFELD .

ld_i_banfn = 'Check type of data required'.
ld_i_bnfpo = 'Check type of data required'.

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 OIO_SC_GET_DELIVERY_EBAN or its description.