SAP RDM_OPT_PROCESS_DCINV_RFC Function Module for NOTRANSL: RFC-Schale fuer Bestand VZ
RDM_OPT_PROCESS_DCINV_RFC is a standard rdm opt process dcinv rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RFC-Schale fuer Bestand VZ 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 rdm opt process dcinv rfc FM, simply by entering the name RDM_OPT_PROCESS_DCINV_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: RDM_OPT_PARALLEL
Program Name: SAPLRDM_OPT_PARALLEL
Main Program: SAPLRDM_OPT_PARALLEL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RDM_OPT_PROCESS_DCINV_RFC 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 'RDM_OPT_PROCESS_DCINV_RFC'"NOTRANSL: RFC-Schale fuer Bestand VZ.
EXPORTING
I_VKORG = "Sales Organization
I_VTWEG = "Distribution Channel
I_BUSINESS_SYSTEM = "System Demand Management
I_L2SERVICE = "RDM: Indicator: Use Level-2 Services
IMPORTING
ET_MESSAGES = "Application Log: Table with Messages
E_SUBRC = "Return Code
ETH_MESSAGE_INFO = "Information for a SAP DM Message
TABLES
IT_PACKAGE = "Structure for Material Number
ITR_WERKS = "Range Structure for Plant
IMPORTING Parameters details for RDM_OPT_PROCESS_DCINV_RFC
I_VKORG - Sales Organization
Data type: VKORGOptional: No
Call by Reference: No ( called with pass by value option)
I_VTWEG - Distribution Channel
Data type: VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
I_BUSINESS_SYSTEM - System Demand Management
Data type: RDM_BUSINESS_SYSTEMOptional: No
Call by Reference: No ( called with pass by value option)
I_L2SERVICE - RDM: Indicator: Use Level-2 Services
Data type: RDM_L2SERVICEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RDM_OPT_PROCESS_DCINV_RFC
ET_MESSAGES - Application Log: Table with Messages
Data type: BAL_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
E_SUBRC - Return Code
Data type: SYSUBRCOptional: No
Call by Reference: No ( called with pass by value option)
ETH_MESSAGE_INFO - Information for a SAP DM Message
Data type: RDM_TH_MESSAGE_INFOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RDM_OPT_PROCESS_DCINV_RFC
IT_PACKAGE - Structure for Material Number
Data type: RDM_S_MATNROptional: No
Call by Reference: Yes
ITR_WERKS - Range Structure for Plant
Data type: RDM_SR_WERKSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RDM_OPT_PROCESS_DCINV_RFC 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_i_vkorg | TYPE VKORG, " | |||
| lt_it_package | TYPE STANDARD TABLE OF RDM_S_MATNR, " | |||
| lv_et_messages | TYPE BAL_T_MSG, " | |||
| lv_e_subrc | TYPE SYSUBRC, " | |||
| lv_i_vtweg | TYPE VTWEG, " | |||
| lt_itr_werks | TYPE STANDARD TABLE OF RDM_SR_WERKS, " | |||
| lv_eth_message_info | TYPE RDM_TH_MESSAGE_INFO, " | |||
| lv_i_business_system | TYPE RDM_BUSINESS_SYSTEM, " | |||
| lv_i_l2service | TYPE RDM_L2SERVICE. " |
|   CALL FUNCTION 'RDM_OPT_PROCESS_DCINV_RFC' "NOTRANSL: RFC-Schale fuer Bestand VZ |
| EXPORTING | ||
| I_VKORG | = lv_i_vkorg | |
| I_VTWEG | = lv_i_vtweg | |
| I_BUSINESS_SYSTEM | = lv_i_business_system | |
| I_L2SERVICE | = lv_i_l2service | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| E_SUBRC | = lv_e_subrc | |
| ETH_MESSAGE_INFO | = lv_eth_message_info | |
| TABLES | ||
| IT_PACKAGE | = lt_it_package | |
| ITR_WERKS | = lt_itr_werks | |
| . " RDM_OPT_PROCESS_DCINV_RFC | ||
ABAP code using 7.40 inline data declarations to call FM RDM_OPT_PROCESS_DCINV_RFC
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.Search for further information about these or an SAP related objects