SAP EXIT_RAICDAS0_001 Function Module for IM Summarization: Fill User-Defined Characteristics
EXIT_RAICDAS0_001 is a standard exit raicdas0 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IM Summarization: Fill User-Defined Characteristics 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 exit raicdas0 001 FM, simply by entering the name EXIT_RAICDAS0_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XAIC
Program Name: SAPLXAIC
Main Program:
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_RAICDAS0_001 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 'EXIT_RAICDAS0_001'"IM Summarization: Fill User-Defined Characteristics.
EXPORTING
I_OBJECT_TYPE = "Object Type
* IS_PRPS_REQ = "WBS element for appropriation request
I_IQ_ASSIGN = "Measure for Appropriation Request
* IS_RAIPATTR = "Attributes for Position, Measure or Appropriation Request
* IS_IMPR = "Investment Program Positions
* IS_IMAK = "Appropriation Requests - General Data
* IS_AUFKV = "Order
* IS_PRPS = "WBS (work breakdown structure) element master data
* IS_REQ_RIMCMC = "Pre-Assignment of Characteristics for Higher-Level Appropriation Request
* IS_AUFKV_REQ = "Order for appropriation request
CHANGING
CS_RIMCMC = "Inv. Prog. Drilldowns: Characteristics for Master Data
IMPORTING Parameters details for EXIT_RAICDAS0_001
I_OBJECT_TYPE - Object Type
Data type: IONRA-OBARTOptional: No
Call by Reference: Yes
IS_PRPS_REQ - WBS element for appropriation request
Data type: PRPS_REQOptional: Yes
Call by Reference: Yes
I_IQ_ASSIGN - Measure for Appropriation Request
Data type: IMIS_TYPE_FLGOptional: No
Call by Reference: Yes
IS_RAIPATTR - Attributes for Position, Measure or Appropriation Request
Data type: RAIPATTROptional: Yes
Call by Reference: Yes
IS_IMPR - Investment Program Positions
Data type: IMPROptional: Yes
Call by Reference: Yes
IS_IMAK - Appropriation Requests - General Data
Data type: IMAKOptional: Yes
Call by Reference: Yes
IS_AUFKV - Order
Data type: AUFKVOptional: Yes
Call by Reference: Yes
IS_PRPS - WBS (work breakdown structure) element master data
Data type: PRPSOptional: Yes
Call by Reference: Yes
IS_REQ_RIMCMC - Pre-Assignment of Characteristics for Higher-Level Appropriation Request
Data type: RIMCMCOptional: Yes
Call by Reference: Yes
IS_AUFKV_REQ - Order for appropriation request
Data type: AUFKV_REQOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for EXIT_RAICDAS0_001
CS_RIMCMC - Inv. Prog. Drilldowns: Characteristics for Master Data
Data type: RIMCMCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_RAICDAS0_001 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_cs_rimcmc | TYPE RIMCMC, " | |||
| lv_i_object_type | TYPE IONRA-OBART, " | |||
| lv_is_prps_req | TYPE PRPS_REQ, " | |||
| lv_i_iq_assign | TYPE IMIS_TYPE_FLG, " | |||
| lv_is_raipattr | TYPE RAIPATTR, " | |||
| lv_is_impr | TYPE IMPR, " | |||
| lv_is_imak | TYPE IMAK, " | |||
| lv_is_aufkv | TYPE AUFKV, " | |||
| lv_is_prps | TYPE PRPS, " | |||
| lv_is_req_rimcmc | TYPE RIMCMC, " | |||
| lv_is_aufkv_req | TYPE AUFKV_REQ. " |
|   CALL FUNCTION 'EXIT_RAICDAS0_001' "IM Summarization: Fill User-Defined Characteristics |
| EXPORTING | ||
| I_OBJECT_TYPE | = lv_i_object_type | |
| IS_PRPS_REQ | = lv_is_prps_req | |
| I_IQ_ASSIGN | = lv_i_iq_assign | |
| IS_RAIPATTR | = lv_is_raipattr | |
| IS_IMPR | = lv_is_impr | |
| IS_IMAK | = lv_is_imak | |
| IS_AUFKV | = lv_is_aufkv | |
| IS_PRPS | = lv_is_prps | |
| IS_REQ_RIMCMC | = lv_is_req_rimcmc | |
| IS_AUFKV_REQ | = lv_is_aufkv_req | |
| CHANGING | ||
| CS_RIMCMC | = lv_cs_rimcmc | |
| . " EXIT_RAICDAS0_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_RAICDAS0_001
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 OBART FROM IONRA INTO @DATA(ld_i_object_type). | ||||
Search for further information about these or an SAP related objects