BAPI_NETWORK_CONF_GETDETAIL SAP Function module - GETDETAIL for BOR Object Network, Subobject Confirmation Method

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

Associated Function Group: CNIF_CONF
Released Date: 13.11.2001
Processing type: Remote-Enabled

Pattern for FM BAPI_NETWORK_CONF_GETDETAIL - BAPI NETWORK CONF GETDETAIL

CALL FUNCTION 'BAPI_NETWORK_CONF_GETDETAIL' "GETDETAIL for BOR Object Network, Subobject Confirmation Method
  EXPORTING
    number =                    " bapi_network_list-network  Network Number
    conf_key =                  " bapi_network_conf_key2  BAPI Structure (Key Fields) for Confirmation
  IMPORTING
    return =                    " bapiret2      Return Parameter
    conf_detail =               " bapi_network_conf_getdet  BAPI Structure for Confirmation: GetDetail
* TABLES
*   e_goodsmovements =          " bapi2017_gm_item_show  BAPI Communication Structure: Display Mat. Document Item
*   e_failedgmoves =            " bapi_coru_fgm  Incorrect and Intended Goods Movements for Confirmation
    .  "  BAPI_NETWORK_CONF_GETDETAIL

ABAP code example for Function Module BAPI_NETWORK_CONF_GETDETAIL

The ABAP code below is a full code listing to execute function module BAPI_NETWORK_CONF_GETDETAIL 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_return  
 
 TYPE BAPIRET2
,
ld_conf_detail  
 
 TYPE BAPI_NETWORK_CONF_GETDET
,
it_e_goodsmovements  
 
 TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_SHOW,"TABLES PARAM
wa_e_goodsmovements
 
 LIKE LINE OF it_e_goodsmovements
,
it_e_failedgmoves  
 
 TYPE STANDARD TABLE OF BAPI_CORU_FGM,"TABLES PARAM
wa_e_failedgmoves
 
 LIKE LINE OF it_e_failedgmoves
.



DATA(ld_number) = some text here

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

"populate fields of struture and append to itab
append wa_e_goodsmovements to it_e_goodsmovements.
 

"populate fields of struture and append to itab
append wa_e_failedgmoves to it_e_failedgmoves.
.

CALL FUNCTION 'BAPI_NETWORK_CONF_GETDETAIL'
  EXPORTING
    number =                     ld_number
    conf_key =                   ld_conf_key
  IMPORTING
    return =                     ld_return
    conf_detail =                ld_conf_detail
* TABLES
*   e_goodsmovements =           it_e_goodsmovements
*   e_failedgmoves =             it_e_failedgmoves
    .  "  BAPI_NETWORK_CONF_GETDETAIL

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_return
 
 TYPE BAPIRET2 ,
ld_number
 
 TYPE BAPI_NETWORK_LIST-NETWORK ,
it_e_goodsmovements
 
 TYPE STANDARD TABLE OF BAPI2017_GM_ITEM_SHOW ,
wa_e_goodsmovements
 
 LIKE LINE OF it_e_goodsmovements,
ld_conf_detail
 
 TYPE BAPI_NETWORK_CONF_GETDET ,
ld_conf_key
 
 TYPE BAPI_NETWORK_CONF_KEY2 ,
it_e_failedgmoves
 
 TYPE STANDARD TABLE OF BAPI_CORU_FGM ,
wa_e_failedgmoves
 
 LIKE LINE OF it_e_failedgmoves.



ld_number = some text here 

"populate fields of struture and append to itab
append wa_e_goodsmovements to it_e_goodsmovements.
ld_conf_key = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e_failedgmoves to it_e_failedgmoves.

SAP Documentation for FM BAPI_NETWORK_CONF_GETDETAIL