SAP EWU_GET_DATE_PLANED_CONV Function Module for NOTRANSL: Finde Planjahr der nächsten geplanten Produktivumstellung
EWU_GET_DATE_PLANED_CONV is a standard ewu get date planed conv 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: Finde Planjahr der nächsten geplanten Produktivumstellung 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 ewu get date planed conv FM, simply by entering the name EWU_GET_DATE_PLANED_CONV into the relevant SAP transaction such as SE37 or SE38.
Function Group: EWU9
Program Name: SAPLEWU9
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EWU_GET_DATE_PLANED_CONV 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 'EWU_GET_DATE_PLANED_CONV'"NOTRANSL: Finde Planjahr der nächsten geplanten Produktivumstellung.
IMPORTING
PAKET = "DE-EN-LANG-SWITCH-NO-TRANSLATION
PLANJAHR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
NO_CONVERSION_FOUND = 1 INCONSISTENT_DATA = 2
EXPORTING Parameters details for EWU_GET_DATE_PLANED_CONV
PAKET - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: EWUPAK-PAKETOptional: No
Call by Reference: No ( called with pass by value option)
PLANJAHR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: EWUPAK-PLANJAHROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CONVERSION_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INCONSISTENT_DATA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EWU_GET_DATE_PLANED_CONV 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_paket | TYPE EWUPAK-PAKET, " | |||
| lv_no_conversion_found | TYPE EWUPAK, " | |||
| lv_planjahr | TYPE EWUPAK-PLANJAHR, " | |||
| lv_inconsistent_data | TYPE EWUPAK. " |
|   CALL FUNCTION 'EWU_GET_DATE_PLANED_CONV' "NOTRANSL: Finde Planjahr der nächsten geplanten Produktivumstellung |
| IMPORTING | ||
| PAKET | = lv_paket | |
| PLANJAHR | = lv_planjahr | |
| EXCEPTIONS | ||
| NO_CONVERSION_FOUND = 1 | ||
| INCONSISTENT_DATA = 2 | ||
| . " EWU_GET_DATE_PLANED_CONV | ||
ABAP code using 7.40 inline data declarations to call FM EWU_GET_DATE_PLANED_CONV
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 PAKET FROM EWUPAK INTO @DATA(ld_paket). | ||||
| "SELECT single PLANJAHR FROM EWUPAK INTO @DATA(ld_planjahr). | ||||
Search for further information about these or an SAP related objects