SAP CRM_IST_IL_API_READ Function Module for
CRM_IST_IL_API_READ is a standard crm ist il api read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 crm ist il api read FM, simply by entering the name CRM_IST_IL_API_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_IST_ORDER_BUNDLE
Program Name: SAPLCRM_IST_ORDER_BUNDLE
Main Program: SAPLCRM_IST_ORDER_BUNDLE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_IST_IL_API_READ 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 'CRM_IST_IL_API_READ'".
EXPORTING
IV_RELTYPE = "Relnship Cat.
* IV_TIME_STAMP = "
* IV_ENQMODE = ' ' "Lock Mode
* IV_RAISE_EXCEPTION = ' ' "Defines Whether an Exception Should be Triggered for Errors
IT_LINK_IDENTS = "
* IV_AUTHORITY_CHECK = ' ' "Checkbox
* IV_LANGU = SY-LANGU "Language Key
IMPORTING
ET_INTERLINKAGE = "Table with Relationship Data
ET_INTERLINKAGE_ALL = "
ET_MESSAGES = "Relationships Where Errors Occurred in Processing
EXCEPTIONS
LOCK_FAILED = 1
IMPORTING Parameters details for CRM_IST_IL_API_READ
IV_RELTYPE - Relnship Cat.
Data type: COMT_IL_RELTYPEOptional: No
Call by Reference: No ( called with pass by value option)
IV_TIME_STAMP -
Data type: COMT_IL_VALID_FROMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ENQMODE - Lock Mode
Data type: COMT_IL_ENQMODEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_RAISE_EXCEPTION - Defines Whether an Exception Should be Triggered for Errors
Data type: COMT_IL_RAISE_EXCEPTIONDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_LINK_IDENTS -
Data type: TABLEOptional: No
Call by Reference: Yes
IV_AUTHORITY_CHECK - Checkbox
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_LANGU - Language Key
Data type: LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CRM_IST_IL_API_READ
ET_INTERLINKAGE - Table with Relationship Data
Data type: COMT_IL_DATA_TABOptional: No
Call by Reference: Yes
ET_INTERLINKAGE_ALL -
Data type: TABLEOptional: No
Call by Reference: Yes
ET_MESSAGES - Relationships Where Errors Occurred in Processing
Data type: COMT_IL_ERROR_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
LOCK_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_IST_IL_API_READ 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_iv_reltype | TYPE COMT_IL_RELTYPE, " | |||
lv_lock_failed | TYPE COMT_IL_RELTYPE, " | |||
lv_et_interlinkage | TYPE COMT_IL_DATA_TAB, " | |||
lv_iv_time_stamp | TYPE COMT_IL_VALID_FROM, " | |||
lv_et_interlinkage_all | TYPE TABLE, " | |||
lv_iv_enqmode | TYPE COMT_IL_ENQMODE, " SPACE | |||
lv_et_messages | TYPE COMT_IL_ERROR_TAB, " | |||
lv_iv_raise_exception | TYPE COMT_IL_RAISE_EXCEPTION, " SPACE | |||
lv_it_link_idents | TYPE TABLE, " | |||
lv_iv_authority_check | TYPE XFELD, " SPACE | |||
lv_iv_langu | TYPE LANGU. " SY-LANGU |
  CALL FUNCTION 'CRM_IST_IL_API_READ' " |
EXPORTING | ||
IV_RELTYPE | = lv_iv_reltype | |
IV_TIME_STAMP | = lv_iv_time_stamp | |
IV_ENQMODE | = lv_iv_enqmode | |
IV_RAISE_EXCEPTION | = lv_iv_raise_exception | |
IT_LINK_IDENTS | = lv_it_link_idents | |
IV_AUTHORITY_CHECK | = lv_iv_authority_check | |
IV_LANGU | = lv_iv_langu | |
IMPORTING | ||
ET_INTERLINKAGE | = lv_et_interlinkage | |
ET_INTERLINKAGE_ALL | = lv_et_interlinkage_all | |
ET_MESSAGES | = lv_et_messages | |
EXCEPTIONS | ||
LOCK_FAILED = 1 | ||
. " CRM_IST_IL_API_READ |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_IL_API_READ
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_iv_enqmode) | = ' '. | |||
DATA(ld_iv_raise_exception) | = ' '. | |||
DATA(ld_iv_authority_check) | = ' '. | |||
DATA(ld_iv_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects