SAP MAP_BAPIBP_PERSONAL_BAPIST Function Module for CM: Map BP BAPI Structure -> Student BAPI Struc. for Person Data
MAP_BAPIBP_PERSONAL_BAPIST is a standard map bapibp personal bapist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CM: Map BP BAPI Structure -> Student BAPI Struc. for Person 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 map bapibp personal bapist FM, simply by entering the name MAP_BAPIBP_PERSONAL_BAPIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRPIQ00STUDENTBAPI
Program Name: SAPLHRPIQ00STUDENTBAPI
Main Program: SAPLHRPIQ00STUDENTBAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP_BAPIBP_PERSONAL_BAPIST 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 'MAP_BAPIBP_PERSONAL_BAPIST'"CM: Map BP BAPI Structure -> Student BAPI Struc. for Person Data.
EXPORTING
IV_PARTNER = "Business Partner Number
* IS_CENTRAL_DATA = "General BP Data, Independent of Business Partner Category
* IS_CENTRAL_PERSONAL_DATA = "SAP BP: BAPI Structure for Personal Data
* IV_ST_FROM_BP = "
IMPORTING
ES_STUDENT_PERSONAL = "BAPI Structure for Student: Personal Data
CHANGING
* CT_RETURN = "Return Table
IMPORTING Parameters details for MAP_BAPIBP_PERSONAL_BAPIST
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IS_CENTRAL_DATA - General BP Data, Independent of Business Partner Category
Data type: BAPIBUS1006_CENTRALOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_CENTRAL_PERSONAL_DATA - SAP BP: BAPI Structure for Personal Data
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ST_FROM_BP -
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MAP_BAPIBP_PERSONAL_BAPIST
ES_STUDENT_PERSONAL - BAPI Structure for Student: Personal Data
Data type: BAPISTUDENT_PERSONALOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for MAP_BAPIBP_PERSONAL_BAPIST
CT_RETURN - Return Table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MAP_BAPIBP_PERSONAL_BAPIST 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_return | TYPE BAPIRET2_T, " | |||
| lv_iv_partner | TYPE BU_PARTNER, " | |||
| lv_es_student_personal | TYPE BAPISTUDENT_PERSONAL, " | |||
| lv_is_central_data | TYPE BAPIBUS1006_CENTRAL, " | |||
| lv_is_central_personal_data | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
| lv_iv_st_from_bp | TYPE XFELD. " |
|   CALL FUNCTION 'MAP_BAPIBP_PERSONAL_BAPIST' "CM: Map BP BAPI Structure -> Student BAPI Struc. for Person Data |
| EXPORTING | ||
| IV_PARTNER | = lv_iv_partner | |
| IS_CENTRAL_DATA | = lv_is_central_data | |
| IS_CENTRAL_PERSONAL_DATA | = lv_is_central_personal_data | |
| IV_ST_FROM_BP | = lv_iv_st_from_bp | |
| IMPORTING | ||
| ES_STUDENT_PERSONAL | = lv_es_student_personal | |
| CHANGING | ||
| CT_RETURN | = lv_ct_return | |
| . " MAP_BAPIBP_PERSONAL_BAPIST | ||
ABAP code using 7.40 inline data declarations to call FM MAP_BAPIBP_PERSONAL_BAPIST
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