SAP IBAPI_S_STATUS_CHECK Function Module for NOTRANSL: ALM-Auftrag: Prüfen, ob bestimmter Status gesetzt ist









IBAPI_S_STATUS_CHECK is a standard ibapi s status check 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: ALM-Auftrag: Prüfen, ob bestimmter Status gesetzt ist 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 ibapi s status check FM, simply by entering the name IBAPI_S_STATUS_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function IBAPI_S_STATUS_CHECK 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 'IBAPI_S_STATUS_CHECK'"NOTRANSL: ALM-Auftrag: Prüfen, ob bestimmter Status gesetzt ist
EXPORTING
* IV_ORDERID = "Order Number
* IV_OBJECT_NO = "Object Number
IV_STAT = "Individual Status of an Object

EXCEPTIONS
STATUS_NOT_ACTIVE = 1 WRONG_CALL = 2 OBJECT_NOT_FOUND = 3 INTERNAL_ERROR = 4
.



IMPORTING Parameters details for IBAPI_S_STATUS_CHECK

IV_ORDERID - Order Number

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

IV_OBJECT_NO - Object Number

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

IV_STAT - Individual Status of an Object

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

EXCEPTIONS details

STATUS_NOT_ACTIVE - Status is Not Active

Data type:
Optional: No
Call by Reference: Yes

WRONG_CALL -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IBAPI_S_STATUS_CHECK 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_iv_orderid  TYPE AUFNR, "   
lv_status_not_active  TYPE AUFNR, "   
lv_wrong_call  TYPE AUFNR, "   
lv_iv_object_no  TYPE J_OBJNR, "   
lv_iv_stat  TYPE J_STATUS, "   
lv_object_not_found  TYPE J_STATUS, "   
lv_internal_error  TYPE J_STATUS. "   

  CALL FUNCTION 'IBAPI_S_STATUS_CHECK'  "NOTRANSL: ALM-Auftrag: Prüfen, ob bestimmter Status gesetzt ist
    EXPORTING
         IV_ORDERID = lv_iv_orderid
         IV_OBJECT_NO = lv_iv_object_no
         IV_STAT = lv_iv_stat
    EXCEPTIONS
        STATUS_NOT_ACTIVE = 1
        WRONG_CALL = 2
        OBJECT_NOT_FOUND = 3
        INTERNAL_ERROR = 4
. " IBAPI_S_STATUS_CHECK




ABAP code using 7.40 inline data declarations to call FM IBAPI_S_STATUS_CHECK

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.

 
 
 
 
 
 
 


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!