SAP Function Modules
STATUS_CHANGE_INTERN_MULTI SAP Function module
STATUS_CHANGE_INTERN_MULTI is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name STATUS_CHANGE_INTERN_MULTI into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
BSVA
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM STATUS_CHANGE_INTERN_MULTI - STATUS CHANGE INTERN MULTI
CALL FUNCTION 'STATUS_CHANGE_INTERN_MULTI' "
* EXPORTING
* client = SY-MANDT " sy-mandt Client (Only for Exceptional Cases!)
* set_chgkz = " jsto-chgkz 'Activate Change Documents' Flag
IMPORTING
error_occurred = " general error occurred
object_not_found = " Status object not found
object_not_found = " Status object not found
status_inconsistent = " Subsequent status situation is inconsistent
status_inconsistent = " Individual status should be set and deleted
status_not_allowed = " Status Change Not Allowed
status_not_allowed = " Status change not allowed
TABLES
status = " jstat Table of individual statuses for the object
objects = " jsto_pre
EXCEPTIONS
OBJECT_NOT_FOUND = 1 " Status object not found
OBJECT_NOT_FOUND = 1 " Status object not found
STATUS_INCONSISTENT = 2 " Individual status should be set and deleted
STATUS_INCONSISTENT = 2 " Subsequent status situation is inconsistent
STATUS_NOT_ALLOWED = 3 " Status change not allowed
STATUS_NOT_ALLOWED = 3 " Status Change Not Allowed
. " STATUS_CHANGE_INTERN_MULTI
ABAP code example for Function Module STATUS_CHANGE_INTERN_MULTI
The ABAP code below is a full code listing to execute function module STATUS_CHANGE_INTERN_MULTI including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_error_occurred | TYPE STRING , |
| ld_object_not_found | TYPE STRING , |
| ld_object_not_found | TYPE STRING , |
| ld_status_inconsistent | TYPE STRING , |
| ld_status_inconsistent | TYPE STRING , |
| ld_status_not_allowed | TYPE STRING , |
| ld_status_not_allowed | TYPE STRING , |
| it_status | TYPE STANDARD TABLE OF JSTAT,"TABLES PARAM |
| wa_status | LIKE LINE OF it_status , |
| it_objects | TYPE STANDARD TABLE OF JSTO_PRE,"TABLES PARAM |
| wa_objects | LIKE LINE OF it_objects . |
DATA(ld_client) = 'Check type of data required'.
SELECT single CHGKZ
FROM JSTO
INTO @DATA(ld_set_chgkz).
"populate fields of struture and append to itab
append wa_status to it_status.
"populate fields of struture and append to itab
append wa_objects to it_objects. . CALL FUNCTION 'STATUS_CHANGE_INTERN_MULTI' * EXPORTING * client = ld_client * set_chgkz = ld_set_chgkz IMPORTING error_occurred = ld_error_occurred object_not_found = ld_object_not_found object_not_found = ld_object_not_found status_inconsistent = ld_status_inconsistent status_inconsistent = ld_status_inconsistent status_not_allowed = ld_status_not_allowed status_not_allowed = ld_status_not_allowed TABLES status = it_status objects = it_objects EXCEPTIONS OBJECT_NOT_FOUND = 1 OBJECT_NOT_FOUND = 1 STATUS_INCONSISTENT = 2 STATUS_INCONSISTENT = 2 STATUS_NOT_ALLOWED = 3 STATUS_NOT_ALLOWED = 3 . " STATUS_CHANGE_INTERN_MULTI
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_error_occurred | TYPE STRING , |
| ld_client | TYPE SY-MANDT , |
| it_status | TYPE STANDARD TABLE OF JSTAT , |
| wa_status | LIKE LINE OF it_status, |
| ld_object_not_found | TYPE STRING , |
| ld_object_not_found | TYPE STRING , |
| ld_set_chgkz | TYPE JSTO-CHGKZ , |
| it_objects | TYPE STANDARD TABLE OF JSTO_PRE , |
| wa_objects | LIKE LINE OF it_objects, |
| ld_status_inconsistent | TYPE STRING , |
| ld_status_inconsistent | TYPE STRING , |
| ld_status_not_allowed | TYPE STRING , |
| ld_status_not_allowed | TYPE STRING . |
ld_client = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_status to it_status.
SELECT single CHGKZ
FROM JSTO
INTO ld_set_chgkz.
"populate fields of struture and append to itab
append wa_objects to it_objects.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name STATUS_CHANGE_INTERN_MULTI or its description.