SAP ORSSRV_CHECK_ACTIVE_COMPLETE Function Module for NOTRANSL: Prüft, ob für die Objektart die stichtagsbez. Statusauswertung a
ORSSRV_CHECK_ACTIVE_COMPLETE is a standard orssrv check active complete 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üft, ob für die Objektart die stichtagsbez. Statusauswertung a 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 active complete FM, simply by entering the name ORSSRV_CHECK_ACTIVE_COMPLETE 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_ACTIVE_COMPLETE 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_ACTIVE_COMPLETE'"NOTRANSL: Prüft, ob für die Objektart die stichtagsbez. Statusauswertung a.
EXPORTING
I_OBJNR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_SIGN_AP = 'A' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IMPORTING
E_ACTIVE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
E_INCOMPLETE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
WRONG_INPUT = 1 ORGUNIT_ERROR = 2
IMPORTING Parameters details for ORSSRV_CHECK_ACTIVE_COMPLETE
I_OBJNR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: J_OBJNROptional: No
Call by Reference: Yes
I_SIGN_AP - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: DJEST-SIGN_APDefault: 'A'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ORSSRV_CHECK_ACTIVE_COMPLETE
E_ACTIVE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: XFELDOptional: No
Call by Reference: Yes
E_INCOMPLETE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: XFELDOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_INPUT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ORGUNIT_ERROR - 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_ACTIVE_COMPLETE 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_i_objnr | TYPE J_OBJNR, " | |||
| lv_e_active | TYPE XFELD, " | |||
| lv_wrong_input | TYPE XFELD, " | |||
| lv_i_sign_ap | TYPE DJEST-SIGN_AP, " 'A' | |||
| lv_e_incomplete | TYPE XFELD, " | |||
| lv_orgunit_error | TYPE XFELD. " |
|   CALL FUNCTION 'ORSSRV_CHECK_ACTIVE_COMPLETE' "NOTRANSL: Prüft, ob für die Objektart die stichtagsbez. Statusauswertung a |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| I_SIGN_AP | = lv_i_sign_ap | |
| IMPORTING | ||
| E_ACTIVE | = lv_e_active | |
| E_INCOMPLETE | = lv_e_incomplete | |
| EXCEPTIONS | ||
| WRONG_INPUT = 1 | ||
| ORGUNIT_ERROR = 2 | ||
| . " ORSSRV_CHECK_ACTIVE_COMPLETE | ||
ABAP code using 7.40 inline data declarations to call FM ORSSRV_CHECK_ACTIVE_COMPLETE
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 SIGN_AP FROM DJEST INTO @DATA(ld_i_sign_ap). | ||||
| DATA(ld_i_sign_ap) | = 'A'. | |||
Search for further information about these or an SAP related objects