SAP N2DOC_RECEIVE_RESPONSE Function Module for









N2DOC_RECEIVE_RESPONSE is a standard n2doc receive response SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 n2doc receive response FM, simply by entering the name N2DOC_RECEIVE_RESPONSE into the relevant SAP transaction such as SE37 or SE38.

Function Group: N2DOC_RECEIVE
Program Name: SAPLN2DOC_RECEIVE
Main Program: SAPLN2DOC_RECEIVE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function N2DOC_RECEIVE_RESPONSE 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 'N2DOC_RECEIVE_RESPONSE'"
EXPORTING
I_DISPATCH_REQUEST = "
I_SENDER_ID = "
I_RECIPIENT_ID = "
I_STATUS = "
I_PROCESSING_INFO = "
I_ASSIGNED_DOC_KEY = "
I_ASSIGNED_DOC_VR = "

EXCEPTIONS
PROCESSING_ERROR = 1
.



IMPORTING Parameters details for N2DOC_RECEIVE_RESPONSE

I_DISPATCH_REQUEST -

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

I_SENDER_ID -

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

I_RECIPIENT_ID -

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

I_STATUS -

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

I_PROCESSING_INFO -

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

I_ASSIGNED_DOC_KEY -

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

I_ASSIGNED_DOC_VR -

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

EXCEPTIONS details

PROCESSING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for N2DOC_RECEIVE_RESPONSE 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_processing_error  TYPE STRING, "   
lv_i_dispatch_request  TYPE N2_MV_DISPATCH_REQUEST, "   
lv_i_sender_id  TYPE N2COMM_PART, "   
lv_i_recipient_id  TYPE N2COMM_PART, "   
lv_i_status  TYPE N2COM_LOG_STATUS, "   
lv_i_processing_info  TYPE STRING, "   
lv_i_assigned_doc_key  TYPE N2COM_EXTKEY, "   
lv_i_assigned_doc_vr  TYPE N2COM_EXTVR. "   

  CALL FUNCTION 'N2DOC_RECEIVE_RESPONSE'  "
    EXPORTING
         I_DISPATCH_REQUEST = lv_i_dispatch_request
         I_SENDER_ID = lv_i_sender_id
         I_RECIPIENT_ID = lv_i_recipient_id
         I_STATUS = lv_i_status
         I_PROCESSING_INFO = lv_i_processing_info
         I_ASSIGNED_DOC_KEY = lv_i_assigned_doc_key
         I_ASSIGNED_DOC_VR = lv_i_assigned_doc_vr
    EXCEPTIONS
        PROCESSING_ERROR = 1
. " N2DOC_RECEIVE_RESPONSE




ABAP code using 7.40 inline data declarations to call FM N2DOC_RECEIVE_RESPONSE

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



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!