SAP BP_START_DATE_EDITOR Function Module for Read/Display/Check Job Start Date/Period Values Using Dialog Box









BP_START_DATE_EDITOR is a standard bp start date editor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read/Display/Check Job Start Date/Period Values Using Dialog Box 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 bp start date editor FM, simply by entering the name BP_START_DATE_EDITOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: BTCH
Program Name: SAPLBTCH
Main Program: SAPLBTCH
Appliation area: S
Release date: 08-May-1996
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BP_START_DATE_EDITOR 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 'BP_START_DATE_EDITOR'"Read/Display/Check Job Start Date/Period Values Using Dialog Box
  EXPORTING
   STDT_DIALOG =  "Dialog Mode  Yes / No
   STDT_INPUT =  "Input: Start Date and Period Values
*  STDT_OPCODE = 0 "Work Mode in Dialog Box: Display or Edit

 IMPORTING
   STDT_MODIFY_TYPE =  "Displays Whether Start Date Data Was Changed
   STDT_OUTPUT =  "Output: (Updated) Start Date / Period Values

EXCEPTIONS
   FCAL_ID_NOT_DEFINED = 1    LAST_STARTDATE_IN_THE_PAST = 10    NO_PERIOD_DATA_GIVEN = 11    NO_STARTDATE_GIVEN = 12    PERIOD_AND_PREDJOB_NO_WAY = 13    PERIOD_TOO_SMALL_FOR_LIMIT = 14    PREDECESSOR_JOBNAME_NOT_UNIQUE = 15    STARTDATE_INTERVAL_TOO_LARGE = 16    STARTDATE_IN_THE_PAST = 17    STARTDATE_IS_A_HOLIDAY = 18    STARTDATE_OUT_OF_FCAL_RANGE = 19    INCOMPLETE_LAST_STARTDATE = 2    STDT_BEFORE_HOLIDAY_IN_PAST = 20    UNKNOWN_FCAL_ERROR_OCCURED = 21    NO_WORKDAY_NR_GIVEN = 22    INVALID_WORKDAY_COUNTDIR = 23    INVALID_WORKDAY_NR = 24    NOTBEFORE_STDT_MISSING = 25    WORKDAY_STARTTIME_MISSING = 26    NO_EVENTID_GIVEN = 27    INCOMPLETE_STARTDATE = 3    INVALID_DIALOG_TYPE = 4    INVALID_EVENTID = 5    INVALID_OPCODE = 6    INVALID_OPMODE_NAME = 7    INVALID_PERIODBEHAVIOUR = 8    INVALID_PREDECESSOR_JOBNAME = 9
.



IMPORTING Parameters details for BP_START_DATE_EDITOR

STDT_DIALOG - Dialog Mode Yes / No

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

STDT_INPUT - Input: Start Date and Period Values

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

STDT_OPCODE - Work Mode in Dialog Box: Display or Edit

Data type: BTCH0000-INT4
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BP_START_DATE_EDITOR

STDT_MODIFY_TYPE - Displays Whether Start Date Data Was Changed

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

STDT_OUTPUT - Output: (Updated) Start Date / Period Values

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

EXCEPTIONS details

FCAL_ID_NOT_DEFINED - Factory Calendar ID Not Defined

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

LAST_STARTDATE_IN_THE_PAST - Last Start Date is in the Past

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

NO_PERIOD_DATA_GIVEN - No Period Specifications

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

NO_STARTDATE_GIVEN - No Start Date Specified

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

PERIOD_AND_PREDJOB_NO_WAY - Predecessor Job Cannot Be Used With Period

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

PERIOD_TOO_SMALL_FOR_LIMIT - Earlier Start and Period < One Week Not Allowed

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

PREDECESSOR_JOBNAME_NOT_UNIQUE - Name of Predecessor Job Not Unique

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

STARTDATE_INTERVAL_TOO_LARGE - (Last Start Date - Start Date) > One Year

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

STARTDATE_IN_THE_PAST - Start Date is in the Past

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

STARTDATE_IS_A_HOLIDAY - Start Date is Not a Workday

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

STARTDATE_OUT_OF_FCAL_RANGE - Start Date is Not Within Factory Calendar

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

INCOMPLETE_LAST_STARTDATE - Incomplete specification of last start date

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

STDT_BEFORE_HOLIDAY_IN_PAST - Workday Before Public Holiday in the Past

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

UNKNOWN_FCAL_ERROR_OCCURED - Unknown Error in Factory Calendar Check

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

NO_WORKDAY_NR_GIVEN - Workday Not Specified

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

INVALID_WORKDAY_COUNTDIR - Count direction for workday is invalid

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

INVALID_WORKDAY_NR - Workday number is invalid

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

NOTBEFORE_STDT_MISSING - Earliest Start Date Missing

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

WORKDAY_STARTTIME_MISSING - Time for Start Date 'On Workday' Missing

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

NO_EVENTID_GIVEN - No Event ID Specified

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

INCOMPLETE_STARTDATE - Incomplete start date

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

INVALID_DIALOG_TYPE - Invalid dialog type

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

INVALID_EVENTID - Event ID specified is invalid

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

INVALID_OPCODE - Invalid Work Mode

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

