SAP CRM_ISULOG_GET_OB Function Module for Lesen von Einträgen aus dem Objekt Puffer
CRM_ISULOG_GET_OB is a standard crm isulog get ob 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 von Einträgen aus dem Objekt Puffer 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 crm isulog get ob FM, simply by entering the name CRM_ISULOG_GET_OB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ISULOG_OB
Program Name: SAPLCRM_ISULOG_OB
Main Program: SAPLCRM_ISULOG_OB
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISULOG_GET_OB 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 'CRM_ISULOG_GET_OB'"Lesen von Einträgen aus dem Objekt Puffer.
EXPORTING
* IV_GUID = "
IMPORTING
ET_ISULOG_WRK = "ISU Container
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for CRM_ISULOG_GET_OB
IV_GUID -
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_ISULOG_GET_OB
ET_ISULOG_WRK - ISU Container
Data type: CRMT_ISULOGA8_WRKTOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_ISULOG_GET_OB 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_iv_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_not_found | TYPE CRMT_OBJECT_GUID, " | |||
lv_et_isulog_wrk | TYPE CRMT_ISULOGA8_WRKT. " |
  CALL FUNCTION 'CRM_ISULOG_GET_OB' "Lesen von Einträgen aus dem Objekt Puffer |
EXPORTING | ||
IV_GUID | = lv_iv_guid | |
IMPORTING | ||
ET_ISULOG_WRK | = lv_et_isulog_wrk | |
EXCEPTIONS | ||
NOT_FOUND = 1 | ||
. " CRM_ISULOG_GET_OB |
ABAP code using 7.40 inline data declarations to call FM CRM_ISULOG_GET_OB
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