SAP LOCATION_CHECK_ALE_CONSISTENCE Function Module for NOTRANSL: Konsistenz ALE-Verteilung Werk/Kunde/Lieferant

Search SAP Function Modules

LOCATION_CHECK_ALE_CONSISTENCE is a standard location check ale consistence 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: Konsistenz ALE-Verteilung Werk/Kunde/Lieferant 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 location check ale consistence FM, simply by entering the name LOCATION_CHECK_ALE_CONSISTENCE into the relevant SAP transaction such as SE37 or SE38.

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

Function LOCATION_CHECK_ALE_CONSISTENCE 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 'LOCATION_CHECK_ALE_CONSISTENCE'"NOTRANSL: Konsistenz ALE-Verteilung Werk/Kunde/Lieferant
  EXPORTING
*  I_KUNNR =  "Customer Number
*  I_LIFNR =  "Account Number of Vendor or Creditor
*  I_WERKS_OLD =  "Plant
*  I_WERKS_NEW =  "Plant

 IMPORTING
   EP_T001W =  "Plants/branches

EXCEPTIONS
   PARAMETER_MISSING = 1    SITE_NOT_UP_TO_DATE = 2    SITE_DOES_NOT_EXIST = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLWR04_001 User Exit for Determining Supplying Site

IMPORTING Parameters details for LOCATION_CHECK_ALE_CONSISTENCE

I_KUNNR - Customer Number

Data type: KNA1-KUNNR
Optional: Yes
Call by Reference: Yes

I_LIFNR - Account Number of Vendor or Creditor

Data type: LFA1-LIFNR
Optional: Yes
Call by Reference: Yes

I_WERKS_OLD - Plant

Data type: T001W-WERKS
Optional: Yes
Call by Reference: Yes

I_WERKS_NEW - Plant

Data type: T001W-WERKS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for LOCATION_CHECK_ALE_CONSISTENCE

EP_T001W - Plants/branches

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

EXCEPTIONS details

PARAMETER_MISSING - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

SITE_NOT_UP_TO_DATE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

SITE_DOES_NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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