SAP OIRE_SUBSEQUENT_DOC_DETERMINE Function Module for Determine subsequent documents for DTF transactions

Search SAP Function Modules

OIRE_SUBSEQUENT_DOC_DETERMINE is a standard oire subsequent doc determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine subsequent documents for DTF transactions processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for oire subsequent doc determine FM, simply by entering the name OIRE_SUBSEQUENT_DOC_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIRE_PC_DTF
Program Name: SAPLOIRE_PC_DTF
Main Program: SAPLOIRE_PC_DTF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIRE_SUBSEQUENT_DOC_DETERMINE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'OIRE_SUBSEQUENT_DOC_DETERMINE'"Determine subsequent documents for DTF transactions
  EXPORTING
   I_LINKNR =  "Link number
   I_LINKYEAR =  "Document link number year
*  I_DOCTYPE = 'SSP' "Subsequent document type
*  I_REFRESH_BUFFER = '' "Refresh the internal buffer table

 IMPORTING
   E_ICON =  "Icon in text fields (substitute display, alias)
   E_VBRK_FKDAT =  "Billing date for billing index and printout

TABLES
   T_DTLT_RESULT =  "

.

IMPORTING Parameters details for OIRE_SUBSEQUENT_DOC_DETERMINE

I_LINKNR - Link number

Data type: OIRA_LINKNR
Optional: No
Call by Reference: Yes

I_LINKYEAR - Document link number year

Data type: OIRA_JAHR
Optional: No
Call by Reference: Yes

I_DOCTYPE - Subsequent document type

Data type: OIRA_DOCTYPE
Default: 'SSP'
Optional: Yes
Call by Reference: Yes

I_REFRESH_BUFFER - Refresh the internal buffer table

Data type: C
Default: ''
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OIRE_SUBSEQUENT_DOC_DETERMINE

E_ICON - Icon in text fields (substitute display, alias)

Data type: ICON_D
Optional: No
Call by Reference: Yes

E_VBRK_FKDAT - Billing date for billing index and printout

Data type: FKDAT
Optional: No
Call by Reference: Yes

TABLES Parameters details for OIRE_SUBSEQUENT_DOC_DETERMINE

T_DTLT_RESULT -

Data type: OIRA3_T_DTLT_RESULT
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIRE_SUBSEQUENT_DOC_DETERMINE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM OIRE_SUBSEQUENT_DOC_DETERMINE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects