OIUXI_BUFFER_DOI_ACTIVE SAP Function module - Retrieve active DOI data

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

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

Pattern for FM OIUXI_BUFFER_DOI_ACTIVE - OIUXI BUFFER DOI ACTIVE

CALL FUNCTION 'OIUXI_BUFFER_DOI_ACTIVE' "Retrieve active DOI data
  EXPORTING
    p_bukrs =                   " bukrs         Company code
    p_vname =                   " jv_name       Joint venture
    p_doi_no =                  " oiu_doi_no    Division of interest (DOI)
*   p_force = SPACE             " char1         Single-character flag
  EXCEPTIONS
    NOT_CHECKED_OUT = 1         "               DOI is not checked out
    NOT_FOUND = 2               "               DOI not found in database
    .  "  OIUXI_BUFFER_DOI_ACTIVE

ABAP code example for Function Module OIUXI_BUFFER_DOI_ACTIVE

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

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

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

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

CALL FUNCTION 'OIUXI_BUFFER_DOI_ACTIVE'
  EXPORTING
    p_bukrs =                    ld_p_bukrs
    p_vname =                    ld_p_vname
    p_doi_no =                   ld_p_doi_no
*   p_force =                    ld_p_force
  EXCEPTIONS
    NOT_CHECKED_OUT =            1
    NOT_FOUND =                  2
    .  "  OIUXI_BUFFER_DOI_ACTIVE

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
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_p_bukrs
 
 TYPE BUKRS ,
ld_p_vname
 
 TYPE JV_NAME ,
ld_p_doi_no
 
 TYPE OIU_DOI_NO ,
ld_p_force
 
 TYPE CHAR1 .


ld_p_bukrs = 'Check type of data required'.
ld_p_vname = 'Check type of data required'.
ld_p_doi_no = 'Check type of data required'.
ld_p_force = 'Check type of data required'.