SAP DTL_RULES_RESET Function Module for API: delete rules for existing (sub)project or conv.obj.

Search SAP Function Modules

DTL_RULES_RESET is a standard dtl rules reset SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for API: delete rules for existing (sub)project or conv.obj. 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 dtl rules reset FM, simply by entering the name DTL_RULES_RESET into the relevant SAP transaction such as SE37 or SE38.

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

Function DTL_RULES_RESET 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 'DTL_RULES_RESET'"API: delete rules for existing (sub)project or conv.obj.
  EXPORTING
   I_PROJECT =  "Identifier for Projects
   I_SUBPROJECT =  "Namefield f. Sub-Projects
*  I_COBJ =  "Name for Conversion Objects
*  I_VISIBILITY = '2' "Rule Visibility
   I_PACKID =  "Package number to specify CMIS and TDMS packages
   I_SESSION_ID =  "MBT PCL SESSION_ID
*  I_TADIR = '-' "Direct TADIR update instead of CTS

 IMPORTING
   E_LOGNUMBER =  "Anwendungs-Log: Protokollnummer
   E_STATUS =  "Status info for MWB activities

TABLES
   IT_RULELIST =  "Structure for passing of rules to DTL (API)

.

IMPORTING Parameters details for DTL_RULES_RESET

I_PROJECT - Identifier for Projects

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

I_SUBPROJECT - Namefield f. Sub-Projects

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

I_COBJ - Name for Conversion Objects

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

I_VISIBILITY - Rule Visibility

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

I_PACKID - Package number to specify CMIS and TDMS packages

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

I_SESSION_ID - MBT PCL SESSION_ID

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

I_TADIR - Direct TADIR update instead of CTS

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

EXPORTING Parameters details for DTL_RULES_RESET

E_LOGNUMBER - Anwendungs-Log: Protokollnummer

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

E_STATUS - Status info for MWB activities

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

TABLES Parameters details for DTL_RULES_RESET

IT_RULELIST - Structure for passing of rules to DTL (API)

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

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

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