SAP ISH_BPMIG_OBJ_DATA_GET Function Module for IS-H: Get Data for IS-H Objects for Migration
ISH_BPMIG_OBJ_DATA_GET is a standard ish bpmig obj data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H: Get Data for IS-H Objects for Migration 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 ish bpmig obj data get FM, simply by entering the name ISH_BPMIG_OBJ_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: NBPMIG_FG
Program Name: SAPLNBPMIG_FG
Main Program: SAPLNBPMIG_FG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_BPMIG_OBJ_DATA_GET 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 'ISH_BPMIG_OBJ_DATA_GET'"IS-H: Get Data for IS-H Objects for Migration.
EXPORTING
I_ISH_OBJ_TYPE = "Object Type for the FI Assignments
I_ISH_OBJ_NUM = "ISH Object Number
* I_BP_NUM = "SAP Business Partner Number
* I_FI_NUM = "Customer Number of FI Customer
* IT_NOK_BP_NUMS = "BP keys for Next-Of-Kins
IMPORTING
ES_OBJ_DATA = "General BP Data and HC Role Specific Data
ET_NOKS = "Table with Patient's Next-Of-Kins
EXCEPTIONS
OBJECT_TYPE_UNKNOWN = 1 OBJECT_TYPE_NOT_SUPPORTED = 2 OBJECT_NUMBER_NOT_FOUND = 3
IMPORTING Parameters details for ISH_BPMIG_OBJ_DATA_GET
I_ISH_OBJ_TYPE - Object Type for the FI Assignments
Data type: ISH_OBJ_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_ISH_OBJ_NUM - ISH Object Number
Data type: ISH_OBJ_NUMOptional: No
Call by Reference: No ( called with pass by value option)
I_BP_NUM - SAP Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
I_FI_NUM - Customer Number of FI Customer
Data type: RF_KUNNROptional: Yes
Call by Reference: No ( called with pass by value option)
IT_NOK_BP_NUMS - BP keys for Next-Of-Kins
Data type: ISH_T_BP_KEYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISH_BPMIG_OBJ_DATA_GET
ES_OBJ_DATA - General BP Data and HC Role Specific Data
Data type: RNBUPA_HCROLESOptional: No
Call by Reference: Yes
ET_NOKS - Table with Patient's Next-Of-Kins
Data type: ISH_T_BUPAOptional: No
Call by Reference: Yes
EXCEPTIONS details
OBJECT_TYPE_UNKNOWN - Object type is unknown.
Data type:Optional: No
Call by Reference: Yes
OBJECT_TYPE_NOT_SUPPORTED - Object type is not supported
Data type:Optional: No
Call by Reference: Yes
OBJECT_NUMBER_NOT_FOUND - Object number not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_BPMIG_OBJ_DATA_GET 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_es_obj_data | TYPE RNBUPA_HCROLES, " | |||
| lv_i_ish_obj_type | TYPE ISH_OBJ_TYPE, " | |||
| lv_object_type_unknown | TYPE ISH_OBJ_TYPE, " | |||
| lv_et_noks | TYPE ISH_T_BUPA, " | |||
| lv_i_ish_obj_num | TYPE ISH_OBJ_NUM, " | |||
| lv_object_type_not_supported | TYPE ISH_OBJ_NUM, " | |||
| lv_i_bp_num | TYPE BU_PARTNER, " | |||
| lv_object_number_not_found | TYPE BU_PARTNER, " | |||
| lv_i_fi_num | TYPE RF_KUNNR, " | |||
| lv_it_nok_bp_nums | TYPE ISH_T_BP_KEY. " |
|   CALL FUNCTION 'ISH_BPMIG_OBJ_DATA_GET' "IS-H: Get Data for IS-H Objects for Migration |
| EXPORTING | ||
| I_ISH_OBJ_TYPE | = lv_i_ish_obj_type | |
| I_ISH_OBJ_NUM | = lv_i_ish_obj_num | |
| I_BP_NUM | = lv_i_bp_num | |
| I_FI_NUM | = lv_i_fi_num | |
| IT_NOK_BP_NUMS | = lv_it_nok_bp_nums | |
| IMPORTING | ||
| ES_OBJ_DATA | = lv_es_obj_data | |
| ET_NOKS | = lv_et_noks | |
| EXCEPTIONS | ||
| OBJECT_TYPE_UNKNOWN = 1 | ||
| OBJECT_TYPE_NOT_SUPPORTED = 2 | ||
| OBJECT_NUMBER_NOT_FOUND = 3 | ||
| . " ISH_BPMIG_OBJ_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISH_BPMIG_OBJ_DATA_GET
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