SAP SD_CHECK_SUBSEQUENT_DOCUMENT Function Module for NOTRANSL: Nachfolgebelege prüfen









SD_CHECK_SUBSEQUENT_DOCUMENT is a standard sd check subsequent document SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Nachfolgebelege prüfen 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 sd check subsequent document FM, simply by entering the name SD_CHECK_SUBSEQUENT_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_CHECK_SUBSEQUENT_DOCUMENT 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 'SD_CHECK_SUBSEQUENT_DOCUMENT'"NOTRANSL: Nachfolgebelege prüfen
EXPORTING
I_VBELN = "Sales Document
* IT_VBFA = "Table Type for Structure vbfa
* I_CHECK_CLEARING = 'X' "
* I_CALLER = "

IMPORTING
E_SUB_DOC_COMPLETED = "

EXCEPTIONS
ERROR_OCCURED = 1
.



IMPORTING Parameters details for SD_CHECK_SUBSEQUENT_DOCUMENT

I_VBELN - Sales Document

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

IT_VBFA - Table Type for Structure vbfa

Data type: VBFA_T
Optional: Yes
Call by Reference: Yes

I_CHECK_CLEARING -

Data type: XFELD
Default: 'X'
Optional: No
Call by Reference: Yes

I_CALLER -

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for SD_CHECK_SUBSEQUENT_DOCUMENT

E_SUB_DOC_COMPLETED -

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR_OCCURED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SD_CHECK_SUBSEQUENT_DOCUMENT 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.

DATA:
lv_i_vbeln  TYPE VBELN_VA, "   
lv_error_occured  TYPE VBELN_VA, "   
lv_e_sub_doc_completed  TYPE XFELD, "   
lv_it_vbfa  TYPE VBFA_T, "   
lv_i_check_clearing  TYPE XFELD, "   'X'
lv_i_caller  TYPE CHAR1. "   

  CALL FUNCTION 'SD_CHECK_SUBSEQUENT_DOCUMENT'  "NOTRANSL: Nachfolgebelege prüfen
    EXPORTING
         I_VBELN = lv_i_vbeln
         IT_VBFA = lv_it_vbfa
         I_CHECK_CLEARING = lv_i_check_clearing
         I_CALLER = lv_i_caller
    IMPORTING
         E_SUB_DOC_COMPLETED = lv_e_sub_doc_completed
    EXCEPTIONS
        ERROR_OCCURED = 1
. " SD_CHECK_SUBSEQUENT_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM SD_CHECK_SUBSEQUENT_DOCUMENT

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.

 
 
 
 
DATA(ld_i_check_clearing) = 'X'.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!