SAP ABAP SOAMANAGER Webservice config tables

Somethimes, After migaration to S4/HANA system. Part of the config of SAP ABAP WebService will changed when create services. In order to find the different. We can use below tables for SAP tcode soamanager .     SRT_CFG_DIR CONFIG_NAME=Z_IF_CRM_SOAP CONFIG_KEY=CB70DE0421AB1EDDBAE6221620731454 SRT_CFG_DIR_T CONFIG_KEY=CB70DE0421AB1EDDBAE6221620731454 SRT_RTC_DIR CONFIG_KEY=CB70DE0421AB1EDDBAE6221620731454 SRT_RTC_BNDG CONFIG_KEY=CB70DE0421AB1EDDBAE6221620731454  BINDING_KEY  = CB70DE0421AB1EDDBAE6221620737454 SRT_RTC_DATA  BINDING_KEY  = CB70DE0421AB1EDDBAE6221620737454 SRT_RTC_CFGVAL CONFIG_KEY=CB70DE0421AB1EDDBAE6221620731454

Use BAPI/FMs to delete SM12 LOCK object in SAP

Purpose:lots of object locked for a long time when the network is pool. I hate to be called to delete/Realease the SM12 lock object in the middle night. Sample Code as ABAP Source Code: DATA: lt_locks TYPE TABLE OF seqg3 . DATA ls_lock TYPE seqg3. CALL FUNCTION ‘ENQUEUE_READ’ EXPORTING *   GCLIENT               = SY-MANDT gname                 = ‘SEOCLSENQ’ *   GARG                  = ‘ ‘ *   GUNAME                = SY-UNAME *   LOCAL                 = ‘ ‘ *   FAST                  = ‘ ‘ *   GARGNOWC              = ‘ ‘ * IMPORTING *   NUMBER                = *   SUBRC                 = TABLES enq                   = lt_locks EXCEPTIONS communication_failure = 1 system_failure        = 2 OTHERS                = 3. IF sy-subrc <> 0.

error RABAX ST22 Dump,SAPSQL_IN_ITAB_ILLEGAL_SIGN

Today SAP ABAP se80 Webservice Provider error RABAX( ST22 Dump:CX_AI_SYSTEM_FAULT-UNCAUGHT_EXCEPTION)Dump SAPSQL_IN_ITAB_ILLEGAL_SIGN Checked the account and password, it is no problem. Interface parameter webservice provided, somebody changed the provide service with Camel-Case naming rule. For example: Internal View=》Service ==》Input==》 【T_MY_LOVE_BABY】CHANGED TO 【TMyLoveBaby】 Theis naming result was saved in the table:VEPFIELDREF and table VEPSTRUTYPE for web service