SAP BAPI_EXGAGRMNT_CREATE Function Module for BAPI for Creating Exchange Agreement Header
BAPI_EXGAGRMNT_CREATE is a standard bapi exgagrmnt 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 for Creating Exchange Agreement Header 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 exgagrmnt create FM, simply by entering the name BAPI_EXGAGRMNT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIA_IF_EXGAGRMNT
Program Name: SAPLOIA_IF_EXGAGRMNT
Main Program: SAPLOIA_IF_EXGAGRMNT
Appliation area:
Release date: 26-Oct-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_EXGAGRMNT_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_EXGAGRMNT_CREATE'"BAPI for Creating Exchange Agreement Header.
EXPORTING
EXCHANGE_TYPE = "Exchange type
EXCHANGE_PARTNER = "Exchange partner (vendor number)
* EXTERNAL_EXCHANGE_NUMBER = "Exchange agreement number
* PARTNER_REFERENCE_NUMBER = "Exchange partner reference code
* EXCHANGE_HEADER_IN = "Exchange header import data for BAPI
IMPORTING
EXCHANGE_NUMBER = "Exchange agreement number
EXCHANGE_HEADER_OUT = "Exchange agreement header export data
TABLES
* EXCHANGE_HEADER_TEXT = "Exchange header text data for BAPI
* RETURN = "Return parameter
* EXTENSIONIN = "Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
* EXTENSIONOUT = "Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
IMPORTING Parameters details for BAPI_EXGAGRMNT_CREATE
EXCHANGE_TYPE - Exchange type
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXCHANGE_PARTNER - Exchange partner (vendor number)
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
EXTERNAL_EXCHANGE_NUMBER - Exchange agreement number
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_NUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
PARTNER_REFERENCE_NUMBER - Exchange partner reference code
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUT-PARTNER_REF_NUMBEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXCHANGE_HEADER_IN - Exchange header import data for BAPI
Data type: BAPI_OIA_EXGAGRMNT_HDR_INOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_EXGAGRMNT_CREATE
EXCHANGE_NUMBER - Exchange agreement number
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
EXCHANGE_HEADER_OUT - Exchange agreement header export data
Data type: BAPI_OIA_EXGAGRMNT_HDR_OUTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_EXGAGRMNT_CREATE
EXCHANGE_HEADER_TEXT - Exchange header text data for BAPI
Data type: BAPI_OIA_EXGAGRMNT_HDR_TXTOptional: Yes
Call by Reference: Yes
RETURN - Return parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXTENSIONIN - Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
EXTENSIONOUT - Ref. structure for BAPI parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_EXGAGRMNT_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_exchange_type | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_TYPE, " | |||
| lv_exchange_number | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_NUMBER, " | |||
| lt_exchange_header_text | TYPE STANDARD TABLE OF BAPI_OIA_EXGAGRMNT_HDR_TXT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_exchange_partner | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_PARTNER, " | |||
| lv_exchange_header_out | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_external_exchange_number | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT-EXCHANGE_NUMBER, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_partner_reference_number | TYPE BAPI_OIA_EXGAGRMNT_HDR_OUT-PARTNER_REF_NUMBER, " | |||
| lv_exchange_header_in | TYPE BAPI_OIA_EXGAGRMNT_HDR_IN. " |
|   CALL FUNCTION 'BAPI_EXGAGRMNT_CREATE' "BAPI for Creating Exchange Agreement Header |
| EXPORTING | ||
| EXCHANGE_TYPE | = lv_exchange_type | |
| EXCHANGE_PARTNER | = lv_exchange_partner | |
| EXTERNAL_EXCHANGE_NUMBER | = lv_external_exchange_number | |
| PARTNER_REFERENCE_NUMBER | = lv_partner_reference_number | |
| EXCHANGE_HEADER_IN | = lv_exchange_header_in | |
| IMPORTING | ||
| EXCHANGE_NUMBER | = lv_exchange_number | |
| EXCHANGE_HEADER_OUT | = lv_exchange_header_out | |
| TABLES | ||
| EXCHANGE_HEADER_TEXT | = lt_exchange_header_text | |
| RETURN | = lt_return | |
| EXTENSIONIN | = lt_extensionin | |
| EXTENSIONOUT | = lt_extensionout | |
| . " BAPI_EXGAGRMNT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_EXGAGRMNT_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.| "SELECT single EXCHANGE_TYPE FROM BAPI_OIA_EXGAGRMNT_HDR_OUT INTO @DATA(ld_exchange_type). | ||||
| "SELECT single EXCHANGE_NUMBER FROM BAPI_OIA_EXGAGRMNT_HDR_OUT INTO @DATA(ld_exchange_number). | ||||
| "SELECT single EXCHANGE_PARTNER FROM BAPI_OIA_EXGAGRMNT_HDR_OUT INTO @DATA(ld_exchange_partner). | ||||
| "SELECT single EXCHANGE_NUMBER FROM BAPI_OIA_EXGAGRMNT_HDR_OUT INTO @DATA(ld_external_exchange_number). | ||||
| "SELECT single PARTNER_REF_NUMBER FROM BAPI_OIA_EXGAGRMNT_HDR_OUT INTO @DATA(ld_partner_reference_number). | ||||
Search for further information about these or an SAP related objects