SAP ISP_CONDITION_REFERENCE_INPUT Function Module for Conversion Table for Condition References and Standard Condition Types

Search SAP Function Modules

ISP_CONDITION_REFERENCE_INPUT is a standard isp condition reference input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Conversion Table for Condition References and Standard Condition Types 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 isp condition reference input FM, simply by entering the name ISP_CONDITION_REFERENCE_INPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_CONDITION_REFERENCE_INPUT 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 'ISP_CONDITION_REFERENCE_INPUT'"Conversion Table for Condition References and Standard Condition Types
  EXPORTING
   KAPPL_IN =  "Application
   KVEWE_IN =  "Where-Used List
   BEZTYP_IN =  "
   KNUMV_IN =  "
   KPOSN_IN =  "

CHANGING
   TKOMK =  "
   TKOMP =  "
   BEZKOND_IO =  "

TABLES
   BKOMV =  "

EXCEPTIONS
   OUT_BEZKOND_NOT_FOUND = 1    NO_COND_IN_PROCEDURE = 2    CONDITION_ERROR = 3 

.

IMPORTING Parameters details for ISP_CONDITION_REFERENCE_INPUT

KAPPL_IN - Application

Data type: TJJ93-KAPPL
Optional: No
Call by Reference: No ( called with pass by value option)

KVEWE_IN - Where-Used List

Data type: T681V-KVEWE
Optional: No
Call by Reference: No ( called with pass by value option)

BEZTYP_IN -

Data type: TJJ93-BEZ_TYP
Optional: No
Call by Reference: No ( called with pass by value option)

KNUMV_IN -

Data type: KONV-KNUMV
Optional: No
Call by Reference: No ( called with pass by value option)

KPOSN_IN -

Data type: KONV-KPOSN
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for ISP_CONDITION_REFERENCE_INPUT

TKOMK -

Data type: KOMK
Optional: No
Call by Reference: Yes

TKOMP -

Data type: KOMP
Optional: No
Call by Reference: Yes

BEZKOND_IO -

Data type: RJLJBK1
Optional: No
Call by Reference: Yes

TABLES Parameters details for ISP_CONDITION_REFERENCE_INPUT

BKOMV -

Data type: KOMV
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

OUT_BEZKOND_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_COND_IN_PROCEDURE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITION_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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