SAP EXIT_SAPLMEAG_001 Function Module for Create/Change Outline Agreement via BAPI: Customer's Own Logic

Search SAP Function Modules

EXIT_SAPLMEAG_001 is a standard exit saplmeag 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create/Change Outline Agreement via BAPI: Customer's Own Logic 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 exit saplmeag 001 FM, simply by entering the name EXIT_SAPLMEAG_001 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XM03
Program Name: SAPLXM03
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLMEAG_001 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 'EXIT_SAPLMEAG_001'"Create/Change Outline Agreement via BAPI: Customer's Own Logic
  EXPORTING
*  IM_ALL_ITEMS_PASSED =  "ABAP Program, ABAP Program Call Mode

CHANGING
   CH_AGREEMENT_HEADER =  "Header Data Outline Agreement
   CH_AGREEMENT_HEADER_X =  "Header Data Outline Agreement (Checkbox Structure)

TABLES
   CHT_AGREEMENT_ITEMS =  "Item Data Outline Agreement
   CHT_AGREEMENT_ITEMS_X =  "Item Data Outline Agreement (Checkbox Structure)
   CHT_RETURN =  "Return Parameter

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
BAPI_AGREEMENT_MAINTAIN Create/Change Contract/Scheduling Agreement
BAPI_AGREEMENT_PROXY_UPLOAD Proxy BAPI for Upload Purchase Contracts/Scheduling Agreements
CONVERT_BDCMSGCOLL_TO_BAPIRET2 NOTRANSL: Konvertieren BTCI-Fehlermeldungen in BAPI-Fehlermeldungen
MAP2I_BAPIOAHEAD_TO_EKKOOAHEAD NOTRANSL: bapioahead -> ekkooahead
MAP2I_BAPIOAHEAX_TO_EKKOOAHEAX NOTRANSL: bapioaheax -> ekkooaheax
MAP2I_BAPIOAITEM_TO_EKPOOAITEM NOTRANSL: bapioaitem -> ekpooaitem
MAP2I_BAPIOAITEX_TO_EKPOOAITEX NOTRANSL: bapioaitex -> ekpooaitex

IMPORTING Parameters details for EXIT_SAPLMEAG_001

IM_ALL_ITEMS_PASSED - ABAP Program, ABAP Program Call Mode

Data type: SY-CALLD
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for EXIT_SAPLMEAG_001

CH_AGREEMENT_HEADER - Header Data Outline Agreement

Data type: BAPIOAHEAD
Optional: No
Call by Reference: Yes

CH_AGREEMENT_HEADER_X - Header Data Outline Agreement (Checkbox Structure)

Data type: BAPIOAHEAX
Optional: No
Call by Reference: Yes

TABLES Parameters details for EXIT_SAPLMEAG_001

CHT_AGREEMENT_ITEMS - Item Data Outline Agreement

Data type: BAPIOAITEM
Optional: No
Call by Reference: Yes

CHT_AGREEMENT_ITEMS_X - Item Data Outline Agreement (Checkbox Structure)

Data type: BAPIOAITEX
Optional: No
Call by Reference: Yes

CHT_RETURN - Return Parameter

Data type: BAPIRET2
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXIT_SAPLMEAG_001 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.

ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLMEAG_001

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