SAP CJWB_MILESTONE_INTERFACE Function Module for NOTRANSL: Bearbeitung Meilensteine aus Project Builder

Search SAP Function Modules

CJWB_MILESTONE_INTERFACE is a standard cjwb milestone interface 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: Bearbeitung Meilensteine aus Project Builder 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 interface FM, simply by entering the name CJWB_MILESTONE_INTERFACE 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_INTERFACE 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_INTERFACE'"NOTRANSL: Bearbeitung Meilensteine aus Project Builder
  EXPORTING
   I_METHOD =  "
   I_PRONR =  "
   I_PSPNR =  "
*  I_MLST_ZAEHL =  "
   I_AKTYP =  "
*  I_SUPERIOR_OBJECT =  "
*  I_OPTIONS =  "

 IMPORTING
   E_IDENT_SCREEN =  "
   E_VIEW_SCREEN =  "
   E_IDENT_PROG =  "
   E_VIEW_PROG =  "
   E_MLST_ZAEHL =  "
   E_AKTYP =  "Activity Category in the Transaction

EXCEPTIONS
   NOT_FOUND = 1    NO_AUTHORITY = 2 

.

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_INTERFACE

I_METHOD -

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

I_PRONR -

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

I_PSPNR -

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

I_MLST_ZAEHL -

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

I_AKTYP -

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

I_SUPERIOR_OBJECT -

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

I_OPTIONS -

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

EXPORTING Parameters details for CJWB_MILESTONE_INTERFACE

E_IDENT_SCREEN -

Data type: SY-DYNNR
Optional: No
Call by Reference: Yes

E_VIEW_SCREEN -

Data type: SY-DYNNR
Optional: No
Call by Reference: Yes

E_IDENT_PROG -

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

E_VIEW_PROG -

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

E_MLST_ZAEHL -

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

E_AKTYP - Activity Category in the Transaction

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

EXCEPTIONS details

NOT_FOUND -

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

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

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

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