OIUXI_INT_FDN_SINGLE_READ SAP Function module - Read Funds deletion control record (Buffered)

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

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

Pattern for FM OIUXI_INT_FDN_SINGLE_READ - OIUXI INT FDN SINGLE READ

CALL FUNCTION 'OIUXI_INT_FDN_SINGLE_READ' "Read Funds deletion control record (Buffered)
  EXPORTING
    oown_no =                   " oiuow_oown_no  Transferor - E&P owner
    oown_int_type_cd =          " oiuow_opart_int_type  Transferor participant interest type
    oown_isq_no =               " oiuow_oown_isq_no  Transferor owner interest sequence number
*   force_db =                  " char01        Character field length 1
  IMPORTING
    e_fdn =                     " oiuxi_int_fdn  Funds Delete Notification Control
  EXCEPTIONS
    NOT_FOUND = 1               "               No control record was found
    .  "  OIUXI_INT_FDN_SINGLE_READ

ABAP code example for Function Module OIUXI_INT_FDN_SINGLE_READ

The ABAP code below is a full code listing to execute function module OIUXI_INT_FDN_SINGLE_READ 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_e_fdn  
 
 TYPE OIUXI_INT_FDN
.


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

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

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

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

CALL FUNCTION 'OIUXI_INT_FDN_SINGLE_READ'
  EXPORTING
    oown_no =                    ld_oown_no
    oown_int_type_cd =           ld_oown_int_type_cd
    oown_isq_no =                ld_oown_isq_no
*   force_db =                   ld_force_db
  IMPORTING
    e_fdn =                      ld_e_fdn
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  OIUXI_INT_FDN_SINGLE_READ

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_e_fdn
 
 TYPE OIUXI_INT_FDN ,
ld_oown_no
 
 TYPE OIUOW_OOWN_NO ,
ld_oown_int_type_cd
 
 TYPE OIUOW_OPART_INT_TYPE ,
ld_oown_isq_no
 
 TYPE OIUOW_OOWN_ISQ_NO ,
ld_force_db
 
 TYPE CHAR01 .


ld_oown_no = 'Check type of data required'.
ld_oown_int_type_cd = 'Check type of data required'.
ld_oown_isq_no = 'Check type of data required'.
ld_force_db = 'Check type of data required'.