SAP UMB_SC_OBJ_STATUS_LOAD Function Module for
UMB_SC_OBJ_STATUS_LOAD is a standard umb sc obj status load 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 umb sc obj status load FM, simply by entering the name UMB_SC_OBJ_STATUS_LOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: UMB_SC
Program Name: SAPLUMB_SC
Main Program: SAPLUMB_SC
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UMB_SC_OBJ_STATUS_LOAD 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 'UMB_SC_OBJ_STATUS_LOAD'".
EXPORTING
I_SCARD = "
I_OBJ = "
I_FISCPER = "
IMPORTING
E_OBJSTATUS = "
E_DOC_ID = "
IMPORTING Parameters details for UMB_SC_OBJ_STATUS_LOAD
I_SCARD -
Data type: UMB_Y_SCARDOptional: No
Call by Reference: Yes
I_OBJ -
Data type: UMB_Y_OBJOptional: No
Call by Reference: Yes
I_FISCPER -
Data type: UMC_Y_FISCPEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for UMB_SC_OBJ_STATUS_LOAD
E_OBJSTATUS -
Data type: UMB_SC151Optional: No
Call by Reference: Yes
E_DOC_ID -
Data type: BDS_DOCIDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UMB_SC_OBJ_STATUS_LOAD 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_scard | TYPE UMB_Y_SCARD, " | |||
| lv_e_objstatus | TYPE UMB_SC151, " | |||
| lv_i_obj | TYPE UMB_Y_OBJ, " | |||
| lv_e_doc_id | TYPE BDS_DOCID, " | |||
| lv_i_fiscper | TYPE UMC_Y_FISCPER. " |
|   CALL FUNCTION 'UMB_SC_OBJ_STATUS_LOAD' " |
| EXPORTING | ||
| I_SCARD | = lv_i_scard | |
| I_OBJ | = lv_i_obj | |
| I_FISCPER | = lv_i_fiscper | |
| IMPORTING | ||
| E_OBJSTATUS | = lv_e_objstatus | |
| E_DOC_ID | = lv_e_doc_id | |
| . " UMB_SC_OBJ_STATUS_LOAD | ||
ABAP code using 7.40 inline data declarations to call FM UMB_SC_OBJ_STATUS_LOAD
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