SAP PMIQ_BUPA_CHANGE_STUDENT Function Module for Change a business partner of student









PMIQ_BUPA_CHANGE_STUDENT is a standard pmiq bupa change student 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 a business partner of student 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 pmiq bupa change student FM, simply by entering the name PMIQ_BUPA_CHANGE_STUDENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: PMIQ_BUPA
Program Name: SAPLPMIQ_BUPA
Main Program: SAPLPMIQ_BUPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PMIQ_BUPA_CHANGE_STUDENT 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 'PMIQ_BUPA_CHANGE_STUDENT'"Change a business partner of student
EXPORTING
IV_STOBJID = "Student
IV_AKTYP = "Activity category
* IV_VALDT = SY-DATLO "Validity date for business partner data

EXCEPTIONS
ILLEGAL_PARAMETERS = 1 STUDENT_NOT_FOUND = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for PMIQ_BUPA_CHANGE_STUDENT

IV_STOBJID - Student

Data type: PIQSTUDENT
Optional: No
Call by Reference: No ( called with pass by value option)

IV_AKTYP - Activity category

Data type: BU_AKTYP
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALDT - Validity date for business partner data

Data type: BU_VALDT
Default: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ILLEGAL_PARAMETERS - Illegal parameter

Data type:
Optional: No
Call by Reference: Yes

STUDENT_NOT_FOUND - Student not found

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PMIQ_BUPA_CHANGE_STUDENT 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_iv_stobjid  TYPE PIQSTUDENT, "   
lv_illegal_parameters  TYPE PIQSTUDENT, "   
lv_iv_aktyp  TYPE BU_AKTYP, "   
lv_student_not_found  TYPE BU_AKTYP, "   
lv_iv_valdt  TYPE BU_VALDT, "   SY-DATLO
lv_internal_error  TYPE BU_VALDT. "   

  CALL FUNCTION 'PMIQ_BUPA_CHANGE_STUDENT'  "Change a business partner of student
    EXPORTING
         IV_STOBJID = lv_iv_stobjid
         IV_AKTYP = lv_iv_aktyp
         IV_VALDT = lv_iv_valdt
    EXCEPTIONS
        ILLEGAL_PARAMETERS = 1
        STUDENT_NOT_FOUND = 2
        INTERNAL_ERROR = 3
. " PMIQ_BUPA_CHANGE_STUDENT




ABAP code using 7.40 inline data declarations to call FM PMIQ_BUPA_CHANGE_STUDENT

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.

 
 
 
 
DATA(ld_iv_valdt) = SY-DATLO.
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!