SAP CRM_INTLAY_OBJECT_ID_CNVT Function Module for Convert agreement GUID to agreement ID
CRM_INTLAY_OBJECT_ID_CNVT is a standard crm intlay object id cnvt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert agreement GUID to agreement ID 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 crm intlay object id cnvt FM, simply by entering the name CRM_INTLAY_OBJECT_ID_CNVT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_INTLAY_CONVERT
Program Name: SAPLCRM_INTLAY_CONVERT
Main Program: SAPLCRM_INTLAY_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_INTLAY_OBJECT_ID_CNVT 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_INTLAY_OBJECT_ID_CNVT'"Convert agreement GUID to agreement ID.
EXPORTING
IV_INTLAY_MODE = "
IV_VALUE = "
* IV_LANGU = "R/3 System, current language
* IV_FIELD1 = "Name of Field on User Interface
* IV_FIELD2 = "Name of Field on User Interface
* IV_FIELD3 = "Name of Field on User Interface
* IS_ITFVALUE = "
IMPORTING
EV_VALUE = "
IMPORTING Parameters details for CRM_INTLAY_OBJECT_ID_CNVT
IV_INTLAY_MODE -
Data type: COptional: No
Call by Reference: Yes
IV_VALUE -
Data type: ANYOptional: No
Call by Reference: Yes
IV_LANGU - R/3 System, current language
Data type: SYLANGUOptional: Yes
Call by Reference: Yes
IV_FIELD1 - Name of Field on User Interface
Data type: CRMT_INTERFACE_FIELDOptional: Yes
Call by Reference: Yes
IV_FIELD2 - Name of Field on User Interface
Data type: CRMT_INTERFACE_FIELDOptional: Yes
Call by Reference: Yes
IV_FIELD3 - Name of Field on User Interface
Data type: CRMT_INTERFACE_FIELDOptional: Yes
Call by Reference: Yes
IS_ITFVALUE -
Data type: ANYOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_INTLAY_OBJECT_ID_CNVT
EV_VALUE -
Data type: ANYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_INTLAY_OBJECT_ID_CNVT 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_ev_value | TYPE ANY, " | |||
lv_iv_intlay_mode | TYPE C, " | |||
lv_iv_value | TYPE ANY, " | |||
lv_iv_langu | TYPE SYLANGU, " | |||
lv_iv_field1 | TYPE CRMT_INTERFACE_FIELD, " | |||
lv_iv_field2 | TYPE CRMT_INTERFACE_FIELD, " | |||
lv_iv_field3 | TYPE CRMT_INTERFACE_FIELD, " | |||
lv_is_itfvalue | TYPE ANY. " |
  CALL FUNCTION 'CRM_INTLAY_OBJECT_ID_CNVT' "Convert agreement GUID to agreement ID |
EXPORTING | ||
IV_INTLAY_MODE | = lv_iv_intlay_mode | |
IV_VALUE | = lv_iv_value | |
IV_LANGU | = lv_iv_langu | |
IV_FIELD1 | = lv_iv_field1 | |
IV_FIELD2 | = lv_iv_field2 | |
IV_FIELD3 | = lv_iv_field3 | |
IS_ITFVALUE | = lv_is_itfvalue | |
IMPORTING | ||
EV_VALUE | = lv_ev_value | |
. " CRM_INTLAY_OBJECT_ID_CNVT |
ABAP code using 7.40 inline data declarations to call FM CRM_INTLAY_OBJECT_ID_CNVT
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