SAP ISM_BP_MIGRATION_STATE_CHANGE Function Module for Change/Create Migration Status of a Business Partner
ISM_BP_MIGRATION_STATE_CHANGE is a standard ism bp migration state change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change/Create Migration Status of a Business Partner 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 ism bp migration state change FM, simply by entering the name ISM_BP_MIGRATION_STATE_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGBP_CONVERT
Program Name: SAPLJGBP_CONVERT
Main Program: SAPLJGBP_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_BP_MIGRATION_STATE_CHANGE 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 'ISM_BP_MIGRATION_STATE_CHANGE'"Change/Create Migration Status of a Business Partner.
EXPORTING
IN_PARTNER_OLD = "
IN_STATUS = "Migration Status of IS-M Business Partner to SAP BP
IN_PARTNER_NEW = "
IMPORTING Parameters details for ISM_BP_MIGRATION_STATE_CHANGE
IN_PARTNER_OLD -
Data type: PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IN_STATUS - Migration Status of IS-M Business Partner to SAP BP
Data type: STATUS_MIGRATIONOptional: No
Call by Reference: No ( called with pass by value option)
IN_PARTNER_NEW -
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_BP_MIGRATION_STATE_CHANGE 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_in_partner_old | TYPE PARTNER, " | |||
| lv_in_status | TYPE STATUS_MIGRATION, " | |||
| lv_in_partner_new | TYPE BU_PARTNER. " |
|   CALL FUNCTION 'ISM_BP_MIGRATION_STATE_CHANGE' "Change/Create Migration Status of a Business Partner |
| EXPORTING | ||
| IN_PARTNER_OLD | = lv_in_partner_old | |
| IN_STATUS | = lv_in_status | |
| IN_PARTNER_NEW | = lv_in_partner_new | |
| . " ISM_BP_MIGRATION_STATE_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM ISM_BP_MIGRATION_STATE_CHANGE
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