SAP PAMS_SPLIT_CHECK_DATE Function Module for NOTRANSL: Plausibilitätsprüfungen: Ist das Datum korrekt









PAMS_SPLIT_CHECK_DATE is a standard pams split check date 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: Plausibilitätsprüfungen: Ist das Datum korrekt 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 pams split check date FM, simply by entering the name PAMS_SPLIT_CHECK_DATE into the relevant SAP transaction such as SE37 or SE38.

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



Function PAMS_SPLIT_CHECK_DATE 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 'PAMS_SPLIT_CHECK_DATE'"NOTRANSL: Plausibilitätsprüfungen: Ist das Datum korrekt
  EXPORTING
   IV_STARTDATE =  "Current Date of Application Server
   IV_ENDDATE =  "Current Date of Application Server
   IV_STARTTIME =  "Current Time of Application Server
   IV_ENDTIME =  "Current Time of Application Server

 IMPORTING
   ET_RETURN =  "Return Table
.



IMPORTING Parameters details for PAMS_SPLIT_CHECK_DATE

IV_STARTDATE - Current Date of Application Server

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

IV_ENDDATE - Current Date of Application Server

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

IV_STARTTIME - Current Time of Application Server

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

IV_ENDTIME - Current Time of Application Server

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

EXPORTING Parameters details for PAMS_SPLIT_CHECK_DATE

ET_RETURN - Return Table

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

Copy and paste ABAP code example for PAMS_SPLIT_CHECK_DATE 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_et_return  TYPE BAPIRET2_T, "   
lv_iv_startdate  TYPE SYDATUM, "   
lv_iv_enddate  TYPE SYDATUM, "   
lv_iv_starttime  TYPE SYUZEIT, "   
lv_iv_endtime  TYPE SYUZEIT. "   

  CALL FUNCTION 'PAMS_SPLIT_CHECK_DATE'  "NOTRANSL: Plausibilitätsprüfungen: Ist das Datum korrekt
    EXPORTING
         IV_STARTDATE = lv_iv_startdate
         IV_ENDDATE = lv_iv_enddate
         IV_STARTTIME = lv_iv_starttime
         IV_ENDTIME = lv_iv_endtime
    IMPORTING
         ET_RETURN = lv_et_return
. " PAMS_SPLIT_CHECK_DATE




ABAP code using 7.40 inline data declarations to call FM PAMS_SPLIT_CHECK_DATE

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!