ISU_PARTNER_OUTAGE_TECHNOBJ SAP Function module - Determines Technical Reference Object in Event of Outage

ISU_PARTNER_OUTAGE_TECHNOBJ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_PARTNER_OUTAGE_TECHNOBJ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: PARTNER_TECHNOBJ
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_PARTNER_OUTAGE_TECHNOBJ - ISU PARTNER OUTAGE TECHNOBJ

CALL FUNCTION 'ISU_PARTNER_OUTAGE_TECHNOBJ' "Determines Technical Reference Object in Event of Outage
  EXPORTING
    x_partner =                 " but000-partner  Business Partner
*   x_connobj =                 " ehau-haus     Connection Object
*   x_devloc =                  " egpld-devloc  Device Location
*   x_device =                  " equi-equnr    Device
*   x_tech_inst =               " equi-equnr    Technical installation
*   x_progress =                " efkkstr-kennzx  Indicator: Progress Display
  IMPORTING
    y_device =                  " equi-equnr    Device
    y_tpl =                     " rfc_viqmel-tplnr  Functional Location
    y_objid =                   " eewm_notif_objid  Reference object type for creation of notifications
    y_regiogroup =              " regiogroup    Regional Structure Grouping
  EXCEPTIONS
    SYSTEM_ERROR = 1            "               System Error
    PARTNER_NOT_FOUND = 2       "
    CONNOBJ_NOT_FOUND = 3       "               Connection Object Does Not Exist
    DEVLOC_NOT_FOUND = 4        "
    DEVICE_NOT_FOUND = 5        "
    DEVICE_NOT_AT_CONNOBJ = 6   "
    DEVICE_NOT_AT_DEVLOC = 7    "
    DEVLOC_NOT_IN_CONNOBJ = 8   "
    COMBINATION_NOT_QUALIFIED = 9  "
    CANCELLED_BY_USER = 10      "               Canceled by user
    .  "  ISU_PARTNER_OUTAGE_TECHNOBJ

ABAP code example for Function Module ISU_PARTNER_OUTAGE_TECHNOBJ

The ABAP code below is a full code listing to execute function module ISU_PARTNER_OUTAGE_TECHNOBJ including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_y_device  
 
 TYPE EQUI-EQUNR
,
ld_y_tpl  
 
 TYPE RFC_VIQMEL-TPLNR
,
ld_y_objid  
 
 TYPE EEWM_NOTIF_OBJID
,
ld_y_regiogroup  
 
 TYPE REGIOGROUP
.

 

SELECT single PARTNER 
  FROM BUT000 
  INTO @DATA(ld_x_partner).



DATA(ld_x_connobj) = some text here


DATA(ld_x_devloc) = some text here
 

SELECT single EQUNR 
  FROM EQUI 
  INTO @DATA(ld_x_device).

 

SELECT single EQUNR 
  FROM EQUI 
  INTO @DATA(ld_x_tech_inst).



DATA(ld_x_progress) = some text here
.

CALL FUNCTION 'ISU_PARTNER_OUTAGE_TECHNOBJ'
  EXPORTING
    x_partner =                  ld_x_partner
*   x_connobj =                  ld_x_connobj
*   x_devloc =                   ld_x_devloc
*   x_device =                   ld_x_device
*   x_tech_inst =                ld_x_tech_inst
*   x_progress =                 ld_x_progress
  IMPORTING
    y_device =                   ld_y_device
    y_tpl =                      ld_y_tpl
    y_objid =                    ld_y_objid
    y_regiogroup =               ld_y_regiogroup
  EXCEPTIONS
    SYSTEM_ERROR =               1
    PARTNER_NOT_FOUND =          2
    CONNOBJ_NOT_FOUND =          3
    DEVLOC_NOT_FOUND =           4
    DEVICE_NOT_FOUND =           5
    DEVICE_NOT_AT_CONNOBJ =      6
    DEVICE_NOT_AT_DEVLOC =       7
    DEVLOC_NOT_IN_CONNOBJ =      8
    COMBINATION_NOT_QUALIFIED =    9
    CANCELLED_BY_USER =          10
    .  "  ISU_PARTNER_OUTAGE_TECHNOBJ

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 8. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 9. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 10. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_y_device
 
 TYPE EQUI-EQUNR ,
ld_x_partner
 
 TYPE BUT000-PARTNER ,
ld_y_tpl
 
 TYPE RFC_VIQMEL-TPLNR ,
ld_x_connobj
 
 TYPE EHAU-HAUS ,
ld_y_objid
 
 TYPE EEWM_NOTIF_OBJID ,
ld_x_devloc
 
 TYPE EGPLD-DEVLOC ,
ld_y_regiogroup
 
 TYPE REGIOGROUP ,
ld_x_device
 
 TYPE EQUI-EQUNR ,
ld_x_tech_inst
 
 TYPE EQUI-EQUNR ,
ld_x_progress
 
 TYPE EFKKSTR-KENNZX .



SELECT single PARTNER 
  FROM BUT000 
  INTO ld_x_partner.


ld_x_connobj = some text here

ld_x_devloc = some text here

SELECT single EQUNR 
  FROM EQUI 
  INTO ld_x_device.


SELECT single EQUNR 
  FROM EQUI 
  INTO ld_x_tech_inst.


ld_x_progress = some text here