SAP IUUC_TCR_PREPROCESSING_SENDER Function Module for OBSOLETE !!!!
IUUC_TCR_PREPROCESSING_SENDER is a standard iuuc tcr preprocessing sender SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OBSOLETE !!!! 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 iuuc tcr preprocessing sender FM, simply by entering the name IUUC_TCR_PREPROCESSING_SENDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: IUUC_TCR_REMOTE
Program Name: SAPLIUUC_TCR_REMOTE
Main Program: SAPLIUUC_TCR_REMOTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function IUUC_TCR_PREPROCESSING_SENDER 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 'IUUC_TCR_PREPROCESSING_SENDER'"OBSOLETE !!!!.
EXPORTING
* IT_PREPROC_TABLES = "Tables for logtab condense
* IV_NUM_PARALL_JOBS = 1 "Number of parallization jobs for tcr pre-condense logic
IV_TCR_TIMESTAMP = "Timestamp for preprocessing (YYYY.MM.DD hh:mm:ss)
IV_MT_ID = "Mass Transfer ID
IV_MODE = "Character Field Length 1
IV_SESSION_ID = "Session ID
* IV_DIALOG = "Execute Preprocessing in Dialog
IMPORTING
ET_IUUC_TCR_PREPROC_CHECK = "Preprocessing Control Table
EXCEPTIONS
WRONG_MODE = 1 NO_AUTHORIZATION = 2 JOB_FACADE_ERROR = 3 POSTPROCESSING_ERROR = 4
IMPORTING Parameters details for IUUC_TCR_PREPROCESSING_SENDER
IT_PREPROC_TABLES - Tables for logtab condense
Data type: IUUC_TCR_COND_TABLES_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_NUM_PARALL_JOBS - Number of parallization jobs for tcr pre-condense logic
Data type: DMC_NUMBER_JOBSDefault: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TCR_TIMESTAMP - Timestamp for preprocessing (YYYY.MM.DD hh:mm:ss)
Data type: IUUC_TCR_TIMESTAMPOptional: No
Call by Reference: No ( called with pass by value option)
IV_MT_ID - Mass Transfer ID
Data type: DMC_MT_IDENTIFIEROptional: No
Call by Reference: No ( called with pass by value option)
IV_MODE - Character Field Length 1
Data type: CHAR01Optional: No
Call by Reference: No ( called with pass by value option)
IV_SESSION_ID - Session ID
Data type: DMC_SESSION_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_DIALOG - Execute Preprocessing in Dialog
Data type: BOOLE_DOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for IUUC_TCR_PREPROCESSING_SENDER
ET_IUUC_TCR_PREPROC_CHECK - Preprocessing Control Table
Data type: IUUC_TCR_PREPROC_CHECK_TABOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_MODE - Mode not supported
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORIZATION - No authorization to execute preprocessing in sender
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
JOB_FACADE_ERROR - Error when using Job Facade
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
POSTPROCESSING_ERROR - Error when requesting the postprocessing
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for IUUC_TCR_PREPROCESSING_SENDER 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_wrong_mode | TYPE STRING, " | |||
| lv_it_preproc_tables | TYPE IUUC_TCR_COND_TABLES_TAB, " | |||
| lv_et_iuuc_tcr_preproc_check | TYPE IUUC_TCR_PREPROC_CHECK_TAB, " | |||
| lv_no_authorization | TYPE IUUC_TCR_PREPROC_CHECK_TAB, " | |||
| lv_iv_num_parall_jobs | TYPE DMC_NUMBER_JOBS, " 1 | |||
| lv_iv_tcr_timestamp | TYPE IUUC_TCR_TIMESTAMP, " | |||
| lv_job_facade_error | TYPE IUUC_TCR_TIMESTAMP, " | |||
| lv_iv_mt_id | TYPE DMC_MT_IDENTIFIER, " | |||
| lv_postprocessing_error | TYPE DMC_MT_IDENTIFIER, " | |||
| lv_iv_mode | TYPE CHAR01, " | |||
| lv_iv_session_id | TYPE DMC_SESSION_ID, " | |||
| lv_iv_dialog | TYPE BOOLE_D. " |
|   CALL FUNCTION 'IUUC_TCR_PREPROCESSING_SENDER' "OBSOLETE !!!! |
| EXPORTING | ||
| IT_PREPROC_TABLES | = lv_it_preproc_tables | |
| IV_NUM_PARALL_JOBS | = lv_iv_num_parall_jobs | |
| IV_TCR_TIMESTAMP | = lv_iv_tcr_timestamp | |
| IV_MT_ID | = lv_iv_mt_id | |
| IV_MODE | = lv_iv_mode | |
| IV_SESSION_ID | = lv_iv_session_id | |
| IV_DIALOG | = lv_iv_dialog | |
| IMPORTING | ||
| ET_IUUC_TCR_PREPROC_CHECK | = lv_et_iuuc_tcr_preproc_check | |
| EXCEPTIONS | ||
| WRONG_MODE = 1 | ||
| NO_AUTHORIZATION = 2 | ||
| JOB_FACADE_ERROR = 3 | ||
| POSTPROCESSING_ERROR = 4 | ||
| . " IUUC_TCR_PREPROCESSING_SENDER | ||
ABAP code using 7.40 inline data declarations to call FM IUUC_TCR_PREPROCESSING_SENDER
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_num_parall_jobs) | = 1. | |||
Search for further information about these or an SAP related objects