SAP CC_MIGRATION_EXECUTE Function Module for Migration from old to new master records
CC_MIGRATION_EXECUTE is a standard cc migration execute SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Migration from old to new master records 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 cc migration execute FM, simply by entering the name CC_MIGRATION_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CC_MIGRATION
Program Name: SAPLCC_MIGRATION
Main Program: SAPLCC_MIGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CC_MIGRATION_EXECUTE 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 'CC_MIGRATION_EXECUTE'"Migration from old to new master records.
EXPORTING
IV_ENCODING = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING
ET_PCA_MASTER = "Table Categories for Central Card Master
ET_PCA_MASTER_ADMIN = "Table Category of Central Card Master (Administration)
ET_PCA_BLOCK = "Table Category Card Master Block
ET_PCA_BLOCK_ADMIN = "Table Category Card Master Block: Administration Data
ET_PCA_SECURITY_RAW = "Payment Card Encryption
CHANGING
CT_BUT0CC = "SAP BP: Table Type for Transfer of Payment Card Data
CT_CCARD = "Table Category Card Master
EXCEPTIONS
NO_ENCODING_POSSIBLE = 1
IMPORTING Parameters details for CC_MIGRATION_EXECUTE
IV_ENCODING - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CC_MIGRATION_EXECUTE
ET_PCA_MASTER - Table Categories for Central Card Master
Data type: PCA_MASTER_TOptional: No
Call by Reference: Yes
ET_PCA_MASTER_ADMIN - Table Category of Central Card Master (Administration)
Data type: PCA_MASTER_ADMIN_TOptional: No
Call by Reference: Yes
ET_PCA_BLOCK - Table Category Card Master Block
Data type: PCAT_BLOCK_TOptional: No
Call by Reference: Yes
ET_PCA_BLOCK_ADMIN - Table Category Card Master Block: Administration Data
Data type: PCAT_BLOCK_ADMIN_TOptional: No
Call by Reference: Yes
ET_PCA_SECURITY_RAW - Payment Card Encryption
Data type: PCA_SECURITY_RAW_TOptional: No
Call by Reference: Yes
CHANGING Parameters details for CC_MIGRATION_EXECUTE
CT_BUT0CC - SAP BP: Table Type for Transfer of Payment Card Data
Data type: TTY_BUT0CCOptional: No
Call by Reference: Yes
CT_CCARD - Table Category Card Master
Data type: CCARD_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENCODING_POSSIBLE - Fehler beim Aufruf der SSF-Funktionen
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CC_MIGRATION_EXECUTE 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_ct_but0cc | TYPE TTY_BUT0CC, " | |||
| lv_iv_encoding | TYPE BOOLE_D, " | |||
| lv_et_pca_master | TYPE PCA_MASTER_T, " | |||
| lv_no_encoding_possible | TYPE PCA_MASTER_T, " | |||
| lv_ct_ccard | TYPE CCARD_T, " | |||
| lv_et_pca_master_admin | TYPE PCA_MASTER_ADMIN_T, " | |||
| lv_et_pca_block | TYPE PCAT_BLOCK_T, " | |||
| lv_et_pca_block_admin | TYPE PCAT_BLOCK_ADMIN_T, " | |||
| lv_et_pca_security_raw | TYPE PCA_SECURITY_RAW_T. " |
|   CALL FUNCTION 'CC_MIGRATION_EXECUTE' "Migration from old to new master records |
| EXPORTING | ||
| IV_ENCODING | = lv_iv_encoding | |
| IMPORTING | ||
| ET_PCA_MASTER | = lv_et_pca_master | |
| ET_PCA_MASTER_ADMIN | = lv_et_pca_master_admin | |
| ET_PCA_BLOCK | = lv_et_pca_block | |
| ET_PCA_BLOCK_ADMIN | = lv_et_pca_block_admin | |
| ET_PCA_SECURITY_RAW | = lv_et_pca_security_raw | |
| CHANGING | ||
| CT_BUT0CC | = lv_ct_but0cc | |
| CT_CCARD | = lv_ct_ccard | |
| EXCEPTIONS | ||
| NO_ENCODING_POSSIBLE = 1 | ||
| . " CC_MIGRATION_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM CC_MIGRATION_EXECUTE
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