SAP BBP_CM_API_INIT_CHANGE_STATUS Function Module for API to change initiative status









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

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



Function BBP_CM_API_INIT_CHANGE_STATUS 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_INIT_CHANGE_STATUS'"API to change initiative status
EXPORTING
* IV_INIT_GUID = "Unique Identifier - Category Management
* IV_INIT_ID = "Initiaitve Id
IV_NEW_STATUS = "State of the Object - Category management

IMPORTING
ES_INIT_HEAD = "UI-Interface - Display Structure initiatve data

TABLES
ET_MESSAGES = "Return Parameter
.



IMPORTING Parameters details for BBP_CM_API_INIT_CHANGE_STATUS

IV_INIT_GUID - Unique Identifier - Category Management

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

IV_INIT_ID - Initiaitve Id

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

IV_NEW_STATUS - State of the Object - Category management

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

EXPORTING Parameters details for BBP_CM_API_INIT_CHANGE_STATUS

ES_INIT_HEAD - UI-Interface - Display Structure initiatve data

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

TABLES Parameters details for BBP_CM_API_INIT_CHANGE_STATUS

ET_MESSAGES - Return Parameter

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

Copy and paste ABAP code example for BBP_CM_API_INIT_CHANGE_STATUS 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:
lt_et_messages  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_es_init_head  TYPE BBPS_CM_INITIATIVE_D, "   
lv_iv_init_guid  TYPE BBP_CM_GUID_D, "   
lv_iv_init_id  TYPE BBP_CM_INIT_ID, "   
lv_iv_new_status  TYPE BBP_CM_OBJ_STATE. "   

  CALL FUNCTION 'BBP_CM_API_INIT_CHANGE_STATUS'  "API to change initiative status
    EXPORTING
         IV_INIT_GUID = lv_iv_init_guid
         IV_INIT_ID = lv_iv_init_id
         IV_NEW_STATUS = lv_iv_new_status
    IMPORTING
         ES_INIT_HEAD = lv_es_init_head
    TABLES
         ET_MESSAGES = lt_et_messages
. " BBP_CM_API_INIT_CHANGE_STATUS




ABAP code using 7.40 inline data declarations to call FM BBP_CM_API_INIT_CHANGE_STATUS

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



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!