SAP Function Modules

FCOM_INTORDER_GET SAP Function module







FCOM_INTORDER_GET 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 FCOM_INTORDER_GET into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FCOM_INTERNAL_ORDER
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM FCOM_INTORDER_GET - FCOM INTORDER GET





CALL FUNCTION 'FCOM_INTORDER_GET' "
* EXPORTING
*   id_objectid =               " string
*   id_intorder =               " aufnr
*   id_controlling_area =       " kokrs
*   id_date = SY-DATUM          " datum
*   ib_authority_check = 'X'    " boolean
  IMPORTING
    es_iodata =                 " coas
    es_ioflags =                " kauf
    es_iotext =                 " fcom_md_addtexte
    es_return =                 " bapiret2
    eb_userfields =             " boolean
* TABLES
*   et_system_status =          " bapi2075_3
*   et_user_status =            " bapi2075_4
*   et_allowed_actions =        " bapi2075_5
*   et_io_longtext =            " fcom_s_text
    .  "  FCOM_INTORDER_GET

ABAP code example for Function Module FCOM_INTORDER_GET





The ABAP code below is a full code listing to execute function module FCOM_INTORDER_GET 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_iodata  TYPE COAS ,
ld_es_ioflags  TYPE KAUF ,
ld_es_iotext  TYPE FCOM_MD_ADDTEXTE ,
ld_es_return  TYPE BAPIRET2 ,
ld_eb_userfields  TYPE BOOLEAN ,
it_et_system_status  TYPE STANDARD TABLE OF BAPI2075_3,"TABLES PARAM
wa_et_system_status  LIKE LINE OF it_et_system_status ,
it_et_user_status  TYPE STANDARD TABLE OF BAPI2075_4,"TABLES PARAM
wa_et_user_status  LIKE LINE OF it_et_user_status ,
it_et_allowed_actions  TYPE STANDARD TABLE OF BAPI2075_5,"TABLES PARAM
wa_et_allowed_actions  LIKE LINE OF it_et_allowed_actions ,
it_et_io_longtext  TYPE STANDARD TABLE OF FCOM_S_TEXT,"TABLES PARAM
wa_et_io_longtext  LIKE LINE OF it_et_io_longtext .

DATA(ld_id_objectid) = 'Check type of data required'.
DATA(ld_id_intorder) = 'Check type of data required'.
DATA(ld_id_controlling_area) = 'Check type of data required'.
DATA(ld_id_date) = 'Check type of data required'.
DATA(ld_ib_authority_check) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_system_status to it_et_system_status.

"populate fields of struture and append to itab
append wa_et_user_status to it_et_user_status.

"populate fields of struture and append to itab
append wa_et_allowed_actions to it_et_allowed_actions.

"populate fields of struture and append to itab
append wa_et_io_longtext to it_et_io_longtext. . CALL FUNCTION 'FCOM_INTORDER_GET' * EXPORTING * id_objectid = ld_id_objectid * id_intorder = ld_id_intorder * id_controlling_area = ld_id_controlling_area * id_date = ld_id_date * ib_authority_check = ld_ib_authority_check IMPORTING es_iodata = ld_es_iodata es_ioflags = ld_es_ioflags es_iotext = ld_es_iotext es_return = ld_es_return eb_userfields = ld_eb_userfields * TABLES * et_system_status = it_et_system_status * et_user_status = it_et_user_status * et_allowed_actions = it_et_allowed_actions * et_io_longtext = it_et_io_longtext . " FCOM_INTORDER_GET
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_iodata  TYPE COAS ,
ld_id_objectid  TYPE STRING ,
it_et_system_status  TYPE STANDARD TABLE OF BAPI2075_3 ,
wa_et_system_status  LIKE LINE OF it_et_system_status,
ld_es_ioflags  TYPE KAUF ,
ld_id_intorder  TYPE AUFNR ,
it_et_user_status  TYPE STANDARD TABLE OF BAPI2075_4 ,
wa_et_user_status  LIKE LINE OF it_et_user_status,
ld_es_iotext  TYPE FCOM_MD_ADDTEXTE ,
ld_id_controlling_area  TYPE KOKRS ,
it_et_allowed_actions  TYPE STANDARD TABLE OF BAPI2075_5 ,
wa_et_allowed_actions  LIKE LINE OF it_et_allowed_actions,
ld_es_return  TYPE BAPIRET2 ,
ld_id_date  TYPE DATUM ,
it_et_io_longtext  TYPE STANDARD TABLE OF FCOM_S_TEXT ,
wa_et_io_longtext  LIKE LINE OF it_et_io_longtext,
ld_eb_userfields  TYPE BOOLEAN ,
ld_ib_authority_check  TYPE BOOLEAN .

ld_id_objectid = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_system_status to it_et_system_status.
ld_id_intorder = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_user_status to it_et_user_status.
ld_id_controlling_area = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_allowed_actions to it_et_allowed_actions.
ld_id_date = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_io_longtext to it_et_io_longtext.
ld_ib_authority_check = 'Check type of data required'.

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 FCOM_INTORDER_GET or its description.