SAP ISHMED_SET_OP_BEGONNEN Function Module for









ISHMED_SET_OP_BEGONNEN is a standard ishmed set op begonnen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ishmed set op begonnen FM, simply by entering the name ISHMED_SET_OP_BEGONNEN into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHMED_SET_OP_BEGONNEN 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 'ISHMED_SET_OP_BEGONNEN'"
EXPORTING
PP_ANKLEI = "
* PP_POPUP = 'X' "
* PP_LOCKFAL = 'X' "Lock Case (ON/OFF)
* PP_ENVIRONMENT = "Environment
* PP_PLANOE = "

IMPORTING
PP_OPNR = "
PP_NEWANKLEI = "
PP_CANCEL = "Cancel
PP_WARNING = "

CHANGING
* PP_DATE = "
* PP_TIME = "Surgery Time
* PP_RAUM = "

EXCEPTIONS
OP_NOT_FND = 1 CASE_NOT_EXISTENT = 10 CASE_LOCKED = 11 ERROR_SY_MSGID = 12 OP_BEG_NOT_POSS = 2 NO_TMN_FND = 3 NO_FAL_FND = 4 OP_BEW_FAILED = 5 NO_AUTH = 6 CASE_CLOSED = 7 CASE_ACCOUNTED = 8 CASE_DISCHARGED = 9
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLN1ON_001 IS-H*MED: User Exit for 'Check Plan' in the Planning List
EXIT_SAPLN1ON_002 IS-H*MED: User Exit OR Schedule & Plan (Selection of add'l Info per Surg)
EXIT_SAPLN1ON_003 IS-H*MED: User Exit for Printing the Planning List
EXIT_SAPLN1ON_004 IS-H*MED: User Exit for Checks Whether Surgery Started
EXIT_SAPLN1ON_005 IS-H*MED: User Exit for Printing the OR Schedule
EXIT_SAPLN1ON_006 IS-H*MED: Planning List & OR Schedule - Menu Exit 1
EXIT_SAPLN1ON_007 IS-H*MED: Planning List & OR Schedule - Menu Exit 2
EXIT_SAPLN1ON_008 IS-H*MED: Planning List & OR Schedule - Menu Exit 3
EXIT_SAPLN1ON_009 IS-H*MED: Planning List/OR Schedule - Additional Double-Click Functions
EXIT_SAPLN1ON_USF IS-H*MED: Function Calls into User-Specific GUI Statuses (OR Schedule)

IMPORTING Parameters details for ISHMED_SET_OP_BEGONNEN

PP_ANKLEI -

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

PP_POPUP -

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PP_LOCKFAL - Lock Case (ON/OFF)

Data type: ISH_ON_OFF
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PP_ENVIRONMENT - Environment

Data type: CL_ISH_ENVIRONMENT
Optional: Yes
Call by Reference: Yes

PP_PLANOE -

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

EXPORTING Parameters details for ISHMED_SET_OP_BEGONNEN

PP_OPNR -

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

PP_NEWANKLEI -

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

PP_CANCEL - Cancel

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

PP_WARNING -

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

CHANGING Parameters details for ISHMED_SET_OP_BEGONNEN

PP_DATE -

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

PP_TIME - Surgery Time

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

PP_RAUM -

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

EXCEPTIONS details

OP_NOT_FND -

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

CASE_NOT_EXISTENT -

Data type:
Optional: No
Call by Reference: Yes

CASE_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

ERROR_SY_MSGID -

Data type:
Optional: No
Call by Reference: Yes

OP_BEG_NOT_POSS -

Data type:
Optional: No
Call by Reference: Yes

NO_TMN_FND -

Data type:
Optional: No
Call by Reference: Yes

NO_FAL_FND -

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

OP_BEW_FAILED -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTH -

Data type:
Optional: No
Call by Reference: Yes

CASE_CLOSED -

Data type:
Optional: No
Call by Reference: Yes

CASE_ACCOUNTED -

Data type:
Optional: No
Call by Reference: Yes

CASE_DISCHARGED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISHMED_SET_OP_BEGONNEN 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_pp_date  TYPE NBEW-BWIDT, "   
lv_pp_opnr  TYPE NLEM-OPNR, "   
lv_pp_anklei  TYPE NLEI, "   
lv_op_not_fnd  TYPE NLEI, "   
lv_case_not_existent  TYPE NLEI, "   
lv_case_locked  TYPE NLEI, "   
lv_error_sy_msgid  TYPE NLEI, "   
lv_pp_time  TYPE NBEW-BWIZT, "   
lv_pp_popup  TYPE NBEW, "   'X'
lv_pp_newanklei  TYPE NLEI, "   
lv_op_beg_not_poss  TYPE NLEI, "   
lv_pp_raum  TYPE NBEW-ZIMMR, "   
lv_pp_cancel  TYPE RNT40-MARK, "   
lv_no_tmn_fnd  TYPE RNT40, "   
lv_pp_lockfal  TYPE ISH_ON_OFF, "   'X'
lv_no_fal_fnd  TYPE ISH_ON_OFF, "   
lv_pp_warning  TYPE CHAR1, "   
lv_pp_environment  TYPE CL_ISH_ENVIRONMENT, "   
lv_pp_planoe  TYPE ORGID, "   
lv_op_bew_failed  TYPE ORGID, "   
lv_no_auth  TYPE ORGID, "   
lv_case_closed  TYPE ORGID, "   
lv_case_accounted  TYPE ORGID, "   
lv_case_discharged  TYPE ORGID. "   

  CALL FUNCTION 'ISHMED_SET_OP_BEGONNEN'  "
    EXPORTING
         PP_ANKLEI = lv_pp_anklei
         PP_POPUP = lv_pp_popup
         PP_LOCKFAL = lv_pp_lockfal
         PP_ENVIRONMENT = lv_pp_environment
         PP_PLANOE = lv_pp_planoe
    IMPORTING
         PP_OPNR = lv_pp_opnr
         PP_NEWANKLEI = lv_pp_newanklei
         PP_CANCEL = lv_pp_cancel
         PP_WARNING = lv_pp_warning
    CHANGING
         PP_DATE = lv_pp_date
         PP_TIME = lv_pp_time
         PP_RAUM = lv_pp_raum
    EXCEPTIONS
        OP_NOT_FND = 1
        CASE_NOT_EXISTENT = 10
        CASE_LOCKED = 11
        ERROR_SY_MSGID = 12
        OP_BEG_NOT_POSS = 2
        NO_TMN_FND = 3
        NO_FAL_FND = 4
        OP_BEW_FAILED = 5
        NO_AUTH = 6
        CASE_CLOSED = 7
        CASE_ACCOUNTED = 8
        CASE_DISCHARGED = 9
. " ISHMED_SET_OP_BEGONNEN




ABAP code using 7.40 inline data declarations to call FM ISHMED_SET_OP_BEGONNEN

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 BWIDT FROM NBEW INTO @DATA(ld_pp_date).
 
"SELECT single OPNR FROM NLEM INTO @DATA(ld_pp_opnr).
 
 
 
 
 
 
"SELECT single BWIZT FROM NBEW INTO @DATA(ld_pp_time).
 
DATA(ld_pp_popup) = 'X'.
 
 
 
"SELECT single ZIMMR FROM NBEW INTO @DATA(ld_pp_raum).
 
"SELECT single MARK FROM RNT40 INTO @DATA(ld_pp_cancel).
 
 
DATA(ld_pp_lockfal) = 'X'.
 
 
 
 
 
 
 
 
 
 


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!