SAP CJWB_MILESTONE_DELETE Function Module for NOTRANSL: Prüfung ob zu Versionsnummer für Sim. Versionen eine Maske exist

Search SAP Function Modules

CJWB_MILESTONE_DELETE is a standard cjwb milestone 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: Prüfung ob zu Versionsnummer für Sim. Versionen eine Maske exist 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 cjwb milestone delete FM, simply by entering the name CJWB_MILESTONE_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function CJWB_MILESTONE_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 'CJWB_MILESTONE_DELETE'"NOTRANSL: Prüfung ob zu Versionsnummer für Sim. Versionen eine Maske exist
  EXPORTING
   I_MLSTD_MLST_ZAEHL =  "Milestone number

EXCEPTIONS
   PSP_ELEMENT_NOT_EXIST = 1    WBS_MILE_NOT_EXIST = 2    MILESTONE_IN_BILLING_PLAN = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCJWB_001 PS Customer Exit WOrk Breakdown Structure User Fields
EXIT_SAPLCJWB_002 PS Customer Exit: User Specific Fields PROJ (Data SAP -> SUBSCREEN)
EXIT_SAPLCJWB_003 PS Customer Exit: User Specific Fields PROJ (Data SUBSCREEN -> SAP)
EXIT_SAPLCJWB_004 PS Customer Exit: User Specific Fields PRPS (Data SAP _> SUBSCREEN)
EXIT_SAPLCJWB_005 PS Customer Exit: User Specific Fields PRPS (Data SUBSCREEN -> SAP)
EXIT_SAPLCJWB_006 PS Customer EXit: Pre-set Search/Replace String

IMPORTING Parameters details for CJWB_MILESTONE_DELETE

I_MLSTD_MLST_ZAEHL - Milestone number

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

EXCEPTIONS details

PSP_ELEMENT_NOT_EXIST -

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

WBS_MILE_NOT_EXIST -

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

MILESTONE_IN_BILLING_PLAN -

Data type:
Optional: No
Call by Reference: Yes

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

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