SAP BORWE_QTY_DIFF_CONFIG Function Module for NOTRANSL: Entscheidung Mengenanpassung bei Mengenabweichung
BORWE_QTY_DIFF_CONFIG is a standard borwe qty diff config SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Entscheidung Mengenanpassung bei Mengenabweichung 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 borwe qty diff config FM, simply by entering the name BORWE_QTY_DIFF_CONFIG into the relevant SAP transaction such as SE37 or SE38.
Function Group: BORWE
Program Name: SAPLBORWE
Main Program: SAPLBORWE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BORWE_QTY_DIFF_CONFIG 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 'BORWE_QTY_DIFF_CONFIG'"NOTRANSL: Entscheidung Mengenanpassung bei Mengenabweichung.
IMPORTING
E_QTYDIFFCONFIG = "Configuration of Quantity Difference Handling
EXCEPTIONS
STOPPING = 1
EXPORTING Parameters details for BORWE_QTY_DIFF_CONFIG
E_QTYDIFFCONFIG - Configuration of Quantity Difference Handling
Data type: /SPE/QTYDIFFCONFIGOptional: No
Call by Reference: Yes
EXCEPTIONS details
STOPPING -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BORWE_QTY_DIFF_CONFIG 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_stopping | TYPE STRING, " | |||
| lv_e_qtydiffconfig | TYPE /SPE/QTYDIFFCONFIG. " |
|   CALL FUNCTION 'BORWE_QTY_DIFF_CONFIG' "NOTRANSL: Entscheidung Mengenanpassung bei Mengenabweichung |
| IMPORTING | ||
| E_QTYDIFFCONFIG | = lv_e_qtydiffconfig | |
| EXCEPTIONS | ||
| STOPPING = 1 | ||
| . " BORWE_QTY_DIFF_CONFIG | ||
ABAP code using 7.40 inline data declarations to call FM BORWE_QTY_DIFF_CONFIG
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