BILL_DOC_INBOUND_ICV SAP Function module - Inbound Adapter for Intercompany Payables

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

Associated Function Group: CRM_BILL_DOC
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM BILL_DOC_INBOUND_ICV - BILL DOC INBOUND ICV

CALL FUNCTION 'BILL_DOC_INBOUND_ICV' "Inbound Adapter for Intercompany Payables
  EXPORTING
    i_bapicrmuh1 =              " bapicrmuh1    Bapi-Struktur Upload Kopfdaten
  TABLES
    t_bapimtcs =                " bapimtcs      Middleware Transaktionenbehälterstruktur
    t_bapiparex =               " bapiparex     Bezugsstruktur für BAPI-Parameter ExtensionIn / ExtensionOut
    t_bapicrmsfk =              " bapicrmsfk    Input Tabellenstruktur für SFA Schlüssel in Proxy Funkt. Mod
  EXCEPTIONS
    EVENT_NOT_CALLED = 1        "
    .  "  BILL_DOC_INBOUND_ICV

ABAP code example for Function Module BILL_DOC_INBOUND_ICV

The ABAP code below is a full code listing to execute function module BILL_DOC_INBOUND_ICV 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:
it_t_bapimtcs  
 
 TYPE STANDARD TABLE OF BAPIMTCS,"TABLES PARAM
wa_t_bapimtcs
 
 LIKE LINE OF it_t_bapimtcs
,
it_t_bapiparex  
 
 TYPE STANDARD TABLE OF BAPIPAREX,"TABLES PARAM
wa_t_bapiparex
 
 LIKE LINE OF it_t_bapiparex
,
it_t_bapicrmsfk  
 
 TYPE STANDARD TABLE OF BAPICRMSFK,"TABLES PARAM
wa_t_bapicrmsfk
 
 LIKE LINE OF it_t_bapicrmsfk
.


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

"populate fields of struture and append to itab
append wa_t_bapimtcs to it_t_bapimtcs.
 

"populate fields of struture and append to itab
append wa_t_bapiparex to it_t_bapiparex.
 

"populate fields of struture and append to itab
append wa_t_bapicrmsfk to it_t_bapicrmsfk.
.

CALL FUNCTION 'BILL_DOC_INBOUND_ICV'
  EXPORTING
    i_bapicrmuh1 =               ld_i_bapicrmuh1
  TABLES
    t_bapimtcs =                 it_t_bapimtcs
    t_bapiparex =                it_t_bapiparex
    t_bapicrmsfk =               it_t_bapicrmsfk
  EXCEPTIONS
    EVENT_NOT_CALLED =           1
    .  "  BILL_DOC_INBOUND_ICV

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_i_bapicrmuh1
 
 TYPE BAPICRMUH1 ,
it_t_bapimtcs
 
 TYPE STANDARD TABLE OF BAPIMTCS ,
wa_t_bapimtcs
 
 LIKE LINE OF it_t_bapimtcs,
it_t_bapiparex
 
 TYPE STANDARD TABLE OF BAPIPAREX ,
wa_t_bapiparex
 
 LIKE LINE OF it_t_bapiparex,
it_t_bapicrmsfk
 
 TYPE STANDARD TABLE OF BAPICRMSFK ,
wa_t_bapicrmsfk
 
 LIKE LINE OF it_t_bapicrmsfk.


ld_i_bapicrmuh1 = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_bapimtcs to it_t_bapimtcs. 

"populate fields of struture and append to itab
append wa_t_bapiparex to it_t_bapiparex. 

"populate fields of struture and append to itab
append wa_t_bapicrmsfk to it_t_bapicrmsfk.