SAP ISU_PARTNER_SERVICE_TECHNOBJ Function Module for Determines Technical Ref. Object for Autom. Generation of Service Order
ISU_PARTNER_SERVICE_TECHNOBJ is a standard isu partner service technobj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Technical Ref. Object for Autom. Generation of Service Order 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 isu partner service technobj FM, simply by entering the name ISU_PARTNER_SERVICE_TECHNOBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: PARTNER_TECHNOBJ
Program Name: SAPLPARTNER_TECHNOBJ
Main Program: SAPLPARTNER_TECHNOBJ
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_PARTNER_SERVICE_TECHNOBJ 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 'ISU_PARTNER_SERVICE_TECHNOBJ'"Determines Technical Ref. Object for Autom. Generation of Service Order.
EXPORTING
X_PARTNER = "Business Partner
X_ORDERCODE = "Order type (table TEWOCODE)
* X_CONNOBJ = "Connection Object
* X_DEVICE = "Device
* X_DISPLAYUNIQUE = "
* X_PROGRESS = "Indicator: Progress Display
IMPORTING
Y_REFOBJTYPE = "
Y_REFOBJ = "
Y_REFOBJTYPE2 = "
Y_REFOBJ2 = "
Y_VAPLZ = "Person Responsible for Work Center
CHANGING
XY_PLANNINGPLANT = "PM Plant
EXCEPTIONS
SYSTEM_ERROR = 1 PARTNER_NOT_FOUND = 2 CONNOBJ_NOT_FOUND = 3 DEVICE_NOT_FOUND = 4 DEVICE_NOT_AT_CONNOBJ = 5 CANCELLED_BY_USER = 6
IMPORTING Parameters details for ISU_PARTNER_SERVICE_TECHNOBJ
X_PARTNER - Business Partner
Data type: BUT000-PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
X_ORDERCODE - Order type (table TEWOCODE)
Data type: TEWOCODES-ORDER_CODEOptional: No
Call by Reference: No ( called with pass by value option)
X_CONNOBJ - Connection Object
Data type: EHAU-HAUSOptional: Yes
Call by Reference: No ( called with pass by value option)
X_DEVICE - Device
Data type: EQUI-EQUNROptional: Yes
Call by Reference: No ( called with pass by value option)
X_DISPLAYUNIQUE -
Data type: REGEN-KENNZXOptional: Yes
Call by Reference: No ( called with pass by value option)
X_PROGRESS - Indicator: Progress Display
Data type: EFKKSTR-KENNZXOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_PARTNER_SERVICE_TECHNOBJ
Y_REFOBJTYPE -
Data type: T399A-BZGSOBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
Y_REFOBJ -
Data type: T399A-BZGSOBJOptional: No
Call by Reference: No ( called with pass by value option)
Y_REFOBJTYPE2 -
Data type: T399A-BZGSOBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
Y_REFOBJ2 -
Data type: T399A-BZGSOBJOptional: No
Call by Reference: No ( called with pass by value option)
Y_VAPLZ - Person Responsible for Work Center
Data type: CAUFVD-VAPLZOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISU_PARTNER_SERVICE_TECHNOBJ
XY_PLANNINGPLANT - PM Plant
Data type: T399A-IWERKOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONNOBJ_NOT_FOUND - Connection Object Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DEVICE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DEVICE_NOT_AT_CONNOBJ -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED_BY_USER -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_PARTNER_SERVICE_TECHNOBJ 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_x_partner | TYPE BUT000-PARTNER, " | |||
| lv_system_error | TYPE BUT000, " | |||
| lv_y_refobjtype | TYPE T399A-BZGSOBJTYP, " | |||
| lv_xy_planningplant | TYPE T399A-IWERK, " | |||
| lv_y_refobj | TYPE T399A-BZGSOBJ, " | |||
| lv_x_ordercode | TYPE TEWOCODES-ORDER_CODE, " | |||
| lv_partner_not_found | TYPE TEWOCODES, " | |||
| lv_x_connobj | TYPE EHAU-HAUS, " | |||
| lv_y_refobjtype2 | TYPE T399A-BZGSOBJTYP, " | |||
| lv_connobj_not_found | TYPE T399A, " | |||
| lv_x_device | TYPE EQUI-EQUNR, " | |||
| lv_y_refobj2 | TYPE T399A-BZGSOBJ, " | |||
| lv_device_not_found | TYPE T399A, " | |||
| lv_y_vaplz | TYPE CAUFVD-VAPLZ, " | |||
| lv_x_displayunique | TYPE REGEN-KENNZX, " | |||
| lv_device_not_at_connobj | TYPE REGEN, " | |||
| lv_x_progress | TYPE EFKKSTR-KENNZX, " | |||
| lv_cancelled_by_user | TYPE EFKKSTR. " |
|   CALL FUNCTION 'ISU_PARTNER_SERVICE_TECHNOBJ' "Determines Technical Ref. Object for Autom. Generation of Service Order |
| EXPORTING | ||
| X_PARTNER | = lv_x_partner | |
| X_ORDERCODE | = lv_x_ordercode | |
| X_CONNOBJ | = lv_x_connobj | |
| X_DEVICE | = lv_x_device | |
| X_DISPLAYUNIQUE | = lv_x_displayunique | |
| X_PROGRESS | = lv_x_progress | |
| IMPORTING | ||
| Y_REFOBJTYPE | = lv_y_refobjtype | |
| Y_REFOBJ | = lv_y_refobj | |
| Y_REFOBJTYPE2 | = lv_y_refobjtype2 | |
| Y_REFOBJ2 | = lv_y_refobj2 | |
| Y_VAPLZ | = lv_y_vaplz | |
| CHANGING | ||
| XY_PLANNINGPLANT | = lv_xy_planningplant | |
| EXCEPTIONS | ||
| SYSTEM_ERROR = 1 | ||
| PARTNER_NOT_FOUND = 2 | ||
| CONNOBJ_NOT_FOUND = 3 | ||
| DEVICE_NOT_FOUND = 4 | ||
| DEVICE_NOT_AT_CONNOBJ = 5 | ||
| CANCELLED_BY_USER = 6 | ||
| . " ISU_PARTNER_SERVICE_TECHNOBJ | ||
ABAP code using 7.40 inline data declarations to call FM ISU_PARTNER_SERVICE_TECHNOBJ
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 PARTNER FROM BUT000 INTO @DATA(ld_x_partner). | ||||
| "SELECT single BZGSOBJTYP FROM T399A INTO @DATA(ld_y_refobjtype). | ||||
| "SELECT single IWERK FROM T399A INTO @DATA(ld_xy_planningplant). | ||||
| "SELECT single BZGSOBJ FROM T399A INTO @DATA(ld_y_refobj). | ||||
| "SELECT single ORDER_CODE FROM TEWOCODES INTO @DATA(ld_x_ordercode). | ||||
| "SELECT single HAUS FROM EHAU INTO @DATA(ld_x_connobj). | ||||
| "SELECT single BZGSOBJTYP FROM T399A INTO @DATA(ld_y_refobjtype2). | ||||
| "SELECT single EQUNR FROM EQUI INTO @DATA(ld_x_device). | ||||
| "SELECT single BZGSOBJ FROM T399A INTO @DATA(ld_y_refobj2). | ||||
| "SELECT single VAPLZ FROM CAUFVD INTO @DATA(ld_y_vaplz). | ||||
| "SELECT single KENNZX FROM REGEN INTO @DATA(ld_x_displayunique). | ||||
| "SELECT single KENNZX FROM EFKKSTR INTO @DATA(ld_x_progress). | ||||
Search for further information about these or an SAP related objects