SAP CRM_BSP_CT_MOVE_FIELD Function Module for Moving fields
CRM_BSP_CT_MOVE_FIELD is a standard crm bsp ct move field SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Moving fields 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 bsp ct move field FM, simply by entering the name CRM_BSP_CT_MOVE_FIELD into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_BSP_CT_UI
Program Name: SAPLCRM_BSP_CT_UI
Main Program: SAPLCRM_BSP_CT_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_BSP_CT_MOVE_FIELD 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_BSP_CT_MOVE_FIELD'"Moving fields.
EXPORTING
IT_NODE_KEYS = "ALV Tree Control: Node Table
IV_NODE_KEY = "ALV Tree Control: Node Key
IMPORTING
EV_ERROR = "
EXCEPTIONS
ACTION_ABORT = 1
IMPORTING Parameters details for CRM_BSP_CT_MOVE_FIELD
IT_NODE_KEYS - ALV Tree Control: Node Table
Data type: LVC_T_NKEYOptional: No
Call by Reference: Yes
IV_NODE_KEY - ALV Tree Control: Node Key
Data type: LVC_NKEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_BSP_CT_MOVE_FIELD
EV_ERROR -
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
ACTION_ABORT - Abort action
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_BSP_CT_MOVE_FIELD 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_ev_error | TYPE ABAP_BOOL, " | |||
| lv_action_abort | TYPE ABAP_BOOL, " | |||
| lv_it_node_keys | TYPE LVC_T_NKEY, " | |||
| lv_iv_node_key | TYPE LVC_NKEY. " |
|   CALL FUNCTION 'CRM_BSP_CT_MOVE_FIELD' "Moving fields |
| EXPORTING | ||
| IT_NODE_KEYS | = lv_it_node_keys | |
| IV_NODE_KEY | = lv_iv_node_key | |
| IMPORTING | ||
| EV_ERROR | = lv_ev_error | |
| EXCEPTIONS | ||
| ACTION_ABORT = 1 | ||
| . " CRM_BSP_CT_MOVE_FIELD | ||
ABAP code using 7.40 inline data declarations to call FM CRM_BSP_CT_MOVE_FIELD
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