SAP CRM_IST_SERVOBJ_LOCKS_UPDATE Function Module for Schreiben des Sets in die entsprechenden Tabellen
CRM_IST_SERVOBJ_LOCKS_UPDATE is a standard crm ist servobj locks update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Schreiben des Sets in die entsprechenden Tabellen 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 ist servobj locks update FM, simply by entering the name CRM_IST_SERVOBJ_LOCKS_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_SERVICE_OBJECT
Program Name: SAPLCRM_IST_SERVICE_OBJECT
Main Program: SAPLCRM_IST_SERVICE_OBJECT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_SERVOBJ_LOCKS_UPDATE 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_IST_SERVOBJ_LOCKS_UPDATE'"Schreiben des Sets in die entsprechenden Tabellen.
EXPORTING
IS_NAV_NEW = "Structure for Maintenance of the TSO_GEN_DATA Set Type
IS_NAV_HISTORY = "Structure for Maintenance of the TSO_GEN_DATA Set Type
* IV_IBASE = "IBase
EXCEPTIONS
ENQUEUE_FAILED = 1
IMPORTING Parameters details for CRM_IST_SERVOBJ_LOCKS_UPDATE
IS_NAV_NEW - Structure for Maintenance of the TSO_GEN_DATA Set Type
Data type: ECRM_ISU_NAV_COMPLETEOptional: No
Call by Reference: Yes
IS_NAV_HISTORY - Structure for Maintenance of the TSO_GEN_DATA Set Type
Data type: ECRM_ISU_NAV_COMPLETEOptional: No
Call by Reference: Yes
IV_IBASE - IBase
Data type: IB_IBASEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ENQUEUE_FAILED - IBase Sperre fehlgeschlagen
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_SERVOBJ_LOCKS_UPDATE 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_nav_new | TYPE ECRM_ISU_NAV_COMPLETE, " | |||
lv_enqueue_failed | TYPE ECRM_ISU_NAV_COMPLETE, " | |||
lv_is_nav_history | TYPE ECRM_ISU_NAV_COMPLETE, " | |||
lv_iv_ibase | TYPE IB_IBASE. " |
  CALL FUNCTION 'CRM_IST_SERVOBJ_LOCKS_UPDATE' "Schreiben des Sets in die entsprechenden Tabellen |
EXPORTING | ||
IS_NAV_NEW | = lv_is_nav_new | |
IS_NAV_HISTORY | = lv_is_nav_history | |
IV_IBASE | = lv_iv_ibase | |
EXCEPTIONS | ||
ENQUEUE_FAILED = 1 | ||
. " CRM_IST_SERVOBJ_LOCKS_UPDATE |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_SERVOBJ_LOCKS_UPDATE
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