SAP EECRM_MAP_CONOBJ_TO_BAPIMTCS Function Module for Map Different BAPI Structures in Container BAPIMTCS
EECRM_MAP_CONOBJ_TO_BAPIMTCS is a standard eecrm map conobj to bapimtcs SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Map Different BAPI Structures in Container BAPIMTCS 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 map conobj to bapimtcs FM, simply by entering the name EECRM_MAP_CONOBJ_TO_BAPIMTCS into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECRM_CO
Program Name: SAPLECRM_CO
Main Program: SAPLECRM_CO
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EECRM_MAP_CONOBJ_TO_BAPIMTCS 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_MAP_CONOBJ_TO_BAPIMTCS'"Map Different BAPI Structures in Container BAPIMTCS.
TABLES
* CT_BAPI_EHAU = "CRM: Master Data Connection Object
* CT_ENOTE = "Allocation of Object to Note for Field Service
* CT_ENOTET = "Text Table for Field Service Notes
* CT_TE582T = "Static Notes to Field Service (Texts)
* CT_IFLOT = "Functional Location (Table)
* CT_IFLOTX = "Functional Location: Short Texts
* CT_ILOA = "PM Object Location and Account Assignment
* CT_IHPA = "Plant Maintenance: Partners
* CT_STXH = "STXD SAPscript text file header
* CT_STXL = "STXD SAPscript text file lines
* CT_ADRC = "Addresses (central address admin.)
* CT_BAPI_EHAUNOTE = "CRM: Meter Reading Notes for Connection Object
* CT_JEST = "Individual Status per Object
* CT_JSTO = "Status Object Information
* TO_BAPISTRUCTURES = "Middleware Transaction Container Structure
* TO_INTERNAL_TABLES = "Middleware Transaction Container Structure
* CT_BAPI_EHAUADR = "CRM: Address Connection Object
* CT_BAPI_EHAUTXT = "CRM: Short Texts Connection Object
* CT_BAPI_JEST = "CRM: Individual Status per Object Tab JEST
* CT_BAPI_JSTO = "CRM: Information for Status Object Tab JSTO
* CT_BAPI_STXH = "CRM: SAPscript Text File Header Tab STXH
* CT_BAPI_STXL = "CRM: SAPscript Text Files Lines Tab STXL
* CT_EHAUISU = "Connection Object
TABLES Parameters details for EECRM_MAP_CONOBJ_TO_BAPIMTCS
CT_BAPI_EHAU - CRM: Master Data Connection Object
Data type: BAPI_EHAU_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_ENOTE - Allocation of Object to Note for Field Service
Data type: ENOTEOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_ENOTET - Text Table for Field Service Notes
Data type: ENOTETOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_TE582T - Static Notes to Field Service (Texts)
Data type: TE582TOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_IFLOT - Functional Location (Table)
Data type: IFLOTOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_IFLOTX - Functional Location: Short Texts
Data type: IFLOTXOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_ILOA - PM Object Location and Account Assignment
Data type: ILOAOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_IHPA - Plant Maintenance: Partners
Data type: IHPAOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STXH - STXD SAPscript text file header
Data type: STXHOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_STXL - STXD SAPscript text file lines
Data type: ITXTLOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_ADRC - Addresses (central address admin.)
Data type: ADRCOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_EHAUNOTE - CRM: Meter Reading Notes for Connection Object
Data type: BAPI_EHAUNOTE_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_JEST - Individual Status per Object
Data type: JESTOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_JSTO - Status Object Information
Data type: JSTOOptional: Yes
Call by Reference: No ( called with pass by value option)
TO_BAPISTRUCTURES - Middleware Transaction Container Structure
Data type: BAPIMTCSOptional: Yes
Call by Reference: No ( called with pass by value option)
TO_INTERNAL_TABLES - Middleware Transaction Container Structure
Data type: BAPIMTCSOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_EHAUADR - CRM: Address Connection Object
Data type: BAPI_EHAUADR_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_EHAUTXT - CRM: Short Texts Connection Object
Data type: BAPI_EHAUTXT_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_JEST - CRM: Individual Status per Object Tab JEST
Data type: BAPI_EJEST_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_JSTO - CRM: Information for Status Object Tab JSTO
Data type: BAPI_EJSTO_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_STXH - CRM: SAPscript Text File Header Tab STXH
Data type: BAPI_ESTXH_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_BAPI_STXL - CRM: SAPscript Text Files Lines Tab STXL
Data type: BAPI_ESTXL_LOCALOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_EHAUISU - Connection Object
Data type: EHAUISUOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EECRM_MAP_CONOBJ_TO_BAPIMTCS 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: | ||||
| lt_ct_bapi_ehau | TYPE STANDARD TABLE OF BAPI_EHAU_LOCAL, " | |||
| lt_ct_enote | TYPE STANDARD TABLE OF ENOTE, " | |||
| lt_ct_enotet | TYPE STANDARD TABLE OF ENOTET, " | |||
| lt_ct_te582t | TYPE STANDARD TABLE OF TE582T, " | |||
| lt_ct_iflot | TYPE STANDARD TABLE OF IFLOT, " | |||
| lt_ct_iflotx | TYPE STANDARD TABLE OF IFLOTX, " | |||
| lt_ct_iloa | TYPE STANDARD TABLE OF ILOA, " | |||
| lt_ct_ihpa | TYPE STANDARD TABLE OF IHPA, " | |||
| lt_ct_stxh | TYPE STANDARD TABLE OF STXH, " | |||
| lt_ct_stxl | TYPE STANDARD TABLE OF ITXTL, " | |||
| lt_ct_adrc | TYPE STANDARD TABLE OF ADRC, " | |||
| lt_ct_bapi_ehaunote | TYPE STANDARD TABLE OF BAPI_EHAUNOTE_LOCAL, " | |||
| lt_ct_jest | TYPE STANDARD TABLE OF JEST, " | |||
| lt_ct_jsto | TYPE STANDARD TABLE OF JSTO, " | |||
| lt_to_bapistructures | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lt_to_internal_tables | TYPE STANDARD TABLE OF BAPIMTCS, " | |||
| lt_ct_bapi_ehauadr | TYPE STANDARD TABLE OF BAPI_EHAUADR_LOCAL, " | |||
| lt_ct_bapi_ehautxt | TYPE STANDARD TABLE OF BAPI_EHAUTXT_LOCAL, " | |||
| lt_ct_bapi_jest | TYPE STANDARD TABLE OF BAPI_EJEST_LOCAL, " | |||
| lt_ct_bapi_jsto | TYPE STANDARD TABLE OF BAPI_EJSTO_LOCAL, " | |||
| lt_ct_bapi_stxh | TYPE STANDARD TABLE OF BAPI_ESTXH_LOCAL, " | |||
| lt_ct_bapi_stxl | TYPE STANDARD TABLE OF BAPI_ESTXL_LOCAL, " | |||
| lt_ct_ehauisu | TYPE STANDARD TABLE OF EHAUISU. " |
|   CALL FUNCTION 'EECRM_MAP_CONOBJ_TO_BAPIMTCS' "Map Different BAPI Structures in Container BAPIMTCS |
| TABLES | ||
| CT_BAPI_EHAU | = lt_ct_bapi_ehau | |
| CT_ENOTE | = lt_ct_enote | |
| CT_ENOTET | = lt_ct_enotet | |
| CT_TE582T | = lt_ct_te582t | |
| CT_IFLOT | = lt_ct_iflot | |
| CT_IFLOTX | = lt_ct_iflotx | |
| CT_ILOA | = lt_ct_iloa | |
| CT_IHPA | = lt_ct_ihpa | |
| CT_STXH | = lt_ct_stxh | |
| CT_STXL | = lt_ct_stxl | |
| CT_ADRC | = lt_ct_adrc | |
| CT_BAPI_EHAUNOTE | = lt_ct_bapi_ehaunote | |
| CT_JEST | = lt_ct_jest | |
| CT_JSTO | = lt_ct_jsto | |
| TO_BAPISTRUCTURES | = lt_to_bapistructures | |
| TO_INTERNAL_TABLES | = lt_to_internal_tables | |
| CT_BAPI_EHAUADR | = lt_ct_bapi_ehauadr | |
| CT_BAPI_EHAUTXT | = lt_ct_bapi_ehautxt | |
| CT_BAPI_JEST | = lt_ct_bapi_jest | |
| CT_BAPI_JSTO | = lt_ct_bapi_jsto | |
| CT_BAPI_STXH | = lt_ct_bapi_stxh | |
| CT_BAPI_STXL | = lt_ct_bapi_stxl | |
| CT_EHAUISU | = lt_ct_ehauisu | |
| . " EECRM_MAP_CONOBJ_TO_BAPIMTCS | ||
ABAP code using 7.40 inline data declarations to call FM EECRM_MAP_CONOBJ_TO_BAPIMTCS
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