SAP COM_HIERARCHY_DELETE_API_INT Function Module for
COM_HIERARCHY_DELETE_API_INT is a standard com hierarchy delete api int SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 com hierarchy delete api int FM, simply by entering the name COM_HIERARCHY_DELETE_API_INT into the relevant SAP transaction such as SE37 or SE38.
Function Group: COM_HIERARCHY_API_INTERNAL
Program Name: SAPLCOM_HIERARCHY_API_INTERNAL
Main Program: SAPLCOM_HIERARCHY_API_INTERNAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function COM_HIERARCHY_DELETE_API_INT 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 'COM_HIERARCHY_DELETE_API_INT'".
EXPORTING
IV_HIERARCHY_GUID = "
EXCEPTIONS
DELETION_NOT_POSSIBLE = 1 INTERNAL_ERROR = 2 WRONG_CALL = 3 FOREIGN_LOCK = 4
IMPORTING Parameters details for COM_HIERARCHY_DELETE_API_INT
IV_HIERARCHY_GUID -
Data type: COMT_HIERARCHY_GUIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
DELETION_NOT_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
WRONG_CALL -
Data type:Optional: No
Call by Reference: Yes
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COM_HIERARCHY_DELETE_API_INT 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_iv_hierarchy_guid | TYPE COMT_HIERARCHY_GUID, " | |||
lv_deletion_not_possible | TYPE COMT_HIERARCHY_GUID, " | |||
lv_internal_error | TYPE COMT_HIERARCHY_GUID, " | |||
lv_wrong_call | TYPE COMT_HIERARCHY_GUID, " | |||
lv_foreign_lock | TYPE COMT_HIERARCHY_GUID. " |
  CALL FUNCTION 'COM_HIERARCHY_DELETE_API_INT' " |
EXPORTING | ||
IV_HIERARCHY_GUID | = lv_iv_hierarchy_guid | |
EXCEPTIONS | ||
DELETION_NOT_POSSIBLE = 1 | ||
INTERNAL_ERROR = 2 | ||
WRONG_CALL = 3 | ||
FOREIGN_LOCK = 4 | ||
. " COM_HIERARCHY_DELETE_API_INT |
ABAP code using 7.40 inline data declarations to call FM COM_HIERARCHY_DELETE_API_INT
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