SAP RCP321_EHS_OBJECTS_DELETE Function Module for NOTRANSL: RMS-RCP: Schreiben der EHS Objekte









RCP321_EHS_OBJECTS_DELETE is a standard rcp321 ehs objects 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 NOTRANSL: RMS-RCP: Schreiben der EHS Objekte 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 rcp321 ehs objects delete FM, simply by entering the name RCP321_EHS_OBJECTS_DELETE into the relevant SAP transaction such as SE37 or SE38.

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



Function RCP321_EHS_OBJECTS_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 'RCP321_EHS_OBJECTS_DELETE'"NOTRANSL: RMS-RCP: Schreiben der EHS Objekte
  EXPORTING
   I_DATA_SCENARIO =  "Data Scenario for API Recipe
   I_GUID =  "Internal Number of iPPE Node
   I_AENNR =  "Change Number
*  I_PVGUID =  "Internal Number of the PVS Variant
*  I_PVCDCNT =  "Internal Counter for iPPE Objects
*  I_VALFROM =  "Valid-From Date
   I_RECN =  "Sequence Number of the Data Record

CHANGING
*  XS_EHS_HEADER =  "
*  XT_IDENT =  "RMS-RCP: API - Table Type for Identifiers
*  XT_ASCOPE =  "RMS-RCP: API - Table Type for Scope of Application
*  XT_PP =  "RMS-RCP: API - Table Type for Process Parameters

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for RCP321_EHS_OBJECTS_DELETE

I_DATA_SCENARIO - Data Scenario for API Recipe

Data type: RCPE_DATASCEN
Optional: No
Call by Reference: Yes

I_GUID - Internal Number of iPPE Node

Data type: PVS_PNGUID
Optional: No
Call by Reference: Yes

I_AENNR - Change Number

Data type: AENNR
Optional: No
Call by Reference: Yes

I_PVGUID - Internal Number of the PVS Variant

Data type: PVS_PVGUID
Optional: Yes
Call by Reference: Yes

I_PVCDCNT - Internal Counter for iPPE Objects

Data type: PVS_COUNT
Optional: Yes
Call by Reference: Yes

I_VALFROM - Valid-From Date

Data type: RCPE_ADATUM
Optional: Yes
Call by Reference: Yes

I_RECN - Sequence Number of the Data Record

Data type: ESERECN
Optional: No
Call by Reference: Yes

CHANGING Parameters details for RCP321_EHS_OBJECTS_DELETE

XS_EHS_HEADER -

Data type: ESPRH_APIRH_WA_TYPE
Optional: Yes
Call by Reference: Yes

XT_IDENT - RMS-RCP: API - Table Type for Identifiers

Data type: RCPTY_API_IDENT
Optional: Yes
Call by Reference: Yes

XT_ASCOPE - RMS-RCP: API - Table Type for Scope of Application

Data type: RCPTY_API_ASCOPE
Optional: Yes
Call by Reference: Yes

XT_PP - RMS-RCP: API - Table Type for Process Parameters

Data type: RCPTY_API_PP
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ERROR - Error When Writing

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

Copy and paste ABAP code example for RCP321_EHS_OBJECTS_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_error  TYPE STRING, "   
lv_xs_ehs_header  TYPE ESPRH_APIRH_WA_TYPE, "   
lv_i_data_scenario  TYPE RCPE_DATASCEN, "   
lv_i_guid  TYPE PVS_PNGUID, "   
lv_xt_ident  TYPE RCPTY_API_IDENT, "   
lv_i_aennr  TYPE AENNR, "   
lv_xt_ascope  TYPE RCPTY_API_ASCOPE, "   
lv_xt_pp  TYPE RCPTY_API_PP, "   
lv_i_pvguid  TYPE PVS_PVGUID, "   
lv_i_pvcdcnt  TYPE PVS_COUNT, "   
lv_i_valfrom  TYPE RCPE_ADATUM, "   
lv_i_recn  TYPE ESERECN. "   

  CALL FUNCTION 'RCP321_EHS_OBJECTS_DELETE'  "NOTRANSL: RMS-RCP: Schreiben der EHS Objekte
    EXPORTING
         I_DATA_SCENARIO = lv_i_data_scenario
         I_GUID = lv_i_guid
         I_AENNR = lv_i_aennr
         I_PVGUID = lv_i_pvguid
         I_PVCDCNT = lv_i_pvcdcnt
         I_VALFROM = lv_i_valfrom
         I_RECN = lv_i_recn
    CHANGING
         XS_EHS_HEADER = lv_xs_ehs_header
         XT_IDENT = lv_xt_ident
         XT_ASCOPE = lv_xt_ascope
         XT_PP = lv_xt_pp
    EXCEPTIONS
        ERROR = 1
. " RCP321_EHS_OBJECTS_DELETE




ABAP code using 7.40 inline data declarations to call FM RCP321_EHS_OBJECTS_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.

 
 
 
 
 
 
 
 
 
 
 
 


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!