SAP Function Modules

comments icon Comments

CO_XT_ORDER_CHANGE SAP Function module







CO_XT_ORDER_CHANGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CO_XT_ORDER_CHANGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: COXT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CO_XT_ORDER_CHANGE - CO XT ORDER CHANGE 





CALL FUNCTION 'CO_XT_ORDER_CHANGE' "
  EXPORTING
    i_order_key =               " coxt_ord_key
    i_priority =                " coxt_priority
    i_priorityx =               " coxt_priorityx
    is_mi_total_quantity =      " coxt_s_quantity
    is_mi_total_quantityx =     " coxt_s_quantityx
    is_mi_yield =               " coxt_s_quantity
    is_mi_yieldx =              " coxt_s_quantityx
*   is_mi_scheduled_dates =     " coxt_s_date_pair
*   is_mi_scheduled_datesx =    " coxt_s_date_pairx
*   is_basic_dates =            " coxt_s_date_pair
*   is_basic_datesx =           " coxt_s_date_pairx
*   is_explosion_date =         " coxt_s_date
*   is_explosion_datex =        " coxt_s_datex
*   i_production_version =      " coxt_prod_version
*   i_production_versionx =     " coxt_prod_versionx
*   is_bom =                    " coxt_s_bom
*   is_bomx =                   " coxt_s_bomx
*   is_routing =                " coxt_s_routing
*   is_routingx =               " coxt_s_routingx
*   i_explode_new =             " c
*   i_explode_newx =            " c
*   i_storage_location =        " coxt_storage_location
*   i_storage_locationx =       " cif_r3ordx-verid
  IMPORTING
    es_bapireturn =             " coxt_bapireturn
    e_error_occurred =          " c
    e_order_category =          " aufk-autyp
    e_new_explosion =           " c
    e_flg_abg =                 " c
    e_flg_loe =                 " c
    e_flg_lvm =                 " c
    e_flg_spe =                 " c
    e_flg_tab =                 " c
  TABLES
    ct_return =                 " coxt_t_bapireturn
    .  "  CO_XT_ORDER_CHANGE

ABAP code example for Function Module CO_XT_ORDER_CHANGE





The ABAP code below is a full code listing to execute function module CO_XT_ORDER_CHANGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_es_bapireturn    TYPE COXT_BAPIRETURN
,
ld_e_error_occurred    TYPE C
,
ld_e_order_category    TYPE AUFK-AUTYP
,
ld_e_new_explosion    TYPE C
,
ld_e_flg_abg    TYPE C
,
ld_e_flg_loe    TYPE C
,
ld_e_flg_lvm    TYPE C
,
ld_e_flg_spe    TYPE C
,
ld_e_flg_tab    TYPE C
,
it_ct_return    TYPE STANDARD TABLE OF COXT_T_BAPIRETURN,"TABLES PARAM
wa_ct_return  LIKE LINE OF it_ct_return
.




DATA(ld_i_order_key) = 'Check type of data required'.

DATA(ld_i_priority) = 'Check type of data required'.

DATA(ld_i_priorityx) = 'Check type of data required'.

DATA(ld_is_mi_total_quantity) = 'Check type of data required'.

DATA(ld_is_mi_total_quantityx) = 'Check type of data required'.

DATA(ld_is_mi_yield) = 'Check type of data required'.

DATA(ld_is_mi_yieldx) = 'Check type of data required'.

DATA(ld_is_mi_scheduled_dates) = 'Check type of data required'.

DATA(ld_is_mi_scheduled_datesx) = 'Check type of data required'.

DATA(ld_is_basic_dates) = 'Check type of data required'.

DATA(ld_is_basic_datesx) = 'Check type of data required'.

DATA(ld_is_explosion_date) = 'Check type of data required'.

DATA(ld_is_explosion_datex) = 'Check type of data required'.

DATA(ld_i_production_version) = 'Check type of data required'.

DATA(ld_i_production_versionx) = 'Check type of data required'.

DATA(ld_is_bom) = 'Check type of data required'.

DATA(ld_is_bomx) = 'Check type of data required'.

DATA(ld_is_routing) = 'Check type of data required'.

DATA(ld_is_routingx) = 'Check type of data required'.

DATA(ld_i_explode_new) = 'Check type of data required'.

DATA(ld_i_explode_newx) = 'Check type of data required'.

DATA(ld_i_storage_location) = 'Check type of data required'.


DATA(ld_i_storage_locationx) = some text here
 

"populate fields of struture and append to itab
append wa_ct_return to it_ct_return.
.

CALL FUNCTION 'CO_XT_ORDER_CHANGE'
  EXPORTING
    i_order_key =                ld_i_order_key
    i_priority =                 ld_i_priority
    i_priorityx =                ld_i_priorityx
    is_mi_total_quantity =       ld_is_mi_total_quantity
    is_mi_total_quantityx =      ld_is_mi_total_quantityx
    is_mi_yield =                ld_is_mi_yield
    is_mi_yieldx =               ld_is_mi_yieldx
