SAP BAPI_PATPATH_GETSTEPNEXT Function Module for IS-H*MED: Determine Next Step









BAPI_PATPATH_GETSTEPNEXT is a standard bapi patpath getstepnext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H*MED: Determine Next Step 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 bapi patpath getstepnext FM, simply by entering the name BAPI_PATPATH_GETSTEPNEXT into the relevant SAP transaction such as SE37 or SE38.

Function Group: 1420
Program Name: SAPL1420
Main Program: SAPL1420
Appliation area:
Release date: 17-May-2004
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_PATPATH_GETSTEPNEXT 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 'BAPI_PATPATH_GETSTEPNEXT'"IS-H*MED: Determine Next Step
EXPORTING
INSTITUTION = "IS-H: Institution
PATIENTID = "IS-H: Patient Number
PATCASEID = "IS-H: Case Number
PATPATHID = "IS-H*MED: Patient Pathway Key
STEPID = "IS-H*MED: Step Key

IMPORTING
WORST_RETURNED_MSGTY = "IS-H: Most Severe Message Type Generated
NEXT_STEPID = "IS-H*MED: Step Key

TABLES
RETURN = "Return Parameter(s)
.



IMPORTING Parameters details for BAPI_PATPATH_GETSTEPNEXT

INSTITUTION - IS-H: Institution

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

PATIENTID - IS-H: Patient Number

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

PATCASEID - IS-H: Case Number

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

PATPATHID - IS-H*MED: Patient Pathway Key

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

STEPID - IS-H*MED: Step Key

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

EXPORTING Parameters details for BAPI_PATPATH_GETSTEPNEXT

WORST_RETURNED_MSGTY - IS-H: Most Severe Message Type Generated

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

NEXT_STEPID - IS-H*MED: Step Key

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

TABLES Parameters details for BAPI_PATPATH_GETSTEPNEXT

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for BAPI_PATPATH_GETSTEPNEXT 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_institution  TYPE BAPINALL-INSTITUTION, "   
lv_worst_returned_msgty  TYPE BAPINALL-WORSTRETMSG, "   
lv_patientid  TYPE BAPINALL-PATIENTID, "   
lv_next_stepid  TYPE BAPI1420-STEPID, "   
lv_patcaseid  TYPE BAPINALL-PATCASEID, "   
lv_patpathid  TYPE BAPI1420-PATPATHID, "   
lv_stepid  TYPE BAPI1420-STEPID. "   

  CALL FUNCTION 'BAPI_PATPATH_GETSTEPNEXT'  "IS-H*MED: Determine Next Step
    EXPORTING
         INSTITUTION = lv_institution
         PATIENTID = lv_patientid
         PATCASEID = lv_patcaseid
         PATPATHID = lv_patpathid
         STEPID = lv_stepid
    IMPORTING
         WORST_RETURNED_MSGTY = lv_worst_returned_msgty
         NEXT_STEPID = lv_next_stepid
    TABLES
         RETURN = lt_return
. " BAPI_PATPATH_GETSTEPNEXT




ABAP code using 7.40 inline data declarations to call FM BAPI_PATPATH_GETSTEPNEXT

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 INSTITUTION FROM BAPINALL INTO @DATA(ld_institution).
 
"SELECT single WORSTRETMSG FROM BAPINALL INTO @DATA(ld_worst_returned_msgty).
 
"SELECT single PATIENTID FROM BAPINALL INTO @DATA(ld_patientid).
 
"SELECT single STEPID FROM BAPI1420 INTO @DATA(ld_next_stepid).
 
"SELECT single PATCASEID FROM BAPINALL INTO @DATA(ld_patcaseid).
 
"SELECT single PATPATHID FROM BAPI1420 INTO @DATA(ld_patpathid).
 
"SELECT single STEPID FROM BAPI1420 INTO @DATA(ld_stepid).
 


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!