SAP FB_CHANGE_DEVC Function Module for

Search SAP Function Modules

FB_CHANGE_DEVC is a standard fb change devc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fb change devc FM, simply by entering the name FB_CHANGE_DEVC into the relevant SAP transaction such as SE37 or SE38.

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

Function FB_CHANGE_DEVC 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 'FB_CHANGE_DEVC'"
  EXPORTING
   I_FORMNAME =  "Smart Forms: Form Name
*  I_WITH_DIALOG = 'X' "Smart Forms: General flag

 IMPORTING
   O_FORMNAME =  "Smart Forms: Form Name

EXCEPTIONS
   NO_NAME = 1    NO_FORM = 2    CANCELED = 3    FAILED = 4    ILLEGAL_LANGUAGE = 5    ILLEGAL_FORMTYPE = 6    NO_ACCESS_PERMISSION = 7    ENQUEUED = 8 

.

IMPORTING Parameters details for FB_CHANGE_DEVC

I_FORMNAME - Smart Forms: Form Name

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

I_WITH_DIALOG - Smart Forms: General flag

Data type: TDSFFLAG
Default: 'X'
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FB_CHANGE_DEVC

O_FORMNAME - Smart Forms: Form Name

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

EXCEPTIONS details

NO_NAME -

Data type:
Optional: No
Call by Reference: Yes

NO_FORM -

Data type:
Optional: No
Call by Reference: Yes

CANCELED -

Data type:
Optional: No
Call by Reference: Yes

FAILED - No change is possible

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_LANGUAGE -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_FORMTYPE -

Data type:
Optional: No
Call by Reference: Yes

NO_ACCESS_PERMISSION -

Data type:
Optional: No
Call by Reference: Yes

ENQUEUED -

Data type:
Optional: No
Call by Reference: Yes

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

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