SAP PS4S_STATUS_PROCESS_MASS Function Module for
PS4S_STATUS_PROCESS_MASS is a standard ps4s status process mass 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 ps4s status process mass FM, simply by entering the name PS4S_STATUS_PROCESS_MASS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PS4S_STATUS
Program Name: SAPLPS4S_STATUS
Main Program: SAPLPS4S_STATUS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PS4S_STATUS_PROCESS_MASS 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 'PS4S_STATUS_PROCESS_MASS'".
EXPORTING
* IT_DOC_NO = "
* IV_DEL_DOCS = ' ' "
IV_SYNC = "
IV_EXPORT_MSG = "
* IT_EXT_REF_FICA = "
* IT_EXT_REF_BILL = "
* IT_BP = "
* IT_CA = "
* IT_CO = "
* IV_DOC_TYPES = ' ' "
* IT_TIMESTAMP = "
* IT_SENT_TIMESTAMP = "
IMPORTING
ET_MSG = "
ET_RETURN = "
IMPORTING Parameters details for PS4S_STATUS_PROCESS_MASS
IT_DOC_NO -
Data type: PS4ST_RANGE_DOCNOOptional: Yes
Call by Reference: Yes
IV_DEL_DOCS -
Data type: PS4S_STATUS_DEL_DOCSDefault: ' '
Optional: No
Call by Reference: Yes
IV_SYNC -
Data type: PS4S_STATUS_SYNCOptional: No
Call by Reference: Yes
IV_EXPORT_MSG -
Data type: PS4S_STATUS_EXPORT_MSGOptional: No
Call by Reference: Yes
IT_EXT_REF_FICA -
Data type: PS4ST_RANGE_REFFICAOptional: Yes
Call by Reference: Yes
IT_EXT_REF_BILL -
Data type: PS4ST_RANGE_REFBILLOptional: Yes
Call by Reference: Yes
IT_BP -
Data type: PS4ST_RANGE_BPOptional: Yes
Call by Reference: Yes
IT_CA -
Data type: PS4ST_RANGE_CAOptional: Yes
Call by Reference: Yes
IT_CO -
Data type: PS4ST_RANGE_COOptional: Yes
Call by Reference: Yes
IV_DOC_TYPES -
Data type: PS4S_STATUS_DOC_TYPESDefault: ' '
Optional: No
Call by Reference: Yes
IT_TIMESTAMP -
Data type: PS4ST_RANGE_TIMESTAMPOptional: Yes
Call by Reference: Yes
IT_SENT_TIMESTAMP -
Data type: PS4ST_RANGE_TIMESTAMPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PS4S_STATUS_PROCESS_MASS
ET_MSG -
Data type: PS4ST_STATUS_MSGOptional: No
Call by Reference: Yes
ET_RETURN -
Data type: PS4ST_MSGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PS4S_STATUS_PROCESS_MASS 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_et_msg | TYPE PS4ST_STATUS_MSG, " | |||
| lv_it_doc_no | TYPE PS4ST_RANGE_DOCNO, " | |||
| lv_iv_del_docs | TYPE PS4S_STATUS_DEL_DOCS, " ' ' | |||
| lv_iv_sync | TYPE PS4S_STATUS_SYNC, " | |||
| lv_iv_export_msg | TYPE PS4S_STATUS_EXPORT_MSG, " | |||
| lv_et_return | TYPE PS4ST_MSG, " | |||
| lv_it_ext_ref_fica | TYPE PS4ST_RANGE_REFFICA, " | |||
| lv_it_ext_ref_bill | TYPE PS4ST_RANGE_REFBILL, " | |||
| lv_it_bp | TYPE PS4ST_RANGE_BP, " | |||
| lv_it_ca | TYPE PS4ST_RANGE_CA, " | |||
| lv_it_co | TYPE PS4ST_RANGE_CO, " | |||
| lv_iv_doc_types | TYPE PS4S_STATUS_DOC_TYPES, " ' ' | |||
| lv_it_timestamp | TYPE PS4ST_RANGE_TIMESTAMP, " | |||
| lv_it_sent_timestamp | TYPE PS4ST_RANGE_TIMESTAMP. " |
|   CALL FUNCTION 'PS4S_STATUS_PROCESS_MASS' " |
| EXPORTING | ||
| IT_DOC_NO | = lv_it_doc_no | |
| IV_DEL_DOCS | = lv_iv_del_docs | |
| IV_SYNC | = lv_iv_sync | |
| IV_EXPORT_MSG | = lv_iv_export_msg | |
| IT_EXT_REF_FICA | = lv_it_ext_ref_fica | |
| IT_EXT_REF_BILL | = lv_it_ext_ref_bill | |
| IT_BP | = lv_it_bp | |
| IT_CA | = lv_it_ca | |
| IT_CO | = lv_it_co | |
| IV_DOC_TYPES | = lv_iv_doc_types | |
| IT_TIMESTAMP | = lv_it_timestamp | |
| IT_SENT_TIMESTAMP | = lv_it_sent_timestamp | |
| IMPORTING | ||
| ET_MSG | = lv_et_msg | |
| ET_RETURN | = lv_et_return | |
| . " PS4S_STATUS_PROCESS_MASS | ||
ABAP code using 7.40 inline data declarations to call FM PS4S_STATUS_PROCESS_MASS
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_iv_del_docs) | = ' '. | |||
| DATA(ld_iv_doc_types) | = ' '. | |||
Search for further information about these or an SAP related objects