SAP CRM_ISU_PDO_STORE Function Module for write session data to database
CRM_ISU_PDO_STORE is a standard crm isu pdo store SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for write session data to database 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 isu pdo store FM, simply by entering the name CRM_ISU_PDO_STORE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ISU_PDO_CLUSTER_DB
Program Name: SAPLCRM_ISU_PDO_CLUSTER_DB
Main Program: SAPLCRM_ISU_PDO_CLUSTER_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISU_PDO_STORE 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_ISU_PDO_STORE'"write session data to database.
EXPORTING
IR_READ_TABLES = "
CHANGING
CS_READ_DATA = "
IMPORTING Parameters details for CRM_ISU_PDO_STORE
IR_READ_TABLES -
Data type: DATAOptional: No
Call by Reference: Yes
CHANGING Parameters details for CRM_ISU_PDO_STORE
CS_READ_DATA -
Data type: ANYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ISU_PDO_STORE 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_cs_read_data | TYPE ANY, " | |||
lv_ir_read_tables | TYPE DATA. " |
  CALL FUNCTION 'CRM_ISU_PDO_STORE' "write session data to database |
EXPORTING | ||
IR_READ_TABLES | = lv_ir_read_tables | |
CHANGING | ||
CS_READ_DATA | = lv_cs_read_data | |
. " CRM_ISU_PDO_STORE |
ABAP code using 7.40 inline data declarations to call FM CRM_ISU_PDO_STORE
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