INVALID_OPMODE_NAME - Invalid Operation Mode Name

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

INVALID_PERIODBEHAVIOUR - Invalid Start Date Restriction

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

INVALID_PREDECESSOR_JOBNAME - Name of predecessor job is invalid

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

Copy and paste ABAP code example for BP_START_DATE_EDITOR 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_stdt_dialog  TYPE BTCH0000-CHAR1, "   
lv_stdt_modify_type  TYPE BTCH0000-INT4, "   
lv_fcal_id_not_defined  TYPE BTCH0000, "   
lv_last_startdate_in_the_past  TYPE BTCH0000, "   
lv_no_period_data_given  TYPE BTCH0000, "   
lv_no_startdate_given  TYPE BTCH0000, "   
lv_period_and_predjob_no_way  TYPE BTCH0000, "   
lv_period_too_small_for_limit  TYPE BTCH0000, "   
lv_predecessor_jobname_not_unique  TYPE BTCH0000, "   
lv_startdate_interval_too_large  TYPE BTCH0000, "   
lv_startdate_in_the_past  TYPE BTCH0000, "   
lv_startdate_is_a_holiday  TYPE BTCH0000, "   
lv_startdate_out_of_fcal_range  TYPE BTCH0000, "   
lv_stdt_input  TYPE TBTCSTRT, "   
lv_stdt_output  TYPE TBTCSTRT, "   
lv_incomplete_last_startdate  TYPE TBTCSTRT, "   
lv_stdt_before_holiday_in_past  TYPE TBTCSTRT, "   
lv_unknown_fcal_error_occured  TYPE TBTCSTRT, "   
lv_no_workday_nr_given  TYPE TBTCSTRT, "   
lv_invalid_workday_countdir  TYPE TBTCSTRT, "   
lv_invalid_workday_nr  TYPE TBTCSTRT, "   
lv_notbefore_stdt_missing  TYPE TBTCSTRT, "   
lv_workday_starttime_missing  TYPE TBTCSTRT, "   
lv_no_eventid_given  TYPE TBTCSTRT, "   
lv_stdt_opcode  TYPE BTCH0000-INT4, "   0
lv_incomplete_startdate  TYPE BTCH0000, "   
lv_invalid_dialog_type  TYPE BTCH0000, "   
lv_invalid_eventid  TYPE BTCH0000, "   
lv_invalid_opcode  TYPE BTCH0000, "   
lv_invalid_opmode_name  TYPE BTCH0000, "   
lv_invalid_periodbehaviour  TYPE BTCH0000, "   
lv_invalid_predecessor_jobname  TYPE BTCH0000. "   

  CALL FUNCTION 'BP_START_DATE_EDITOR'  "Read/Display/Check Job Start Date/Period Values Using Dialog Box
    EXPORTING
         STDT_DIALOG = lv_stdt_dialog
         STDT_INPUT = lv_stdt_input
         STDT_OPCODE = lv_stdt_opcode
    IMPORTING
         STDT_MODIFY_TYPE = lv_stdt_modify_type
         STDT_OUTPUT = lv_stdt_output
    EXCEPTIONS
        FCAL_ID_NOT_DEFINED = 1
        LAST_STARTDATE_IN_THE_PAST = 10
        NO_PERIOD_DATA_GIVEN = 11
        NO_STARTDATE_GIVEN = 12
        PERIOD_AND_PREDJOB_NO_WAY = 13
        PERIOD_TOO_SMALL_FOR_LIMIT = 14
        PREDECESSOR_JOBNAME_NOT_UNIQUE = 15
        STARTDATE_INTERVAL_TOO_LARGE = 16
        STARTDATE_IN_THE_PAST = 17
        STARTDATE_IS_A_HOLIDAY = 18
        STARTDATE_OUT_OF_FCAL_RANGE = 19
        INCOMPLETE_LAST_STARTDATE = 2
        STDT_BEFORE_HOLIDAY_IN_PAST = 20
        UNKNOWN_FCAL_ERROR_OCCURED = 21
        NO_WORKDAY_NR_GIVEN = 22
        INVALID_WORKDAY_COUNTDIR = 23
        INVALID_WORKDAY_NR = 24
        NOTBEFORE_STDT_MISSING = 25
        WORKDAY_STARTTIME_MISSING = 26
        NO_EVENTID_GIVEN = 27
        INCOMPLETE_STARTDATE = 3
        INVALID_DIALOG_TYPE = 4
        INVALID_EVENTID = 5
        INVALID_OPCODE = 6
        INVALID_OPMODE_NAME = 7
        INVALID_PERIODBEHAVIOUR = 8
        INVALID_PREDECESSOR_JOBNAME = 9
. " BP_START_DATE_EDITOR




ABAP code using 7.40 inline data declarations to call FM BP_START_DATE_EDITOR

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 CHAR1 FROM BTCH0000 INTO @DATA(ld_stdt_dialog).
 
"SELECT single INT4 FROM BTCH0000 INTO @DATA(ld_stdt_modify_type).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single INT4 FROM BTCH0000 INTO @DATA(ld_stdt_opcode).
 
 
 
 
 
 
 
 


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!