SAP CP_99_PLAN_MESSAGE_SET Function Module for NOTRANSL: Plantyp-abhäniges setzen einer T100-Nachricht

Search SAP Function Modules

CP_99_PLAN_MESSAGE_SET is a standard cp 99 plan message set 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: Plantyp-abhäniges setzen einer T100-Nachricht 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 cp 99 plan message set FM, simply by entering the name CP_99_PLAN_MESSAGE_SET into the relevant SAP transaction such as SE37 or SE38.

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

Function CP_99_PLAN_MESSAGE_SET 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 'CP_99_PLAN_MESSAGE_SET'"NOTRANSL: Plantyp-abhäniges setzen einer T100-Nachricht
  EXPORTING
*  MSGNR_IMP =  "virtual message number
   MSGTY_IMP =  "Message type
*  MSGV1_IMP = ' ' "Message parameter 1
*  MSGV2_IMP = ' ' "Message parameter 2
*  MSGV3_IMP = ' ' "Message parameter 3
*  MSGV4_IMP = ' ' "Message parameter 4
   PLNTY_IMP =  "Task list type

.

IMPORTING Parameters details for CP_99_PLAN_MESSAGE_SET

MSGNR_IMP - virtual message number

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

MSGTY_IMP - Message type

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

MSGV1_IMP - Message parameter 1

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

MSGV2_IMP - Message parameter 2

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

MSGV3_IMP - Message parameter 3

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

MSGV4_IMP - Message parameter 4

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

PLNTY_IMP - Task list type

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

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

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