SAP CCMSBI_PSEUDO_ENQUEUE Function Module for Pseudo-Enqueue via Monitoring









CCMSBI_PSEUDO_ENQUEUE is a standard ccmsbi pseudo enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Pseudo-Enqueue via Monitoring 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 ccmsbi pseudo enqueue FM, simply by entering the name CCMSBI_PSEUDO_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.

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



Function CCMSBI_PSEUDO_ENQUEUE 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 'CCMSBI_PSEUDO_ENQUEUE'"Pseudo-Enqueue via Monitoring
EXPORTING
LONG_OBJ_NAME = "Long name of an object node
PROCESS_ID = "Character Field Length - 32
STEP_ID = "Character field, 8 characters long
* WAIT_MODE = 'A' "A or F or N
* MAX_WAIT_TIME = 360 "Seconds
* OPTIONAL_PARAMETERS = "Parameter with Values

IMPORTING
FIRST_CALL = "Single-Character Indicator
PREV_STEPS = "Natural Number

EXCEPTIONS
MONITORING_ERROR = 1 IMPOSSIBLE_ERROR = 2 WAIT_TIME_OUT = 3
.



IMPORTING Parameters details for CCMSBI_PSEUDO_ENQUEUE

LONG_OBJ_NAME - Long name of an object node

Data type: ALMTNAME_L-ALMTFULLNM
Optional: No
Call by Reference: Yes

PROCESS_ID - Character Field Length - 32

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

STEP_ID - Character field, 8 characters long

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

WAIT_MODE - A or F or N

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

MAX_WAIT_TIME - Seconds

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

OPTIONAL_PARAMETERS - Parameter with Values

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

EXPORTING Parameters details for CCMSBI_PSEUDO_ENQUEUE

FIRST_CALL - Single-Character Indicator

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

PREV_STEPS - Natural Number

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

EXCEPTIONS details

MONITORING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

IMPOSSIBLE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

WAIT_TIME_OUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CCMSBI_PSEUDO_ENQUEUE 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_first_call  TYPE CHAR1, "   
lv_long_obj_name  TYPE ALMTNAME_L-ALMTFULLNM, "   
lv_monitoring_error  TYPE ALMTNAME_L, "   
lv_prev_steps  TYPE INT4, "   
lv_process_id  TYPE CHAR32, "   
lv_impossible_error  TYPE CHAR32, "   
lv_step_id  TYPE CHAR8, "   
lv_wait_time_out  TYPE CHAR8, "   
lv_wait_mode  TYPE CHAR1, "   'A'
lv_max_wait_time  TYPE INT4, "   360
lv_optional_parameters  TYPE ALPF_PARAMLIST_STRING_TAB. "   

  CALL FUNCTION 'CCMSBI_PSEUDO_ENQUEUE'  "Pseudo-Enqueue via Monitoring
    EXPORTING
         LONG_OBJ_NAME = lv_long_obj_name
         PROCESS_ID = lv_process_id
         STEP_ID = lv_step_id
         WAIT_MODE = lv_wait_mode
         MAX_WAIT_TIME = lv_max_wait_time
         OPTIONAL_PARAMETERS = lv_optional_parameters
    IMPORTING
         FIRST_CALL = lv_first_call
         PREV_STEPS = lv_prev_steps
    EXCEPTIONS
        MONITORING_ERROR = 1
        IMPOSSIBLE_ERROR = 2
        WAIT_TIME_OUT = 3
. " CCMSBI_PSEUDO_ENQUEUE




ABAP code using 7.40 inline data declarations to call FM CCMSBI_PSEUDO_ENQUEUE

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.

 
"SELECT single ALMTFULLNM FROM ALMTNAME_L INTO @DATA(ld_long_obj_name).
 
 
 
 
 
 
 
DATA(ld_wait_mode) = 'A'.
 
DATA(ld_max_wait_time) = 360.
 
 


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!