SAP CONDITION_IMPORT_FROM_MEMORY Function Module for Import conditions from memory

Search SAP Function Modules

CONDITION_IMPORT_FROM_MEMORY is a standard condition import from memory SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Import conditions from memory 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 condition import from memory FM, simply by entering the name CONDITION_IMPORT_FROM_MEMORY into the relevant SAP transaction such as SE37 or SE38.

Function Group: V14A
Program Name: SAPLV14A
Main Program: SAPLV14A
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CONDITION_IMPORT_FROM_MEMORY 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 'CONDITION_IMPORT_FROM_MEMORY'"Import conditions from memory
 IMPORTING
   XVAKE_MEM =  "
   XKONP =  "
   STAFFEL =  "

.

EXPORTING Parameters details for CONDITION_IMPORT_FROM_MEMORY

XVAKE_MEM -

Data type: IF_PRC_WITH_EXT_COND_TYPES=>TY_T_VAKE_MEM
Optional: No
Call by Reference: Yes

XKONP -

Data type: IF_PRC_WITH_EXT_COND_TYPES=>TY_T_KONP_MEM
Optional: No
Call by Reference: Yes

STAFFEL -

Data type: IF_PRC_WITH_EXT_COND_TYPES=>TY_T_CONDSCALE_MEM
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CONDITION_IMPORT_FROM_MEMORY 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.

ABAP code using 7.40 inline data declarations to call FM CONDITION_IMPORT_FROM_MEMORY

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