SAP BAPI_INVRADVDOC_CREATE Function Module for BAPI IS-U-EDM: Create Invoice or Payment Advice Note Document
BAPI_INVRADVDOC_CREATE is a standard bapi invradvdoc create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI IS-U-EDM: Create Invoice or Payment Advice Note Document processing and below is the pattern details for this FM, 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 invradvdoc create FM, simply by entering the name BAPI_INVRADVDOC_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EE_INVOICE_BAPI
Program Name: SAPLEE_INVOICE_BAPI
Main Program: SAPLEE_INVOICE_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_INVRADVDOC_CREATE 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_INVRADVDOC_CREATE'"BAPI IS-U-EDM: Create Invoice or Payment Advice Note Document.
EXPORTING
CONTROLDATA = "BAPI Structure: Control Data of BAPI Control
INVREMADVHEAD = "BAPI Structure: Bill Header
IMPORTING
INV_HEAD = "Bill Header
INV_DOC_TAB = "Table Category: Bill Document
INV_LINE_TAB_I = "Table Category: Bill Line with Information
INV_LINE_TAB_B = "Table Category: Bill Line with Posting Information
INV_LINE_TAB_A = "Table Category: Payment Advice Note Lines
TABLES
INVREMADVDOCS = "BAPI Structure: Bill Document
INVREMADVLINES = "BAPI Structure: Bill Line Item
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_INVRADVDOC_CREATE
CONTROLDATA - BAPI Structure: Control Data of BAPI Control
Data type: BAPI_INV_CONTROLOptional: No
Call by Reference: No ( called with pass by value option)
INVREMADVHEAD - BAPI Structure: Bill Header
Data type: BAPI_INV_HEADOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_INVRADVDOC_CREATE
INV_HEAD - Bill Header
Data type: TINV_INV_HEADOptional: No
Call by Reference: No ( called with pass by value option)
INV_DOC_TAB - Table Category: Bill Document
Data type: TTINV_INV_DOCOptional: No
Call by Reference: No ( called with pass by value option)
INV_LINE_TAB_I - Table Category: Bill Line with Information
Data type: TTINV_INV_LINE_IOptional: No
Call by Reference: No ( called with pass by value option)
INV_LINE_TAB_B - Table Category: Bill Line with Posting Information
Data type: TTINV_INV_LINE_BOptional: No
Call by Reference: No ( called with pass by value option)
INV_LINE_TAB_A - Table Category: Payment Advice Note Lines
Data type: TTINV_INV_LINE_AOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_INVRADVDOC_CREATE
INVREMADVDOCS - BAPI Structure: Bill Document
Data type: BAPI_INV_DOCOptional: No
Call by Reference: Yes
INVREMADVLINES - BAPI Structure: Bill Line Item
Data type: BAPI_INV_LINEOptional: No
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_INVRADVDOC_CREATE 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_inv_head | TYPE TINV_INV_HEAD, " | |||
| lv_controldata | TYPE BAPI_INV_CONTROL, " | |||
| lt_invremadvdocs | TYPE STANDARD TABLE OF BAPI_INV_DOC, " | |||
| lv_inv_doc_tab | TYPE TTINV_INV_DOC, " | |||
| lv_invremadvhead | TYPE BAPI_INV_HEAD, " | |||
| lt_invremadvlines | TYPE STANDARD TABLE OF BAPI_INV_LINE, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_inv_line_tab_i | TYPE TTINV_INV_LINE_I, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_inv_line_tab_b | TYPE TTINV_INV_LINE_B, " | |||
| lv_inv_line_tab_a | TYPE TTINV_INV_LINE_A. " |
|   CALL FUNCTION 'BAPI_INVRADVDOC_CREATE' "BAPI IS-U-EDM: Create Invoice or Payment Advice Note Document |
| EXPORTING | ||
| CONTROLDATA | = lv_controldata | |
| INVREMADVHEAD | = lv_invremadvhead | |
| IMPORTING | ||
| INV_HEAD | = lv_inv_head | |
| INV_DOC_TAB | = lv_inv_doc_tab | |
| INV_LINE_TAB_I | = lv_inv_line_tab_i | |
| INV_LINE_TAB_B | = lv_inv_line_tab_b | |
| INV_LINE_TAB_A | = lv_inv_line_tab_a | |
| TABLES | ||
| INVREMADVDOCS | = lt_invremadvdocs | |
| INVREMADVLINES | = lt_invremadvlines | |
| EXTENSIONIN | = lt_extensionin | |
| RETURN | = lt_return | |
| . " BAPI_INVRADVDOC_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_INVRADVDOC_CREATE
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.Search for further information about these or an SAP related objects