SAP ISU_M_HYPER_OBJECT_NAMES_SET Function Module for IS-U Migration: Naming for Hyper-Objects

Search SAP Function Modules

ISU_M_HYPER_OBJECT_NAMES_SET is a standard isu m hyper object names set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U Migration: Naming for Hyper-Objects 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 m hyper object names set FM, simply by entering the name ISU_M_HYPER_OBJECT_NAMES_SET into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_M_HYPER_OBJECT_NAMES_SET 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_M_HYPER_OBJECT_NAMES_SET'"IS-U Migration: Naming for Hyper-Objects
  EXPORTING
   X_FIRMA =  "Company (Client) for IS-U Migration
   X_OBJECT =  "Migration Object
*  X_REF_OBJECT =  "
*  X_LEVEL =  "
*  X_NODE =  "

 IMPORTING
   Y_AUTOSTRUCTURE =  "Table Name
   Y_INFOSTRUCTURE =  "Table Name
   Y_INPSTRUCTURE =  "Table Name
   Y_FUNCPOOL =  "Function group, to which the function module belongs
   Y_FUNCNAME =  "Name of Function Module
   Y_TYPEGROUP =  "Type Group

EXCEPTIONS
   INVALID_OBJECT = 1 

.

IMPORTING Parameters details for ISU_M_HYPER_OBJECT_NAMES_SET

X_FIRMA - Company (Client) for IS-U Migration

Data type: TEMOB-FIRMA
Optional: No
Call by Reference: No ( called with pass by value option)

X_OBJECT - Migration Object

Data type: TEMDB-OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

X_REF_OBJECT -

Data type: TEMDB-REF_OBJECT
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_LEVEL -

Data type: TEMDB-A_LEVEL
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_NODE -

Data type: TEMDB-A_NODE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISU_M_HYPER_OBJECT_NAMES_SET

Y_AUTOSTRUCTURE - Table Name

Data type: DD03L-TABNAME
Optional: No
Call by Reference: No ( called with pass by value option)

Y_INFOSTRUCTURE - Table Name

Data type: DD03L-TABNAME
Optional: No
Call by Reference: No ( called with pass by value option)

Y_INPSTRUCTURE - Table Name

Data type: DD03L-TABNAME
Optional: No
Call by Reference: No ( called with pass by value option)

Y_FUNCPOOL - Function group, to which the function module belongs

Data type: TLIBG-AREA
Optional: No
Call by Reference: No ( called with pass by value option)

Y_FUNCNAME - Name of Function Module

Data type: TFDIR-FUNCNAME
Optional: No
Call by Reference: No ( called with pass by value option)

Y_TYPEGROUP - Type Group

Data type: DD50D-TYPEGROUP
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INVALID_OBJECT - Object Not Found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_M_HYPER_OBJECT_NAMES_SET 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.

ABAP code using 7.40 inline data declarations to call FM ISU_M_HYPER_OBJECT_NAMES_SET

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