SAP BAPI_EXTORDER_CH_CHANGE Function Module for









BAPI_EXTORDER_CH_CHANGE is a standard bapi extorder ch change 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 bapi extorder ch change FM, simply by entering the name BAPI_EXTORDER_CH_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: 1312CH
Program Name: SAPL1312CH
Main Program: SAPL1312CH
Appliation area: N
Release date: 13-May-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_EXTORDER_CH_CHANGE 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 'BAPI_EXTORDER_CH_CHANGE'"
EXPORTING
CLIENT = "
INSTITUTION = "
EXTORDER_NO = "
EXTORDER_HEADERX = "
* EXTORDER_ADDRESS_DATAX = "
* TESTRUN = ' ' "

IMPORTING
WORST_RETURNED_MSGTY = "

TABLES
* EXTORDER_POSITION = "
* EXTORDER_LTEXT = "
* RETURN = "
.



IMPORTING Parameters details for BAPI_EXTORDER_CH_CHANGE

CLIENT -

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

INSTITUTION -

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

EXTORDER_NO -

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

EXTORDER_HEADERX -

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

EXTORDER_ADDRESS_DATAX -

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

TESTRUN -

Data type: BAPINALL-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_EXTORDER_CH_CHANGE

WORST_RETURNED_MSGTY -

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

TABLES Parameters details for BAPI_EXTORDER_CH_CHANGE

EXTORDER_POSITION -

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

EXTORDER_LTEXT -

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

RETURN -

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

Copy and paste ABAP code example for BAPI_EXTORDER_CH_CHANGE 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_client  TYPE BAPINALL-CLIENT, "   
lt_extorder_position  TYPE STANDARD TABLE OF BAPI1312CHVBAPX, "   
lv_worst_returned_msgty  TYPE BAPINALL-WORSTRETMSG, "   
lv_institution  TYPE BAPINALL-INSTITUTION, "   
lt_extorder_ltext  TYPE STANDARD TABLE OF BAPI1312CHLTEXT, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_extorder_no  TYPE BAPIVBELN-VBELN, "   
lv_extorder_headerx  TYPE BAPI1312CHVBAKX, "   
lv_extorder_address_datax  TYPE BAPI1312CHPATDRIX, "   
lv_testrun  TYPE BAPINALL-TESTRUN. "   SPACE

  CALL FUNCTION 'BAPI_EXTORDER_CH_CHANGE'  "
    EXPORTING
         CLIENT = lv_client
         INSTITUTION = lv_institution
         EXTORDER_NO = lv_extorder_no
         EXTORDER_HEADERX = lv_extorder_headerx
         EXTORDER_ADDRESS_DATAX = lv_extorder_address_datax
         TESTRUN = lv_testrun
    IMPORTING
         WORST_RETURNED_MSGTY = lv_worst_returned_msgty
    TABLES
         EXTORDER_POSITION = lt_extorder_position
         EXTORDER_LTEXT = lt_extorder_ltext
         RETURN = lt_return
. " BAPI_EXTORDER_CH_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_EXTORDER_CH_CHANGE

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 CLIENT FROM BAPINALL INTO @DATA(ld_client).
 
 
"SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty).
 
"SELECT single INSTITUTION FROM BAPINALL INTO @DATA(ld_institution).
 
 
 
"SELECT single VBELN FROM BAPIVBELN INTO @DATA(ld_extorder_no).
 
 
 
"SELECT single TESTRUN FROM BAPINALL INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 


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!