SAP ISH_N2_DOC_SET_BUFFER_STATUS Function Module for
ISH_N2_DOC_SET_BUFFER_STATUS is a standard ish n2 doc set buffer status 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 ish n2 doc set buffer status FM, simply by entering the name ISH_N2_DOC_SET_BUFFER_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: N234
Program Name: SAPLN234
Main Program: SAPLN234
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_N2_DOC_SET_BUFFER_STATUS 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 'ISH_N2_DOC_SET_BUFFER_STATUS'".
EXPORTING
IS_DOCUMENT_KEY = "IS-H*MED: Key for a Document
I_STATUS = "
IS_NEXT_STATUS = "BAPIS DMS: status data
* I_NEXT_LOGFIELD = "
IMPORTING Parameters details for ISH_N2_DOC_SET_BUFFER_STATUS
IS_DOCUMENT_KEY - IS-H*MED: Key for a Document
Data type: RN2DOC_KEYOptional: No
Call by Reference: Yes
I_STATUS -
Data type: DOKSTOptional: No
Call by Reference: Yes
IS_NEXT_STATUS - BAPIS DMS: status data
Data type: BAPI_DOC_TDWSOptional: No
Call by Reference: Yes
I_NEXT_LOGFIELD -
Data type: PROTFOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ISH_N2_DOC_SET_BUFFER_STATUS 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_is_document_key | TYPE RN2DOC_KEY, " | |||
| lv_i_status | TYPE DOKST, " | |||
| lv_is_next_status | TYPE BAPI_DOC_TDWS, " | |||
| lv_i_next_logfield | TYPE PROTF. " |
|   CALL FUNCTION 'ISH_N2_DOC_SET_BUFFER_STATUS' " |
| EXPORTING | ||
| IS_DOCUMENT_KEY | = lv_is_document_key | |
| I_STATUS | = lv_i_status | |
| IS_NEXT_STATUS | = lv_is_next_status | |
| I_NEXT_LOGFIELD | = lv_i_next_logfield | |
| . " ISH_N2_DOC_SET_BUFFER_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM ISH_N2_DOC_SET_BUFFER_STATUS
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