SAP FB_ICRC_MOVE_DATA_003 Function Module for Moving Data
FB_ICRC_MOVE_DATA_003 is a standard fb icrc move data 003 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 Data 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 fb icrc move data 003 FM, simply by entering the name FB_ICRC_MOVE_DATA_003 into the relevant SAP transaction such as SE37 or SE38.
Function Group: FB_ICRC_SERVICES
Program Name: SAPLFB_ICRC_SERVICES
Main Program: SAPLFB_ICRC_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FB_ICRC_MOVE_DATA_003 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 'FB_ICRC_MOVE_DATA_003'"Moving Data.
EXPORTING
ID_POPER = "Posting Period
* ID_COMMIT_WORK = "'X' = Commit Work
* ID_COMMIT_WAIT = "'X' = Commit Work
* ID_MANUAL_ASSIGN = "'X' = Manual Assignment, ' ' = Automatic Assignment
CHANGING
CT_ORG_UNASSIGN = "
CT_PART_UNASSIGN = "
CT_ASSIGN_DIFF = "
CT_ASSIGN = "
IMPORTING Parameters details for FB_ICRC_MOVE_DATA_003
ID_POPER - Posting Period
Data type: POPEROptional: No
Call by Reference: Yes
ID_COMMIT_WORK - 'X' = Commit Work
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: Yes
ID_COMMIT_WAIT - 'X' = Commit Work
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: Yes
ID_MANUAL_ASSIGN - 'X' = Manual Assignment, SPACE = Automatic Assignment
Data type: FB_ICRC_FLAGOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for FB_ICRC_MOVE_DATA_003
CT_ORG_UNASSIGN -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
CT_PART_UNASSIGN -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
CT_ASSIGN_DIFF -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
CT_ASSIGN -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FB_ICRC_MOVE_DATA_003 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_id_poper | TYPE POPER, " | |||
| lv_ct_org_unassign | TYPE STANDARD TABLE, " | |||
| lv_id_commit_work | TYPE FB_ICRC_FLAG, " | |||
| lv_ct_part_unassign | TYPE STANDARD TABLE, " | |||
| lv_ct_assign_diff | TYPE STANDARD TABLE, " | |||
| lv_id_commit_wait | TYPE FB_ICRC_FLAG, " | |||
| lv_ct_assign | TYPE STANDARD TABLE, " | |||
| lv_id_manual_assign | TYPE FB_ICRC_FLAG. " |
|   CALL FUNCTION 'FB_ICRC_MOVE_DATA_003' "Moving Data |
| EXPORTING | ||
| ID_POPER | = lv_id_poper | |
| ID_COMMIT_WORK | = lv_id_commit_work | |
| ID_COMMIT_WAIT | = lv_id_commit_wait | |
| ID_MANUAL_ASSIGN | = lv_id_manual_assign | |
| CHANGING | ||
| CT_ORG_UNASSIGN | = lv_ct_org_unassign | |
| CT_PART_UNASSIGN | = lv_ct_part_unassign | |
| CT_ASSIGN_DIFF | = lv_ct_assign_diff | |
| CT_ASSIGN | = lv_ct_assign | |
| . " FB_ICRC_MOVE_DATA_003 | ||
ABAP code using 7.40 inline data declarations to call FM FB_ICRC_MOVE_DATA_003
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