SAP IQS2_CHANGE_OBJNR Function Module for NOTRANSL: Wechseln OBJNR für Bezugsobjekt
IQS2_CHANGE_OBJNR is a standard iqs2 change objnr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Wechseln OBJNR für Bezugsobjekt 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 iqs2 change objnr FM, simply by entering the name IQS2_CHANGE_OBJNR into the relevant SAP transaction such as SE37 or SE38.
Function Group: IQS2
Program Name: SAPLIQS2
Main Program: SAPLIQS2
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IQS2_CHANGE_OBJNR 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 'IQS2_CHANGE_OBJNR'"NOTRANSL: Wechseln OBJNR für Bezugsobjekt.
EXPORTING
O_OBJNR = "Object Number for Status Management
N_OBJNR = "Object Number for Status Management
EXCEPTIONS
NUMBER_BLANK = 1
IMPORTING Parameters details for IQS2_CHANGE_OBJNR
O_OBJNR - Object Number for Status Management
Data type: RIQS4-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
N_OBJNR - Object Number for Status Management
Data type: RIQS4-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NUMBER_BLANK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IQS2_CHANGE_OBJNR 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_o_objnr | TYPE RIQS4-OBJNR, " | |||
| lv_number_blank | TYPE RIQS4, " | |||
| lv_n_objnr | TYPE RIQS4-OBJNR. " |
|   CALL FUNCTION 'IQS2_CHANGE_OBJNR' "NOTRANSL: Wechseln OBJNR für Bezugsobjekt |
| EXPORTING | ||
| O_OBJNR | = lv_o_objnr | |
| N_OBJNR | = lv_n_objnr | |
| EXCEPTIONS | ||
| NUMBER_BLANK = 1 | ||
| . " IQS2_CHANGE_OBJNR | ||
ABAP code using 7.40 inline data declarations to call FM IQS2_CHANGE_OBJNR
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.| "SELECT single OBJNR FROM RIQS4 INTO @DATA(ld_o_objnr). | ||||
| "SELECT single OBJNR FROM RIQS4 INTO @DATA(ld_n_objnr). | ||||
Search for further information about these or an SAP related objects