*   is_mi_scheduled_dates =      ld_is_mi_scheduled_dates
*   is_mi_scheduled_datesx =     ld_is_mi_scheduled_datesx
*   is_basic_dates =             ld_is_basic_dates
*   is_basic_datesx =            ld_is_basic_datesx
*   is_explosion_date =          ld_is_explosion_date
*   is_explosion_datex =         ld_is_explosion_datex
*   i_production_version =       ld_i_production_version
*   i_production_versionx =      ld_i_production_versionx
*   is_bom =                     ld_is_bom
*   is_bomx =                    ld_is_bomx
*   is_routing =                 ld_is_routing
*   is_routingx =                ld_is_routingx
*   i_explode_new =              ld_i_explode_new
*   i_explode_newx =             ld_i_explode_newx
*   i_storage_location =         ld_i_storage_location
*   i_storage_locationx =        ld_i_storage_locationx
  IMPORTING
    es_bapireturn =              ld_es_bapireturn
    e_error_occurred =           ld_e_error_occurred
    e_order_category =           ld_e_order_category
    e_new_explosion =            ld_e_new_explosion
    e_flg_abg =                  ld_e_flg_abg
    e_flg_loe =                  ld_e_flg_loe
    e_flg_lvm =                  ld_e_flg_lvm
    e_flg_spe =                  ld_e_flg_spe
    e_flg_tab =                  ld_e_flg_tab
  TABLES
    ct_return =                  it_ct_return
    .  "  CO_XT_ORDER_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_es_bapireturn  TYPE COXT_BAPIRETURN ,
it_ct_return  TYPE STANDARD TABLE OF COXT_T_BAPIRETURN ,
wa_ct_return  LIKE LINE OF it_ct_return,
ld_i_order_key  TYPE COXT_ORD_KEY ,
ld_e_error_occurred  TYPE C ,
ld_i_priority  TYPE COXT_PRIORITY ,
ld_e_order_category  TYPE AUFK-AUTYP ,
ld_i_priorityx  TYPE COXT_PRIORITYX ,
ld_e_new_explosion  TYPE C ,
ld_is_mi_total_quantity  TYPE COXT_S_QUANTITY ,
ld_e_flg_abg  TYPE C ,
ld_is_mi_total_quantityx  TYPE COXT_S_QUANTITYX ,
ld_e_flg_loe  TYPE C ,
ld_is_mi_yield  TYPE COXT_S_QUANTITY ,
ld_e_flg_lvm  TYPE C ,
ld_is_mi_yieldx  TYPE COXT_S_QUANTITYX ,
ld_is_mi_scheduled_dates  TYPE COXT_S_DATE_PAIR ,
ld_e_flg_spe  TYPE C ,
ld_e_flg_tab  TYPE C ,
ld_is_mi_scheduled_datesx  TYPE COXT_S_DATE_PAIRX ,
ld_is_basic_dates  TYPE COXT_S_DATE_PAIR ,
ld_is_basic_datesx  TYPE COXT_S_DATE_PAIRX ,
ld_is_explosion_date  TYPE COXT_S_DATE ,
ld_is_explosion_datex  TYPE COXT_S_DATEX ,
ld_i_production_version  TYPE COXT_PROD_VERSION ,
ld_i_production_versionx  TYPE COXT_PROD_VERSIONX ,
ld_is_bom  TYPE COXT_S_BOM ,
ld_is_bomx  TYPE COXT_S_BOMX ,
ld_is_routing  TYPE COXT_S_ROUTING ,
ld_is_routingx  TYPE COXT_S_ROUTINGX ,
ld_i_explode_new  TYPE C ,
ld_i_explode_newx  TYPE C ,
ld_i_storage_location  TYPE COXT_STORAGE_LOCATION ,
ld_i_storage_locationx  TYPE CIF_R3ORDX-VERID .



 

"populate fields of struture and append to itab
append wa_ct_return to it_ct_return.
ld_i_order_key = 'Check type of data required'.
ld_i_priority = 'Check type of data required'.
ld_i_priorityx = 'Check type of data required'.
ld_is_mi_total_quantity = 'Check type of data required'.
ld_is_mi_total_quantityx = 'Check type of data required'.
ld_is_mi_yield = 'Check type of data required'.
ld_is_mi_yieldx = 'Check type of data required'.
ld_is_mi_scheduled_dates = 'Check type of data required'.
ld_is_mi_scheduled_datesx = 'Check type of data required'.
ld_is_basic_dates = 'Check type of data required'.
ld_is_basic_datesx = 'Check type of data required'.
ld_is_explosion_date = 'Check type of data required'.
ld_is_explosion_datex = 'Check type of data required'.
ld_i_production_version = 'Check type of data required'.
ld_i_production_versionx = 'Check type of data required'.
ld_is_bom = 'Check type of data required'.
ld_is_bomx = 'Check type of data required'.
ld_is_routing = 'Check type of data required'.
ld_is_routingx = 'Check type of data required'.
ld_i_explode_new = 'Check type of data required'.
ld_i_explode_newx = 'Check type of data required'.
ld_i_storage_location = 'Check type of data required'.

ld_i_storage_locationx = some text here

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CO_XT_ORDER_CHANGE or its description.


   
 

CO_XT_ORDER_CHANGE - 
CO_XT_OPERATION_FIND - 
CO_XT_OPERATION_CHANGE - 
CO_XT_OPERATIONS_GET_ALL - 
CO_XT_OPERATIONS_DELETE - 
CO_XT_ITEM_FIND -