SAP OMS_CHECK_DATE_IN_OMSET_TBL Function Module for Determine op. type which should be active according to op. mode set t

Search SAP Function Modules

OMS_CHECK_DATE_IN_OMSET_TBL is a standard oms check date in omset tbl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine op. type which should be active according to op. mode set t 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 oms check date in omset tbl FM, simply by entering the name OMS_CHECK_DATE_IN_OMSET_TBL into the relevant SAP transaction such as SE37 or SE38.

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

Function OMS_CHECK_DATE_IN_OMSET_TBL 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 'OMS_CHECK_DATE_IN_OMSET_TBL'"Determine op. type which should be active according to op. mode set t
  EXPORTING
*  DATE = SY-DATUM "desired date
*  TIME = SY-UZEIT "desired time of day

 IMPORTING
   OMSET_INTERVAL =  "Interval in which the date / time is
   ENDTIME_OF_INTERVAL =  "

TABLES
   OMSET_TABLE =  "table with operation type sets to be examined

EXCEPTIONS
   INVALID_DATE = 1    INVALID_TIME = 2    NO_INTERVAL_FOUND = 3 

.

IMPORTING Parameters details for OMS_CHECK_DATE_IN_OMSET_TBL

DATE - desired date

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

TIME - desired time of day

Data type: SY-UZEIT
Default: SY-UZEIT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for OMS_CHECK_DATE_IN_OMSET_TBL

OMSET_INTERVAL - Interval in which the date / time is

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

ENDTIME_OF_INTERVAL -

Data type: SY-UZEIT
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for OMS_CHECK_DATE_IN_OMSET_TBL

OMSET_TABLE - table with operation type sets to be examined

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

EXCEPTIONS details

INVALID_DATE - invalid date specification

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

INVALID_TIME - invalid time specification

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

NO_INTERVAL_FOUND - Date/time lies in no defined interval

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

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

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