SAP ORSSRV_CHECK_STATUS Function Module for NOTRANSL: Prüfung, ob ein Status stichtagsbezogen ausgewertet werden soll









ORSSRV_CHECK_STATUS is a standard orssrv check status 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: Prüfung, ob ein Status stichtagsbezogen ausgewertet werden soll 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 orssrv check status FM, simply by entering the name ORSSRV_CHECK_STATUS into the relevant SAP transaction such as SE37 or SE38.

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



Function ORSSRV_CHECK_STATUS 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 'ORSSRV_CHECK_STATUS'"NOTRANSL: Prüfung, ob ein Status stichtagsbezogen ausgewertet werden soll
EXPORTING
I_OBART = "Object Type
I_STSMA = "Status Profile
I_STAT = "Status
* I_ALL = ' ' "DE-EN-LANG-SWITCH-NO-TRANSLATION

IMPORTING
E_ACTIVE = "DE-EN-LANG-SWITCH-NO-TRANSLATION

TABLES
E_STAT = "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
WRONG_INPUT = 1
.



IMPORTING Parameters details for ORSSRV_CHECK_STATUS

I_OBART - Object Type

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

I_STSMA - Status Profile

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

I_STAT - Status

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

I_ALL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: XFLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ORSSRV_CHECK_STATUS

E_ACTIVE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

TABLES Parameters details for ORSSRV_CHECK_STATUS

E_STAT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXCEPTIONS details

WRONG_INPUT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

Copy and paste ABAP code example for ORSSRV_CHECK_STATUS 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_e_stat  TYPE STANDARD TABLE OF TORS1, "   
lv_i_obart  TYPE J_OBART, "   
lv_e_active  TYPE XFLAG, "   
lv_wrong_input  TYPE XFLAG, "   
lv_i_stsma  TYPE J_STSMA, "   
lv_i_stat  TYPE J_STATUS, "   
lv_i_all  TYPE XFLAG. "   SPACE

  CALL FUNCTION 'ORSSRV_CHECK_STATUS'  "NOTRANSL: Prüfung, ob ein Status stichtagsbezogen ausgewertet werden soll
    EXPORTING
         I_OBART = lv_i_obart
         I_STSMA = lv_i_stsma
         I_STAT = lv_i_stat
         I_ALL = lv_i_all
    IMPORTING
         E_ACTIVE = lv_e_active
    TABLES
         E_STAT = lt_e_stat
    EXCEPTIONS
        WRONG_INPUT = 1
. " ORSSRV_CHECK_STATUS




ABAP code using 7.40 inline data declarations to call FM ORSSRV_CHECK_STATUS

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.

 
 
 
 
 
 
DATA(ld_i_all) = ' '.
 


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!