SAP BBP_CM_API_VALID_STATES Function Module for Retrieve valid States for Object









BBP_CM_API_VALID_STATES is a standard bbp cm api valid states SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve valid States for Object 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 bbp cm api valid states FM, simply by entering the name BBP_CM_API_VALID_STATES into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_CM_API_VALID_STATES 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 'BBP_CM_API_VALID_STATES'"Retrieve valid States for Object
EXPORTING
IV_OBJECT_TYPE = "Object Types (Program, Initiative, Methodology)
IV_CURR_STATE = "State of the Object - Category management

TABLES
ET_VALID_STATES = "Possible state Transitions - Category management
ET_MESSAGES = "Return Parameter
.



IMPORTING Parameters details for BBP_CM_API_VALID_STATES

IV_OBJECT_TYPE - Object Types (Program, Initiative, Methodology)

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

IV_CURR_STATE - State of the Object - Category management

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

TABLES Parameters details for BBP_CM_API_VALID_STATES

ET_VALID_STATES - Possible state Transitions - Category management

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

ET_MESSAGES - Return Parameter

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

Copy and paste ABAP code example for BBP_CM_API_VALID_STATES 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_iv_object_type  TYPE BBPD_CM_P_STATES-CM_OBJECT, "   
lt_et_valid_states  TYPE STANDARD TABLE OF BBPS_CM_P_STATES_D, "   
lt_et_messages  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_curr_state  TYPE BBPD_CM_STATES-CM_STATE. "   

  CALL FUNCTION 'BBP_CM_API_VALID_STATES'  "Retrieve valid States for Object
    EXPORTING
         IV_OBJECT_TYPE = lv_iv_object_type
         IV_CURR_STATE = lv_iv_curr_state
    TABLES
         ET_VALID_STATES = lt_et_valid_states
         ET_MESSAGES = lt_et_messages
. " BBP_CM_API_VALID_STATES




ABAP code using 7.40 inline data declarations to call FM BBP_CM_API_VALID_STATES

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 CM_OBJECT FROM BBPD_CM_P_STATES INTO @DATA(ld_iv_object_type).
 
 
 
"SELECT single CM_STATE FROM BBPD_CM_STATES INTO @DATA(ld_iv_curr_state).
 


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!