SAP ECRM_ISU_READ_BUFFER Function Module for Lesen des internen Navigator Puffers
ECRM_ISU_READ_BUFFER is a standard ecrm isu read buffer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lesen des internen Navigator Puffers 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 ecrm isu read buffer FM, simply by entering the name ECRM_ISU_READ_BUFFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECRM_ISU_WSP_NAVIGATOR
Program Name: SAPLECRM_ISU_WSP_NAVIGATOR
Main Program: SAPLECRM_ISU_WSP_NAVIGATOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ECRM_ISU_READ_BUFFER 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 'ECRM_ISU_READ_BUFFER'"Lesen des internen Navigator Puffers.
EXPORTING
* IM_ITEM_GUID = "GUID of a CRM Order Object
* IM_IBASE_GUID = "IB: Component (Instance)
* IM_ISUHEAD = "General Flag
* IM_ISUITEM = "General Flag
IMPORTING
EX_READ_RESULT = "Structure for IS-U Navigator Search (Display)
EX_SECONDCALL = "Schon wieder
EXCEPTIONS
NO_ENTRIES_FOUND = 1
IMPORTING Parameters details for ECRM_ISU_READ_BUFFER
IM_ITEM_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
IM_IBASE_GUID - IB: Component (Instance)
Data type: IB_RECNO_16Optional: Yes
Call by Reference: Yes
IM_ISUHEAD - General Flag
Data type: FLAGOptional: Yes
Call by Reference: Yes
IM_ISUITEM - General Flag
Data type: FLAGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ECRM_ISU_READ_BUFFER
EX_READ_RESULT - Structure for IS-U Navigator Search (Display)
Data type: ECRM_ISU_NAV_COMPLETEOptional: No
Call by Reference: Yes
EX_SECONDCALL - Schon wieder
Data type: FLAGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRIES_FOUND - keine Einträge im Puffer vorhanden
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ECRM_ISU_READ_BUFFER 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_im_item_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_ex_read_result | TYPE ECRM_ISU_NAV_COMPLETE, " | |||
| lv_no_entries_found | TYPE ECRM_ISU_NAV_COMPLETE, " | |||
| lv_ex_secondcall | TYPE FLAG, " | |||
| lv_im_ibase_guid | TYPE IB_RECNO_16, " | |||
| lv_im_isuhead | TYPE FLAG, " | |||
| lv_im_isuitem | TYPE FLAG. " |
|   CALL FUNCTION 'ECRM_ISU_READ_BUFFER' "Lesen des internen Navigator Puffers |
| EXPORTING | ||
| IM_ITEM_GUID | = lv_im_item_guid | |
| IM_IBASE_GUID | = lv_im_ibase_guid | |
| IM_ISUHEAD | = lv_im_isuhead | |
| IM_ISUITEM | = lv_im_isuitem | |
| IMPORTING | ||
| EX_READ_RESULT | = lv_ex_read_result | |
| EX_SECONDCALL | = lv_ex_secondcall | |
| EXCEPTIONS | ||
| NO_ENTRIES_FOUND = 1 | ||
| . " ECRM_ISU_READ_BUFFER | ||
ABAP code using 7.40 inline data declarations to call FM ECRM_ISU_READ_BUFFER
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