SAP LOCATION_ISSUING_DATE_CHECK Function Module for NOTRANSL: Datums-Kollisionen ermitteln









LOCATION_ISSUING_DATE_CHECK is a standard location issuing date check 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: Datums-Kollisionen ermitteln 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 issuing date check FM, simply by entering the name LOCATION_ISSUING_DATE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function LOCATION_ISSUING_DATE_CHECK 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_ISSUING_DATE_CHECK'"NOTRANSL: Datums-Kollisionen ermitteln
TABLES
PI_T_AWRF3 = "Dynamic part, delivering plants
PI_T_ZWRF3 = "Dynamic part, delivering plants
.



TABLES Parameters details for LOCATION_ISSUING_DATE_CHECK

PI_T_AWRF3 - Dynamic part, delivering plants

Data type: WRF3D
Optional: No
Call by Reference: No ( called with pass by value option)

PI_T_ZWRF3 - Dynamic part, delivering plants

Data type: WRF3D
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for LOCATION_ISSUING_DATE_CHECK 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:
lt_pi_t_awrf3  TYPE STANDARD TABLE OF WRF3D, "   
lt_pi_t_zwrf3  TYPE STANDARD TABLE OF WRF3D. "   

  CALL FUNCTION 'LOCATION_ISSUING_DATE_CHECK'  "NOTRANSL: Datums-Kollisionen ermitteln
    TABLES
         PI_T_AWRF3 = lt_pi_t_awrf3
         PI_T_ZWRF3 = lt_pi_t_zwrf3
. " LOCATION_ISSUING_DATE_CHECK




ABAP code using 7.40 inline data declarations to call FM LOCATION_ISSUING_DATE_CHECK

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!