SAP RSCRT_RDA_ASSIGN_IPAK Function Module for Start (near-) real-time InfoPackage
RSCRT_RDA_ASSIGN_IPAK is a standard rscrt rda assign ipak SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start (near-) real-time InfoPackage 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 rscrt rda assign ipak FM, simply by entering the name RSCRT_RDA_ASSIGN_IPAK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSCRT_RDA
Program Name: SAPLRSCRT_RDA
Main Program: SAPLRSCRT_RDA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSCRT_RDA_ASSIGN_IPAK 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 'RSCRT_RDA_ASSIGN_IPAK'"Start (near-) real-time InfoPackage.
EXPORTING
I_DEMONID = "Daemon ID for (Near)-Real-Time Data Transfer into BW
I_LOGDPID = "Logical InfoPackage Variant (ID)
* I_MODE = RSCRT_C_MODE-MAINTAIN "Processing Mode (Display, Change, Create...)
* I_WITH_COMMIT = RS_C_TRUE "Boolean
IMPORTING
E_DEMON_TO_USE = "Daemon ID for (Near)-Real-Time Data Transfer into BW
EXCEPTIONS
FAILED = 1 IPAK_EXECUTED_BY_DEMON = 2 WRONG_INFOPACKAGE = 3 WRONG_DEMON_USED = 4 NO_AUTHORITY = 5 NOT_ALLOWED = 6 NO_LOCK_POSSIBLE = 7
IMPORTING Parameters details for RSCRT_RDA_ASSIGN_IPAK
I_DEMONID - Daemon ID for (Near)-Real-Time Data Transfer into BW
Data type: RSCRT_DEMONIDOptional: No
Call by Reference: No ( called with pass by value option)
I_LOGDPID - Logical InfoPackage Variant (ID)
Data type: RSLOGDPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_MODE - Processing Mode (Display, Change, Create...)
Data type: RS_MODEDefault: RSCRT_C_MODE-MAINTAIN
Optional: Yes
Call by Reference: Yes
I_WITH_COMMIT - Boolean
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSCRT_RDA_ASSIGN_IPAK
E_DEMON_TO_USE - Daemon ID for (Near)-Real-Time Data Transfer into BW
Data type: RSCRT_DEMONIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FAILED - Errors occurred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IPAK_EXECUTED_BY_DEMON - Is in progress
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_INFOPACKAGE - InfoPackage not maintained
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_DEMON_USED - Wrong demon
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY - Obsolete
Data type:Optional: No
Call by Reference: Yes
NOT_ALLOWED - Demon is not allowed
Data type:Optional: No
Call by Reference: Yes
NO_LOCK_POSSIBLE - No lock possible on the Ipak
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSCRT_RDA_ASSIGN_IPAK 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_failed | TYPE STRING, " | |||
| lv_i_demonid | TYPE RSCRT_DEMONID, " | |||
| lv_e_demon_to_use | TYPE RSCRT_DEMONID, " | |||
| lv_i_logdpid | TYPE RSLOGDPID, " | |||
| lv_ipak_executed_by_demon | TYPE RSLOGDPID, " | |||
| lv_i_mode | TYPE RS_MODE, " RSCRT_C_MODE-MAINTAIN | |||
| lv_wrong_infopackage | TYPE RS_MODE, " | |||
| lv_i_with_commit | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_wrong_demon_used | TYPE RS_BOOL, " | |||
| lv_no_authority | TYPE RS_BOOL, " | |||
| lv_not_allowed | TYPE RS_BOOL, " | |||
| lv_no_lock_possible | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSCRT_RDA_ASSIGN_IPAK' "Start (near-) real-time InfoPackage |
| EXPORTING | ||
| I_DEMONID | = lv_i_demonid | |
| I_LOGDPID | = lv_i_logdpid | |
| I_MODE | = lv_i_mode | |
| I_WITH_COMMIT | = lv_i_with_commit | |
| IMPORTING | ||
| E_DEMON_TO_USE | = lv_e_demon_to_use | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| IPAK_EXECUTED_BY_DEMON = 2 | ||
| WRONG_INFOPACKAGE = 3 | ||
| WRONG_DEMON_USED = 4 | ||
| NO_AUTHORITY = 5 | ||
| NOT_ALLOWED = 6 | ||
| NO_LOCK_POSSIBLE = 7 | ||
| . " RSCRT_RDA_ASSIGN_IPAK | ||
ABAP code using 7.40 inline data declarations to call FM RSCRT_RDA_ASSIGN_IPAK
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_i_mode) | = RSCRT_C_MODE-MAINTAIN. | |||
| DATA(ld_i_with_commit) | = RS_C_TRUE. | |||
Search for further information about these or an SAP related objects