SAP SCMA_OFFICE_DOCUMENT_PROCESS Function Module for
SCMA_OFFICE_DOCUMENT_PROCESS is a standard scma office document process 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 scma office document process FM, simply by entering the name SCMA_OFFICE_DOCUMENT_PROCESS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SCMA_OFFICE_INTEGRATION
Program Name: SAPLSCMA_OFFICE_INTEGRATION
Main Program: SAPLSCMA_OFFICE_INTEGRATION
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SCMA_OFFICE_DOCUMENT_PROCESS 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 'SCMA_OFFICE_DOCUMENT_PROCESS'".
EXPORTING
ID_PROCESSING_MODE = "
ID_APPLICATION_NAME = "
* ID_DOCUMENT_ID = "
ID_DOCUMENT_CLASS = "
* ID_RECONFIRM_FUNCNAME = '' "
* IB_NO_CONFIRMATION = ' ' "
IMPORTING
ED_DOCUMENT_ID_NEW = "
EXCEPTIONS
NOTHING_FOUND = 1 FUNCTION_CANCELLED = 2 OFFICE_INTEGRATION_ERROR = 3 NOT_AUTHORIZED = 4
IMPORTING Parameters details for SCMA_OFFICE_DOCUMENT_PROCESS
ID_PROCESSING_MODE -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
ID_APPLICATION_NAME -
Data type: ITEX132Optional: No
Call by Reference: No ( called with pass by value option)
ID_DOCUMENT_ID -
Data type: BDS_DOCIDOptional: Yes
Call by Reference: No ( called with pass by value option)
ID_DOCUMENT_CLASS -
Data type: SBDST_CLASSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
ID_RECONFIRM_FUNCNAME -
Data type: RS38L_FNAMDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
IB_NO_CONFIRMATION -
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SCMA_OFFICE_DOCUMENT_PROCESS
ED_DOCUMENT_ID_NEW -
Data type: BDS_DOCIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOTHING_FOUND - Document Not Found
Data type:Optional: No
Call by Reference: Yes
FUNCTION_CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OFFICE_INTEGRATION_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SCMA_OFFICE_DOCUMENT_PROCESS 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_nothing_found | TYPE STRING, " | |||
| lv_ed_document_id_new | TYPE BDS_DOCID, " | |||
| lv_id_processing_mode | TYPE CHAR1, " | |||
| lv_function_cancelled | TYPE CHAR1, " | |||
| lv_id_application_name | TYPE ITEX132, " | |||
| lv_id_document_id | TYPE BDS_DOCID, " | |||
| lv_office_integration_error | TYPE BDS_DOCID, " | |||
| lv_not_authorized | TYPE BDS_DOCID, " | |||
| lv_id_document_class | TYPE SBDST_CLASSNAME, " | |||
| lv_id_reconfirm_funcname | TYPE RS38L_FNAM, " '' | |||
| lv_ib_no_confirmation | TYPE CHAR1. " ' ' |
|   CALL FUNCTION 'SCMA_OFFICE_DOCUMENT_PROCESS' " |
| EXPORTING | ||
| ID_PROCESSING_MODE | = lv_id_processing_mode | |
| ID_APPLICATION_NAME | = lv_id_application_name | |
| ID_DOCUMENT_ID | = lv_id_document_id | |
| ID_DOCUMENT_CLASS | = lv_id_document_class | |
| ID_RECONFIRM_FUNCNAME | = lv_id_reconfirm_funcname | |
| IB_NO_CONFIRMATION | = lv_ib_no_confirmation | |
| IMPORTING | ||
| ED_DOCUMENT_ID_NEW | = lv_ed_document_id_new | |
| EXCEPTIONS | ||
| NOTHING_FOUND = 1 | ||
| FUNCTION_CANCELLED = 2 | ||
| OFFICE_INTEGRATION_ERROR = 3 | ||
| NOT_AUTHORIZED = 4 | ||
| . " SCMA_OFFICE_DOCUMENT_PROCESS | ||
ABAP code using 7.40 inline data declarations to call FM SCMA_OFFICE_DOCUMENT_PROCESS
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_id_reconfirm_funcname) | = ''. | |||
| DATA(ld_ib_no_confirmation) | = ' '. | |||
Search for further information about these or an SAP related objects