SAP UJN_API_HIE_DELETE Function Module for BPC: Delete hierarchy









UJN_API_HIE_DELETE is a standard ujn api hie delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC: Delete hierarchy 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 ujn api hie delete FM, simply by entering the name UJN_API_HIE_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: UJN_API_BI_IOBJ
Program Name: SAPLUJN_API_BI_IOBJ
Main Program: SAPLUJN_API_BI_IOBJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function UJN_API_HIE_DELETE 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 'UJN_API_HIE_DELETE'"BPC: Delete hierarchy
EXPORTING
I_HIER_ID = "BPC: Hierarch Internal ID
* I_USE_SERVICE_USER = ABAP_TRUE "BPC: Generic indicator
* I_OBJVERS = 'A' "Hierarchy version

IMPORTING
EF_SUCCESS = "Return Value of ABAP Statements
ET_MESSAGE_LINE = "BPC: Messages
.



IMPORTING Parameters details for UJN_API_HIE_DELETE

I_HIER_ID - BPC: Hierarch Internal ID

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

I_USE_SERVICE_USER - BPC: Generic indicator

Data type: UJ_FLG
Default: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_OBJVERS - Hierarchy version

Data type: RSOBJVERS
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UJN_API_HIE_DELETE

EF_SUCCESS - Return Value of ABAP Statements

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

ET_MESSAGE_LINE - BPC: Messages

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

Copy and paste ABAP code example for UJN_API_HIE_DELETE 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_i_hier_id  TYPE UJ_HIER_ID, "   
lv_ef_success  TYPE UJ_FLG, "   
lv_et_message_line  TYPE UJ0_T_MESSAGE, "   
lv_i_use_service_user  TYPE UJ_FLG, "   ABAP_TRUE
lv_i_objvers  TYPE RSOBJVERS. "   'A'

  CALL FUNCTION 'UJN_API_HIE_DELETE'  "BPC: Delete hierarchy
    EXPORTING
         I_HIER_ID = lv_i_hier_id
         I_USE_SERVICE_USER = lv_i_use_service_user
         I_OBJVERS = lv_i_objvers
    IMPORTING
         EF_SUCCESS = lv_ef_success
         ET_MESSAGE_LINE = lv_et_message_line
. " UJN_API_HIE_DELETE




ABAP code using 7.40 inline data declarations to call FM UJN_API_HIE_DELETE

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_i_use_service_user) = ABAP_TRUE.
 
DATA(ld_i_objvers) = 'A'.
 


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!