SAP EECRM_MAPING_TO_STXL Function Module for Relevant Fields from STXL ->BAPI_STXL
EECRM_MAPING_TO_STXL is a standard eecrm maping to stxl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Relevant Fields from STXL ->BAPI_STXL 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 eecrm maping to stxl FM, simply by entering the name EECRM_MAPING_TO_STXL into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECRM_CO
Program Name: SAPLECRM_CO
Main Program: SAPLECRM_CO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EECRM_MAPING_TO_STXL 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 'EECRM_MAPING_TO_STXL'"Relevant Fields from STXL ->BAPI_STXL.
EXPORTING
* ITXTL = "Static Notes to Field Service (Texts)
CHANGING
* BAPI_STXL = "CRM: Master Data Connection Object
IMPORTING Parameters details for EECRM_MAPING_TO_STXL
ITXTL - Static Notes to Field Service (Texts)
Data type: ITXTLOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for EECRM_MAPING_TO_STXL
BAPI_STXL - CRM: Master Data Connection Object
Data type: BAPI_ESTXL_LOCALOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EECRM_MAPING_TO_STXL 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_itxtl | TYPE ITXTL, " | |||
lv_bapi_stxl | TYPE BAPI_ESTXL_LOCAL. " |
  CALL FUNCTION 'EECRM_MAPING_TO_STXL' "Relevant Fields from STXL ->BAPI_STXL |
EXPORTING | ||
ITXTL | = lv_itxtl | |
CHANGING | ||
BAPI_STXL | = lv_bapi_stxl | |
. " EECRM_MAPING_TO_STXL |
ABAP code using 7.40 inline data declarations to call FM EECRM_MAPING_TO_STXL
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