SAP RM_DATASTR_ACT_CLIENT Function Module for RM: Nachbearbeitung bei Import Aktivstatus
RM_DATASTR_ACT_CLIENT is a standard rm datastr act client SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: Nachbearbeitung bei Import Aktivstatus 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 rm datastr act client FM, simply by entering the name RM_DATASTR_ACT_CLIENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMIMP
Program Name: SAPLRMIMP
Main Program: SAPLRMIMP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DATASTR_ACT_CLIENT 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 'RM_DATASTR_ACT_CLIENT'"RM: Nachbearbeitung bei Import Aktivstatus.
EXPORTING
IV_TARCLIENT = "Zielmandant
I_TRKORR = "Transportauftrag
IMPORTING
E_LOG_T = "Log-Tabelle
IMPORTING Parameters details for RM_DATASTR_ACT_CLIENT
IV_TARCLIENT - Zielmandant
Data type: E070C-TARCLIENTOptional: No
Call by Reference: Yes
I_TRKORR - Transportauftrag
Data type: TRKORROptional: No
Call by Reference: Yes
EXPORTING Parameters details for RM_DATASTR_ACT_CLIENT
E_LOG_T - Log-Tabelle
Data type: RMLOG_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_DATASTR_ACT_CLIENT 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_e_log_t | TYPE RMLOG_T, " | |||
| lv_iv_tarclient | TYPE E070C-TARCLIENT, " | |||
| lv_i_trkorr | TYPE TRKORR. " |
|   CALL FUNCTION 'RM_DATASTR_ACT_CLIENT' "RM: Nachbearbeitung bei Import Aktivstatus |
| EXPORTING | ||
| IV_TARCLIENT | = lv_iv_tarclient | |
| I_TRKORR | = lv_i_trkorr | |
| IMPORTING | ||
| E_LOG_T | = lv_e_log_t | |
| . " RM_DATASTR_ACT_CLIENT | ||
ABAP code using 7.40 inline data declarations to call FM RM_DATASTR_ACT_CLIENT
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.| "SELECT single TARCLIENT FROM E070C INTO @DATA(ld_iv_tarclient). | ||||
Search for further information about these or an SAP related objects