SAP BBP_CM_API_METH_SAVE Function Module for Interface to Save Methodology

Search SAP Function Modules

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

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

Function BBP_CM_API_METH_SAVE 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_METH_SAVE'"Interface to Save Methodology
  EXPORTING
   IS_METH_HEAD =  "UI-Interface - Structure for Methodology Data

 IMPORTING
   ES_METH_HEAD =  "UI-Interface - Structure for Methodology Data

TABLES
*  IT_METH_STEP =  "UI Fields - Methodology Step
*  ET_METH_TASKS =  "Structure for Task Instance
*  ET_METH_TASK_ATTRIBS =  "Structure for Task Attributes
   ET_MESSAGES =  "Return Parameter

.

IMPORTING Parameters details for BBP_CM_API_METH_SAVE

IS_METH_HEAD - UI-Interface - Structure for Methodology Data

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

EXPORTING Parameters details for BBP_CM_API_METH_SAVE

ES_METH_HEAD - UI-Interface - Structure for Methodology Data

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

TABLES Parameters details for BBP_CM_API_METH_SAVE

IT_METH_STEP - UI Fields - Methodology Step

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

ET_METH_TASKS - Structure for Task Instance

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

ET_METH_TASK_ATTRIBS - Structure for Task Attributes

Data type: BBPS_CM_TASKATT_D
Optional: Yes
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_METH_SAVE 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 BBP_CM_API_METH_SAVE

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